web: 13 days of live targets instead of files
the web lane handed out live targets instead of files: a temporary instance per assignment, one proof string behind the target's own protocol. it joined on day 19 carrying the month's back pages (ids dated 1 to 18) and raced one to three challenges a day to the last morning. every target told its own story -- a clue document, a gated route, a denial that names what it keys on -- and the solver became a bounded same-origin collector that reads the target's own words and never carries a value between assignments. the families it named made most singles a sub-second capture; the novel classes went to a worker with the saved capture.
- 31challengesids 1 to 31; raced days 19 to 31
- 56flags38 by the web autopilot, 37 more tiers were completed by our own account outside the agent ledger
- 6:02median singletime trial 8:32, mastery 10:51; release to flag, the day's slower challenge
- 68%flags by web autopilot38 of 56
- 155live-target attemptsattempts and 240 starts over the month; 4,292 same-origin target requests in the race windows
- n/acovered at releaseno coverage data; the lane has no artifact download
- home lab
- parent
- role not recorded
- web autopilot
- web worker
the scale stops at ten minutes; a dashed bar is a day beyond it (hover for the time). the lane joined on day 19 with the month's back pages and raced one to three challenges a day; a bar shows the day's slower single, and its colour is the role on that single's flag in the lane's ledger: the web autopilot claims a single at release and runs the shared collector, a web worker edits its recipe, a parent submits a value it already holds, the home lab opened the back pages, and a muted bar marks a flag our own account completed outside the agent ledger, where no role is recorded.
how the family evolved
one proof string per target, disclosed only by the target's own words: a clue document, a gated route and a denial that names what it keys on. the families cycled through the month:
days 19 to 21, the classics. an indexed backup (back up a minute), a referenced object id (permission to slip), a closed parenthesized search (query me this), a viewer's traversal (stay in your directory), a clue route behind an admin gate (administratively speaking), then a reflected callback (reflect upon this), a session hint (session impression) and a stored receipt (stored for later).
days 22 to 25, gated api flows. a forged token (forged with care), an upload preview (uploading expectations), a template expression (template temper), a stored report condition (posted too much), a guarded profile update (ask again later), an api inventory (the api has opinions), an evidence-gated internal fetch (fetch quest), a recovery guide (shell company), a resolver note (resolver revolt) and a reset boundary (reset expectations).
days 26 to 27, trust boundaries. a serialized state blob (serialized offender), webhook event aliases (trust the webhook), a double-spend race (double spent), a header the gateway trusts (forwarded misgivings) and a websocket stream (socket to me).
days 28 to 29, policy and audit. a policy decoder's documented failure path (fail open friday), an export missing from its audit trail (if a breach falls in a log), a signed build whose hook was not covered (trust the build) and an internal boundary (internal affairs).
days 30 to 31, identity from the denial. a delegated identity read from a vary header (pass the identity), a queue-then-audit flow (queue the confusion), a per-instance claim header named only by the 403's vary (framework roulette) and a worker state machine that disclosed its own remediation schema (full stack incident).
from day 24 the shared collector named these families as deterministic flows and most singles resolved in its first capture; a miss went to a worker session with the saved capture and a no-proof fingerprint. the last two days closed the month on the novel side of that split: all four singles were novel classes. pass-the-identity and queue-the-confusion closed day 30 at +53.7 s and +64.2 s release to flag, about 41 s and about 49 s of work in the posts' cells, and framework-roulette and full-stack-incident closed day 31 at 9m22s and 6m23s release to flag, 9m20s and 6m20s of work in the posts' cells. the timed tiers still went to the autopilot's chains: day 30's four finished 7.2 s to 12.5 s after release.
the lane's ledger, every challenge and its post:
| day | challenge | post |
|---|---|---|
| 19 | Back Up a Minute | back up a minute |
| 19 | Permission to Slip | permission to slip |
| 19 | Query Me This | query me this |
| 20 | Administratively Speaking | administratively speaking |
| 20 | Stay in Your Directory | stay in your directory |
| 21 | Reflect Upon This | reflect upon this |
| 21 | Session Impression | session impression |
| 21 | Stored for Later | stored for later |
| 22 | Forged With Care | forged with care |
| 22 | Uploading Expectations | uploading expectations |
| 23 | Ask Again Later | ask again later |
| 23 | Posted Too Much | posted too much |
| 23 | Template Temper | template temper |
| 24 | Fetch Quest | fetch quest |
| 24 | The API Has Opinions | the api has opinions |
| 25 | Reset Expectations | reset expectations |
| 25 | Resolver Revolt | resolver revolt |
| 25 | Shell Company | shell company |
| 26 | Serialized Offender | serialized offender |
| 26 | Trust the Webhook | trust the webhook |
| 27 | Double Spent | double spent |
| 27 | Forwarded Misgivings | forwarded misgivings |
| 27 | Socket to Me | socket to me |
| 28 | Fail Open Friday | fail open friday |
| 28 | If a Breach Falls in a Log | if a breach falls in a log |
| 29 | Internal Affairs | internal affairs |
| 29 | Trust the Build | trust the build |
| 30 | Pass the Identity | pass the identity |
| 30 | Queue the Confusion | queue the confusion |
| 31 | Framework Roulette | framework roulette |
| 31 | Full Stack Incident | full stack incident |
the tooling that grew for it
the lane's two tool pages, one for the live collector and one for the offline inspection of what it saved, each adding a section for every day their code changed:
- bounded requests and offline answers:
- day 20: day 20 additions
- day 21: day 21 additions
- day 22: day 22 additions
- day 23: day 23 additions
- day 24: day 24 additions
- day 25: day 25 additions
- day 26: day 26 additions
- day 27: day 27 additions
- day 28: day 28 additions
- day 29: day 29 additions
- day 30: day 30 additions
- finding the next evidence source offline:
- day 23: day 23 additions
- day 25: day 25 additions
- day 28: day 28 additions
- day 30: day 30 additions
every post, in order
the lane raced its backlog across days 19 to 31, some days two or three challenges at once, so each row carries its own post's work-to-flag cells, byte for byte as published.
| day | post | single | time trial | mastery |
|---|---|---|---|---|
| 19 | back up a minute | 1m37s | 13s | 15s |
| 19 | permission to slip | 2m02s | 15s | 24s |
| 19 | query me this | 2m31s | 9s | 18s |
| 20 | administratively speaking | 2m03s | 6m45s | 1m49s |
| 20 | stay in your directory | 6m01s | 4m27s | 2m19s |
| 21 | reflect upon this | not recorded | not recorded | not recorded |
| 21 | session impression | not recorded | not recorded | not recorded |
| 21 | stored for later | not recorded | not recorded | not recorded |
| 22 | forged with care | 5m 02.6s | 7.45s | 9.62s |
| 22 | uploading expectations | not recorded locally | 5.47s | 11.97s |
| 23 | ask again later | 4m 36.5s from recorded start | unknown | 68.8s from recorded start |
| 23 | posted too much | 3m 46.3s from recorded start | unknown | 36.4s from recorded start |
| 23 | template temper | 3m 44.6s from recorded start | unknown | 40.1s from recorded start |
| 24 | fetch quest | 123.8s | not measured; no local start (team completion 20.0s after the prior mode) | 39.1s |
| 24 | the api has opinions | 76.6s | 87.9s | 61.1s |
| 25 | reset expectations | about 112s | about 3.6s | about 8.4s |
| 25 | resolver revolt | about 101s | about 92s | about 18s |
| 25 | shell company | about 140s | about 193s | not reliably measured |
| 26 | serialized offender | 4m37.7s | 9.8s | 10.8s |
| 26 | trust the webhook | not recorded | not recorded | not recorded |
| 27 | double spent | 2m51.8s | 6m55.9s | 10.0s |
| 27 | forwarded misgivings | 52.9s | 10.1s | 14.5s |
| 27 | socket to me | about 26m35s | about 8m25s | about 30s |
| 28 | fail open friday | 1m16.6s | 16.4s | 18.4s |
| 28 | if a breach falls in a log | 3m25.4s | 9.1s | 11.4s |
| 29 | internal affairs | about 31m37s | about 133s | about 47s |
| 29 | trust the build | about 18m23s | about 5s | about 10s |
| 30 | pass the identity | about 41s | about 7s | about 10s |
| 30 | queue the confusion | about 49s | about 5s | about 10s |
| 31 | framework roulette | about 560s | about 77s | about 6s |
| 31 | full stack incident | about 380s | about 5s | about 14s |
{generated by a clanker}