Fluid interface for telegram messaging and interaction platform.
tegwick
3aa8cb7eaf
The channel publishes a post written from a hall entry -- condensed, personal, reach-optimized -- not the entry itself. That changes what this interface is for and where its boundary sits. Composition is deliberately outside the interface. Composing is a probabilistic editorial task, and Blueprint 48.1 forbids an LLM in the mandatory request path, so an interface that composed on demand would be non-deterministic exactly where determinism is the whole claim. It is also editorial: a post speaks about a named person's work in HelixForge's voice, and a review step inside the request path is a review step nobody performs. The contract now takes a composed post with a required reviewer, a cited source entry and a consent basis. A post carrying none of those is refused. Absence of objection is not consent, and in an audit trail an unfaithful post looks exactly like a faithful one -- the defence is that a human read it, the source is named, and both are recorded. The first experiment is rebuilt accordingly. The old competition asked how to fit a whole entry into Telegram; that question no longer exists. The new one asks whether the portrait earns the 3072 characters of caption limit it costs, which is a delivery question this interface actually owns. Competition over editorial voice belongs to the campaign and runs on the per-variant engagement this interface reports. Adds T05b (composition and review), T05c (consent basis for the 94 existing participants, blocking public publication) and T11 (extracting the campaign into pr-hall-of-helix). 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 |
||
|---|---|---|
| contracts | ||
| docs | ||
| experiments | ||
| hypotheses | ||
| pressure | ||
| revisions | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| AGENTS.md | ||
| INTENT.md | ||
| InterfaceEvolutionIntent.md | ||
| README.md | ||
| SCOPE.md | ||
| TelegramCapabilityCanon.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 T11). - Work:
workplans/FT-WP-0001-telegram-identity-and-hall-channel.md - Handover from fluid-core:
fluid-core/docs/handover/fluid-telegram.md