ODAMReference

The ecosystem: parts and interfaces

Each part of the end-state ecosystem, what it does, what it takes in and what it hands on. The home page shows the same parts as cards.

Back to the home page

1The whole map

One diagram shows every part and the flows between them.

The ODAM ecosystem map: every part named in the table below, and the flows between them.
Open the map at full size. The table below carries the same content as text.

2Parts, inputs and outputs

Every part of the ecosystem, with its inputs and outputs
PartWhat it doesTakes inHands on
Open-ended attacks against finite rulesThreat pressureAttack paths keep changing, harmful objectives arrive in harmless-looking fragments, and consequences accumulate across agents. Finite rules and capacity have to address context, composition and cumulative effects.
  • Open-ended attack paths
  • Coordinated agents and tools
  • Attempted actions at agents and the gateway
  • Anomalous signals in Observed
People, purpose and accountable authorityPurposeOne outcome for the people served. Someone accountable grants and scopes authority. The people affected can challenge the aim, measure, rule or evidence.
  • Measurements at review
  • Challenges from the people affected
  • The outcome, owner, resources and limits
  • Scoped grants and delegation
  • Challenges into Join and the Ledger
Consent and sovereigntyBinding constraintsConsent, jurisdiction and data sovereignty are checked, never weighed.
  • Consent and obligations
  • Rules in Declared
  • Checks per action
Tamed AutonomyAppropriateness · shouldA normative judgment made before anyone asks whether an action may proceed. Norms bind once an accountable party adopts them. Contributed by Robin Martherus.
  • A proposed purpose and use
  • Adopted purpose and norms, into Declared
ODAMDelivery and adaptationThe delivery loop. People's tools, services and AI agents request and carry out bounded work; the team reviews effects and unknowns and decides to continue, change, pause or stop.
  • The outcome and its limits
  • Requirements and evidence
  • Decisions with an owner
  • Requests to act
  • Effects, observed
Declared → Join ← ObservedData Universe · three connected graphsDeclared holds commitments, requirements, roles, scope, authority and the decision profile. Observed holds readings and events with sources, times and limits, including what's missing. Join matches scope and context, compares, and records findings and decisions. Comparison grants no authority by itself.
  • Requirements and adopted norms
  • Readings and observed effects
  • Presence evidence
  • Shared vocabulary
  • Findings and decisions
  • Limits and current context for each action
  • Evidence for reasoning
Data CompassDecision reasoningThe reasoning practice inside the loop: connect observations, explanations and unknowns to the action the evidence supports.
  • Findings from Join
  • Requirements and evidence
  • A decision, its owner and time, into the Ledger
  • The supported action
LedgerHistory · the record of every decisionWhat was known, who decided, what happened, and every correction. Records keep their source, scope and history; corrections are added, never written over.
  • Decisions from the Compass
  • Decision and execution records
  • Challenges and corrections
  • History for review
  • Records for the three measures
Days at RiskMeasureA plain count from the earliest record that shows you knew, never shortened by a slow acknowledgment.
  • Ledger: awareness to mitigation
  • Where to fix next, at review
Time to Good DecisionMeasureThe decision must hold through its stated window. Measured per incident class at the 90th percentile, with reversed and open cases shown beside it.
  • Ledger: first signal to decision
  • Whether response is fast enough, at review
Ambient BreachMeasureCompares the arrival of uncertainty with verified repair. A flat backlog doesn't prove the reserve is safe.
  • Join: arrivals against verified repair
  • Staff, automate or escalate, at review
Action GatewayExecutionBinds the decision to the exact action, sends the actor and action to the Infrastructure Layer for evaluation, enforces the result at release, and records the execution. After a required human review, a fresh evaluation runs before release.
  • The actor and exact action
  • The decision, limits and supervision from the Infrastructure Layer
  • The actor and exact action, to the Infrastructure Layer
  • Release of the authorized action, within limits
  • Decision and execution records, into the Ledger
  • Holds for required human review, to the owner
Infrastructure LayerInfrastructureEvaluates each action and answers the gateway through its own interface.
  • Actor and exact action
  • Scoped grants
  • Declared limits
  • Current context
  • Decision, limits, supervision
Kinetic Trust ProtocolAuthorizationAuthority is evaluated at the moment of the act, from the grant, the exact action and the current context, not only from a credential issued earlier. A correctly evaluated veto is not bypassed; corrections lead to a fresh evaluation.
  • Scoped grants and delegation
  • The exact action request
  • Limits and current context
  • Allow, shape, require supervision, or deny
  • Act and record, or hold for review
Data Universe ExplorerReference viewTrace outcomes, work, roles and signals across Macro, Meso and Micro.
  • The shared reference library
  • Reference structure for Declared
Open Trust CommonsCoordination and registryProjects describe what they claim and what supports it, in one vocabulary, so they can be compared. An entry is not an endorsement.
  • Project scope, claims and evidence
  • Shared vocabulary for Declared
NomaPresence evidencePresence informs the evidence. Presence is evidence, not permission.
  • Mutually chosen encounters
  • Presence evidence in Observed

3Rules that hold across the map

  • Comparison grants no authority. A finding in Join informs a decision; it doesn't authorize the action.
  • Conditions tighten granted authority; they never widen it.
  • Consent, jurisdiction and data sovereignty are checked, never weighed against a score.
  • Presence is evidence, not permission.
  • A registry entry is not an endorsement.
  • Records are corrected by adding to them, never by writing over them.
  • The people affected can challenge the aim, the measure, the rule or the evidence.
Back to the home page