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.
21 commits 1 branch 0 tags 310 KiB
Find a file
tegwick 854e807899 Request a credential lane for the Telegram operator 
Addressed to ops-warden as the front door, and explicit that the lane
itself is railiance-platform's to create -- ops-warden routes this row
rather than executing it.

States the two things that are easy to get wrong. The lane needs write and
not only read: apply's critical write happens immediately after BotFather
issues the bot token, and a denial there leaves a registered bot whose only
credential is a chat message, with a re-run creating a second bot. And the
redaction salt must never be rotated, so write-once on that path would be
welcome if the lane tooling can express it.

Leaves the <domain> segment open rather than assuming infotech: the only
concrete lane we can read uses "coulomb", which looks like a tenant rather
than a sector, and the segment belongs to its owner.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0172sgCZEEDJcnQmr4SGDvKa

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1361245@bnt-lap001
Assistant-Session: b3b428ef-f3e6-4688-b091-01f71461d66a
2026-09-04 23:11:24 +02:00
cmd/provision Read the standard token sink, and tell a 403 from an outage 2026-09-04 22:27:01 +02:00
contracts Reframe the interface around composed posts, not republished entries 2026-09-04 11:57:28 +02:00
docs Request a credential lane for the Telegram operator 2026-09-04 23:11:24 +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 Adopt the confirmed secret layout 2026-09-04 23:03:52 +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 Ground the repo docs and move presence provisioning to a declared spec 2026-09-04 19:21:08 +02:00
workplans Implement the avatar and a preflight dry run 2026-09-04 22:12:56 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-09-04 12:41:37 +02:00
.gitignore Implement provision plan: spec, resolved state, and the diff 2026-09-04 21:25:49 +02:00
AGENTS.md Point at the helix-forge topic 2026-09-04 21:08:59 +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 Ground the repo docs and move presence provisioning to a declared spec 2026-09-04 19:21:08 +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 Ground the repo docs and move presence provisioning to a declared spec 2026-09-04 19:21:08 +02:00
TelegramCapabilityCanon.md Prepare the FLUID interface for HelixForge Telegram publishing 2026-09-04 11:07:11 +02:00
WORK-RECORDS.md Ground the repo docs and move presence provisioning to a declared spec 2026-09-04 19:21:08 +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.