Huginn/schemas/README.md
Meta Vens c46b0ec183 Rename the pipeline leaf to eureka-pipeline and take it as a path dependency
Package and lib become eureka-pipeline / eureka_pipeline; the crate joins the
workspace; huginn-mind's git dependency on GameCult/Epiphany is replaced by
the path, and Cargo.lock is regenerated (the Epiphany source entry is gone).
Every epiphany_pipeline mention in huginn-mind, huginn-daemon and eureka-state
is renamed. The schema-publication test reads ../../schemas/cultnet. The
leaf's license-file key (../LICENSE, which Huginn has no file for) is dropped.
Type ids, the epoch and every schema_id string are untouched. Schemas README
and the pipeline section of schemas/cultnet/README.md are rewritten for the
new home; README and AGENTS no longer say the leaf is pinned by git. New test:
the catalogue lists exactly the schema files beside it.

Not yet built or tested; verification follows on Yggdrasil.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 14:09:16 +02:00

1.7 KiB

Schemas

This folder is the canonical paperwork shrine for the state contracts Huginn publishes and the pipeline leaf derives.

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 Eureka's 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/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.