coulomb/fluid-telegram
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Fluid interface for telegram messaging and interaction platform.
10 commits 1 branch 0 tags 310 KiB
Find a file
tegwick 5a785b9d9f 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
contracts Reframe the interface around composed posts, not republished entries 2026-09-04 11:57:28 +02:00
docs Ground the repo docs and move presence provisioning to a declared spec 2026-09-04 19:21:08 +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
presence Ground the repo docs and move presence provisioning to a declared spec 2026-09-04 19:21:08 +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 Ground the repo docs and move presence provisioning to a declared spec 2026-09-04 19:21:08 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-09-04 12:41:37 +02:00
.gitignore Register with State Hub 2026-09-04 11:09:02 +02:00
AGENTS.md Ground the repo docs and move presence provisioning to a declared spec 2026-09-04 19:21:08 +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

README.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.