Implementation
What is built for Open Agri Stack (October 2026), component by component, and how.
These pages describe what is built and how. The design behind each part is in Design; what is still open is in TODOs and open items.
Registry platform
Activity registers (data model, write path, projections, aggregates, final figures on period lock, geography, indicators, staff UI); typed participants; partner corrections; per-subject and filtered DCI queries on activity registers; aggregate search across subjects for allow-listed partners; consent per registry and subject enforcement; context_fields and ui_hints; the activity register configuration file (declarations, output record templates per format, JSON Logic plausibility rules); the sample-data task
Consent Manager
One consent with a grant per registry; bindings per (partner, controller); replay per (jti, controller); a stored decision returned only after the binding and signature checks
Crop Sown Registry
The crop-season activity register; the Cluster entity register; sample clusters and crop seasons; DCI records (activities, crop seasons, season summaries); reporting views
Farmer Registry
Declared main crops replacing the Crops tab; sample lands numbered to match the Crop Sown Registry; FARMER_ID in the DCI farmer record
Use-case composite
The generic composite service, its partner API, the loan-profile use case, Helm chart, partner test kit and end-to-end test
Standards
The open standards used in each area, our own formats, and standards still to explore
Repositories
The registry platform, including activity registers
The Crop Sown Registry extension and chart
The Farmer Registry extension and chart
The Consent Manager
The use-case composite (composite/): service, Helm chart, use cases, scripts
Last updated
Was this helpful?