coulomb/fluid-telegram
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Fluid interface for telegram messaging and interaction platform.
8 commits 1 branch 0 tags 310 KiB
Find a file
repo-manager ca47f7879d repo.work.assign_missing_identifiers 
source: repo-manager
reason: deterministic projection registration

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1116572@bnt-lap001
Assistant-Session: 8ba9bb93-a72a-4883-b189-2499cce5c400
2026-09-04 11:58:09 +02:00
contracts Reframe the interface around composed posts, not republished entries 2026-09-04 11:57:28 +02:00
docs Reframe the interface around composed posts, not republished entries 2026-09-04 11:57:28 +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
pressure Reframe the interface around composed posts, not republished entries 2026-09-04 11:57:28 +02:00
revisions Prepare the FLUID interface for HelixForge Telegram publishing 2026-09-04 11:07:11 +02:00
workplans repo.work.assign_missing_identifiers 2026-09-04 11:58:09 +02:00
.custodian-brief.md Register with State Hub 2026-09-04 11:09:02 +02:00
.gitignore Register with State Hub 2026-09-04 11:09:02 +02:00
AGENTS.md Register with State Hub 2026-09-04 11:09:02 +02:00
INTENT.md Register with State Hub 2026-09-04 11:09:02 +02:00
InterfaceEvolutionIntent.md Reframe the interface around composed posts, not republished entries 2026-09-04 11:57:28 +02:00
README.md Renumber tasks sequentially for the hub identifier scheme 2026-09-04 11:58:09 +02:00
SCOPE.md Register with State Hub 2026-09-04 11:09:02 +02:00
TelegramCapabilityCanon.md Prepare the FLUID interface for HelixForge Telegram publishing 2026-09-04 11:07:11 +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 and the adapter's connector contract are in place; the bot, the channel and the adapter itself are not.