RUBIX
INTERNAL · AI ORGANISATION OVERVIEW

The RUBIX AI Organisation, on one page.

A full consulting company modelled as 110 coordinated AI agents — C-suite, delivery, sales, finance, an advisory board and more — now running natively in Claude Code.

Where the build is at

Build status

This org was first assembled for Perplexity, then rebuilt for Claude Code. Here's what's been done to get it actually running — and what's next.

Step 1 · done

Folder understood DONE

Mapped the project into four clear layers — strategy docs, two parallel org builds, and the live marketing website.

Step 2 · done

Direction set DONE

Decided to continue on the Claude Code build as the engine and migrate the richer Perplexity content into it.

Step 3 · done

One agent proven live DONE

Ran the receptionist agent (Cheryl) end-to-end — she classified inbound messages, routed them, and wrote real handoff files. Verified on disk.

Step 4 · done

All 110 agents cleaned to run natively DONE

Stripped Perplexity-isms from every agent: workspace paths, memory model, email stack (→ Outlook/M365) and brand domain all corrected.

Step 5 · done

Relocated to a clean, stable home DONE

Moved the command-centre out of a fragile folder name and re-pointed every path. Verified by a fresh live agent run.

Step 6 · done

Company content migrated into the workspace DONE

Brand kit, company context, knowledge base, research, Star City project and sales collateral migrated and path-cleaned. Verified live: a sales agent read the files and drafted an on-brand quote using real figures.

Step 7 · done

Live secrets found & neutralised DONE

A security scan during migration found plaintext credentials in the build (a Pipedrive token, Xero/Azure secrets). Redacted from the repo — but these must be rotated. Nothing was ever published.

⚠ Action for the founder: live credentials were found stored in plaintext in the original build (Pipedrive API token, Xero refresh token, Azure client secret, Timesheets password). They've been redacted from the working files, but should be treated as compromised and rotated.
How to read the folder

The project in four layers

The folder mixes four distinct things. Keeping them separate is the key to making sense of it.

📐

1 · Strategy & design

The thinking: reference architecture, org diagrams, and the founder's idea dumps. The blueprint both builds reach toward.

🗂️

2 · Perplexity build (v1)

The content-rich original — 110 agents plus knowledge, research and collateral. Built but never actually run. The source of cargo.

⚙️

3 · Claude Code build (v2)

The runtime-real rebuild — agents as native Claude Code sub-agents. The forward path. The better engine.

rubix-command-centre/
🌐

4 · The website

The real rubix.com.au marketing site and lead quiz, deployed on Netlify. Production — separate from the AI-org R&D.

Leadership & structure

Org chart

Founder Dylan Smith sits above an AI CEO who integrates a full C-suite; an advisory board (famous-founder personas) advises on strategy. Below sit nine departments.

Departments

Tap a department to jump to its agents.

The workforce

Agent roster

Every agent in the organisation. Search by name or role, or filter by department.