fix-consistency C-06 wrote state_hub_workstream_id and the two state_hub_task_ids back into the workplan file and regenerated WORK-RECORDS.md. Committing the writeback so the file and hub agree. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HHwvAEQfmzLHtrFGhXtVjq Assistant: claude-code Assistant-Model: opus Assistant-Process: 823014@bnt-lap001 Assistant-Session: 2a0786b1-efea-4c38-959b-6e86a493f259
4.2 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated | depends_on | unblocks | origin | origin_ref | state_hub_workstream_id | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TEN-WP-0012 | workplan | Track the two external dispositions tenant-engine is waiting on | infotech | tenant-engine | blocked | claude | netkingdom | 2026-09-07 | 2026-09-07 |
|
residual | TEN-WP-0011 | cb7387d0-431d-56a2-bb7b-86a024aeeefb |
TEN-WP-0012 — Track the two external dispositions tenant-engine is waiting on
TEN-WP-0011 closed correctly. Its T04 and T06 are done in the sense that
matters here: this repository built everything it owns. What neither task
could close is the other side — a credential audit-core issues, and a canon
edit only net-kingdom may make.
Those two waits have no durable local record. The intakes were filed
outbound, on other repositories' intake files, so nothing in this checkout
holds them. SCOPE.md mentions both in prose, but prose is not scanned.
The cost is small and repeating: session protocol Step 3 scans workplans/
for open work, finds none, and each session re-derives the same two
externally-owned gaps from SCOPE.md and the audit-core source before
concluding — correctly — that there is nothing to do. This workplan holds
that conclusion so it is read rather than rediscovered.
Why this is a workplan and not an intake
This repository's intake files record work it may act on. Both records
here are the opposite: work filed elsewhere, awaiting someone else's
disposition. Only workplans/ is read at session start, and wait is the
convention's status for work that is blocked on another party.
Non-goals
- Not editing
net-kingdomcanon from this repository.TEN-WP-0011-T06settled that: file an intake, never fork the contract. - Not requesting a credential over the message bus. Credential routing is
explicit that
POST /messages/asking for a token is an anti-pattern; sender registration is audit-core's to issue. - Not re-opening
TEN-WP-0011. Our side of both items shipped. - No code change is expected from this workplan. If either disposition arrives and does require code, that becomes its own workplan.
T01 — audit-core sender registration (AUDIT-IN-0002)
id: TEN-WP-0012-T01
status: wait
priority: medium
state_hub_task_id: "7898c1aa-b5de-54cf-87b7-67b727b5d0b2"
The emission path shipped in TEN-WP-0011-T04: the local outbox is inside
the mutation transaction, the drain POSTs /v1/events and never fails a
mutation, and the trade is declared in docs/evidence-emission.md. What is
missing is sender registration — a credential audit-core issues and holds
custody of. src/tenant_engine/audit_core.py documents that this module
holds no audit-core credential beyond that sender token.
Waiting on: AUDIT-IN-0002, filed on audit-core.
Done when: audit-core registers the sender and production mutations land
externally, or audit-core declines and SCOPE.md row
"Independent audit-core emission" is restated to say so.
Do not: request the token by message, or synthesize a local stand-in that would make the outbox look drained when it is not.
T02 — boundary-contract amendment (NET-IN-0002)
id: TEN-WP-0012-T02
status: wait
priority: low
state_hub_task_id: "f7d27d7c-f599-5d0e-b60b-9c3ad2b27b87"
net-kingdom/canon/standards/tenant-engine-boundary-contract_v0.1.md still
calls guardrail/quota policy "reserved, not implemented" and this repository
"not a policy enforcement point". Guardrails shipped in TEN-WP-0006/0007,
and the write path is PEP-shaped without this repository being a PDP, so
both sentences now mislead a reader who trusts the contract over the code.
Waiting on: NET-IN-0002, filed on net-kingdom by TEN-WP-0011-T06.
Done when: the contract is amended at its next cut, or net-kingdom
declines and the standing divergence is recorded here rather than left as
a live contradiction between contract and code.
Closing this workplan
Close when both tasks reach a disposition, whichever way each falls. If
either stays open long enough to stop being worth re-reading, cancel the
task and say in SCOPE.md that the gap is permanent — an accepted,
documented divergence beats an indefinite wait.