TrustB0–B1
Freeze and characterize
Pin sources by SHA, license and relationship. Inventory behavior, dependencies and risks without executing legacy code by default.
FORGE 3.2 · Brownfield & Consolidation
FORGE 3.2
Evolve without losing what matters.
One existing system or several legacies: FORGE structures analysis, capability and data decisions, and the consolidation plan for a target product. The path starts with static characterization and advances only with evidence and authorization.
Implemented · integrated tests completed, independent review pending. Recommendation remains suspended. This does not mean a pilot was executed, a migration completed or a system is operating.
From legacy to target product
Every transition has a gate.
B2–B3
Reconcile and decide
Decide what to keep, merge, redesign, retire or investigate. Resolve identity and data; approve the target architecture and wave plan.
B4–B5
Migrate and retire with control
Execute authorized waves, reconcile results and rehearse rollback. Cutover and retirement require human decisions and evidence about consumers, data and secrets.
UNKNOWN, restricted licensing, unresolved identity, stale evidence or missing approval block progress. A synthetic fixture never authorizes changes to a real system.
Snapshot of August 28, 2026
What exists. What remains to be proven.
Contracts, controls, collectors, reconciliation, wave plans and runbooks. Runtime 0.20.1 released with verified signature and native immutability.
Technical verification passed: eight scenarios, seven negative tests and three consumers on the same release. The record is a candidate under review; recommendation remains suspended until an independent decision on the chain and residual issues.
No real legacy system was migrated in this snapshot. Operating, cutover and decommission require their own scope, authorization, observation window and receipts.
Public version record · JSON. Sanitized metadata and digests do not replace access to complete artifacts or an independent audit.
A new project starts with authorization.
Intake defines owners, sources, permissions, data classes, validity and stop gates. The greenfield flow remains available; Brownfield is activated explicitly. No project inherits another project's qualification.
Version 3.2 adds Brownfield & Consolidation. It does not declare roadmap items for model parity, broad MCP support or attestation complete.
Discuss a project