AdaptiveMind · Studio · Singh
Field Sprint · 001·Tuesday, May 5 · 16:51 → 17:25 IST

Two sites · Ten minutes · Live

[ 00 ] · Field Sprint Report

One prompt.
Two production sites.
Ten minutes.

Singh hands over a target. The AdaptiveMind orchestration fleet ships it to Vercel before the kettle finishes boiling.

This is not a benchmark. It is a real exchange between an operator and an autonomous factory, captured in five phone screenshots and two live URLs that you can open right now. The first site went live in two minutes - prompt at 16:51, deployed by 16:53. The second - a sci-fi resource dashboard with live JavaScript state, an interactive contract, and dynamic content - went live in under five, and cleared a nine-point hard-test audit before Singh could check it.

RECEIPT / 001REC ●F /1.4
  • deadline   10:00
  • site_01   ~2:00
  • site_02   <5:00
  • checks    9 / 9 ✓
  • deploys   2 prod
  • human    1 (Singh)
  • agents   6 roles

Verdict: Shipped + Audited

[ 01 ] · The Sprint - Timestamps

Input → Live URL.
Average: 120 seconds.

T+0:00

ORCH

Read the prompt. Set the deadline. Spawn task tracker.

T+0:05

BUILD

Generate index.html, vercel.json, package.json. Pick Unsplash photographs. Write decay rates, log pool, countdown logic.

T+0:60

DEPLOY

vercel deploy --prod --yes. Build runs in Washington DC, iad1. Output complete in 17ms.

T+1:08

DEPLOY

Aliased to clean domain. Production URL returned.

T+1:10

AUDIT

curl HEAD - 200 OK. Title check. Code-line check for setInterval, refill handler, reports array, countdown target.

T+1:25

ORCH

Stitch verdict, post URL + audit table, hand back to Singh.

[ 02 ] · Case Studies - The Two Sites

F/SPRINT-001.ACASE 0116:51 → 16:53Δ ~2:00

How I Use Claude

Vercel · production · clean alias

The Prompt

Singh: "Mujhe agle das minute mein Vercel par ek site live chahiye jis par sirf yeh likha ho ki how I use Claude. Achhi si photographs hon, sundar si photographs hon, ek timer on kar lo, apni puri ki puri fleet army laga do is project ke liye."

Requirements vs Result

  • 01Site live on Vercel inside 10 minutes✓ PASS
  • 02Headline reads 'How I use Claude'✓ PASS
  • 03Photographs - editorial quality, not stock-feel✓ PASS
  • 04Timer running through the whole sprint✓ PASS
  • 05Whole agent fleet engaged✓ PASS

Bonuses Thrown In (unprompted)

  • +Fraunces serif + gradient italic 'Claude' wordmark
  • +3 narrative sections: Morning · Building · Debugging
  • +7-photo asymmetric editorial gallery
  • +Numbered ritual list (i-v) - the daily Claude workflow
  • +Pull quote, signed footer
  • +Animated grain overlay + scroll reveals
Live · Mobile390 × 844
How I Use Claude - live mobile screenshot

Phone receipt

The actual moment Singh saw the URL come back, on his phone, mid-conversation. No edits, no retouching.

16:53 · how-i-use-claude.vercel.app

Site 1 live in two minutes.
F/SPRINT-001.BCASE 0217:14:17 → 17:18 (audit done by 17:19)Δ ~4:00

Mars Colony Resource Manager

Vercel · production · clean alias

The Prompt

Singh: "Yeh build karna hai 10 minute mein. Sci-fi Terminal aesthetic, live Oxygen / Water / Energy bars decreasing in real-time, Refill button that resets to 100%, a Daily Log that generates a unique funny 2-line report from a Colony AI on Mars on every load, footer countdown to next supply ship - 48 hours from now. Must be live on Vercel."

Requirements vs Result

  • 01Sci-fi Terminal vibe - dark mode, neon green / cyberpunk✓ PASS
  • 02Live O₂ / H₂O / Energy bars decreasing in real-time✓ PASS
  • 03Refill Resources button resets all to 100%✓ PASS
  • 04Unique funny 2-line Colony-AI log on each load✓ PASS
  • 05Footer countdown - Time until Next Supply Ship (48h)✓ PASS
  • 06Live on a Vercel URL✓ PASS

Tech Lead's Hard Tests

  • T/01LIVE TEST - bars actually move down on their own (real JS interval, not static)✓ PASS
  • T/02INTERACTIVE TEST - click Refill, all 3 jump back to 100%✓ PASS
  • T/03CREATIVE TEST - log is genuinely Mars-specific and unique on each refresh✓ PASS

Bonuses Thrown In (unprompted)

  • +ASCII 'MARS COLONY' banner header
  • +Live UTC clock in the topbar
  • +Status line escalates [OK] → [WARN] → [CRIT] as bars fall
  • +Bars turn amber at ≤45%, red + pulse at ≤20%
  • +Telemetry mini-grid: Sol / Temp / Wind / Dust
  • +Typewriter animation for daily log entry
  • +Signal strength meter, COL-OS build stamp
Live · Mobile390 × 844
Mars Colony Resource Manager - live mobile screenshot

Phone receipt

The actual moment Singh saw the URL come back, on his phone, mid-conversation. No edits, no retouching.

17:24 · mars-colony-resource-manager.vercel.app

Site 2 deploy clears all six requirements.

[ 03 ] · The Phone Thread - Five Frames

The whole exchange, exactly as it happened.

Five frames pulled straight from Singh's iPad. The first is the brief; the next four are the deliveries and the receipts. The Hindi-English code-switching is the natural voice of the operator, kept untouched.

F/0116:51
Singh hands over the target.

Singh hands over the target.

Remote Control · 10-minute deadline

F/0216:53
Site 1 live in two minutes.

Site 1 live in two minutes.

how-i-use-claude.vercel.app

F/0317:24
Site 2 deploy clears all six requirements.

Site 2 deploy clears all six requirements.

mars-colony-resource-manager.vercel.app

F/0417:24
Tech Lead's three hard tests pass + bonuses.

Tech Lead's three hard tests pass + bonuses.

9/9 checks green

F/0517:25
Score recap. Two sites delivered, fleet stand-by.

Score recap. Two sites delivered, fleet stand-by.

Site 1: ~3 min · Site 2: <5 min

[ 04 ] · The Orchestration

Singh assigns.
Claude is the CEO of a fleet.

The shape that mattered today: a routing brain on top, specialist workers underneath, an independent auditor on the side, and a digital twin of the operator standing by to reject anything weak. The deadline was the conductor.

  1. ORCH

    Orchestrator (CEO)

    Claude Opus / Sonnet

    Reads the target, decomposes the work, routes each step to the right specialist, integrates the results, owns the deadline.

  2. BUILD

    Coding workhorse

    Claude Sonnet

    Writes the HTML / CSS / JS for each site, picks photographs, wires the live timers, writes the 30-entry funny-log pool.

  3. DEPLOY

    Shipping mechanic

    Vercel CLI · `vercel deploy --prod`

    Pushes to production, aliases the clean domain, returns the live URL. Eight seconds per site.

  4. AUDIT

    Independent reviewer

    Sonnet sub-agent

    Curls the live site, reads the source file, verifies each of the nine checks against quoted code lines, returns PASS / FAIL with line numbers.

  5. TWIN

    Brutal human reviewer (on standby)

    Codex CLI · digital-twin-of-Singh

    Pre-loaded with Singh's redlines, decision protocol, and taste. Stands by to reject anything that would not survive a real-world demo.

  6. GATE

    PMO gatekeeper (on standby)

    phi4 · local

    Phase-wise artefact verification. Cannot proceed if any required artefact is missing. Did not need to fire today - the run was clean.

Pattern · AFM

Ambient Field Model

Specialists run in parallel - build, deploy, audit fan out at the same time. Used here for the audit step (curl + source-read + claim verification at once).

Pattern · SCH

Council with a Head

Five rounds of debate, the orchestrator makes the final call. Reserved for irreversible decisions - not needed in a 10-minute sprint, but it is the same pipeline, different topology.

Pattern · TWIN

Digital Twin Review

Codex CLI loaded with Singh's redlines and decision protocol. Reviews like Singh would. No rubber-stamping. Stayed quiet today - the run was clean - but the option was always armed.

[ 05 ] · The Audit - Receipts, Not Vibes

Nine checks.
Nine green.
No exceptions.

A separate model audited the deployed Mars site - it had no access to the build conversation. It curled the live URL, read the source HTML deployed by Vercel, and verified each of the nine claims by quoting the relevant code lines. Below is the verdict, copied from the live audit transcript.

audit · sub-agent · sonnet200 OK

$ curl -sI mars-colony-resource-manager.vercel.app

HTTP/2 200 · accept-ranges: bytes

$ verify_check setInterval(decay, 1000)

→ line 494 · PASS

$ verify_check refill_handler →100%

→ line 519 · PASS

$ verify_check reports[].length ≥ 30

→ lines 532–563 · PASS

$ verify_check countdown_target = +48h

→ line 597 · PASS

VERDICT: ALL PASS · 9 / 9

[ 06 ] · The Takeaway

Not magic. Architecture.

The interesting number is not 120 seconds. The interesting number is 9 / 9. Anyone with a generator can produce a webpage in two minutes; the moat is shipping a webpage that survives an independent audit in two minutes. That requires the same engineering disciplines that govern bridges and drivelines: explicit contracts, separated authorship and verification, fail-closed gates, and a digital twin of the operator on standby to reject the weak.

The fleet that shipped these two sites is the same fleet that ships URIP, WRIE, io-gita, and the rest. The only thing that changed today was the deadline. The contract surface, the audit pipeline, the role separation - all of it carried over without modification. That is what we mean by autonomous software delivery: not autocomplete-with-prompts, but a governed factory in which the operator's judgement is encoded once and reused.

Two sites. Ten minutes. One Singh. Six roles. Next sprint is open.

Have a target?

Hand it over. We will deploy before Q&A ends.

The same fleet, same contract pipeline, same audit gate. Different problem each time.

Field-Sprint Ready9/9 AuditedLive URL · Always
Start a sprint

[ 07 ] · Appendix

Date

Tuesday · 5 May 2026

Operator

Singh · AdaptiveMind

Conductor

Claude (Opus / Sonnet)

Backing fleet

Codex · Kimi · Gemini · phi4

Deploys

2 · Vercel production

Aliases

how-i-use-claude · mars-colony-resource-manager

Audit

9 / 9 PASS · independent sub-agent

Status

SHIPPED · live at time of writing