Schematics

Diagrams that can be checked

Every schematic has a stable identity, a version, a stated scope, and a table carrying the same information. A diagram that cannot be expressed as a table is usually decorating rather than explaining.

Schematic	Version	Status	Scope
How a record becomes public	`1.0.0`	Published	The publication architecture of this website.
The private-to-public boundary	`1.0.0`	Published	The controlled path from the private programme to this site.
What verification proves, and what it does not	`1.0.0`	Published	Six distinct things that are commonly conflated.
Tiffany system topology	`—`	Awaiting publication	Not released.

How a record becomes public

A typed record passes policy and schema gates, is sealed against its digest, and is rendered once into every surface.

The same diagram as a table

Component	Role	Feeds into
Typed records	Claim versions, artifacts and the status ontology, in version control. The only source of truth.	Policy as code (checked by); Schema enforcement (validated against)
Policy as code	Fifteen deterministic rules plus state-machine invariants. Decides what may be published; no override path exists.	Deterministic build (gates)
Schema enforcement	Every emitted document validated against its published schema. A failure stops the build.	Deterministic build (gates)
Deterministic build	Zero dependencies. Same inputs produce the same bytes in any directory on any machine.	Human surfaces (renders); Machine surfaces (emits); Build manifest (digests)
Digest lock	Sealed digest of every published claim version. Editing a published version aborts the build.	Deterministic build (gates)
Human surfaces	Script-free pages at three depths: understand, inspect, verify.	terminal
Machine surfaces	Twenty-two endpoints, OpenAPI, schemas and portable bundles, generated in the same pass.	terminal
Build manifest	SHA-256 of every shipped file, so a reader can verify the whole site at once.	terminal

The private-to-public boundary

Nine controls in one direction. Nothing has passed through them yet.

The same stages as a table

#	Stage	What happens
1	Private environment	The authoritative scientific work. This site never reads from it.
2	Explicit export	A deliberate act, never a sync.
3	Secret scanning	MANDATORY before the first export. Not yet built, and nothing may cross until it is.
4	Sanitisation	Private inputs become attested transformations with digests, never disclosed inputs.
5	Classification	Fails closed. Absent or ambiguous means internal.
6	Licence and IP review	Ambiguous ownership is non-releasable.
7	Schema validation	Structure checked before meaning is trusted.
8	Release policy	The same deterministic rules that gate every claim.
9	Public record	Immutable, digested, citable.

What verification proves, and what it does not

Each step establishes strictly less than the next, and none of them establishes that a claim is true.

The same stages as a table

#	Stage	What happens
1	Transport success	A 200 came back. Says nothing about content.
2	Artifact integrity	Bytes match a published digest.
3	Cryptographic authenticity	A signature ties bytes to a key. Not available here — no signing exists.
4	Reproducibility	Re-running the code gave the same output. Can faithfully reproduce a broken measurement.
5	Scientific qualification	The record passed the published rules for its status.
6	Independent replication	Different people, implementation and data met criteria fixed in advance.

The demonstration claim on this site passes the first four and fails the last two, which is why it was withdrawn. The full treatment →

Tiffany system topology Awaiting publication

Not released. No diagram of Tiffany's internal structure appears on this site, and one will not be drawn from inference.