---
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: todo
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.

## Add authoritative estate coverage

```task
id: RMGR-WP-0010-T05
status: todo
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.

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

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