The snapshot and manifest schemas, both example dataspaces, and the shared text renderer now pass the fixture validator and the negative contract tests. JSON, NDJSON, and Markdown frontmatter publish a snapshot only when rights, identity, and references allow it. CONTENT-WP-0001 and CONTENT-WP-0003 are marked finished against those artifacts. CONTENT-WP-0000-T04 stays open. SCOPE.md and the 19:05 scope-against-intent note record the stop. Assistant: grok Assistant-Session: 01a130f1-abfb-7d71-9cd6-a8b75ec7f95a
745 B
745 B
Snapshot format 0.1
Normative files:
contracts/snapshot.schema.json— entity, relation, source, and claim document.contracts/manifest.schema.json— presentation. Kind names, facet names, and relation wording live here.contracts/MIGRATIONS.md— version gate.contracts/fact-policy.md— missing, unknown, and contradiction.
Identifiers for entities are urn:ce:<dataspace>:<kind>:<key>. The same key in another dataspace is a different entity. Relation ids are local to the snapshot.
A published example must contain at least three kinds and eight entities. scripts/validate_fixtures.py enforces that, plus the schema, dangling references, duplicate ids, missing sources, and cycles on acyclicPredicates only.