Fluid interface for telegram messaging and interaction platform.
The repo record moved from topic "custodian" (the register default) to "helix-forge", where these repos belong: they are one loop around HelixForge, and a query for its work should return the loop intact. rmgr sync updates the hub but not the topic id embedded in these files, so the orientation commands here were still querying the old topic. 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 |
||
|---|---|---|
| contracts | ||
| docs | ||
| experiments | ||
| hypotheses | ||
| presence | ||
| pressure | ||
| revisions | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| AGENTS.md | ||
| 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