ProvenMap keeps a software estate's architecture provably in sync with the code that implements it — through governed boards, intents and insights.

ProvenMap System Landscape

The command center for the rocket-space workspace. Mapped from the estate as it exists on 2026-09-06, from a shallow identity scan of five local repository paths plus the architect's own testimony.

First-party systems — five repo-backed slots, each with its own app board: platform (the product itself), portal, plugins (the Code, Connect and Architect IDE plugins), infra (the IaC stacks) and skills-library (shared skills, hosted in the contextdx org). Every one of them is a monorepo or a library; content arrives from the developer's first push.

Grouping — one container only. External Integrations is a vendor cohort: its members are grouped because they are all externally governed, not because they call one another. Infrastructure (postgres-rds, aws-lambda, aws-ecs) sits at root level because it is cross-cutting; actors sit at root level because they are boundary. No ownership container was drawn — at this size the landscape reads fine flat.

Provenance of the edges — the 24 connections were inferred at scaffold time from repository identity and the obvious shape of the estate, not asserted by the architect and not proven by code. Each edge description says so. They are the first thing a /sync will reconcile once repositories bind and push.

Attributes deliberately empty — owner and stage were not supplied and were left blank rather than guessed. They are the architect's to fill.

Not yet bound — app boards are born empty. Nothing here is code truth until each repository is connected with the code plugin and pushes.