Route audit
Inventory of routes, static links and basic protection checks.
The new public pages enter the canonical map.
Back home
Audit
Gates, hashes and bundles for verifiable release
The audit layer compares entities, relationships, report bundles and contract readiness before publishing or continuing the plan.
Bundle invariance
The report and subgraph are recalculated to detect differences.
Audit does not depend on screenshots or visual state.
Contract readiness
Roles, compliance, oracle, treasury and anchors are aligned with real modules.
Studio exposes proposals, not on-chain execution.
Release gate
QA commands group build, tests, routes and release packaging.
Documentation explains how to reproduce the close.
Operational quality
PRODUCT_GO does not replace data availability or quality
Gates separate product capability, provider connectivity, input sufficiency and agronomic validity. The UI exposes these states without fabricating results.
01Product gate
Publishable capability
Code, UX, permissions and tests are available as a product.
- Verified routes and navigation
- Fail-closed contracts and degraded states
- 30/30 capabilities with a product gate
02Data gate
Sufficient input
A ready engine may still require a crop, scene, pricebook or approved plan.
- Provider freshness and coverage
- Minimum parameters and units
- No recommendations with insufficient data
03Model gate
Analysis validity
Advanced models need a separate review before forecasting.
- Determinism and regression tests
- Agronomic review and monitoring
- ML forecast remains in research
Release gate
Evidence before claims
- 01Validate code and contract
- 02Check source and freshness
- 03Review input and result
- 04Publish state and evidence