Context fragments
Repositories, delivery files, standards, and agent sessions each hold only part of the project story.
Back to Projects
Engineering Case Study
Company Orchestrator
Controlled Project Standards and Delivery
A local control plane that discovers project context, manages evolving standards, and turns proposed repository changes into reviewed, verifiable delivery.
Local control plane
Read-only discovery
Human-gated changes
Exact-commit evidence
Designed and built by Irving M. as an evolving engineering system. This case study documents implemented behavior; it is not a product sales page.
01
Product Evidence
The Project Network makes discovered dependencies and reviewed contracts inspectable in the same interface used to understand project state.
02
The Problem
Project knowledge fragments across repositories, tools, and agent sessions while shared standards continue to evolve. Existing projects need a controlled way to understand what they run, compare it with current capabilities, and adopt changes without giving automation unrestricted write access.
Standards keep moving
A capability adopted today still needs a controlled upgrade path when its contract changes tomorrow.
Automation needs limits
Repository changes are useful only when inspection, approval, delivery, and evidence remain independently reviewable.
03
Controlled Workflow
Each stage establishes a reviewable boundary between understanding a repository and changing what it delivers.
- 1
Register
Add a new workspace or an existing repository inside an approved local root.
- 2
Inspect
Read project structure, declarations, pipelines, and exact HTTP or MQTT evidence without writing.
- 3
Propose
Create a versioned, digest-protected change plan and unified diff from the inspected state.
- 4
Approve
Require an explicit human decision against a stable review artifact before mutation begins.
- 5
Apply
Materialize only reviewed paths in an orchestrator-owned checkout and publish a review branch.
- 6
Verify
Bind policy, merge, pipeline, and deployment evidence to the exact commit that was delivered.
04
Architecture
Built one local portal for new-project bootstrap and existing-project adoption. Read-only inspection records repository evidence and cross-project relationships; versioned profiles produce immutable proposals; isolated Git candidates, explicit approval, Azure DevOps policy checks, guarded merge, and exact-commit verification keep every mutation reviewable.
React + TypeScript portal
Guided setup, project inspection, network context, proposals, review state, and delivery evidence.
FastAPI application boundary
Authenticated local API delegating state transitions and transaction boundaries to application services.
Worker + durable state
Background jobs, leases, immutable artifacts, SQLAlchemy models, Alembic migrations, and SQLite persistence.
Git + Azure delivery adapters
Managed checkouts, review branches, PR policy checks, guarded merge, and exact-commit pipeline verification.
Read-only MCP adapter
Project identity, dependencies, inspection evidence, and path impact for trusted local coding agents.
05
Engineering Decisions
Local security boundary
Repository paths and credentials stay behind a loopback-only portal and trusted local worker account.
Read-only discovery first
Inspection creates evidence and immutable snapshots without modifying the registered checkout.
Isolated proposal candidates
Reviewed output is materialized in orchestrator-owned checkouts instead of switching or dirtying user repositories.
Immutable human review
Approval refers to digest-protected operations and diffs so later state cannot silently change the decision.
Guarded merge
The PR head and blocking policy evidence are refreshed before merge, with policy bypass explicitly disabled.
Evidence tied to delivery
Pipeline and artifact verification accept only the target branch and exact merge commit.
06
Skills Demonstrated
System architecture
Full-stack product engineering
Workflow and domain modeling
Git and CI/CD integration
Agent and MCP integration
Security-conscious automation
- Unified guided project bootstrap and controlled adoption for existing repositories in one local portal
- Mapped repository evidence and cross-project HTTP and MQTT relationships without modifying registered projects
- Turned evolving standards into immutable proposals, isolated candidates, and explicit human approval gates
- Connected review branches, Azure DevOps policy checks, guarded merge, and exact-commit pipeline verification
- Exposed project identity, dependencies, and path impact to coding agents through a read-only MCP boundary
07
Technology Stack
React
TypeScript
FastAPI
Python
SQLAlchemy
SQLite
Git
Azure DevOps
MCP
Codex
The Company Orchestrator repository is private. This case study presents the implemented architecture and product evidence without exposing source control.