dag-ml-data Table Of Contents¶
Use this as a validation map before development starts.
Area |
File |
Purpose |
Validate |
|---|---|---|---|
Entry point |
|
Project scope, layout and quick start |
The repo can be understood in under five minutes |
Agent handoff |
|
Rules for autonomous implementation work |
A new agent knows boundaries and green gate |
Architecture |
|
Data-layer modules and DAG-ML frontier |
No execution graph responsibility leaks in |
ABI |
|
Data provider ABI and ownership |
Host buffers stay host-owned |
Shared contract schemas |
|
JSON Schemas for the coordinator data-plan envelope and feature fusion selector produced for |
Fixtures and bindings declare the same v1 wire shapes |
Rationale |
|
Split from DAG-ML and design tradeoffs |
Data scope is independently defensible |
MVP acceptance |
|
First data-contract target for UC6/UC11 |
Data plans support stacking without owning OOF logic |
Capability matrix |
|
Full nirs4all replacement data surface |
Data contracts expose identity without owning OOF |
OOF fixtures |
|
Shared tiny campaign data contracts |
DAG-ML can consume fixture identities without guessing |
Roadmap |
|
Sequenced delivery phases |
Every phase has an observable definition of done |
Status |
|
Current scaffold state and next actions |
No hidden implementation claims |
Test plan |
|
Schema, planner and ABI tests |
Fingerprints and path solving are covered |
Supported surface |
|
Release support matrix and public-signature policy |
Production, conformance, experimental and backlog surfaces are separated |
Aggregation interop |
|
Mapping between data-side reducers and coordinator aggregation policies |
Cross-repo reducer drift is explicit |
Performance probes |
|
Private 0.2.0 performance sanity probes |
Critical data-path regressions are measurable |
Source design |
|
Full ML_DATA contract |
Used as implementation source of truth |
Core crate |
|
Schema, representation and data-plan primitives |
|
C ABI crate |
|
FFI-safe helpers and |
Header mirrors Rust ABI structs |
CLI crate |
|
Local validation and fingerprinting |
Example schema fingerprints |
Python provider package |
|
Installable stdlib-only ctypes provider shim ( |
Python can materialize, view, read identity/features/targets/tensors and release handles |
Validation Checklist¶
Check |
Command |
|---|---|
Rust formatting |
|
Rust tests |
|
Lints |
|
Contract schema syntax |
|
Shared contract drift |
|
Example schema |
|
Python ABI smoke |
|