coulomb/fluid-telegram
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Fluid interface for telegram messaging and interaction platform.
28 commits 1 branch 0 tags 727 KiB
Find a file
tegwick bfebca3aee Implement the R-1 adapter (FT-WP-0001 T05/T09); mark workplans blocked 
Builds internal/adapter and cmd/adapter: the three contracts/r1.openapi.yaml
operations, idempotency on post_id, the reviewed_by/consent-basis refusals,
per-form (R-2/R-3) length limits, and Markdown-to-Telegram rendering, all
against a Sender interface so it's testable without a live bot token.

Every other open task in FT-WP-0001 and FT-WP-0002 needs something this repo
can't supply on its own: the human session bootstrap in FT-WP-0002 T01, the
fluid CLI from fluid-core, or a person's judgment (consent basis, editorial
review, publishing pace). Set both workplans to status: blocked and flagged
FT-WP-0002-T01 needs_human on the hub, since it's the single blocker gating
everything else.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 278411@bnt-lap001
Assistant-Session: 19568045-15bc-4b88-ba3d-8e95b4f9c6f1
2026-09-27 23:15:37 +02:00
cmd Implement the R-1 adapter (FT-WP-0001 T05/T09); mark workplans blocked 2026-09-27 23:15:37 +02:00
contracts Reframe the interface around composed posts, not republished entries 2026-09-04 11:57:28 +02:00
docs Finish the provisioner's remaining plane: honest check, adapter config, IEI-2 2026-09-14 02:55:58 +02:00
experiments Reframe the interface around composed posts, not republished entries 2026-09-04 11:57:28 +02:00
hypotheses Reframe the interface around composed posts, not republished entries 2026-09-04 11:57:28 +02:00
internal Implement the R-1 adapter (FT-WP-0001 T05/T09); mark workplans blocked 2026-09-27 23:15:37 +02:00
presence Add the operator seeding runbook and enforce the presence schema 2026-09-04 19:30:54 +02:00
pressure Ground the repo docs and move presence provisioning to a declared spec 2026-09-04 19:21:08 +02:00
revisions Finish the provisioner's remaining plane: honest check, adapter config, IEI-2 2026-09-14 02:55:58 +02:00
workplans Implement the R-1 adapter (FT-WP-0001 T05/T09); mark workplans blocked 2026-09-27 23:15:37 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-09-22 08:27:42 +02:00
.gitignore Implement provision plan: spec, resolved state, and the diff 2026-09-04 21:25:49 +02:00
AGENTS.md AGENTS.md: fill unresolved {CREDENTIAL_ROUTING} placeholder with the credential-routing section 2026-09-22 08:26:52 +02:00
go.mod Implement the MTProto client, session bootstrap and apply 2026-09-04 21:39:30 +02:00
go.sum Implement the MTProto client, session bootstrap and apply 2026-09-04 21:39:30 +02:00
INTENT.md Finish the provisioner's remaining plane: honest check, adapter config, IEI-2 2026-09-14 02:55:58 +02:00
InterfaceEvolutionIntent.md Finish the provisioner's remaining plane: honest check, adapter config, IEI-2 2026-09-14 02:55:58 +02:00
README.md Finish the provisioner's remaining plane: honest check, adapter config, IEI-2 2026-09-14 02:55:58 +02:00
SCOPE.md Finish the provisioner's remaining plane: honest check, adapter config, IEI-2 2026-09-14 02:55:58 +02:00
TelegramCapabilityCanon.md Prepare the FLUID interface for HelixForge Telegram publishing 2026-09-04 11:07:11 +02:00
WORK-RECORDS.md chore(consistency): write back hub IDs and refresh WORK-RECORDS 2026-09-22 08:35:43 +02:00

README.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, the adapter's connector contract and the presence provisioner are in place; the bot, the channel and the adapter itself are not. The first live apply waits on the operator seeding runbook.