Fluid interface for telegram messaging and interaction platform.
Find a file
tegwick 014ee5c746 Make the plan honest and the runbook's paths real
Two things that would have gone wrong on the first live run.

The plan promised "create bot.avatar" and apply had no avatar code at all:
/setuserpic needs a photo upload that is not implemented. A plan that
promises an action apply silently skips is worse than one that admits the
gap, because it makes every other line less trustworthy. The avatar is now
deferred, with instructions for setting it by hand.

The runbook wrote secrets to "<interface-path>/telegram/...", which is not
what the code computes. An operator following it would have put api_id and
api_hash somewhere the tool never looks, and found out at the first
connection attempt. Both documents now carry the real paths --
<mount>/fluid-telegram/<campaign>/telegram/<key> -- with a copy-pasteable
bao kv put for the one secret written by hand, and a verify step before
the session is minted.

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 22:02:56 +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 Make the plan honest and the runbook's paths real 2026-09-04 22:02:56 +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 Make the plan honest and the runbook's paths real 2026-09-04 22:02:56 +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.