Learn the deal object before you model the deal.
A tutorial template for practical deal structures: project agreements, bond issuance, credit facilities, and amortising loans. Each tutorial starts with the commercial object, then maps its parties, dates, rights, triggers, and failure paths into signed YieldFabric primitives.
The natural-language frame: recitals, commercial intent, definitions, and governing terms.
The canonical object parties sign. The rendered agreement and executable actions point at the same hash.
Obligations, swaps, escrows, payments, workflows, gates, and periodic phases.
Proposed, signed, activated, paid, released, defaulted, cured, redeemed, completed.
Tutorial library
The first pass is structure. Drop the material into these rails.
Project agreement
Escrow, milestone payments, acceptance gates, release conditions.
Bond issuance
Issuer promises, noteholder rights, coupon periods, redemption.
Credit facility
Commitment, drawdowns, borrowing base, covenants, repayments.
Amortising loan
Principal, interest, schedule, arrears, optional prepayment.
Read the deal before you choose the primitive.
Contracts
Deal-maker sees: A promise to pay, redeem, deliver, or perform.
YF represents: One instrument with one or more payment streams, schedules, locks, and conditions.
Swaps
Deal-maker sees: Two sides exchanging value without settlement gap.
YF represents: Atomic exchange: both legs settle together or the transaction fails.
Repos
Deal-maker sees: Secured funding with collateral and a repurchase window.
YF represents: A contingent position: repurchase cash before expiry, or collateral after forfeiture.
Payments
Deal-maker sees: Cash today, credit tomorrow, scheduled or conditional value movement.
YF represents: Immediate cash or tracked credit obligations with unlock dates and event gates.
Distributions
Deal-maker sees: Many recipients sharing coupon, dividend, waterfall, royalty, or fee flows.
YF represents: One-to-many payments with independently claimable recipient shares.
Intelligent accounts
Deal-maker sees: Segregated funds, role-based authority, and policy-controlled drawdowns.
YF represents: Accounts governed by signatures, delegation, and configured policy/oracle checks.
The principles every tutorial will reuse.
Cash is immediate and unconditional. Credit is a future obligation with an obligor and an outstanding balance.
Acceptance windows are separate from payment unlock dates. A contract can be signed before anything is payable.
Contracts create related streams together. Swaps settle both sides together. Failed legs do not leak partial state.
Repo repurchase cash and forfeited collateral route to the current holder of the position, not the original lender.
Every tutorial will answer
What kind of economic promise is this? What is the object trying to preserve, transfer, lock, or release?
Who can commit, who can receive value, who approves state changes, and who needs visibility into the audit trail?
Amounts, dates, covenants, milestones, conditions, cure periods, and the exact signatures required at each boundary.
How the agreement becomes a DealPlan, which obligations and swaps exist, which workflow gates run, and what settles on-chain.
Representing a deal in YF
The canonical plan: parties, action DAG, periodic phases, agreement metadata, and hash.
An obligation or swap leg that holds value until an acceptance, date, or approval gate fires.
A human or agent step: approve milestone, verify covenant, sign release, cure default.
Payment, swap, obligation creation, collateral movement, coupon, redemption, or completion.
Project agreements with escrow and milestone payments
How to think about a project as a sequence of commitments: buyer funds escrow, supplier performs work, acceptance gates release milestone payments, dispute paths hold or redirect value.
Buyer deposits the project amount, or a first tranche, into an escrowed account or locked payment structure.
Delivery, inspection, certification, or acceptance evidence becomes the milestone gate.
Approved milestones release staged payments; failed gates hold, refund, or route value into dispute.
A project agreement is not one invoice. It is a funded promise with staged release conditions and a failure path.
Intelligent account escrow or locked payment stream, milestone workflow gates, acceptance signatures, and release payments.
Escrow policies, oracle or human verification, progress-payment streams, partial completion, and refund mechanics.
Bond issuance
How to represent issuer obligations, investor consideration, coupon dates, redemption, transferability, and proof of holding.
Investor pays principal consideration through an issuance swap; issuer delivers the signed bond obligation.
Coupon streams unlock quarterly, semi-annually, or on another agreed schedule.
Principal redemption unlocks at maturity; optional call, put, or collateral branches can be added.
A bond is a schedule of issuer promises: investor consideration now, coupons over time, principal at maturity.
A multi-stream contract for coupon and redemption obligations, issued through an atomic swap and optionally paid via distributions.
Coupon rate, notional, payment frequency, maturity, transfer rules, covenants, defaults, early redemption, collateralization.
Credit facilities
How to model a reusable credit line: commitment amount, draw requests, conditions precedent, borrowing base tests, covenants, repayments.
Facility terms define the limit, availability period, permitted use, margin, fees, and covenant package.
Borrower submits a drawdown intent; policy checks purpose, availability, documents, and approvals.
Drawn amounts become repayment obligations and update utilisation and outstanding credit state.
A facility is capacity plus rules. The borrower can draw only when availability, purpose, and covenant conditions hold.
Intelligent account policy plus drawdown intents, covenant gates, payment obligations, and utilisation state.
Transferable facility token, equipment or project-use restriction, document verification, balance update, fees, and security package.
Amortising loans
How to represent principal reduction over time: repayment schedule, interest calculation, arrears, prepayment, default and cure.
Lender advances principal; borrower signs scheduled principal and interest obligations.
Each period reduces principal and calculates interest against the outstanding balance.
Missed payment creates arrears, cure logic, acceleration, or collateral enforcement.
An amortising loan is a repayment ladder: principal declines over time while interest follows the remaining balance.
A contract with principal and interest streams, periodic payment obligations, outstanding balance tracking, and exception branches.
Principal schedule, interest rule, payment frequency, collateralized-loan option, prepayment, cure, acceleration, and default.
The next tutorials can grow out of these patterns.
Self-referential construction
Build and accept the structure with yourself first, then transfer it atomically to the real counterparty.
Multi-stream contracts
Put coupons, principal, fees, milestone releases, or amortisation legs into one signed instrument.
Conditional payment structures
Use human, agent, oracle, or date gates to keep payments locked until the agreed condition is true.
Repo rolling
Move collateral into a new repo with new terms without manual repurchase and recreation.
Tranching and waterfalls
Separate senior, mezzanine, and equity claims by priority, risk, and distribution path.
Collateral chains
A repo lender position can itself become collateral, with forfeit-forward and repurchase-cash cascade semantics.
This is the reusable teaching frame.
The first source pass now pulls from the financial structuring guide. Next, each tutorial can take real deal material: diagrams, example terms, a sample agreement projection, and a compact DealPlan sketch. The code still comes after the commercial object is understood.