ARCHITECTURE · ORCHESTRATION · STANDARDS

How CareerStudioMax
actually works

Not marketing copy — the real registry, the real grounding rules, the real orchestration engine, and the real open standard it's built on. Every number on this page is live.

Real Tools
Domains
1
Orchestration Engine
5
Model Fallback Tiers
Overview Domain Grounding Orchestration Model Cascade MCP Tool Directory Sources
01 · Overview

Three real layers, not one big black box

Every one of the tools on this platform runs through the same real code path — there's no per-tool bespoke backend hiding behind each of the 354 cards on the catalog page. What actually differs between "CV Score Analysis" and "Concrete Mix Advisor" is which real data grounds the answer, not which engine answers it.

🗂️ Registry
One flat table (activityRegistry.js) of every real tool — id, label, domain, icon. No tool exists that isn't a real key in this file; the API 404s on anything else rather than guessing.
📡 Grounding
A domain-keyed switch that decides what's real and checkable is handed to the model before it answers — live database data, named industry standards, a user's own saved records, or nothing at all if none applies.
🧠 Execution
One universal executor builds the prompt and streams it through a real 5-tier model fallback chain. The Workspace Agent uses the exact same executor internally — it just calls it several times in a row.
02 · Domain Grounding

What "real" means, tool by tool

This is the actual switch statement (services/featureGrounding.js) every one of the 354 tools passes through before the model sees the request. It is deliberately honest about which domains get live data versus a static reference anchor versus nothing — a tool with no live data source still gets a genuine AI answer, it just isn't tagged as verified.

DomainGrounding sourceWhat it actually does
Salary Intelligence● live dataQueries a real salary-benchmark collection built from real market data, not a model guess.
Intelligent Job Hunt● live dataQueries real, currently-indexed job postings for the role/location asked about.
Career Goals● personal recordPulls this specific user's own real saved goals — never another user's, never fabricated ones.
LifePath AI● live dataBuilds context from real, already-computed career-trajectory data for that role/country.
Civil Engineering● named standardsAnchors on real, named codes (ACI 318, AISC 360, Eurocode, AASHTO) and forces a licensed-engineer sign-off line on every calculation-shaped answer.
Architecture● named standardsAnchors on real named frameworks (RIBA Plan of Work, LEED/BREEAM) and flags anything jurisdiction-specific as needing local verification.
Everything else (CV, Cover Letters, Interview, LinkedIn, Brain AI, Tools, Enterprise)○ no live sourceA genuine AI answer with no external anchor to check it against — same honesty level as any other AI chat, just not claiming to be verified.
Every claim the model states is asked to self-label: [VERIFIED] for an established fact, [INFERRED] for reasoned extrapolation, [ESTIMATED] for a calibrated guess, [UNKNOWN] when it genuinely doesn't know — and when real fetched data appears above, that exact figure gets tagged [LIVE DATA] instead.
03 · The Workspace Agent

Real multi-step orchestration, not a longer prompt

The Workspace Agent is the one place the "354 separate tools" framing breaks down on purpose — it plans a real sequence of them, chains each real output into the next, and only ever executes a step after either the system validates it against the real tool list or a human explicitly approves it.

Anatomy of one real run
Goal
real user input
Plan
1 real LLM call
Step 1
TOOL
Step 2
ACTION*
Step N
DELEGATE†
Report
draft→critique→refine
Up to 6 steps per plan. *ACTION steps (real email/calendar/webhook) only fire after explicit human approval of the real proposed content — never auto-approved. †DELEGATE steps hand a sub-goal to another persona as a real child project, depth-limited to 1 so delegation can't chain indefinitely. The report stage runs the same real draft→self-critique→refine pipeline as Brain AI's own "deliberate reasoning" mode — a genuine second pass, not a longer single prompt.
💰 Real cost per run
A full run is genuinely ~9–10 real model calls (1 plan + up to 6 steps + a 3-stage report) — this is why it's rate-limited separately from everything else and gated to the Elite plan.
🚦 Real limits
20 requests/minute per user on every AI-cost route, 10/minute per IP on the public trigger endpoint — both enforced server-side, both independently load-tested to confirm they actually 429 at the stated threshold.
🛑 Real stop button
A running project can be cancelled between steps (never mid-call) — already-completed steps stay real and kept, nothing is discarded.
04 · Reliability

Why every answer goes through a 5-tier chain

Every real AI call — a single tool or one step of a Workspace Agent run — is tried against a real fallback chain, not a single provider with no plan B. This exists because a single-provider platform goes fully dark the moment that one provider has an outage; the chain exists to keep answering anyway.

Tier 1 · Proprietary
Tier 2
Tier 3
Tier 4
Tier 5
Tier 1 is this platform's own proprietary, self-hosted model tier — tried first because it's genuinely faster once warm (no third-party network hop at all). Every tier after it is an independent external provider, so one provider's outage degrades quality, not availability. The specific providers and routing order are kept private by design — publishing the exact chain would hand an attacker a map of exactly what to target to degrade this platform's availability. The full request context — which of the 358+ tools is running, live grounding data, a user's real saved profile — is threaded through to every tier via a compact system prompt, a real fix for a live-caught bug where the fastest tier was silently answering with none of that context at all.
05 · Open Standards

Real MCP integration, honestly scoped

The Model Context Protocol is Anthropic's real open standard (donated to the Linux Foundation's Agentic AI Foundation in December 2025) for connecting an AI model to external tools and data without a bespoke integration per pair. This platform implements a real MCP client, not just the word "MCP" in a marketing sentence.

✅ What's real
A genuine MCP client speaking the real protocol transport (stdio, JSON-RPC 2.0) to @apify/actors-mcp-server, wired to two real actors: a Google Places crawler and a website-content crawler. A real, valid Apify API credential is already configured in this environment.
⏸ What's honest about its status
The client is gated behind its own feature flag and is currently switched off in this environment — wired and credentialed, not actively processing live requests right now. Stated here plainly rather than implied as "live" when it isn't.
06 · Reference

Every real tool, by domain

Live from the same registry the API serves — this is documentation, not the interactive version. To actually run one, use the catalog page.

Real distribution — tools per domain
Loading live catalog…
Try any of these live →
07 · Sources & Standards Referenced

Where the reference claims on this page come from

Real citations, not invented statistics — anything not a first-party fact about this platform's own code links to where it actually came from.

MCP donated to the Linux Foundation's Agentic AI Foundation, Dec 2025; ~97M monthly SDK downloadsThe Register →
MCP origins, architecture, and real-world impact since Anthropic's Nov 2024 introductionWeights & Biases →
Concrete/steel design standards referenced by the Civil Engineering domainACI 318 · AISC 360 · Eurocode · AASHTO
Design process/sustainability frameworks referenced by the Architecture domainRIBA Plan of Work · LEED · BREEAM