Workflowrun again on a new scope

Public data consolidation

Piecing together everything public about a sector is a job someone starts over every time, and it goes stale again within the week they finish.

The problem to solve

The knowledge a sector runs on is scattered across the whole internet. It is public, and it is still hard to know about, hard to reach, and hard to hold together in one place. Anyone who needs the whole picture assembles it by hand, and it goes stale the week after they finish.

The solution it delivers

One navigable public reference for the sector, built out of sources that were only ever scattered, and answering for what is true this week rather than last quarter.

01

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

SCATTERED, UNKNOWNONE PUBLIC REFERENCETemplatestructureHub recordBuild recordScan + corroborateHub recordBuild inputBuild recordDeployWHICH SECTORS NEEDTHISNOT MECHANISED YETMASON (FORK ANDBRAND)CRAWLSTARTER DATA FOR THEHUBMASON (BUILD ANDSHIP)BUILD RECORDLIVE FRONT DOORPUBLIC SOURCESHUB DATAMASON

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.
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
Fork hub-template, brand, declare structure
actuate
Seed the verified corpus
03How the work crosses between them

Fork → seed is a contract read (the template's config declares the structure Crawl seeds into); seed → build is a state write (hub record); ship is a state write (build record).

Crawl → Mason is a state write: Crawl updates the hub's own hub record and source credibility record, Mason reads the hub data as its build input. Mason → ship is a state write again.

The tools this workflow runs through