TerraYield need (build-once guarantee). md/design/app-integration-playbook.md is a design doc, and v0.1 code reflects the older chat-first framing. TerraYield will not implement ione_view hints, foreign-tenant whoami, or context-slice shapes against an unfrozen contract — one IONe refactor would strand the peer implementation.
Acceptance
- Versioned contract doc (v1) with concrete schemas:
ione_view enum + resource metadata shape, whoami request/response, context-slice payload, webhook signature scheme (HMAC-SHA256 header format, timestamp/replay window), error conventions.
- Explicit compatibility rule (what a v1 peer can rely on across IONe releases).
- Large-resource conventions: pagination/cursor semantics and size limits for MCP resources (county GeoJSON runs to MBs; TerraYield uses cursor pagination — the contract must say how that maps).
Consumed by the conformance kit; prerequisite for TerraYield surfaces 4/5/6 (eo_ag#17, eo_ag#18).
TerraYield need (build-once guarantee). md/design/app-integration-playbook.md is a design doc, and v0.1 code reflects the older chat-first framing. TerraYield will not implement
ione_viewhints, foreign-tenant whoami, or context-slice shapes against an unfrozen contract — one IONe refactor would strand the peer implementation.Acceptance
ione_viewenum + resource metadata shape, whoami request/response, context-slice payload, webhook signature scheme (HMAC-SHA256 header format, timestamp/replay window), error conventions.Consumed by the conformance kit; prerequisite for TerraYield surfaces 4/5/6 (eo_ag#17, eo_ag#18).