Expand description
§chrs-slurp
Intelligence Crate – Provides the curation layer for the CHORUS system.
The purpose of this crate is to take Decision Records generated by autonomous agents, validate them, and persist them into the graph database. It isolates the validation and storage concerns so that other components (e.g. provenance, security) can work with a clean, audited data model.
§Architectural Rationale
- Separation of concerns – Agents produce raw decisions; this crate is the single source of truth for how those decisions are stored.
- Auditability – By persisting to a Dolt‑backed graph each decision is versioned and can be replay‑backed, satisfying CHORUS’s requirement for reproducible reasoning.
- Extensibility – The
CurationEnginecan be extended with additional validation steps (e.g. policy checks) without touching the agents themselves.
The crate depends on:
chrs-graph– a thin wrapper around a Dolt‑backed graph implementation.ucxl– for addressing external knowledge artefacts.chrono,serde,uuid– standard utilities for timestamps, (de)serialization and unique identifiers.
§Public API
The public surface consists of three items:
DecisionRecord– data structure representing a curated decision.SlurpError– enumeration of possible errors while curating.CurationEngine– the engine that validates and persistsDecisionRecords.
Each item is documented in‑line below.
Structs§
- Curation
Engine - Core engine that validates and persists
DecisionRecords into the Dolt‑backed graph. - Decision
Record - A record representing a curated decision within the CHORUS system.
Enums§
- Slurp
Error - Errors that can arise while slurping (curating) a decision record.