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.
18 commits 1 branch 0 tags 310 KiB
Find a file
tegwick de7a7bdd2a Read the standard token sink, and tell a 403 from an outage 
NewFromEnv now falls back to ~/.vault-token, the file `bao login` writes and
the bao and vault CLIs already read. An operator who has logged in once
should not have to re-export a secret, and a token that never has to be
typed is a token that never lands in shell history.

Preflight distinguishes the two things a 403 means. An expired token and a
token missing a policy look identical in the error, and the check that
separates them -- whether `bao token lookup` also fails -- is worth naming
where it is read rather than left to be rediscovered.

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 22:27:01 +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 Implement the avatar and a preflight dry run 2026-09-04 22:12:56 +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 Read the standard token sink, and tell a 403 from an outage 2026-09-04 22:27:01 +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.