Post work. Get back an approval or a completed task.
The single marketplace face above the two registers of human gig work — expert (value = signature) and work (value = presence). The constitution is ratified and the supply doors serve; the exchange itself is a reserved name, and the page at the apex says so.
Every gigs.* door on record recruits one tribe of workers in its own words — attorneys at gigs.lawyer, adjusters at gigs.claims, every doorless credential at the flagship gigs.expert. This name caps that family from the other side: gigs.exchange is where the buyer of human work shows up, and it is constitutionally the only place they need to.
The family constitution (gigs ADR 0001, owner-ratified 2026-07-26) splits human gig work into two registers, keyed on where the human's value lives — never on collar color, which a master plumber breaks in both directions:
One test decides everything, and it is the buyer's own question: what are you purchasing — an approval, or a completed task? That deliverable test is the whole routing logic of the exchange, and the reason its intake can be one question long.
The seam between registers is where the mechanism earns its keep. One real-world job that needs both presence and signature — a CAT field inspection, an IME exam — is modeled as two linked gigs joined by a lineage edge, one per register, each with its own economics: the field scope visit is a work-register Shift; the coverage decision stays an expert-register act. Where law requires the field human and the signing human to be one person, a Same-Worker Bind carries it. Never a hybrid third register; two meters cannot share one release.
The expert register's flagship serves today: gigs.expert is live with field-first signup, target figures labeled illustrative on the page itself, and no member anywhere called verified before verification runs. Cold check 2026-07-31.
The exchange's credibility is a list of refusals, each one a ratified rule:
The registers price differently and release identically — on deterministic facts, never on satisfaction:
–·–posts when first live postings measured resolves · –·–posts when first ninety days of measured routing resolves — published when measured, never asserted in advance.
No fee figure, band, or spread appears in this record. The registers' numbers post where they are earned — on the doors and in measurement — never in a deck ahead of them.
The motion is B2B at the surface and B2A underneath. The poster answers for a business; the native caller is the agent acting under that business's mandate — the next billion users of software resolve, they don't browse. The do.industries masthead already files this name in its stack as the estate's human-capability resolver, the twin of apis.directory's machine-capability catalog: ask for a capability, get a graded, live, payable answer — and where the capability is human, the answer is a register.
That filing is intent, not integration. The masthead's own record carries this apex as a pending Claim, and this record mirrors it rather than improving on it. The grading surface designed to sit behind both resolvers — api.qa, a machine grade and a human credential as the same signed, replayable attestation — is likewise stated across the estate as design intent, not a live wire.
Demand for the expert register's hardest vertical already has a served supply side: gigs.lawyer answers today with the attorney door. Cold check 2026-07-31.
gigs.claims answers today with the adjuster door — flat-fee claim reviews, the fee fixed before claim, stated on its own page. Cold check 2026-07-31.
The apex answers 200 with the estate's own RESERVED register leaf — title "gigs.exchange · RESERVED · apis.finance family register", the sentence "Reserved for a marketplace name of the gigs estate", and the words "Nothing at this domain is live" on the page itself. Cold check 2026-07-31. Serving a truthful reservation is the liveness fact; it is not the exchange.
The machine leaf serves the same reservation in kind — status RESERVED, the register line, and the family contact — so an agent resolving this name cold is told, truthfully, that nothing here is live. What the leaf files the name as is the seam below. Cold check 2026-07-31.
The exchange itself — the posting surface, the deliverable-test intake, the cross-register view — is not built. This is the same gate the do.industries masthead carries for this apex, mirrored verbatim; it flips green when the apex answers as the face this record describes, and not before.
The filing seam is worn openly, and it runs three deep: the live leaf files this name under the apis.finance family register; its reservation sentence scopes the name to "routed finance work"; and — sharpest of the three — both the apex and llms.txt class the name "Supply face · gigs estate · apis finance family · holding" (cold check 2026-07-31), the direct inversion of this record's identity as the one gigs.* record whose ICP sits on the DEMAND side. The ratified family constitution seats the name above both registers of the whole gigs estate, facing demand. The seam is queued in the estate's program doc (2026-07-30); whichever way it resolves, every green Claim in this deck stays curl-true.
Half the exchange's routable universe has no serving door: on a cold check (2026-07-31) gigs.work does not resolve at all — the family map files its purchase as in progress — and the constitution itself rules that the W2-vs-1099 classification survey gates the first live Shift. The work register is filed design, stated here as exactly that.
The routing mechanics, Shift lifecycle, and minimum-honest-v1 spec quoted through this deck are the constitution's PROPOSED design work under its RATIFIED rulings. The two-register split, the exchange's seat above both, and the refusals list are ratified; the machinery is design until ruled.
The constitution is ratified and the supply doors serve today; the exchange itself is a reserved name — the page at the apex says so.
If this was forwarded to you: gigs.exchange is the reserved marketplace face of the gigs estate — one name where a business, or its agent, will post work and get back an approval (from the credential-gated expert register) or a completed task (from the dispatched work register), routed by one question about the deliverable. Nothing at the domain is live yet, the apex says so itself, and this deck carries four ambers saying the rest out loud: the unbuilt surface, a filing seam on the reservation, a work register that is still design, and mechanics awaiting ratification. The doors underneath it serve today, each with its own record in this estate. If you post work: the capture is keys@apis.finance. If you hold a credential: the doors are open.