informed-decision/docs/batches/2026-10-05-dependency-roots/OPERATOR.md

Dependency-root sitting — operator packet

Drafted 2026-10-05 and queued the same day. An agent may not accept, decline, or seal. Review group: net-kingdom-admins. Open each review while signed in as the platform reviewer: https://decisions.coulomb.social/ Generator: tools/prepare_dependency_root_batch.py.

This sitting groups separate hub decisions. There is no approve-all. An answer on one memo does not answer the others. resolves: never means the answer must not be written back as a resolve of the shared hub decision.

n	memo_id	review	task	resolves	question
1	infd-20261005-s1-red-controls	review-9eb3b31f-cd08-4141-af7f-48e151bdebbf	RAIL-HO-WP-0011-T05	on-answer	Approve remediation of exactly the two red S1 controls found by the 2026-10-05 Goss refresh?
2	infd-20261005-activity-empty-projections	review-1ece4f3e-d0e3-4fd6-abc8-272f1b1876f4	STATE-WP-0095-T04	never	Approve retirement of only the three named empty Activity projections while preserving their parent projection?
3	infd-20261005-hall-signing-key	review-774bf3ce-e8c8-424a-98d6-d1b2b94f2bf4	FT-WP-0001-T04	on-answer	Authorize a durable Hall of Helix R-1 signing key held outside git, without creating that key in this draft?
4	infd-20261005-telegram-bot	review-51834acb-8b62-4b3b-bd03-be4e30e03766	FLUID-WP-0008-T02	never	Authorize one attended BotFather registration of the HelixForge bot, with the credential stored only through the attended OpenBao path?
5	infd-20261005-telegram-channels	review-94a73510-3307-4180-b1d1-1e0607d410fc	FLUID-WP-0008-T03	never	Authorize one attended creation of the private HelixForge test channel and then the public channel?
6	infd-20261005-telegram-user-session	review-0030fd73-2fe6-4443-940c-74af02245ca4	FT-WP-0002-T01	never	Authorize one attended bootstrap of a dedicated Telegram account session for FT-WP-0002, with the account material kept outside git?

Excluded

• KEY-WP-0037-T03 (caafe4be-4f68-47b4-9567-316d47b94992): Custody boundary 632a8893 is approved. The live registration still has no exact reviewed revision, image digest, config preservation test, or synthetic issuance and denial record. Resolving caafe4be would be that live go.
• FT-WP-0001-T07 (8a095daa-35f9-4561-ae50-256558600be7): Ninety-four hall entries have no Telegram-channel agreement. The decision asks which basis to record, including whether a revocable standing agreement belongs in hall-of-helix/ENTRY.md and how earlier contributors are asked. That choice is not yet a single prepared act.
• RAPPS-WP-0014-T03 (d06307e5-2737-461a-a2f4-a12c3b492a9a): The invited two-user workflow is not ready to run. Create login for the invited tenant-admin was refused because that email already belongs to directory login platform-root. No second login was created.
• STATE-WP-0079-T06 (2fd5849c-240e-4d0a-bf07-5ebf8dfce3fd): The same hub decision also covers the single-node risk, the core-hub cutover, clock verification, and live-host authorization. Stopping the primary still waits on STATE-WP-0079-T04 route receipts and the legacy-meter week.
• RPF-WP-0044-T03 (89f1058f-33bc-47a8-8a49-0b44d426c67e): The ArgoCD go-ahead covers issue-core, policy-nexus, activity-core automation, and prune restoration. The policy-nexus Application draft still has unfilled revision and values placeholders. One memo cannot carry those acts.

Queued 2026-10-05

Each source memo is registered, published to net-kingdom-admins, and has a review request. The dispatcher delivered all six envelopes. Intake created the review approvals and addressed them to the platform reviewer. None is accepted, declined, or sealed.

The lifecycle envelope does not carry serves. An answer on the site does not resolve the hub decision. The resolves column is the intended later mapping.

Open a review at https://decisions.coulomb.social/review?memo_id=<review id>. The same questions are in the decision workspace under the source memo id.