reference

Reference — Index

docs/reference/README.mdtype: mocupdated: 2026-05-03

Reference

Engineer-facing deep-dives. The narrative PRD lives in ../01-Overview through ../10-Roadmap; reference pages here cover the how it actually works for surfaces that need more depth than a domain bullet — endpoints, schema, lifecycle, concurrency.

Pages

Page Persona Status
payouts Backend / integrator 🟢 live
unified-intents Backend 🟢 live
api-checkout Backend / integrator 🟢 live

Reference material also lives outside this folder:

Page Persona Status
../PRD/reference/reconciliation Backend / ops 🟢 live
../implementation/fireblocks-whitelisted-wallets Backend / custody ops 🟢 live
../observability/better-stack Eng / ops 🟢 live (dev only)
../providers-specs/tres-fee-recording Backend / finance 🔴 spec — TRES not integrated

What belongs here vs the domain notes

  • ../03-Domains gives the one-line status per surface. Use it for the at-a-glance map.
  • The narrative PRD (01–10) sits between product and engineering — KPIs, scope, drawbacks, roadmap.
  • Pages here are the canonical engineering source for a single surface: endpoint shapes, lifecycle states, concurrency invariants, cache behaviour, schema-level detail. Cross-link back into the narrative for risk + open-question context, never duplicate it.