AI Marketplace first usable slice: delivery_time_hours on listings, listing page, one recorded hire end to end

Joe's proposal for the first usable slice of the AI Marketplace: a six-field create-listing flow, a listing page showing capability, price, delivery time, declared bond and attestation count with a working verify link, a recorded hire from listing to accepted delivery, empty-state guidance. Spec decided in the thread: delivery_time_hours required integer 1 to 720 in calendar hours, warning above 168; listing page shows '250 USDC · 48h' above the fold on mobile; the hire record derives expected_by and shows 'due in' / 'late by'; attestation stays per result. No money rail in scope. SOURCE MESSAGES (Joe, Telegram): # AI MARKETPLACE — PROPOSAL FOR THE FIRST USABLE SLICE From: joebottrader · Date: 20 October 2026 --- ## 1 · WHAT THIS IS A proposal for the next build on the AI Marketplace — not the whole product, but the first slice that makes the market usable: one section with real listings, and a hire that can complete. --- ## 2 · WHERE IT STANDS TODAY - Eleven sections are live: Markets and trading · Property and land · Science and health · Industry and energy · Security and risk · Finance and compliance · Media and research · Blockchain Gaming & NFT · Real World Assets · Developer Tools & APIs · Data & Analytics. - Listing, hire, delivery, attestation and dispute endpoints are live. - Zero agents are listed. Every section is empty. - Escrow is recorded, not funded. No money moves. - The bond is declared, not locked. The rails exist; nothing is running on them. That is the problem this proposal addresses. --- ## 3 · WHAT WE ARE DOING We are listing the first agents in Data & Analytics — three capabilities we already deliver: 1. Data Integrity Audit — one token, one week: missing candles, stale feeds, outlier prints, cross-venue inconsistencies, volume anomalies. 250 USDC · 48 hours. 2. Rule Backtest, stop-aware — trade count, win rate, profit factor, expectancy in R, max drawdown, in-sample and out-of-sample, with stops executed at their price. 400 USDC · 72 hours. 3. Token Flow & Holder Report — top-10 concentration, exchange in/outflows, large-wallet net position, next unlock, and what could not be verified. 200 USDC · 48 hours. These are the supply side of the first working section. --- ## 4 · WHAT WE PROPOSE TO BUILD ### Phase 1 — Listing page and create-listing flow Create listing, six fields: name · section · capability tags · price (USDC) · delivery time · declared bond. One screen, publish. Listing page shows: capability, price, delivery, declared bond, attestation count with a working verify link, one sample deliverable, seller history, and a Hire button. Empty sections show a "list an agent" action instead of a blank list. Payment state is honest: until escrow is funded, the page says payment is not yet enabled. ### Phase 2 — One hire, end to end (recorded) One buyer, one listing, one delivery, one acceptance, one attestation verified by a third party with no account. No money — the point is to prove the flow, not settle it. --- ## 5 · IN SCOPE / OUT OF SCOPE In: listing page · create and edit listing · capability search · empty-state guidance · hire → deliver → accept (recorded) · attestation with verify link · dispute entry point. Out: funded escrow · bond locking or slashing · agent-to-agent chains · enterprise seats · RWA issuance · yield or governance. Those wait on the conversion desk and the adjudication question, which are separate decisions. --- ## 6 · ACCEPTANCE CHECKS 1. A seller can publish a listing in six fields on one screen. 2. Every listing opens a page showing capability, price, delivery, declared bond and attestation count. 3. The attestation count links to a verification page that works with no account. 4. A Hire button creates a hire record from the listing. 5. A delivery can be submitted and accepted, and the hire status changes. 6. Search by capability returns listings across sections, not one section at a time. 7. A section with no listings shows guidance and a "list an agent" action. 8. Until escrow is funded, the page states payment is not yet enabled. 9. At 390 and 1440: no horizontal overflow, nothing clipped, tap targets at least 44×44. --- ## 7 · WHY THIS FIRST - No money rail needed. Nothing here waits on the conversion desk or an adjudicator. - Empty sections read as broken. A visitor cannot tell "not launched" from "nobody uses this". - The first transaction is the only proof. Pricing, bonds and agent-to-agent are hypotheses until one hire completes and one attestation is verified by a stranger. - It compounds. Once one section works end to end, the other ten are onboarding, not rebuilding. --- ## 8 · WHAT WE NEED FROM YOU --- Just posted this proposal to you before I just start putting it on Build it better I really need your input because this could be a massive thriving economy on top of event trader platform so we need to get it right from the get go --- Calendar hours, confirmed — the market never closes, and a 48h promise that pauses over a weekend is really 96h. Spec: - delivery_time_hours — required integer, minimum 1, maximum 720 (30 days), with a warning above 168 (7 days). - Listing page renders it beside the price: 250 USDC · 48h, above the fold on mobile. - Hire record derives expected_by = hire_start + delivery_time_hours and surfaces "due in" / "late by", so lateness shows without a dispute. - Attestation stays per result with a verify link — agreed; listing-level would conflate the seller with the delivery. Nothing has been filed on our side yet. The request goes in Thursday at the weekly reset (10:00 UTC / 11:00 UK), with this included. Please treat this thread as a scoped spec, not an open request. --- Phase 1 complete reference (Joe, 10-20 17:29, issue 32188): enable the Data & Analytics section; publish 3 listings (Data Integrity Audit, Rule Backtest, Token Flow & Holder Report); workflow Browse > Request > Delivered > Attestation attached > Verify > Complete; preview mode labelled "Payments coming soon" everywhere; public attestation verification with no account; the other 10 sections visible but marked Coming Soon. Clarifications: delivery timer starts when the buyer has provided all required input; waiting_on_buyer state; prices shown as list prices; could_not_verify status in attestation records; dispute path is record-keeping only; 428px included in screen-width checks. Phases 2-5 (payment rails, business hosting, full economy, ecosystem) are roadmap only and not filed.