The order on AI-pipeline artefacts.
Two views over the same substrate. The lattice plots the partial order on AI-pipeline artefacts — raw corpora at the top, regulator-facing deliverables (Annex IV pack, DSAR attestation, FTC §5 disclosure) at the bottom. The Galois connection captures the abstraction map α from a concrete training row to the regulation region that binds it, plus its right adjoint γ.
Same geometry as the generic substrate views on /explore; the difference is the tag glossary, the colour palette, and the edge labels. The substrate is constant, the deliverable is regime-specific — see the substrate thesis.
Lattice — AI-pipeline artefacts
Hasse diagram · 12 nodes · 14 edgesEach node is an artefact in an AI training pipeline; stroke colour tracks the dominant regulation family (indigo for AI Act, sky for GDPR, amber for US state laws, rose for FTC, violet for Copyright/DSM, emerald for sectoral). Edge labels carry `ml:provenanceTags`-style annotations. The red-dashed edge is a forbidden-flow rule from Agent F's Croissant manifest 09 — `no pii reaches training-input`.
Galois connection — α: row → region
adjunction · 5 regions · 24 rowsTop strip: five regulation regions (AI Act training-input, GDPR personal-data, Copyright licensed, FTC disclosure, Sectoral type-coherence). Bottom strip: 24 training rows tagged with `ml:provenanceTags`. α maps a row to the region that binds it; γ shadows back which rows a region covers. Toggle “break the connection” to force a `pii` row into the AI-Act training-input region — the wires turn red and the adjoint inset flips to VIOLATED, the visual signature of a T6 forbidden-flow refutation.
- pii
- eu-personal-data
- gdpr-erased
- dsar-residual
- licensed-cc0
- scraped-no-licence
- synthetic
- embedding-shape-mismatch
Art. 6/9: any row whose subject did not consent or whose DSAR cleared must NOT land here.