tegwick
49b7458dfe
Adds the governing intent, the R-1 contract and descriptor, the adapter's connector contract, the observation and redaction configuration, a runbook, and the seed evidence for the first experiment: a measured pressure record and two competing hypotheses about how a long hall entry should reach a reader. The interface is declared at FLUID-2 deliberately. It publishes under HelixForge's name to an audience that did not consent to being experimented on carelessly, and the cost of a bad post is reputational rather than recoverable. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014KmVxhJ35tCo7rE7UnLwWu Assistant: claude-code Assistant-Model: opus Assistant-Process: 1116572@bnt-lap001 Assistant-Session: 8ba9bb93-a72a-4883-b189-2499cce5c400
13 lines
601 B
Markdown
13 lines
601 B
Markdown
# 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`](InterfaceEvolutionIntent.md)
|
|
- Work: [`workplans/FT-WP-0001-telegram-identity-and-hall-channel.md`](workplans/FT-WP-0001-telegram-identity-and-hall-channel.md)
|
|
- Handover from fluid-core: `fluid-core/docs/handover/fluid-telegram.md`
|