Huginn/schemas
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Meta Vens 8e288867ad Repo activity: a repo dark on a later read is told, a listed repo with a dark feed and an all-dark later read fail the read, and a redirect names a repo only by the forge's own feed route
The wire no longer answers a clean success for a forge that is dark. A Location is
forge-controlled text: it is taken only on the read's origin, by path, as
<prefix>/api/v1/repos/<owner>/<name>/activities/feeds, and only if the name passes
the grammar the daemon checks on requests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 04:17:08 +01:00
..
cultnet Repo activity: a repo dark on a later read is told, a listed repo with a dark feed and an all-dark later read fail the read, and a redirect names a repo only by the forge's own feed route 2026-11-03 04:17:08 +01:00
README.md Rename the pipeline leaf to eureka-pipeline and take it as a path dependency 2026-10-09 14:09:16 +02:00

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.