bijux-dag-artifacts¶
bijux-dag-artifacts owns run artifact models, persistence helpers, integrity
proofs, storage hardening, and lifecycle policy helpers.
Use this page when the question is about what a DAG run leaves behind, how that material is identified, and how artifact integrity is verified over time.
Responsibility Map¶
| Surface | Ownership |
|---|---|
| artifact identity | storage models, paths, platform layout, and lineage material |
| integrity | hashes, proofs, schema material, and verification helpers |
| lifecycle | promotion, retention, and persistence service helpers |
| boundary | does not own CLI routing or runtime scheduler behavior |
Source Layout¶
crates/bijux-dag-artifacts/src/storagecrates/bijux-dag-artifacts/src/layoutcrates/bijux-dag-artifacts/src/integritycrates/bijux-dag-artifacts/src/lifecyclecrates/bijux-dag-artifacts/src/io
Open Next¶
- open
bijux-dag-runtimewhen artifact work is tied to execution and replay policy - open the DAG Handbook for the full DAG ownership map
- open the Repository Handbook when artifact contracts affect shared governance
Code Anchors¶
crates/bijux-dag-artifacts/README.mdcrates/bijux-dag-artifacts/CONTRACT.mdcrates/bijux-dag-artifacts/src/lib.rscrates/bijux-dag-artifacts/src/integrity/proof.rscrates/bijux-dag-artifacts/src/lifecycle/retention.rs
Review Lens¶
- artifact identity and integrity should stay authoritative and inspectable
- lifecycle helpers should not drift into execution-engine policy
- retention and promotion rules should remain explicit enough to audit