Yard Read the blueprint ↗

THE YARD AT WORK / LIVE SANDBOX

Describe it.
Sign it once.
Get it built.

Your idea needs a place to become a working thing. A clear blueprint. A builder who clocks in. Payment when the work stands.

Hosted Yard. The Board, events, site log and private intake run on Render. Stood connects to the PayPal sandbox. The illustrated examples below are demonstrations: No payment is executed.

Open Yard See Stood’s gate ↗

Yard builds. Stood decides the money. Every builder faces the same gate.

WO–024 / BOOKING APPSIMULATED
A blueprint you can build on.Illustrative work order. The Foreman and hosted previews are planned.
FIXED PRICEYOUR REPOSIGNED TESTSONE MONEY GATENO SPECIAL TREATMENT

01 / THE PLAN

You touch it
three times.

Describe what you need. Read the tests. Take the keys to your finished app. That’s the product we’re building.

  1. 01

    Describe.

    Save a private brief or import Startup Tribunal research. The hosted Foreman connection comes next. Acceptance tests are the contract.

    LIVE INTAKE · FOREMAN NEXT
  2. 02

    Sign.

    Approve the scope, tests and fixed budget. Work goes on the Board. A builder clocks in with a 48-hour lease.

    STOOD SANDBOX SIGNING · YARD CONNECTION NEXT
  3. 03

    Hand over.

    The intended finish: your repo, your hosting, your live keys. The final payment waits until you use the product.

    PLANNED · HOSTING + HANDOVER

02 / WALK THE YARD

Work moves.
Money has a gate.

Try the illustrated outcomes below. This page uses local fixtures; it is not a live Board or a payment control.

Choose an illustrative milestone

ADAEZE’S BOOKING APP

Make the booking flow work.

FIXTURE BUDGET$120.00
WO–024 · MILESTONE 2 / 3Checking
booking.contract.test.tsREAD ONLY / SIGNED FIXTURE
01 test('a buyer can book a slot', () => {
02   expect(booking.confirmed).toBe(true);
03 });
  • Signed testsUnchanged ✓
  • Test executionPassed ✓
  • Payment confirmationWaiting

A green test run alone never makes the Board say paid.

Illustrative fixture · simulated provider proof · no payment executed. Selecting a scenario changes this illustration only.

RUN THE LOCAL INTEGRATION CHECKscripts/dev mockFifteen network scenarios. Isolated test services. Read the guide ↗

03 / SAME GROUND. SAME RULES.

Yard can build it.
It can’t pay itself.

Yard owns the work: terms, claims and submissions. Stood owns the decision about money. Yard’s own Crew gets exactly the same gate as any outside builder.

BUYERYARD / BUILDERSTOOD’S GATE
Yard builds. Stood pays.Meet Stood ↗

04 / BUILD IT IN THE OPEN

The blueprint
is yours to read.

The Board, events, site log and private intake are hosted. Stood’s PayPal sandbox supports saved-account signing and funding. The live Foreman, repository and preview adapters are next; the Crew arrives in the final batch.

Open the Yard docs ↗