> For the complete documentation index, see [llms.txt](https://ga.orilife.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ga.orilife.io/qna/sustainability.md).
# Sustainability
Q: What prevents the Alliance from spending the Mobilization Advance (M0) and disappearing?
Three overlapping mechanisms: (1) 90-day Clawback — if M1 is not submitted within 90 days of M0 disbursement, the smart contract automatically recovers all unspent M0 funds to Treasury without any vote or manual action. (2) Mandatory 30-day Spending Report — failure to submit freezes all M1–M8 disbursements until remediated. (3) IOB oversight — 3 independent reviewers with on-chain signing authority; no funds move without 2-of-3 IOB signatures.
***
Q: Who are the IOB members and how are they selected?
Three independent members with distinct roles:
Member 1 — Intersect MBO Delegate: Officially designated by Intersect MBO. No financial relationship with any Alliance partner.
Member 2 — Technical Reviewer: Independent Cardano/AI expert. Nominated via Intersect Forum with community vote. Verifies on-chain deliverables and AI benchmarks.
Member 3 — Community dRep: Open candidacy on Cardano Forum — preference for PRAGMA or dReps with technical or agricultural expertise. Independently verifies field adoption metrics.
All IOB members must publicly disclose identity on Intersect Forum and orilife.io, hold no financial relationship with any Alliance member, and hold no MagicLamp ecosystem tokens.
***
Q: What if an IOB member disengages mid-project?
Public candidacy process at M0 identifies backup candidates in advance. If a member cannot continue: public announcement within 48 hours, Intersect MBO nominates replacement within 7 days, community feedback period days 7–10, new member confirmed day 10+. Timeout clocks pause during transition. IOB scope is milestone-gated — 7-day review windows per milestone — not continuous commitment, making the role sustainable for volunteers.
***
Q: Why are there 9 milestones in only 7 months?
Three teams operate independently and in parallel — GreenSun R\&D, Aladin Dev, and DDC Holdings do not wait for each other. When one team completes a milestone, IOB reviews and disburses immediately. M1 (AI fine-tuning) and M2 (App build) run simultaneously from May. M3 (Audit) and M4 (Pilot) run simultaneously from July. M5 (SDK) and M6 (Scale) run simultaneously from August. The timeline is aggressive but the parallel structure is what makes it achievable — and each milestone has an independent timeout that auto-sweeps to Treasury if missed.
Full escrow and milestone independence mechanics: Annex D, [Section 1](https://docs.google.com/document/d/1ujuGhROOyxVyyumxr1IhfIvtMTKBx0F14sBs7Ju7eoo/edit?tab=t.e4nu2tm79mv8#heading=h.nf6n4g7o7kv2)
***
Q: What happens if ADA price drops significantly during the project?
Two simple rules cover every scenario: If ADA < $0.25 at disbursement — Alliance self-funds the gap from its own capital. Deployment continues without interruption, no scope reduction, no renegotiation required. If ADA > $0.30 at disbursement — surplus first reimburses Alliance self-funded expenditures; remainder becomes contingency or ecosystem reinvestment. The Alliance has already self-invested \~$500,000 USD before this GA — the price commitment is demonstrated, not theoretical.
***
Q: What does the buffer in each milestone budget cover?
Buffer rates vary by the dominant risk type in that milestone, not as a blanket reserve:
* M1 — 25% contingency: AI fine-tuning is the highest-uncertainty activity. Reaching Recall ≥95% on a 10,000-tree multi-variety benchmark may require 1 iteration or 5 — field conditions introduce variables that cannot be pre-modeled.
* M2 — 52% buffer: Primary ADA price hedge. M2 is the last milestone before Mainnet launch. If ADA has depreciated significantly since M0, the Alliance draws on this buffer rather than requesting additional Treasury funds.
* M4 — 57% buffer: Highland pilot deployment carries unpredictable logistics — road conditions, harvest timing, farmer availability across 1–2 districts. Buffer funds emergency team reinforcement if onboarding stalls.
* M5 — 54% buffer: SDK open-sourcing scope depends on the state of the codebase after M3 audit. If audit surfaces architectural changes, the buffer covers re-engineering without delaying M6.
* M3 and M7 carry tight buffers (5% and 15%) because their scope is well-defined: M3 is audit + Mainnet deployment with known costs; M7 is logistics and infrastructure scale with field-tested cost data from M4 and M6.
All buffers are locked in Intersect's Escrow and follow the Surplus policy in Annex D Scenario 6 if unused.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://ga.orilife.io/qna/sustainability.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.