The agentic network · a Gord Holdings companyRoadmap
The Machine

How the estate stays honest.

The whole thesis of IntentMesh is that a claim is worth what a stranger can check. So the estate does not describe its own condition — it runs the machinery that measures, records and proves it, and commits every number as a diff anyone can re-derive.

These are the distinctive workflows behind that. Each seals a fact, merges a record from live domains, or audits the estate against itself — and each page links to the exact YAML that runs it and the format it keeps current. A self-auditing estate, in the open.

The record

The past tense, sealed. One entry per thing that shipped, hashed so a stranger can re-verify it, and merged across the estate from what each property actually publishes.

Shiplog
Every thing this repository shipped, sealed so a stranger can re-verify it.
shiplog.yml
Estate record
The estate’s two tenses, merged from the live sites and never from these checkouts.
estate-record.yml

The intent

The future tense, decaying. What each repository means to do, filed where the work happens and never allowed to over-report how current it still is.

Backlog
What this repository intends to do, published the way facts are and never allowed to go stale quietly.
backlog.yml

The relationships

Who an organisation is to a stranger: the record it is the authority for, and the door it opens — validated at the point each is made, so a bad one fails where it was written.

Directory
This repository’s slice of the record, validated at the point it is made.
directory.yml
Front door
The door this repository opens to strangers, re-emitted and validated on every push.
frontdoor.yml

The measurement

The estate auditing itself. Every number here is committed as a diff and read from the live network, so a regression arrives as a failing check rather than a slightly worse percentage nobody looked at.

Registry
A badge granted once and never re-checked becomes a sticker, so this re-verifies every conformant org.
registry.yml10 / 10
Surfaces
Can a stranger actually read what this estate says it publishes.
surfaces.yml
Estate graph
One graph, assembled from what properties actually publish rather than from any checkout.
graph.yml
Adoption signal
Is anybody outside the estate actually using this — and the honest answer is the whole point.
adoption-signal.yml0
Integration
Whether the work arrives — stranded branches, dead pipelines, and trunks a property is deploying behind.
integration.yml
Hygiene
The estate’s own condition, ratcheted against a floor so nothing fixed can quietly break.
hygiene.yml
Scoreboard
The estate grades itself in public, read from the live sites the way a stranger would.
scoreboard.yml
ShipOS gate
Is tested-and-green work waiting past budget anywhere in the estate.
shipos-gate.yml
FlashyOS branch mesh sync
This repository’s active branches, reported to the mesh under the role that owns each one.
flashyos-branch-mesh.yml

The operational baseline

The rest is the build, security and publish machinery every serious repository runs — distinctive to nobody, and listed here honestly rather than dressed up. Each links to its own workflow.

CIci.yml ↗
Typecheck, lint and the whole test suite, on every pull request and every push off main.
CodeQLcodeql.yml ↗
GitHub’s static security analysis over the source, on main and production and weekly.
SBOMsbom.yml ↗
A software bill of materials generated on every published release.
OpenSSF Scorecardscorecard.yml ↗
The OpenSSF supply-chain posture score, on main, on branch-protection changes and weekly.
secret-scansecret-scan.yml ↗
Scans pushes and pull requests for committed credentials, and sweeps weekly.
Directory refreshdirectory-refresh.yml ↗
Re-asserts the directory fragment once a day, so every fact in it carries a date somebody restated rather than one frozen when the file was written. Its sibling directory.yml validates on every push and is deliberately deterministic, which means it can prove the fragment was generated and can never advance it — this is the half that does.
Deploy proddeploy.yml ↗
Builds and deploys production on every push to main.
Fleetfleet.yml ↗
Connects each organisation’s chartered agents hourly so the Live HQ floor shows what is running rather than a snapshot, and once a day lets them offer help on another organisation’s published want — a draft a human at each side still has to approve.
Pulsepulse.yml ↗
Seals one snapshot of every dimension the estate measures, so a figure can be compared with last Tuesday’s rather than only read today.
Publish packages to npmpublish-agent.yml ↗
Publishes the open packages when a version bump to one of them lands on main.
Publish @flashyos/mcp to npmpublish-mcp.yml ↗
Publishes the MCP server on its own cadence, when packages/mcp changes on main.
Publish the wallet plane packages to npmpublish-wdk.yml ↗
Publishes @flashyos/wallet-wdk, @flashyos/signer and @flashyos/wdk together, in dependency order, when one of their versions changes on main. Testnets only: the signer refuses any chain outside its own table, and no flag in the workflow changes that.
Flashy Mind nightly compilemind-nightly.yml ↗
Every night, recompiles the brain from the repository’s own documents, commits the result if a claim changed, and only then ingests it into the vault the API reads — git stays the source of truth and the database a disposable index over it.
Canon fan-outcanon-fanout.yml ↗
When a fact this host is the authority for changes, signals every property that renders it — a notification, not a push: the receiving repository still decides what to do with it, which is the difference between propagation and a write nobody consented to.
Claim auditclaim-audit.yml ↗
Every two hours, reads the network endpoints and then the pages actually being served, and fails if a figure on a page disagrees with the reading behind it. Everything else here checks the code; this checks the deployment, which is the only place its failure can live — a page rendered days ago, cached at the edge, still confidently stating a number from a different week. It exists because a reader compared the homepage’s floor badge against its network pill and concluded the site could not count: both figures were right, they counted different populations, and neither said which.
Operator's weekly digestoperator-digest.yml ↗
Once a week, renders the operator lane as markdown and upserts a single labelled issue — never a new one per run. Telling rather than enforcing: `operator --check` inside the ShipOS gate is the half that fails a build, and this is the half that says what the lane holds. One issue edited in place because a stream of near-identical issues is how a queue gets muted, and a muted queue is the chat-transcript failure with extra steps.
Deliverydelivery.yml ↗
Settles the last four rungs of delivery/1 by fetching this estate’s own URLs, because `published`, `distributed` and `linked` cannot be read from git — only a fetch can say whether a thing reached anybody. It fails on two conditions, and neither is a test failure in the usual sense: a regression, where something that was live is not any more, and an unshipped live page, where a URL answers from a branch the default branch does not contain, so the repository cannot reproduce what is deployed. It runs here rather than by hand because a developer sandbox has neither the history nor the unrestricted egress: the first round run locally came back `403 Host not in allowlist` from a proxy, which is a fact about the runner and not about the page.
Defineddefined.yml ↗
Validates org/flashyos’s defined/1 vocabulary on every push, and asks the live domain whether it serves the same bytes. It only checks and never commits, so it spends no deploy budget and needs no [skip ci] marker — regenerating a property’s own definitions is that property’s business, and noticing that its fragment no longer validates is everybody’s. A committed fragment with nothing that re-reads it does not decay for a year; it stops being true, silently, which reads exactly like a current one.
Ritualritual.yml ↗
Keeps the Daily Office: once a day it validates org/flashyos’s ritual/1 calendar and records one observance whose evidence is its own run URL. The observance lands performed and stays there — this workflow can never witness its own practice, because unwitnessed practice moving nothing is the format’s rule, left visibly true in our own record.
Gatewayz seam verificationgatewayz-verify.yml ↗
On-demand smoke test of the inference-provider seam, run from an environment that can reach the provider — an operational check of one integration, not estate-condition machinery, and already the “stays honest” workflow on /packages/llm-gateway.
Bolt readingbolt-reading.yml ↗
Takes a deployed reading of the bolt hunt — fetches each property from a runner with the egress a sandbox lacks and records which serve their own shard live — and on request proposes the next sealed tier over exactly those, for a human to append. Sealing a tier is permanent, so it prints rather than writes.
Decision reminder sweepdecision-reminder-sweep.yml ↗
Hourly, and on demand, POSTs the API’s internal decision-reminder-sweep route so every PENDING decision older than 24 hours gets one reminder card, remindedAt claimed atomically first. One request and nothing committed; it fails loudly when GROWTH_METRICS_KEY is unset rather than skipping, because a sweep that went green for sending nothing would read exactly like one that reminded everybody.
Open-source registeropen.yml ↗
Re-reads every repository’s visibility from GitHub once a day and regenerates the open/1 projection this site serves at /.well-known/open.json — the one fact the three registers behind it cannot derive from the tree. Refuses without the estate token rather than writing unread over every row, and its commit carries no skip marker because the change is one /open renders.
Why this is not marketing

Every claim on these pages is checkable against a file the estate publishes. The triggers are read from each workflow’s real on: block, the honest numbers are read from committed JSON, and a drift test fails the build if a page names a workflow that does not exist or a real workflow goes uncategorised.

The formats these keep current →The estate’s own scoreboard →The conformance ladder →