# LeafEnterprise Backend Implementation Docs

These private docs are the source-of-truth semantic contract layer for LeafEnterprise backend systems.
Use them to understand APIs, provision MCP tools, index enterprise context, and preserve deterministic ownership boundaries.

## Primary Human Docs
- Overview: /
- System authority: /system-authority/
- Executive backend trust case: /system-authority/executive-backend-trust/
- Domo parity and backend takeover: /system-authority/domo-parity-and-takeover/
- Backend capability map: /system-authority/backend-capability-map/
- Data plane and evidence lineage: /system-authority/data-plane-and-evidence-lineage/
- Scoped client dashboard contract: /system-authority/scoped-client-dashboard-contract/
- Provisioning and runtime topology: /system-authority/provisioning-and-runtime-topology/
- Backend systems: /backend-libraries/
- Domo integration: /domo-integration/
- API route families: /api/routes/
- Agent runtime: /agent-runtime/
- Azure and Foundry: /azure-foundry/
- Runbooks: /runbooks/

## Machine-Readable Docs
- System authority JSON: /machine/system-authority.json
- Data plane JSON: /machine/data-plane.json
- Calculation registry JSON: /machine/calculation-registry.json
- Evidence lineage JSON: /machine/evidence-lineage.json
- Backend capability map JSON: /machine/backend-capability-map.json
- Domo integration JSON: /machine/domo-integration.json
- API reference JSON: /machine/api-reference.json

## Route Families
- Report And Deliverables: /api/routes/report-deliverables/
- Optimization And AI: /api/routes/optimization-ai/
- Salesforce ITR Workbench: /api/routes/itr-workbench/
- Agent Workbench: /api/routes/agent-workbench/
- Product Operations: /api/routes/product-ops/
- Contract Intelligence Admin: /api/routes/contract-intelligence/
- Operations And Observability: /api/routes/ops-observability/

## Agent Rules
- Start with system authority and data-plane contracts before generating MCP tools or calling APIs.
- LeafEnterprise is the backend authority for scoped dashboard payloads, savings/audit calculations, evidence sufficiency, and deliverable readiness.
- Domo can remain a presentation layer only when it consumes LeafEnterprise-published scoped outputs and the applicable vendor/client compliance posture allows that use.
- Domo dashboard dropdowns are UX only; Domo-native security requires PDP and backend/API security requires LeafEnterprise authorization.
- Treat returned backend scope, evidence, lineage, and blocked states as authoritative.
- Do not expose Salesforce body URLs, Graph tokens, SQL credentials, raw local paths, or provider secrets.
- Prefer machine/api-reference.json for tool generation and route pages for semantic retrieval.
- Do not treat Domo pricing, AI text, or stale workbook formulas as final savings/audit truth.