repo-manager/workplans/RMGR-WP-0010-authoritative-workload-references.md
tegwick 72bcb62ff9 docs(workloads): record adoption handoffs
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a023c0-a0a3-7c03-b395-5a0d2757214d
2026-08-22 14:04:43 +02:00

134 lines
3.8 KiB
Markdown

---
id: RMGR-WP-0010
type: workplan
title: "Authoritative workload declarations and explicit references"
domain: infotech
repo: repo-manager
status: active
owner: codex
topic_slug: infotech
created: "2026-08-22"
updated: "2026-08-22"
related:
- ZONE-WP-0001
- RMASTER-ADR-0007
- WARDEN-WP-0032
---
# Authoritative workload declarations and explicit references
## Goal
Make authoritative workload identities resolvable across repository boundaries
without inventing them from paths or repository names, while preserving
Railiance Master schema ownership and consumer-catalog boundaries.
## Record the authority ruling
```task
id: RMGR-WP-0010-T01
status: done
priority: high
```
Record the authoritative declaration surface, owner split, non-workload
boundary, and resolved/unknown/not-applicable semantics.
**Result (2026-08-22):** accepted as `RMGR-ADR-004`. Railiance Master owns the
normative vocabulary; rapp repositories own their declarations; Repo Manager
owns integration and resolution; consumers own explicit references.
## Publish the workload-reference contract
```task
id: RMGR-WP-0010-T02
status: done
priority: high
```
Define a stable reference that can be carried by pointer catalogs without
copying workload metadata or depending on a storage schema.
**Result (2026-08-22):** `docs/workload-reference-contract_v1.{md,yaml}` defines
the `(rapp_id, workload_identity.name)` key, optional deployable, forbidden
fallbacks, and three resolution outcomes.
## Implement read-only indexing and resolution
```task
id: RMGR-WP-0010-T03
status: done
priority: high
```
Index all checked-out rapp declarations, detect missing/duplicate authority,
and resolve exact references without inference.
**Result (2026-08-22):** `rmgr workload index|resolve` indexes the nine current
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
```task
id: RMGR-WP-0010-T04
status: wait
priority: medium
```
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.
**Handoff (2026-08-22):** sent hub-core message
`1ea93859-7cdf-4c8e-86d6-003e93e70eef`; waiting for its owner workplan/task
identifier.
## Add authoritative estate coverage
```task
id: RMGR-WP-0010-T05
status: wait
priority: high
```
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.
**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.
## Adopt explicit ops-warden references
```task
id: RMGR-WP-0010-T06
status: wait
priority: high
```
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.
**Handoff (2026-08-22):** sent ops-warden message
`ca18c1ab-540f-4765-89ba-43c068bb49d2`; waiting for its adoption workplan/task
identifier.
## Prove Zone Engine consumption
```task
id: RMGR-WP-0010-T07
status: wait
priority: high
```
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.
**Handoff (2026-08-22):** replied through Zone Engine message
`a271dc75-b2c9-4c9a-a91c-20aaa1cfb5dc`; waiting for its adoption/proof task
identifier.