Data Contracts

Everything that crosses a boundary in Noetic Aperture — between a client and their ledger, between the framework and a Spire cluster — travels as JSON-LD against a declared schema. Universal data contracts, not vague psychological frameworks.

Why JSON-LD

• Linked: every term in a ledger references its public anchor (a WordNet synset) and its private extensions by IRI. Meaning is addressable.
• Contractual: documents validate against the schema before they enter the graph. A ledger entry that doesn’t validate doesn’t exist.
• Portable: the same contract shape configures both substrates — a cognition map and a cluster manifest are consumed by the same tooling.

Shape of a ledger entry

An illustrative (abbreviated) entry:

{
  "@context": "https://noeticaperture.com/schema/v1",
  "@type": "LedgerEntry",
  "term": "finished",
  "anchor": { "@type": "WordNetSynset", "id": "wn:finished%3:00:00" },
  "definition": "The state the system recognizes as complete — no further gate required.",
  "gates": ["Exist=Now", "Me=Not-Me"],
  "relations": [{ "predicate": "grounds", "target": "term:point" }]
}

The full schema set is versioned and delivered to clients with their bound Codex.