> For the complete documentation index, see [llms.txt](https://jordan-7.gitbook.io/jordan-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jordan-7.gitbook.io/jordan-docs/internal/run-b-verification/work-history.md). # Work history One page per significant work period, built from `DECISIONS.md`, `OPEN-ISSUES.md`, `docs/briefs/`, the `HANDOFF-*.md` files and the git log of `origin/v0-ui-migration`. Each page says what shipped, what it found — real defects and near-misses especially — the judgment calls, and the verification result. This is the project's memory; the source files remain authoritative and are cited on every page. | Period | Page | One line | | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | 2026-07-05 → 07-23 | [Migration era](/jordan-docs/internal/run-b-verification/work-history/2026-07-migration-era.md) | Arc → Tempo, MPP meter, passkeys, dashboard, handles, LiveKit as default transport | | 2026-07-24 | [Browse deck](/jordan-docs/internal/run-b-verification/work-history/2026-07-24-browse-deck.md) | The Kick-class landing board behind `BROWSE_DECK` | | 2026-07-25 | [Lazy connect and bounty Run A](/jordan-docs/internal/run-b-verification/work-history/2026-07-25-lazy-connect-and-bounty-run-a.md) | The LiveKit leak fixed structurally; the bounty state machine, ledger and stub settlement | | 2026-07-26 → 07-27 | [Hardening and the bounty program](/jordan-docs/internal/run-b-verification/work-history/2026-07-26-27-hardening-and-bounty-program.md) | Evidence chain, per-playback nonce, the mechanic found dead at go-live, fan-facing build | | 2026-07-28 | [Run B verification](/jordan-docs/internal/run-b-verification/work-history/2026-07-28-run-b-verification.md) | The machine-readable badge, the deterministic decoder, real frame sources | | 2026-07-29 | [Prove, calibrate, OBS one-click](/jordan-docs/internal/run-b-verification/work-history/2026-07-29-prove-calibrate-obs.md) | The first real broadcast and the two P0s only it could find; per-VOD calibration; Add to OBS | | 2026-08-24 → 08-25 | [Platform parity and capture hardening](/jordan-docs/internal/run-b-verification/work-history/2026-08-24-25-parity-and-capture-hardening.md) | Self-capture, route authorization as a table, confidence tiers, pump.fun un-parked | | 2026-08-26 → 09-03 | [Real broadcasts](/jordan-docs/internal/run-b-verification/work-history/2026-08-26-09-03-real-broadcasts.md) | Self-capture could never have worked (`OPEN-ISSUES.md`); the overlay polled 4× too slowly; a dead recorder scored as an absent badge; five platforms proven | | 2026-08-29 → 09-06 | [UI overhaul](/jordan-docs/internal/run-b-verification/work-history/2026-08-29-09-06-ui-overhaul.md) | Create-room page, the Nerve skin, the landing, `/app` as a directory | | 2026-09-05 | [Guest whitelist](/jordan-docs/internal/run-b-verification/work-history/2026-09-05-guest-whitelist.md) | Named guests ride free above the cap, keyed to the streamer | | 2026-09-11 → 09-14 | [Follow my stream and airings](/jordan-docs/internal/run-b-verification/work-history/2026-09-11-14-follow-and-airings.md) | Measured Twitch liveness, the follow loop, the booth camera alert, the airing record | | 2026-09-15 → 09-16 | [Pass A and Pass B](/jordan-docs/internal/run-b-verification/work-history/2026-09-15-16-pass-a-and-pass-b.md) | Reconciling the tree, the underpay fix reaches prod, whitelist hardened, layout editor, posters, the gate history reconciled, this handbook | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://jordan-7.gitbook.io/jordan-docs/internal/run-b-verification/work-history.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.