This repository has been archived on 2026-10-29. You can view files and clone it, but you cannot make any changes to its state, such as pushing and creating new issues, pull requests or comments.
Epiphany/schemas
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Meta Vens 9699751f00 Key a resolution and a stewardship by sequence
A subject's resolutions and a repo's assignments on a mind each carried
one key, so the second record of either overwrote the first and a
withdrawn resolution could not be kept under its subject. Both keys now
end in a writer-set `sequence: u32`, `n<N>`, last so the history of a
subject or a repo is one key prefix and R2 keeps that prefix exact:
`question.Q1.n` cannot match `question.Q10.n1`, and a withdrawal keys one
nesting out under the resolution it withdraws.

`assigned_on` stops being a key input and stays a field, validated where
every field is, so the same assignment recorded on two days is one
document and a repo transferred away and back on one day does not
collide. A hand-off is unchanged in shape and key: a transfer back is the
same document with the instances swapped, and no field names a return.

Nesting arithmetic moves with the shape: each nesting prepends
`resolution.` and appends `.n<s>`, so a chain composes `14 * (d - 1) + L`
bytes against `LOCAL_MAX`, and both fixtures key four deep. The leaf
refuses no sequence value -- not `0`, not a gap -- as it refuses no
`revision` value; which sequence a document may claim and which record is
in force are admission's, and are not in this crate. `pipeline_id` gains
no arm and no key is parsed back.

Two schema files regenerate from the derivation, gaining the property,
the required entry and the new doc comments. No epoch moves: no store is
written at this epoch and no reader is pinned to the file.

Cut 6b's M2 is re-anchored on the new parts line, as N7 and N8 re-anchored
Cut 6's M12 and M13.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-16 18:26:46 +02:00
..
cultnet Key a resolution and a stewardship by sequence 2026-09-16 18:26:46 +02:00
README.md Record runtime registry ownership cut 2026-08-23 16:29:33 +02:00

Schemas

This folder is the canonical paperwork shrine for Epiphany's shared state contracts.

If a Persona field or Mind document matters enough to steer the machine, it should have a receipt here instead of living only in one Rust struct or one developer's damp recollection.

Canonical surfaces

  • cultnet/gamecult.persona_state.v0.schema.json: portable Persona state contract for Epiphany Persona, VoidBot repo Personas, and Ghostlight characters. It carries explicit provenance, public presentation metadata, typed candidateActions, and a non-authoritative extension bag for source-specific fields; social bonds, status reads, and doctrine stances are typed affect records rather than generic thought blobs. Timestamps use JSON Schema date-time, presentation is required, and custom enum values have companion custom-label fields.
  • cultnet/epiphany.work_organ_state.v0.schema.json: light function-shaped state for Epiphany internal work organs.
  • cultnet/README.md: JSON Schema publication artifacts for typed CultNet boundaries. Live providers own their schema-catalog responses.

Source Of Truth

The living implementation is in code:

The rule is simple:

  • code owns executable truth
  • this folder owns human-readable contract receipts
  • vendored copies are downstream, not the throne

Update Discipline

When changing any of the following, update this folder in the same pass:

  • canonical organ-state or Persona family names
  • standing role trait names
  • schema version identifiers

If a change lands in code without a matching receipt here, assume the machine has started whispering to itself in the walls again.