Workflowrun again on a new scope

Targeted knowledge discovery

A local supply of data sits exactly where its buyers will never look, and every route to it on offer starts by asking to take custody of it first.

The problem to solve

A local supply of data sits with the people who hold it, and the market that would pay for it cannot find it. Nobody can search it, nobody can be permissioned onto it, and the routes on offer start by taking custody of the thing itself.

The solution it delivers

A local data supply reaches the markets that want it: discoverable, permissioned and payable at the holder’s own discretion, with nobody taking custody of it to make that true.

01

The run as one route: which tools get involved, in what order, and where the chain is not mechanised yet.

HELD, FOUND BY NOBODYFOUND AND PAYABLEVerified corpusCorrection store(NO READER)ConformedrecordsHub recordApp configPermissioningPUBLIC / THIRD-PARTYSOURCECRAWLSCRIBESCRIBE CORRECTIONSSPINENOT MECHANISED YETCONSUMER REACHES THEDATAHUB DATAAPP CONFIGFORGEAPP SURFACEEXTERNAL CONTRIBUTORSPINENOT MECHANISED YETSPINENOT MECHANISED YETNOT MECHANISED YET

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.

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.
writes current state
Current state, replacing the prior value. A registry holds what is true now, not how it got there.
02Which tools, in what capacity
actuate
Verify the source
actuate
Render into schema-conforming records against the standard schema, the commoditisation target, not an app config
actuate
Discoverability, permissioning, audit
actuate
Surface it
03How the work crosses between them

Crawl → Scribe is a contract read (Scribe reads the verified corpus and the schema; no message is sent); Scribe → Spine is a contract read again (conformed records are published against the primitive schema Spine indexes); operator corrections along the way are a signal append into Scribe's tenant-gated correction store.

Crawl → Scribe a state write registry (hub record); Scribe → app a contract read config projection (the app config is the handoff); Spine gating a contract read; Forge build signal a signal append into Forge's own corpus.

Identity+permissioning is Spine's own act, no declared corpus exists for it (see gaps); Scribe's conformance corrections are a signal append in shape (correction store, Postgres, tenant-gated, same write path as System migration/Documentation mapping to schema); Spine's exchange-readiness act has no declared corpus either.

The tools this workflow runs through