fluid-telegram/WORK-RECORDS.md

# Work Records — fluid-telegram

> Generated by `statehub fix-consistency` (CUST-WP-0061-T04, work-record
> stage 3). Do not edit by hand — edit the source file/block listed for
> each record and re-run fix-consistency to refresh this index. Archived
> workplans are omitted; closed decisions/intakes/engagements stay listed
> so recently-resolved work is still visible. [auto]

| Kind | ID | Status | Lane | Source |
| --- | --- | --- | --- | --- |
| workplan | FT-WP-0001 | active | — | workplans/FT-WP-0001-telegram-identity-and-hall-channel.md |
| task | FT-WP-0001-T01 | todo | — | workplans/FT-WP-0001-telegram-identity-and-hall-channel.md |
| task | FT-WP-0001-T02 | todo | — | workplans/FT-WP-0001-telegram-identity-and-hall-channel.md |
| task | FT-WP-0001-T03 | todo | — | workplans/FT-WP-0001-telegram-identity-and-hall-channel.md |
| task | FT-WP-0001-T04 | todo | — | workplans/FT-WP-0001-telegram-identity-and-hall-channel.md |
| task | FT-WP-0001-T05 | todo | — | workplans/FT-WP-0001-telegram-identity-and-hall-channel.md |
| task | FT-WP-0001-T06 | todo | — | workplans/FT-WP-0001-telegram-identity-and-hall-channel.md |
| task | FT-WP-0001-T07 | todo | — | workplans/FT-WP-0001-telegram-identity-and-hall-channel.md |
| task | FT-WP-0001-T08 | todo | — | workplans/FT-WP-0001-telegram-identity-and-hall-channel.md |
| task | FT-WP-0001-T09 | todo | — | workplans/FT-WP-0001-telegram-identity-and-hall-channel.md |
| task | FT-WP-0001-T10 | todo | — | workplans/FT-WP-0001-telegram-identity-and-hall-channel.md |
| task | FT-WP-0001-T11 | todo | — | workplans/FT-WP-0001-telegram-identity-and-hall-channel.md |
| task | FT-WP-0001-T12 | todo | — | workplans/FT-WP-0001-telegram-identity-and-hall-channel.md |
| task | FT-WP-0001-T13 | todo | — | workplans/FT-WP-0001-telegram-identity-and-hall-channel.md |
Ground the repo docs and move presence provisioning to a declared spec Align AGENTS.md with the FT-WP- prefix the hub already registered, and rewrite INTENT.md and SCOPE.md, which were still the generated stubs and carried none of the composed-post framing the interface is built around. Fix two artifact inconsistencies: R-1's retry comment still described POST /v1/hall-entries idempotent on entry_id, from before the reframe to composed posts; and the seed pressure record listed only one of the two hypotheses that cite it. Rename it to match its id. Replace the manual T01-T03 route with FT-WP-0002. The Bot API cannot create a bot or a channel, so provisioning is an MTProto client acting as a designated operator account (Canon INT-03), driven from a declared presence spec owned by the campaign. One bounded human bootstrap remains and docs/provisioning.md says why it cannot be removed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0172sgCZEEDJcnQmr4SGDvKa Assistant: claude-code Assistant-Model: opus Assistant-Process: 1361245@bnt-lap001 Assistant-Session: b3b428ef-f3e6-4688-b091-01f71461d66a 2026-09-04 19:21:08 +02:00			`# Work Records — fluid-telegram`

			> Generated by `statehub fix-consistency` (CUST-WP-0061-T04, work-record
			`> stage 3). Do not edit by hand — edit the source file/block listed for`
			`> each record and re-run fix-consistency to refresh this index. Archived`
			`> workplans are omitted; closed decisions/intakes/engagements stay listed`
			`> so recently-resolved work is still visible. [auto]`

			`\| Kind \| ID \| Status \| Lane \| Source \|`
			`\| --- \| --- \| --- \| --- \| --- \|`
			`\| workplan \| FT-WP-0001 \| active \| — \| workplans/FT-WP-0001-telegram-identity-and-hall-channel.md \|`
			`\| task \| FT-WP-0001-T01 \| todo \| — \| workplans/FT-WP-0001-telegram-identity-and-hall-channel.md \|`
			`\| task \| FT-WP-0001-T02 \| todo \| — \| workplans/FT-WP-0001-telegram-identity-and-hall-channel.md \|`
			`\| task \| FT-WP-0001-T03 \| todo \| — \| workplans/FT-WP-0001-telegram-identity-and-hall-channel.md \|`
			`\| task \| FT-WP-0001-T04 \| todo \| — \| workplans/FT-WP-0001-telegram-identity-and-hall-channel.md \|`
			`\| task \| FT-WP-0001-T05 \| todo \| — \| workplans/FT-WP-0001-telegram-identity-and-hall-channel.md \|`
			`\| task \| FT-WP-0001-T06 \| todo \| — \| workplans/FT-WP-0001-telegram-identity-and-hall-channel.md \|`
			`\| task \| FT-WP-0001-T07 \| todo \| — \| workplans/FT-WP-0001-telegram-identity-and-hall-channel.md \|`
			`\| task \| FT-WP-0001-T08 \| todo \| — \| workplans/FT-WP-0001-telegram-identity-and-hall-channel.md \|`
			`\| task \| FT-WP-0001-T09 \| todo \| — \| workplans/FT-WP-0001-telegram-identity-and-hall-channel.md \|`
			`\| task \| FT-WP-0001-T10 \| todo \| — \| workplans/FT-WP-0001-telegram-identity-and-hall-channel.md \|`
			`\| task \| FT-WP-0001-T11 \| todo \| — \| workplans/FT-WP-0001-telegram-identity-and-hall-channel.md \|`
			`\| task \| FT-WP-0001-T12 \| todo \| — \| workplans/FT-WP-0001-telegram-identity-and-hall-channel.md \|`
			`\| task \| FT-WP-0001-T13 \| todo \| — \| workplans/FT-WP-0001-telegram-identity-and-hall-channel.md \|`