Capacity signup playbooks

The reusable framework for opening the per-platform accounts that tcp.systems capacity work needs — the account-maker kit. One method, one dossier per platform, no second copy of a platform’s data.

The boundary

Every dossier in this kit carries the same four rules:

1. One account per platform. No alias, no burner, no trial reset, no second identity. An existing account is recovered, never duplicated.
2. The owner’s own legal identity in every field. James White, 7 Bell Yard, London WC2A 2JR, United Kingdom, plus the owner’s real mailbox, phone and company details. No invented values.
3. Every verification is a human handoff. Email confirmation, CAPTCHA, SMS or voice code, passkey, ID/KYC and payment are performed by the owner.
4. The submit click is the owner’s. The agent drives the browser up to the control and stops. It never submits, solves, receives a code, replays a request, or calls a create-account API.

If a platform’s terms forbid assisted signup, the owner completes the page manually. The boundary is a floor, not a licence.

Files

File	What it is
signup-playbook-template.md	The method: field map, step sequence, handoff sentences, post-signup key storage and catalog seat registration, dossier JSON shape, and the validator contract.
../../tools/signup-checklist.sh	The generic checker: validates one dossier and prints the step-by-step checklist with every handoff marked. Read-only; it never fetches or submits anything.
../../tools/signup-checklist.test.mjs	Tests for the checker: valid dossier exits 0; a second account, an automated verification, or a credential-shaped field value is rejected.

The template is the only place the method lives. A per-platform dossier holds only that platform’s values.

Finder dossiers

The finder workers file the per-platform dossiers as a document plus GitHub issues. This kit keeps the method and links the dossiers by reference; it does not copy their data.

Finder	Scope	Dossier document	Per-platform issues
W98	expansion plan	capacity-expansion-2026-10-21.md (PR #43, merged)	#38–#41, plus catalog seat #42
W101	Western/US	capacity-finders-western-2026-10-21.md (PR #61, merged)	#44–#60
W102	Asia	Asia dossiers PR #74 (open)	#62–#73

Each per-platform issue must link this template and carry the filled JSON block from §7 of the template (replace the placeholders; keep the fixed values). The issues were filed before this template landed, so the link is added when a dossier is worked, not copied into the issue. The issue remains the source of truth for that platform’s values.

Finder issue header

Copy this header into a dossier issue when you pick it up, so the link is explicit and the fixed values cannot drift:

Playbook: https://github.com/tcpsystems/ops/blob/main/docs/capacity/signup-playbook-template.md
Finder: W98 | W101 | W102
Platform: <vendor and platform id>
Account quota: 1 (fixed)
Identity: owner-legal-identity (fixed)
Verification: human-only (fixed)
Dossier JSON: <the filled block from §7; no credential values>

The issue is the dossier. It holds that platform’s values; it does not hold a second copy of the method, a key, a password, a one-time code or a card number. Do not invent an issue number; use the finder’s issue.

Run the checker on a dossier

tools/signup-checklist.sh path/to/dossier.json

• Exit 0: the dossier is valid and the checklist is printed.
• Exit 2: usage error or invalid dossier; every problem is named on stderr.
• It reads one local file. It makes no network call, opens no browser, submits nothing and handles no credential value.

Attach the command and its exit code to the finder issue as evidence. A checklist that prints is not proof the account exists; the account page and the catalog seat verification are.