Fluid interface for telegram messaging and interaction platform.
source: repo-manager reason: deterministic projection registration 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