coulomb/repo-manager
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(handoffs): publish owner task interfaces

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a023c0-a0a3-7c03-b395-5a0d2757214d
This commit is contained in:
tegwick 2026-08-22 14:15:48 +02:00
parent a3952113d5
commit 890f3b05b5
12 changed files with 754 additions and 38 deletions
Download patch file Download diff file Expand all files Collapse all files

77
workplans/RMGR-WP-0010-authoritative-workload-references.md
View file

@ -4,7 +4,7 @@ type: workplan
title: "Authoritative workload declarations and explicit references"
domain: infotech
repo: repo-manager
status: active
status: finished
owner: codex
topic_slug: infotech
created: "2026-08-22"
@ -13,6 +13,7 @@ related:
- ZONE-WP-0001
- RMASTER-ADR-0007
- WARDEN-WP-0032
- RMGR-ADR-005
state_hub_workstream_id: "f1fdfd70-76e0-5133-8365-4e68b9e9ca12"
---
@ -73,70 +74,80 @@ declarations, rejects duplicate deployable ownership, reports missing rapp
declarations, and returns `unknown` rather than guessing. Unit tests cover
positive resolution and fail-closed cases.
## Publish the normalized projection port
## Publish the normalized projection owner interface
```task
id: RMGR-WP-0010-T04
status: wait
status: done
priority: medium
state_hub_task_id: "187fed63-63ab-57b3-92cb-83acf5870977"
```
Expose the v1 index through the Repo Manager observation contract and hub-core
port with source revision, declaration path, and observation timestamp. Do not
expose private persistence models.
Supply hub-core with a directly adoptable task interface for the v1 projection,
including provenance, canonical UTC observation time, rebuild semantics, and
the private-persistence boundary.
**Handoff (2026-08-22):** sent hub-core message
`1ea93859-7cdf-4c8e-86d6-003e93e70eef`; waiting for its owner workplan/task
identifier.
**Result (2026-08-22):**
`interfaces/workload-projection-transport-v1.yaml` is the complete owner-ready
interface. Initial routing message:
`1ea93859-7cdf-4c8e-86d6-003e93e70eef`.
## Add authoritative estate coverage
## Publish the authoritative estate-coverage owner interface
```task
id: RMGR-WP-0010-T05
status: wait
status: done
priority: high
state_hub_task_id: "71a4dae7-8484-57f7-96b9-c2ef93aa4642"
```
Join declarations to an authoritative runtime/deployable observation source and
report running units lacking rapp coverage. Repository names are insufficient
evidence. Separate non-workload operational subjects from undeclared workloads.
Supply Railiance Master with a directly adoptable schema-owner task clarifying
universal managed-deployable coverage, migration debt, and the non-workload
boundary.
**Handoff (2026-08-22):** sent Railiance Master message
`d8e64195-9117-4439-bc67-d2e7696a9bf5` for the normative coverage clarification
and an owner work record. Runtime observation-source selection remains open.
**Result (2026-08-22):** `interfaces/rapp-workload-coverage-v1.yaml` is the
complete owner-ready interface. Initial routing message:
`d8e64195-9117-4439-bc67-d2e7696a9bf5`. Runtime observation-source selection
belongs in the adopting owner work record, not as a duplicate Repo Manager todo.
## Adopt explicit ops-warden references
## Publish the ops-warden reference owner interface
```task
id: RMGR-WP-0010-T06
status: wait
status: done
priority: high
state_hub_task_id: "72aa51a0-2a06-571c-967d-fb18ee96b30f"
```
Ops-warden owns its catalog schema. Add an explicit workload reference and an
unambiguous not-applicable/unknown distinction, then validate every resolved
reference through Repo Manager. Do not copy classification or criticality.
Supply ops-warden with the exact catalog adoption task, including field
semantics, owner boundary, validation, and no-inference acceptance tests.
**Handoff (2026-08-22):** sent ops-warden message
`ca18c1ab-540f-4765-89ba-43c068bb49d2`; waiting for its adoption workplan/task
identifier.
**Result (2026-08-22):**
`interfaces/ops-warden-workload-reference-v1.yaml` is directly adoptable by
`WARDEN-WP-0032`. Initial routing message:
`ca18c1ab-540f-4765-89ba-43c068bb49d2`.
## Prove Zone Engine consumption
## Publish the Zone Engine consumption owner interface
```task
id: RMGR-WP-0010-T07
status: wait
status: done
priority: high
state_hub_task_id: "b68f40b1-cf63-589f-96ee-c6c1098d9802"
```
Zone Engine consumes the declaration projection and explicit catalog references,
reports unknown subjects without inference, and demonstrates that path/repo-name
drift cannot alter membership.
Supply Zone Engine with a directly adoptable join-and-proof task that consumes
the declaration projection and explicit catalog references, reports unknown
subjects, and prohibits path/repository-name inference.
**Handoff (2026-08-22):** replied through Zone Engine message
`a271dc75-b2c9-4c9a-a91c-20aaa1cfb5dc`; waiting for its adoption/proof task
identifier.
**Result (2026-08-22):**
`interfaces/zone-engine-workload-resolution-v1.yaml` is directly adoptable by
`ZONE-WP-0001-T07`, which already links `RMGR-WP-0010-T07`. Initial routing
message: `a271dc75-b2c9-4c9a-a91c-20aaa1cfb5dc`.
## Completion
The Repo Manager boundary is complete. `RMGR-ADR-005` makes interface
publication the producer-side terminal action: approval, amendment, and
implementation live only in each target owner's file-backed work record. No
cross-owner implementation todo remains duplicated in this workplan.