This repository’s slice of the record, validated at the point it is made.
The workflow emits this repository’s `directory/1` fragment — the nodes and edges it is the authority for — checks the charter conforms, and validates the fragment, declaring with `--external` every id it references but does not own so it cannot quietly assert a definition of somebody else’s organisation.
The estate-wide merge already catches contested authority and dangling references, but it runs elsewhere and cannot say which repository caused them. This runs here, so a bad fragment fails where it was written.
Two diffs close the loop: the committed fragment must match a freshly emitted one, so nobody edited the JSON instead of its source, and the served copy under `public/` must match the root, so the estate’s federated directory can be assembled without a git checkout.
That the fragment a machine reads is the fragment the source describes. Validate any fragment with `npx @flashyos/directory` against the file itself; the served copy and the committed copy are asserted identical, so a hand-edit cannot hide.
A federated directory is a record where each repository emits only the nodes and edges it is the authority for, and the fragments merge into one graph — so an organisation, person or product has a single record and contradictions surface as findings rather than being averaged away.
federated directory →