FEATURE INVENTORY
This is a product capability list, not a sales pitch. Some items are active surfaces now; some are capability paths the architecture is built to support through setup, adapters, policy, and Sign-off.
Turns loose work into durable operating objects instead of another chat thread.
Lets people work together around shared Office context while keeping Case authority and visibility scoped.
Breaks large work into bounded execution units and coordinates workers around evidence.
The Bureau is intended to move work forward, not only summarize it.
Runtime power is modeled as governed capability with explicit authority, not hidden automation.
Work can enter from the places it already appears, then be routed into governed Bureau objects.
Memory is scoped, inspectable, and promoted deliberately.
Provider-backed judgment sits inside rails for context, validation, redaction, and recovery.
Every meaningful action keeps proof, authority, consequence, and recovery visible.
The Bureau can set itself up and expose platform state without making users read backend machinery.
The Oracle maps and proposes; The Bureau decides, authorizes, routes, and executes.
HOW WORK CHANGES
The Bureau does not replace the tools people use. It operates across them with Cases, skills, PAs, agents, software, evidence, and Sign-off boundaries.
People copy context between email, chat, files, tickets, CRMs, browsers, admin panels, spreadsheets, docs, Git, and internal tools.
The Bureau can work through approved channels, APIs, browser or desktop PA workstations, and VM-hosted app profiles that use the same tools humans use.
Each person remembers process, tone, standards, handoff rules, and tool quirks manually.
Specialists and workers can use skills, role packs, Protocols, examples, memory rules, and quality rubrics scoped to the Case or Office.
People make spreadsheets, scripts, dashboards, automations, parsers, or internal tools by hand when existing apps do not fit.
The Bureau can create purpose-built software, workflows, scripts, parsers, mini-apps, dashboards, and test or validation tools to move a Case forward.
Work is split across people and channels, ownership gets lost, and updates are manually assembled.
Offices, Cases, owners, blockers, Dossiers, Sign-offs, and prepared updates keep team work coordinated.
Humans split prompts, supervise agents, click through tools, and reconcile results.
Case Managers, Specialists, batched Work Orders, run workers, and PA or VM runtimes operate inside one governed Case.
Approvals rely on memory, screenshots, chat trust, or an informal sense that something is ready.
Prepared work carries Dossier proof, action previews, Sign-offs, receipts, and rollback or recovery paths.
Email, chat, tickets, files, and Git contain fragments of work that someone has to interpret and route.
Channel content becomes scoped Case context, next actions, missing-proof requests, and owner-routed decisions.
Claude, Codex, Gemini, and chat sessions are usually separate from the work system.
Model providers, coding agents, PA workers, and future adapters can operate from the same Case context and boundaries where configured.
ARCHITECTURE OVERVIEW
The Bureau is not one chat box. It is a set of apps, packages, data stores, runtimes, channels, and hosting patterns that turn intent into governed work.
Where people, teams, and channels enter or review Bureau work.
The Next.js and React app hosts the public landing, login, My Desk, Cases, Offices, admin surfaces, provider operations, approvals, and review screens.
The reusable landing app keeps the Prime page, archived story route, shared landing styles, and public front-door copy separate from the product shell.
The Vite and React extension can capture page context, browser evidence, quick asks, and channel fragments into scoped Bureau work where installed.
The command-line surface gives developer and workstation flows a direct way to participate in auth, local workspace, and execution loops where configured.
Proof-focused tooling supports evidence, harnesses, and repeatable proof checks around work that needs to be shown, tested, or reviewed.
The governed API layer that turns intent into Case state, policy checks, and records.
The API app uses Firebase Functions v2, Hono, Firebase Admin, and TypeScript for tenant APIs, Case intake, provider status, approvals, and operating records.
Web app routes handle public landing flows, local-dev helpers, capture endpoints, dashboard context, and app-specific server actions close to the UI.
Firebase Auth and app authorization decide whether a person lands on login, onboarding, the dashboard, or a governed app route.
Sensitive, external, destructive, production, cost, credential, and authority-changing actions are represented as explicit preview and approval boundaries.
Where Work Orders, PAs, agents, and adapters actually move a Case forward.
The local Node and Express daemon watches workspace and Firestore state, exposes approved local capabilities, syncs tasks, and records runtime progress.
Queued or batched workers can lease Work Orders, run them, block on missing input, retry, repair, and return receipts or Dossier evidence.
Browser, desktop, local-machine, or VM-hosted PA profiles can use approved apps and tools like a human operator while staying inside Case grants.
Provider, browser, desktop, file, API, channel, and custom-system adapters become capability surfaces instead of one-off scripts hidden from governance.
The records that make Bureau work durable, reviewable, and recoverable.
The current primary operational store for Cases, Work Orders, Dossiers, Sign-offs, queues, tenant state, daemon logs, provider health, and ledger-style records.
Identity and sign-in state sit beside app authorization so user, tenant, setup, and support access can be checked before work routes forward.
Worker queues, leases, blocked states, retries, budgets, and completion receipts are represented as records instead of invisible background activity.
Artifacts, deliverables, source payloads, exports, and large evidence can live behind storage references instead of being copied into every Dossier.
Codebases, generated files, test output, desktop artifacts, and local app state can be used through explicit daemon or PA grants where appropriate.
Important decisions, receipts, citations, costs, assumptions, action previews, recovery paths, and Sign-offs stay attached to the Case instead of chat memory.
The packages that keep the apps speaking the same operating language.
Shared TypeScript contracts, Bureau foundation records, invariants, validators, and testable operating models keep web, API, daemon, and tools aligned.
Shared design tokens and CSS primitives keep Bureau Suit visual language consistent across public, login, and app surfaces.
Local workspace scripts, browser-proof checks, architecture locks, standards gates, and release checks make the system testable outside the happy path.
External intelligence and human tools become governed inputs or execution paths.
OpenAI, Claude, Gemini, Codex-style coding agents, and future model adapters can be routed as Specialist or worker capability where configured.
Email, chat, tickets, Git, docs, files, CRMs, forms, admin panels, and internal systems can feed Case context or become PA/API work surfaces.
When no existing integration fits, The Bureau can create task-specific scripts, parsers, dashboards, mini-apps, or validation tools under the same Case boundary.
WORK PATH
A person, extension, channel, API, CLI, or PA surface brings in intent, files, links, screenshots, or operating context.
The control plane turns loose input into a Case, Directives, Context Packs, owners, setup needs, and Dossier proof requirements.
Case Managers and Specialists break work into Work Orders, choose skills, select providers or PA runtimes, and expose cost or authority gates.
Workers, agents, adapters, daemon capabilities, browser sessions, local tools, or VM-hosted PA workstations execute only inside approved boundaries.
Outputs come back with receipts, citations, logs, previews, files, tests, rollback paths, and Dossier records instead of only a chat answer.
Humans or authorized roles review Sign-offs, unblock decisions, route updates to Offices or channels, and keep the Case state durable.
HOSTING OPTIONS
Hosting is a deployment decision: keep the control plane, data, workers, PAs, and adapters together or split them across cloud, local, office, and customer-run boundaries.