> 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/risks.md).
# Risks
**Q: What if ADA price drops sharply 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 proposal — this is a demonstrated commitment, not a theoretical one.
***
**Q: What if key team members leave during the project?**
DDC Holdings operates across 46 communes with institutionalized relationships that predate any individual. GreenSun Tech holds 4 USPTO PPAs on core IP — technology assets are legally protected and transferable. Aladin Contract has an engineering team with AI-assisted workflows. The IOB has authority to freeze disbursements if team continuity is compromised, and the auto-sweep mechanism returns ADA to Treasury in any extended inactivity scenario.
***
**Q: What if Vietnam's government changes traceability requirements mid-project?**
The December 1, 2026 deadline is law — not a policy recommendation. OriLife's open-source Compliance SDK can be updated to match new reporting format requirements without changing the core blockchain infrastructure. On-chain data — Farm NFTs, Bio-IDs, LampNet records — remains valid regardless of how reporting standards evolve. Regulatory format changes are addressed at the Compliance Adapter layer; the underlying architecture is unaffected.
***
**Q: What if GACC does not accept Midnight View Key format?**
Midnight is an optional privacy layer, not a GACC compliance prerequisite. OriLife exports full GACC-required data fields (origin, harvest date, plantation code, phytosanitary) independently of Midnight. The M4 pilot shipment validates GACC acceptance before full rollout — any required format adjustments are addressed at M4, not M7. The Compliance Adapter SDK handles format changes without modifying core infrastructure.
***
**Q: What if the August harvest season is missed during rollout?**
M4 Pilot is specifically scheduled to operate during the August 2026 durian harvest season in Đắk Lắk — this is the primary validation window for the harvest module. M6 and M7 scale after the peak season. Missing the August window would delay harvest module validation but not block infrastructure milestones. IOB would assess impact and adjust milestone timing within the existing escrow timeout structure.
***
**Q: What if farmers don't adopt the system?**
Adoption risk is low for two reasons. First, Circular 11 creates direct legal pressure — non-connected farms risk product recall from December 1, 2026. Second, DDC Holdings has already presented OriLife to 46 communes covering 50,000+ people over two harvest seasons; the UX has been validated with farmers aged 50+ who had no prior smartphone experience. PhoenixKey registration takes \~3 minutes via fingerprint and face scan — no technical knowledge required. The Extension Center's institutional mandate further ensures engagement at the commune leadership level before individual farmer outreach.
***
**Q: What if there is a smart contract bug post-Mainnet?**
The audit strategy is specifically designed to minimize this risk: reuse Intersect's battle-tested Escrow template (audit only customization), independent security audit before any Mainnet deployment, Bug Bounty program live from M3+, and smart contract frozen at M2 for the full audit period before M3 deployment. Zero unresolved Critical or High severity findings is a hard M3 acceptance criterion — no deployment proceeds until the audit is clean.
---
# 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/risks.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.