---
id: RMGR-WP-0010
type: workplan
title: "Authoritative workload declarations and explicit references"
domain: infotech
repo: repo-manager
status: finished
owner: codex
topic_slug: infotech
created: "2026-08-22"
updated: "2026-08-22"
related:
  - ZONE-WP-0001
  - RMASTER-ADR-0007
  - WARDEN-WP-0032
  - RMGR-ADR-005
state_hub_workstream_id: "f1fdfd70-76e0-5133-8365-4e68b9e9ca12"
---

# 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
state_hub_task_id: "4e3d09ea-12ba-540d-bbd4-25cf9535adb3"
```

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
state_hub_task_id: "59bb09f9-e9ed-5f20-8021-6bc8a64858e6"
```

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
state_hub_task_id: "c528c135-2ca5-5d12-891d-d5935230a648"
```

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 owner interface

```task
id: RMGR-WP-0010-T04
status: done
priority: medium
state_hub_task_id: "187fed63-63ab-57b3-92cb-83acf5870977"
```

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.

**Result (2026-08-22):**
`interfaces/workload-projection-transport-v1.yaml` is the complete owner-ready
interface. Initial routing message:
`1ea93859-7cdf-4c8e-86d6-003e93e70eef`.

## Publish the authoritative estate-coverage owner interface

```task
id: RMGR-WP-0010-T05
status: done
priority: high
state_hub_task_id: "71a4dae7-8484-57f7-96b9-c2ef93aa4642"
```

Supply Railiance Master with a directly adoptable schema-owner task clarifying
universal managed-deployable coverage, migration debt, and the non-workload
boundary.

**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.

## Publish the ops-warden reference owner interface

```task
id: RMGR-WP-0010-T06
status: done
priority: high
state_hub_task_id: "72aa51a0-2a06-571c-967d-fb18ee96b30f"
```

Supply ops-warden with the exact catalog adoption task, including field
semantics, owner boundary, validation, and no-inference acceptance tests.

**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`.

## Publish the Zone Engine consumption owner interface

```task
id: RMGR-WP-0010-T07
status: done
priority: high
state_hub_task_id: "b68f40b1-cf63-589f-96ee-c6c1098d9802"
```

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.

**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.