Architecture
RadixOS is a governance layer. It records explicit human judgment without collapsing boundaries between context, decision, observation, and execution.
Boundaries
This page describes system shape and separation lines. It is not a runtime document, a compliance claim, or an execution guide.
System shape
Core objects
- Decision — a human-authored record of judgment with ownership, constraints, assumptions, and review cadence.
- WorkItem — a unit of execution tied to scope and ownership.
- Incident — a record of failure modes and response, kept for durable learning.
- HealthCheck — a recurring integrity snapshot: what’s stable, what’s drifting, what needs attention.
- Cadence — the review rhythm that keeps learning consistent across time and turnover.
Visible surfaces
- Decisions — the decision record surface.
- Governance — review structure and traceability posture.
- Architecture — boundaries and system shape.
Separation lines
RadixOS keeps roles separate so accountability stays legible.
- Judgment ≠ execution
- Record ≠ evaluation
- Context ≠ authority
- Observation ≠ action
context ≠ decide ≠ observe ≠ execute
Data posture
Recorded
- Ownership (who authored the decision)
- Constraints (time, resources, irreversibility)
- Assumptions and confidence bounds
- Attribution and timestamps
- Declared review cadence
Outside the spine
- External observation feeds
- Action guidance and execution triggers
- Outcome scoring and correctness grades
- Automation that collapses authority into the system
Failure modes this design avoids
- Post-hoc rationalization drift
- Authority collapse (system becomes the decider)
- Accountability blur (ownership becomes ambiguous)
- Execution sprawl (governance surface turns into a control plane)
Context
Operational surfaces: