Nozdormu is the reference implementation project for the Embodied Intelligence Platform Architecture: a reusable data, learning, evidence, and runtime foundation for AI cars, robots, and other long-lived embodied agents.
The repository is currently in the contract-first architecture stage. The v1.x specification set remains the implementation baseline. CP-2026-001 is a proposed major-version evolution toward v2.0; it is reviewable but not yet approved.
- a unified
Data Loop Event Recordcontract emitted by domain Trigger Nodes; - Structured Context Records, Evidence Packages and immutable Data Artifacts with window coalescing and governance-scoped deduplication;
- unified short-window and continuous Data Collection Policies and shared physical jobs; the Event/Case/Collection Run object boundary remains an active open design topic;
- structure-first User Behavior Models (UBM) and deterministic human-verifiable rendering;
- fleet defect attribution gates before personal and population learning;
- closed Effect catalogs, external confidence calibration, deterministic arbitration, and domain gateway veto;
- a public Edge Data Loop Service plus Cloud DAG orchestration and pluggable business Processing Nodes;
- contract registries, generated documentation, validation tools, and regression evidence loops.
.
├── docs/
│ ├── baseline/v1.x/ Current approved specification family
│ └── change-proposals/CP-2026-001/ Proposed v2.0 architecture evolution
├── schemas/
│ ├── registry/ Closed vocabularies and contract registries
│ └── json_schema/ Executable object contracts
├── tools/ Registry validation and quantitative analyses
├── src/nozdormu/ Implementation packages (initial skeleton)
└── tests/ Contract and repository checks
Start with the document index, then read the change proposal package. The current Event/Case/ROS 2 bag discussion is recorded in ODN-2026-001.
python3 tools/validate_registries.py
python3 tools/render_effect_tables.py --all --outdir tools/generated
python3 -m pytest- v1.x documents: current baseline
- CP-2026-001 v1.4: proposed, under review
- v2.0 specifications: not yet generated or approved
- runtime implementation: skeleton only