Fluid interface for telegram messaging and interaction platform.
Find a file
tegwick 5ddfee8250 Implement the MTProto client, session bootstrap and apply
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
2026-09-04 21:39:30 +02:00
cmd/provision Implement the MTProto client, session bootstrap and apply 2026-09-04 21:39:30 +02:00
contracts Reframe the interface around composed posts, not republished entries 2026-09-04 11:57:28 +02:00
docs Add the operator seeding runbook and enforce the presence schema 2026-09-04 19:30:54 +02:00
experiments Reframe the interface around composed posts, not republished entries 2026-09-04 11:57:28 +02:00
hypotheses Reframe the interface around composed posts, not republished entries 2026-09-04 11:57:28 +02:00
internal Implement the MTProto client, session bootstrap and apply 2026-09-04 21:39:30 +02:00
presence Add the operator seeding runbook and enforce the presence schema 2026-09-04 19:30:54 +02:00
pressure Ground the repo docs and move presence provisioning to a declared spec 2026-09-04 19:21:08 +02:00
revisions Ground the repo docs and move presence provisioning to a declared spec 2026-09-04 19:21:08 +02:00
workplans Implement the MTProto client, session bootstrap and apply 2026-09-04 21:39:30 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-09-04 12:41:37 +02:00
.gitignore Implement provision plan: spec, resolved state, and the diff 2026-09-04 21:25:49 +02:00
AGENTS.md Point at the helix-forge topic 2026-09-04 21:08:59 +02:00
go.mod Implement the MTProto client, session bootstrap and apply 2026-09-04 21:39:30 +02:00
go.sum Implement the MTProto client, session bootstrap and apply 2026-09-04 21:39:30 +02:00
INTENT.md Ground the repo docs and move presence provisioning to a declared spec 2026-09-04 19:21:08 +02:00
InterfaceEvolutionIntent.md Reframe the interface around composed posts, not republished entries 2026-09-04 11:57:28 +02:00
README.md Renumber tasks sequentially for the hub identifier scheme 2026-09-04 11:58:09 +02:00
SCOPE.md Ground the repo docs and move presence provisioning to a declared spec 2026-09-04 19:21:08 +02:00
TelegramCapabilityCanon.md Prepare the FLUID interface for HelixForge Telegram publishing 2026-09-04 11:07:11 +02:00
WORK-RECORDS.md Ground the repo docs and move presence provisioning to a declared spec 2026-09-04 19:21:08 +02:00

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.