coulomb/ops-mason
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

MASON-IN-0003: ask fluid-telegram for the adapter deployment identity

Browse source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 327203@bnt-lap001
Assistant-Session: 55028ae3-4914-4bd1-8f5c-815f3527aef0
This commit is contained in:
tegwick 2026-10-09 10:45:03 +02:00
parent 515644de98
commit c24732e8a8
1 changed files with 8 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
intakes/intakes.md
View file

@ -97,6 +97,14 @@ updated: '2026-09-04T21:55:00+02:00'
state_hub_intake_id: "01a06e68-8c29-7230-b0dc-88f1e374afa4"
```
2026-10-09: the parent operator plan is approved (MASON-WP-0005-T03), so this
lane can be designed once the adapter's deployment identity is known. Nothing
in fluid-telegram declares one yet (no manifests; FT-WP-0002-T06 delivered only
`internal/adaptercfg`, whose `LoadToken` reads `bot-token` alone). Asked
fluid-telegram (message `6d06bd9d`): where the adapter runs (Kubernetes SA with
ESO, or a host AppRole), whether it needs `redaction-salt` as well as
`bot-token`, and per-campaign or shared.
## MASON-IN-0004 — Close the policy-plus-AppRole escalation path in ops-mason-build
```yaml