SmartSystem catalog
Evidence-backed discovery reconciles real HTTP and MQTT traffic across projects. Unique matches become code-confirmed relationships; the rest stay visible as potential boundaries.
Bootstrap studio & local adoption control plane
Company Orchestrator prepares new projects for coding agents and safely adopts company standards into existing repositories — inspection without mutation, reviewed proposals, guarded merges, and certification backed by immutable evidence.
$ orchestrator adopt telemetry-gateway --standard azure-pipeline-security
✓ inspect read-only snapshot rev 4f2a9c1 — no working-tree access
✓ propose digest-protected plan · 7 operations · unified diff ready
✓ approve reviewed by operator — candidate prepared in isolated checkout
✓ deliver review branch pushed · PR checks green · guarded merge
✓ certify immutable run receipt build 8813 — state: current
Every repository holds only part of the story — code, pipelines, standards, and agent sessions each know a fragment. Company Orchestrator sits one level up: it registers your projects, reads their evidence, and keeps a living catalog of what each one runs, exposes, and depends on.
The adoption workflow
Add a workspace or existing repository inside an approved local root.
Read structure, declarations, pipelines, and exact HTTP/MQTT evidence — without writing.
Generate a versioned, digest-protected change plan from the inspected state.
Review the plan and diff. Stale-state and path checks block anything out of date.
Apply to an orchestrator-owned checkout, publish a review branch, pass PR checks, merge guarded.
Verify the exact merged runs and record immutable receipts. Compliance becomes current.
Company standards
Evidence-backed discovery reconciles real HTTP and MQTT traffic across projects. Unique matches become code-confirmed relationships; the rest stay visible as potential boundaries.
Governed onboarding of container deployment records, certified against the exact artifacts in your registry — digest-pinned, never assumed.
Adopts a hardened pipeline contract, validates it against your project's own CI, and certifies the result from immutable run receipts — with a no-rebuild state pipeline.
Base images from outside registries are discovered, validated, and admitted through the same guarded proposal flow — including Docker Hardened Images.
A global map of observed links and reviewed contracts between your projects — provider and consumer proposals are generated from real evidence, never guessed.
Coding agents get read-only MCP access to catalog context — what a project is, what it talks to, which standards apply — before they write a line.
Pipeline Map
A static, evidence-backed graph of your Azure pipelines: stages, jobs, checks, dependencies, and artifact boundaries — projected from exact commits, tied to immutable inspection snapshots, with revision history and structural change summaries. No source code, no secrets, no execution controls.
The safety model
Registration, inspection, discovery, and mapping never touch a working tree.
Changes are prepared in orchestrator-owned checkouts. Your checkout stays untouched.
Generation, approval, and delivery are separate operations with stale-state checks.
Missing build IDs, commits, or digests block state generation. No evidence, no compliance.
Company Orchestrator is a working system, developed and run in production on real projects and pipelines.