Migration of existing systems for interoperability
The system nobody can maintain anymore is still the one the organisation depends on, and its replacement cannot read years of the records it is meant to inherit.
An organisation depends on a system nobody can maintain any more, and holds years of records in a shape its replacement cannot read. Installing something new leaves that history outside it, and rebuilding by hand risks the thing people work in every day.
The system people already depend on keeps working, on a substrate that can be maintained, and the legacy records come across with it, reconciled rather than stranded.
One run, start to finish. A box with an accent tick is a tool acting and opens its own page; a rounded box is an artefact or a record; a diamond is a decision the work cannot pass without. A dashed line is a hand-off the suite has not mechanised yet.
- dispatches scoped work
- A scoped instruction to an executor, with its guardrails and its scope enumerated. The brief is consumed; the outcome returns as signal.
- reads the declared contract
- Nothing is sent. The downstream tool reads the upstream tool’s declared contract at call time, which is why substrate tools have no invoke step.
- appends signal
- One append-only row of signal. It survives the session, and reaches a reader on that record’s own cadence.
- hands over tracked work
- One unit of work owed, carrying an owner and a next act. The one hand-off that reliably survives a seat ending.
The existing system and its legacy records are recomposed on the framework, the records are conformed as they cross, and the result is parity-proved before it ships.
Each step in the order it runs, and where one stops before the next begins.
- 01RUN · toolSCRIBE Reconciles legacy data, human PATCH corrections: accept/edit/reject + rationale + embedding, into the tenant-gated correction store.Nothing in this run reaches it. Hands on to SCRIBE CORRECTIONS.
- 02RECORDEXISTING APP A record the run reads, writes or hands on.Nothing in this run reaches it. Hands on to HELM.
- 03RECORDEXISTING APP + LEGACY DATA A record the run reads, writes or hands on.Nothing in this run reaches it. Hands on to HELM.
- 04GOVERN · toolHELM Dispatch + ledger.Reached from EXISTING APP, EXISTING APP + LEGACY DATA. Hands on to FORGE (CONVERT).
- 05RECORDSCRIBE CORRECTIONS A record the run reads, writes or hands on.Reached from SCRIBE. The run parks here.
- 06RUN · toolFORGE (CONVERT) .Reached from HELM. Hands on to FRAME, WORKING NOTES.
- 07RECORDWORKING NOTES A record the run reads, writes or hands on.Reached from FORGE (CONVERT). Hands on to GIMBAL.
- 08SUBSTRATE · toolFRAME .Reached from FORGE (CONVERT). Hands on to BUILT APP, MIGRATED APP.
- 09PROPOSE · toolGIMBAL Reads the allocation rows every packet emits.Reached from WORKING NOTES. The run parks here.
- 10RECORDBUILT APP A record the run reads, writes or hands on.Reached from FRAME. Hands on to GAUGE.
- 11PROPOSE · toolGAUGE Verify-propose-only, it proves parity and routes fixes, it never fixes.Reached from BUILT APP. Hands on to FLAGGED FOR REVIEW, SHIPS ON THE BUILD LINE, MIGRATED APP.
- 12RECORDFLAGGED FOR REVIEW A record the run reads, writes or hands on.Reached from GAUGE. The run parks here.
- 13RECORDSHIPS ON THE BUILD LINE A record the run reads, writes or hands on.Reached from GAUGE. The run parks here.
- 14RECORDMIGRATED APP A record the run reads, writes or hands on.Reached from FRAME, GAUGE. Hands on to STEWARD.
- 15RUN · toolSTEWARD Hosts.Reached from MIGRATED APP. Hands on to ESTATE-LOG.
- 16RECORDESTATE-LOG A record the run reads, writes or hands on.Reached from STEWARD. The run parks here.
- 01picked upHELM EXISTING APP.Matter the run starts from. No member of the suite put it there.
- 02dispatches scoped workHELM → FORGE (CONVERT) dispatches scoped work.A scoped instruction to an executor, with its guardrails and its scope enumerated. The brief is consumed; the outcome returns as signal.
- 03reads the declared contractFORGE (CONVERT) → FRAME App config.Nothing is sent. The downstream tool reads the upstream tool’s declared contract at call time, which is why substrate tools have no invoke step.
- 04hands onFRAME → GAUGE BUILT APP, BUILT APP.A step following the one before it.
- 05parks hereGAUGE FLAGGED FOR REVIEW.Divergence.Nothing later in this run reads it, so this is where that branch of the run stops.
- 06parks hereGAUGE SHIPS ON THE BUILD LINE.Nothing later in this run reads it, so this is where that branch of the run stops.
- 07appends signalFORGE (CONVERT) → GIMBAL Allocation + capture/drift.One append-only row of signal. It survives the session, and reaches a reader on that record’s own cadence.
- 08picked upHELM EXISTING APP + LEGACY DATA.Matter the run starts from. No member of the suite put it there.
- 09parks hereSCRIBE SCRIBE CORRECTIONS.Correction store, pattern unconfirmed.Nothing later in this run reads it, so this is where that branch of the run stops.
- 10hands onFRAME → STEWARD MIGRATED APP, MIGRATED APP.A step following the one before it.
- 11parks hereSTEWARD ESTATE-LOG.Estate-log.Nothing later in this run reads it, so this is where that branch of the run stops.
Dispatch is a dispatch brief; packet return is a signal append (allocation row); wave close is a signal append (capture/drift into Forge's corpus); Gauge findings are a ledger item ledger items (it routes fixes to Helm, never actuates); adjudications are a signal append into the Forge the decision record.
Dispatch to Forge is a dispatch brief (same shape as App migration); Forge → Frame is a contract read (app config); Scribe's reconciliation corrections land in its tenant-gated Postgres correction store, the row's own logging procedure names this "Scribe's own write path" without resolving it to one of the eight patterns, closest in shape to a signal append but not confirmed as such; hosting is a signal append.