Repository navigation
v0.93.0
The landscape pack says where a system runs and what it is a copy of (#357), so core moves to 0.68.0 and the three packs' manifests move with it, and the package moves to 0.93.0 with both reusable workflows' refs.
environmentis a type of the pack: where a system runs, in the company's words,Production,UAT, a laptop, ranked along the path from a developer's machine to the customer, with a section that says what is deployed there, who may deploy to it and what data it holds. An environment no system names is told so, as a kind nobody names is.- A system gains
instance-of, the software it is a running copy of, one level deep and never in a circle, andenvironment, written on a copy and on a platform alike. The writing rules put what is the same everywhere on the software page, what differs on the copy, another product in the same role beside it as a system of its own joined by the service both provide, and ports, commands and log paths into## Referenceswith the cost and the version; and they say that a holder need not be a master. - A service gains
domainbesiderealizes, since an API, an SDK client and a set of MCP tools are three services and a domain groups them; a service names no bounded context, by R20. - The README's mapping takes the artifact back as a copy assigned to its node and the environment as a Grouping of the Common Domain, and no longer names an architecture tool as the source of a system's lifecycle (#348).
What breaks. Nothing. Every field is optional and the type's folder is empty until an instance writes an environment; a page of any instance changes only where one did.
How to take it. Move the pin to v0.93.0 and run companygraph upgrade, which moves the vendored core and packs to 0.68.0. An instance that runs the same software in several environments then writes one environment page each and one system page per running copy.
Verified: npm run verify with its release check, typecheck, build:check and every test:* script pass, as do conventions-format and conventions-check; companygraph, robertblust and guestgraph mental-model, cloned at their main commits and upgraded with this checkout's CLI, go from core 0.67.0 to 0.68.0, pass check, and find nothing to do on a second upgrade.