Guides
Long-form developer documentation. The OpenAPI reference lives at /docs/api — these are the narrative companions.
Start here
The alignment economy
The thesis. YF as infrastructure for the alignment economy — humans build entangled joint wanting through AI-augmented conversation; the moment of agreement is the measurement event that collapses it into a realised deal. Five operational roles: reason · communicate · negotiate · structure · execute. Read this first.
Building with YieldFabric
Wire-level reference for LLMs (and humans) building apps on YieldFabric. Auth flows, the five most-common operations, error handling, common pitfalls. Pragmatic companion to the alignment-economy thesis.
Walkthroughs
Reason · Communicate · Negotiate
Agents, knowledge & workspaces
The first three operational roles of the alignment economy: knowledge graphs and pipelines (reason), working groups and threads (communicate), intents and drafts (negotiate). Working groups, agents-as-members, the Weaver, Studio, RAG with cross-group federation, the personal notebook, and the safety architecture of Intent → Confirm.
LLM access & AI APIs
YieldFabric as your app’s LLM access layer. The OpenAI-compatible /v1 endpoint (point any SDK at YF with a yf_api_… key), per-request model selection, standard tool calling, the yf extension for RAG grounding and server-executed rag_search / start_reasoning tools, citation-to-frame exploration of the knowledge substrate, and per-entity usage metering. Includes end-to-end tutorials.
Structure
DMS (Deal Management System)
The Structure-stage machinery. DealPlan as the typed action DAG two parties sign over; the deal lifecycle (Draft → Proposed → Accepted → Active → Completed); plan compilation to workflows; agreement projection as legal-style markdown; the deal_structurer agent persona; the dms-deals system workspace.
Derived Deals & Contributor Entitlements
How new deals derive from existing deals, and how contributors to a parent deal hold entitlements over the revenues of deals derived from it: derivation, dependency, standing consent, crystallisation, the entitlement register, and settlement preconditions.
Collateralisation
A specific kind of structured deal artifact — the contingent-contract model. Full repo lifecycle, rolls, and rehypothecation chains. Where a confirmed Intent becomes an on-chain collateralised position.
Loans
Periodic / amortizing loan deals — the sibling of the one-shot rental deal. Deploy a transferable loan-note class, mint the creditor position to the borrower, disburse principal, then service repayments period-by-period (interest/principal split paid to the lender), and sell the note to re-route collection.
NFT-holder policy executors
Make a data policy’s spend authority transferable: name an ERC-721 (collection, tokenId) as the executor and whoever holds the NFT may move funds within the policy’s bounds. Transfer the NFT = transfer the right to act — the property-management “agency credential” pattern, with mandatory amount bounds and live ownerOf authorisation.
Integration
SDK generation
How to generate type-safe clients from the OpenAPI specs. Per-language generator recommendations + gotchas.
Webhooks & events
Indexed catalog of every public event surface: webhooks, SSE streams, and polling endpoints.
MCP integration
Model Context Protocol integration. 19 tools, 2 prompts, 4 discovery endpoints. Wiring for Claude Code + Cursor.
Auto-accept payments
Make incoming payments spendable without a manual accept. Arm a wallet so a background worker sweeps its incoming (one asset, a set, or all — present and future), or call acceptAll on demand. Covers the mint-key → setAcceptAutomation flow, status/revoke, group-wallet delegation, and the default-on UX pattern.