fluid-core/workplans/FLUID-WP-0008-fluid-telegram-handover.md

id	type	title	domain	repo	status	owner	topic_slug	created	updated	planning_priority	planning_order	depends_on	related_repos
FLUID-WP-0008	workplan	Handover: HelixForge Telegram identity and hall-of-helix channel	infotech	fluid-core	active	worsch	fluid-core	2026-09-04	2026-09-04	high	7	FLUID-WP-0007	fluid-telegram helix-forge hall-of-helix

FLUID-WP-0008 - Handover to fluid-telegram

The point of the whole sequence. Establish a Telegram identity for HelixForge and a channel publishing hall-of-helix entries, as the first real FLUID interface. Outbound-first: agents and publishing jobs are the consumers, Telegram is the backend.

Deliverables land in docs/handover/fluid-telegram.md here and as FT-WP-0001 in the fluid-telegram repository.

T01 - Interface evolution intent

id: FLUID-WP-0008-T01
status: todo
priority: high

Fill the template for helix-forge-telegram-publishing. Parent intent is helix-forge/INTENT.md. Initial authority mode FLUID-2 (advisory): the Daimon may propose and never generate or promote. Out of scope for now: inbound commands, payments, Mini Apps, moderation. Non-authority: never create Telegram entities, change membership, or touch credentials.

T02 - Bot identity

id: FLUID-WP-0008-T02
status: todo
priority: high

Human step. Register the HelixForge bot via BotFather (Canon BOT-01). Store the token in OpenBao per Canon SEC-04, consistent with HF-WP-0002. The token never enters the repository; the adapter receives only that credential, per Blueprint §28.1 runtime identity.

T03 - Channels

id: FLUID-WP-0008-T03
status: todo
priority: high

Human step. Create a private test channel first, then the public hall-of-helix channel (Canon PUB-01). Bot is administrator with post rights only. All verification runs against the private channel before anything is published publicly.

T04 - Revision R-1 contract

id: FLUID-WP-0008-T04
status: todo
priority: high

POST /v1/hall-entries (idempotent on entry id) and GET /v1/hall-entries/{id}. OpenAPI plus signed revision descriptor.

T05 - Telegram adapter and connector contract

id: FLUID-WP-0008-T05
status: todo
priority: high

Map a hall-of-helix/entries/*.md file to a Telegram post. The adapter is a separate process and may be written in whatever suits the platform. Declare the connector capability contract: identity, auth, timeouts, retry, rate limits, error mapping.

T06 - Cohorts, telemetry and redaction

id: FLUID-WP-0008-T06
status: todo
priority: high

Subscriber classes and agent consumers as cohorts. Redaction rules that keep Telegram user identity (Canon ID-01) out of the evidence store entirely.

T07 - First competing hypotheses

id: FLUID-WP-0008-T07
status: todo
priority: high

Telegram's 4096-character message limit against long-form entries is the first genuine pressure. Two presentation adaptations compete: H-A, teaser plus link back to the hall; H-B, full entry serialized as a multi-part rich post (Canon PUB-02/MED-02). Blueprint §37 argues presentation is the safest and highest-value place to start.

T08 - Live experiment and audit

id: FLUID-WP-0008-T08
status: todo
priority: high

R-2 and R-3 implement H-A and H-B. Run the experiment on real subscriber traffic, measure read-through and reaction, and confirm fluid audit trace reconstructs the whole chain. This is the §50 slice on a real workload.

T09 - Runbook and handover package

id: FLUID-WP-0008-T09
status: todo
priority: medium

Token rotation, channel admin recovery, rollback to R-1, and the assembled handover document.