002-decision-contract-and-pure-core
Decision contract and pure core
Lifecycle approvedImplementation completeVerification unknownQualification unknown
Increment 1: the versioned wire contract (`rustev-contract`) and the pure core (`rustev-core`). Bounded parsing, canonical form and identities, value kinds without silent conversion, fixed-point decimals and millisecond time, input validation with provenance, freshness and conflict, a closed versioned exact-operator registry, decision definitions entered through a typed builder or canonical JSON, the plan compiler with capability matching, declared fallbacks and typed refusals, calibration binding, deterministic selection policy with explicit unresolved handling, and derivation classes with lineage. No I/O, no clock, no async executor, no model.
Read the full pinned specification ↗Relationships
depended on by
Claimed units
- establishes
{ "kind": "directory", "path": "crates/rustev-contract/" } - establishes
{ "kind": "directory", "path": "crates/rustev-core/" } - extends
{ "nature": "additive", "spec": "001-boundaries-and-authority", "unit": { "kind": "file", "path": "Cargo.toml" } } - extends
{ "nature": "additive", "spec": "001-boundaries-and-authority", "unit": { "kind": "file", "path": "Cargo.lock" } } - extends
{ "nature": "additive", "spec": "001-boundaries-and-authority", "unit": { "kind": "file", "path": "Makefile" } }
Source headings
- 002: Decision contract and pure core
- 1. Purpose
- 2. Territory
- 3. Behavior
- 3.1 Purity
- 3.2 Documents and bounded parsing
- 3.3 Canonical form and identities
- 3.4 Numbers and time
- 3.5 Value kinds
- 3.6 Calibration
- 3.7 Inputs, provenance and freshness
- 3.8 Exact operators
- 3.9 Definitions and compilation
- 3.10 Staged evaluation
- 3.11 Selection policy
- 3.12 Derivation and lineage
- 3.13 Reference plans
- 4. Out of scope
- 5. Observable negative cases
- Acceptance
- Verification
- Engineering choices
- Implementation record
- Decision history
Frozen anchors
No frozen anchors declared.