/theory/schema

Schema

The structural codification of the model. A snapshot, not a final specification.


This page is a working reference. The structural codification of the model is a snapshot, not a final specification. It emerged from successive refinements of the underlying model and is at the resolution where it can be built against — not where it is finished. The substrate-level commitments below — events-as-primary, append-only ledger, cross-cutting point-in-time truth, observation-as-scoped-event-topic, derivable-not-denormalized perspective — feel stable enough to build against. Other areas are still moving. Unsettled material lives at /theory/open-questions#schema.

The schema is what the system answers to. It is not the system itself.


TypeDescriptionNotes
Discrete entityPerspective-bearing, non-aggregate. Has capacity-for-observation and a position in perspective-space. Subtypes: human, agent, deterministic-system.Plays the Emitter role within events.
Aggregate-perspectivePerspective-bearing aggregate (team, squad, affinity group, etc.). Has position-in-perspective-space, accumulates trajectory, but does not emit.Membership is a set of discrete entities.
ResourceNon-perspective-bearing addressable artifact. Subject of resource-lifecycle events.Documents, code files, decisions-as-records, etc.
Resource-aggregateEntity produced by perspective-laden inclusion/exclusion of resources.Itself a resource for downstream purposes.
Role-classCharacterizable perspective-class providing Bayesian priors over intention-vectors and field-sets.Applies to both individual and group classes.
EventAtomic recorded observation. The substrate's primary and universal unit.All other facts derive from events.

Event structure (universal)

Every event in the substrate carries this core, regardless of topic.

Core (always present):

  • Emitter (discrete entity)
  • Time
  • Topic (determines payload-schema expectations and downstream semantic)
  • Payload (consistency-marked against topic)
  • References (relations to other events or entities)
  • On-behalf-of (optional; aggregate-perspectives in whose scope the emission occurred)
  • Traceability metadata

Notably not in core:

  • Perspective — derivable from emitter+time via the emitter's trajectory; never denormalized.
  • Observer — observation is a topic; observation-events have an emitter who is also the observer of the referenced event (self-reference within payload).

Categories below are illustrative, not closed.

Topic ClassExamplesNotes
Resource lifecyclepublication, contribution, modification, supersessionActs on resources; emissions add or alter geometry
Declarationdecision, role-grant, authority-grant, membership-grantEstablish or change relations; strong deformations
ObservationobservationObserving-entity-scoped; emitter is the observer; payload references the event observed; terminal — not itself observable; no implied commitment
Operational commitmentack, rej, act, dispatchSecondary to observation-events; represent observer's agency in publicly engaging
Judgmentattribution-judgment, evaluation, scar-markingRecorded assessments about other events or entities
Translationtranslation-event, bridge-formationTranslation-work-as-events between perspectives
State changerole-change, position-update, membership-changeEntity-trajectory events; project to point-in-time entity state
Deformationstrong-deformation, decay-marker, fold-eventManifold-reshaping events

RoleEntity TypeCardinality per event
EmitterDiscrete entityExactly one
On-behalf-ofAggregate-perspectiveZero, one, or many
SubjectResource or entityZero or many (per topic)

For observation-topic events, the emitter is also the observer of the referenced event; this is recorded in the payload, not as a separate role.


Computed from event history at projection time, not maintained as separate state.

StructureDescription
Manifold geometryHigh-dimensional space of positions; deformed by event history per topic-class
Event-graphNetwork of events connected by references; carries temporal structure
Resource-graphNetwork of resources connected by aboutness/supersession/derivation; non-isomorphic to event-graph
Field configurationActive concerns/intentions as forces at projection time
Aggregate trajectoryArc-through-time of an aggregate-perspective; computed from events emitted on-behalf-of it
Entity trajectoryArc-through-time of a discrete entity; computed from its emissions and state-change events about it
Entity state at time TProjection of entity's trajectory to a specific time; supports cross-cutting as-of queries
Bridging structureAccumulated translation outcomes between perspectives
Authority projectionWho-directs-whom; declared and emergent strata projected separately

MechanicDescriptionWhat it answers
Strong deformationDiscrete, deliberate, substantial geometric change (declaration topics; strong-deformation topic)When is the manifold reshaped overtly?
Weak deformationContinuous, sub-recording pressureWhat accumulates without being captured?
Emission-adds-geometryResource-lifecycle and declaration events add new positions to the manifoldHow does the manifold acquire new structure?
Observation-reinforces-geometryObservation-topic events reinforce the position-strength of events they referenceHow does engagement strengthen existing structure?
Correction-scars-geometrySupersession and correction events both deform and carry scar-propertyHow does past-wrongness persist as a property of corrected regions?
Self-cohesionResistance to bending under weak forces at any momentDoes this deformation register?
Background relaxationTendency to return to ambient state over time without reinforcementDoes it stick?
Recording thresholdBoundary at which weak crystallizes into strongWhen does sub-recording attention become tracked?
Decay (forgetting)Drift away from active manifold region without reinforcementWhen does this become "no longer relevant"?
Deformation (forgetting)Topological change after correction/supersessionWhen does this become "no longer true"?
Folding (forgetting)Moved to separate sheet, accessible only by deliberate time-travelWhat is "preserved but not present"?
ScarificationProperty attached to corrective deformationsHow does trace of past-wrongness inform future engagement?
AggregationPerspective-act of inclusion/exclusion producing a new entityHow does selection produce new addressable things?
ProjectionLens-enacted view at query-timeHow does a perspective surface what matters?

LayerDescription
SubstrateTotality of recorded events (all topics), append-only. Not "objective data"; the perspective-laden record of past emissions.
InformationWhat happens when one perspective engages with events emitted by other perspectives (including past versions of itself).
KnowledgeRelational outcome of engagement — never stored, always produced.

Accountability vectors

Accountability decomposes into distinguishable vectors, not types. A single event may have all of them pointing at different entities.

VectorWhat it captures
EmissionDiscrete entity whose act produced the event; the formally traceable one
Attribution-by-contributionWeighted across contributors based on what they contributed; never computed by the substrate
AuthorityPower-relations that shaped the emission; has declared and emergent strata
On-behalf-of chainsScopes within which the emission occurred; may chain across delegation kinds

Chain link kinds (within on-behalf-of chains)

KindExample
Technical delegationAgent invokes another agent for a subtask
Instrumental delegationHuman deploys agent with instructions
Representational membershipHuman acts as part of an aggregate
Organizational authorityAggregate operates under another aggregate's scope

The schema's load-bearing commitments. Stable enough to build against.

  • Attention is the teleological anchor; design constraints derive from it.
  • Events-as-primary; the substrate IS the event history.
  • Append-only ledger: no retroactive mutation; everything else is derivable.
  • Cross-cutting point-in-time truth: for any event at time T, all associated entities' states at T are projectable from the trajectory of state-change events.
  • Every event has an emitter and a perspective; perspective is derivable from emitter-trajectory at event-time, not denormalized.
  • Emitter is discrete-non-aggregate.
  • Aggregate-perspectives have positions and trajectories but do not emit.
  • On-behalf-of is the bridge primitive between discrete accountability and aggregate scope.
  • Observation is an event-topic (observing-entity-scoped, terminal, no implied commitment); audit happens at projection, not as further observation-emissions.
  • Operational commitments (ack/rej/act) are secondary emissions referencing observation-events; receipt does not imply commitment.
  • Emissions add geometry; observations reinforce geometry; corrective deformations scar geometry — bidirectional coupling differentiated by topic-class.
  • Entity state is derived from state-change events, not stored as denormalized state.
  • Capture richly, project plurally: substrate carries consistent metadata; weighting/scoring lives in projections.
  • System surfaces, does not resolve: translation, attribution, accountability, disagreement.
  • Resource-graph and event-graph are non-isomorphic derived structures.
  • Atomicity is observer-relative, not absolute.
  • A single substrate-emission can produce multiple observation-events (one source event; one observation-event per engaging observer).
  • Affordance-composition over typed inheritance; topic carries payload-schema affordances.
  • Authority has declared (formal) and emergent (practical) strata; may diverge; both projectable.
  • Weak observer-relativity: shared substrate, observer-specific projections; shared understanding emerges from convergent histories.
  • Knowledge is relational; the system stores conditions for knowledge production, not knowledge.
  • Internal multitudes of perspectives are a commitment-about-what-we-don't-model; substrate records emissions, not perspective-states.

Two classes of unsettled material live at /theory/open-questions#schema:

  • Intentionally open — questions the model deliberately does not specify. Downstream system designs answer these; the schema does not. Examples: storage substrate, query language, authority model, persona/role library.
  • Pending opinionated stance — gaps the schema needs to close before it is fully coherent. Each wants pressure before stabilizing. Examples: minimum-viable state-change event schema, whether on-behalf-of chains nest on the emission or as a separate graph, scar decay mechanics, manifold composition.

The boundary between intentionally open and pending opinionated stance will shift as the work continues. See /theory/open-questions#schema for the live lists.