Interactive Layer Graph

Navigate L0–L7. Each layer highlights connected RFCs and repositories via GraphProvider.

View Architecture Graph →

Normative stack

Data and control flow move downward from external observation sources to applications. Each band has a governing specification.

SensOS stack architecture from external sources to applications
SensOS Architecture Stack Vertical flow: External Sources, Observation Runtime, HEXT, HEKB, NVS Kernel, DLNP, Runtime Governance, SDRP, Applications. External Sources Sensors · Streams · Agents · APIs Observation Runtime Ingress · Normalization · L0–L1 HEXT Canonical object model HEKB Immutable knowledge substrate NVS Kernel Geometry · Belief · Risk (L4–L5) DLNP Layer negotiation · Pipeline binding Runtime Governance Budgets · Admission · Audit SDRP Distributed runtime mesh Applications Products · Tools · Integrations

Responsibility bands

Band Concern Governing RFCs
External Sources Sensors, streams, agents, and inbound APIs
Observation Runtime Ingress, normalization, L0–L1 observation objects RFC-NVS-0200
HEXT Canonical object model after L3 RFC-NVS-0200
HEKB Immutable knowledge substrate and audit evidence HEKB
NVS Kernel Geometry, belief, and risk evaluation NVS Kernel
DLNP Layer negotiation and pipeline binding RFC-NVS-0201
Runtime Governance Admission, budgets, cancellation, audit RFC-NVS-0202
SDRP Distributed mesh, attestation, remote ports RFC-NVS-0203
Applications Products and integrations consuming the runtime Products

Design pillars

  1. Observation before meaning — wire observations without forcing taxonomy at the edge.
  2. Capability before execution — CBAC authorizes every privileged DLNP/SDRP action.
  3. Canonicalization before identity — stable content_id exists only after L3.
  4. Evidence before inference — audit objects record authorization lineage without raw tokens.
  5. Specification before implementation — see RFC-NVS-GOV-0001.