The code estate is operated as a system rather than a loose folder of repositories. One canonical manifest records what exists, who owns it, its lifecycle, its criticality, how it validates, and where it deploys.
System
- The workspace manifest governs 16 active repositories across production apps, open-source packages, a private monorepo, and shared tools.
- Repository profiles define expected files, policy checks, validation depth, platform integrations, and deployment surfaces.
- Shared tools provide estate audits, health reports, security-scan runners, video production, paper publishing, standards, and stable command-line entry points.
Control
- Product code remains in product repositories while standards, reporting, and reusable operators stay in the shared tooling layer.
- Generated reports preserve observed state as evidence and do not silently become executable configuration.
- Destructive cleanup requires explicit approval, and third-party upstream code remains visibly separated from local patches.
Proof
- The manifest records validation commands, criticality, lifecycle, ownership, remotes, deployment targets, and enforcement status for every active repository.
- Estate-level validation can audit repository policy, shared tooling, security configuration, and production baselines from one entry point.
- The public portfolio is generated from the same code estate rather than maintained as an unrelated marketing inventory.