Issue → plan → code → reviewable PR or migration.
GitHub Copilot Cloud AgentOpenRewrite OSS
STEP 1 · THE INSPECTABLE SYSTEM ATLASPlace the system
Place the system
before you praise it.
Start here. A “factory” is only one kind of system. The Atlas places it beside the data, identity, security, platform, evidence and Day 2 organs a complete department needs.
THE ATLAS IN ONE SCREEN
Four rooms. One department.
Use the rooms to orient yourself, not to crown a winner. A factory can make a change while another organ owns identity, evidence, deployment and the living service.
01Intentwhat needs doing→02Workerwho or what acts→03Evidencewhat proves it→04Day 2what survives launch
Signal → diagnosis → bounded repair → independent verification.
Stakpak AgentOpenTelemetry
Metadata, lineage, quality, memory and evidence with a source boundary.
Identity, policy, cost, contracts, access and recovery.
Microsoft 365Cloudflare Zero TrustPostgreSQL
THE FACTORY LANE
Where a factory actually sits.
The Atlas maps the whole department. A factory is the narrower loop between intent and an accepted change. Follow the lane to see what it produces, then compare only the machines doing the same work.
01Intentissue, event or migration→02Factoryworker, workflow or fleet→03ArtifactPR, patch, image or report→04Acceptanceindependent proof→05Day 2live service and recovery
⚒23 assessed examplesProduct change factories
Can it produce a useful change without pretending to own release or production?
0 Day 2 evidenced · 12 boundedCompare this family →⟳13 assessed examplesTransformation factoriesCan it transform a known shape without guessing at business meaning?
0 Day 2 evidenced · 5 boundedCompare this family →✹7 assessed examplesDay‑2 operatorsDoes it stop at a hypothesis, a rollout signal, a bounded action—or a verified recovery?
0 Day 2 evidenced · 7 boundedCompare this family →◇17 assessed examplesFactory substratesWhat would we have to own to make the substrate safe?
0 Day 2 evidenced · 3 boundedCompare this family →THE MOST IMPORTANT CROSS-CUTTING LENS
Day 2 is a stopping point, not a feature.
Use this rail whenever a factory sounds impressive. The useful question is whether its evidence reaches the deployed service—or stops at a branch, PR, image, report or workflow result.
Learn the six-part Day 2 loop →REFERENCE CATALOG
588 named systems in the current lensNow name the system.
Use the inventory after the map. Search for a tool, open its passport, and keep its source and boundary attached to the claim.
588 systems
USE IN REFERENCE STACKLAB TRIALDEFER UNTIL A GAPWATCH / RESEARCHNEGATIVE CONTROL
Ready for the full inventory?588 named systems with stance, features, provenance and a primary-source link.