Fluid interface for telegram messaging and interaction platform.
Completes the provisioner's write path. internal/tg drives BotFather as a conversation rather than pretending it is an endpoint, creates channels, claims usernames with fallbacks, and grants post_messages. internal/apply sequences it: bot before administrator, test channel before public, and state saved after every step that changed the world -- a channel that exists but is unrecorded is worse than one that does not exist, because the next run creates a second. The operator session lives in OpenBao, not on disk. gotd's FileStorage would leave a full-account credential in the working directory, where it outlives the run and can be committed by accident. The bot token goes straight from BotFather's reply to OpenBao and is cleared from memory; if that write fails the error says how to recover by hand and warns against re-running, since a retry creates a second bot. Closes T05: the redaction salt is create-if-absent with no overwrite path, and the test asserts it, because rotating it invalidates every longitudinal comparison with no visible failure. 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 |
||
|---|---|---|
| cmd/provision | ||
| contracts | ||
| docs | ||
| experiments | ||
| hypotheses | ||
| internal | ||
| presence | ||
| pressure | ||
| revisions | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| AGENTS.md | ||
| go.mod | ||
| go.sum | ||
| INTENT.md | ||
| InterfaceEvolutionIntent.md | ||
| README.md | ||
| SCOPE.md | ||
| TelegramCapabilityCanon.md | ||
| WORK-RECORDS.md | ||
fluid-telegram
Fluid interface for telegram messaging and interaction platform.
Status
The FLUID interface helix-forge-telegram-publishing is prepared but not yet
live. Governance, contract, seed hypotheses and the adapter's connector contract
are in place; the bot, the channel and the adapter itself are not.
- Governance:
InterfaceEvolutionIntent.md - The channel publishes composed posts written from hall entries, not the
entries themselves. Composition happens upstream and moves to
pr-hall-of-helixonce the loop has closed once (FT-WP-0001 T13). - Work:
workplans/FT-WP-0001-telegram-identity-and-hall-channel.md - Handover from fluid-core:
fluid-core/docs/handover/fluid-telegram.md