repo-manager/interfaces/ops-warden-workload-reference-v1.yaml
tegwick 890f3b05b5 feat(handoffs): publish owner task interfaces
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a023c0-a0a3-7c03-b395-5a0d2757214d
2026-08-22 14:15:48 +02:00

49 lines
2 KiB
YAML

apiVersion: helixforge.repo-manager/v1
kind: OwnerTaskInterface
metadata:
id: helixforge.workloads.ops-warden-reference.v1
title: Add explicit workload references to ops-warden lanes
source:
repo: repo-manager
workplan_task: RMGR-WP-0010-T06
target:
repo: ops-warden
owner_agent: ops-warden
suggested_work_record: WARDEN-WP-0032
approval:
dispositions: [approved, amended, rejected]
record_in: WARDEN-WP-0032 task or an ops-warden owner decision
task:
title: Adopt explicit workload references in the lane catalog
priority: high
objective: >-
Let workload-applicable lanes point to authoritative rapp workload identity
while keeping the catalog a pointer layer.
inputs:
- ref: repo-manager/docs/workload-reference-contract_v1.md
authority: repo-manager
- ref: ops-warden/registry/routing/catalog.yaml
authority: ops-warden
deliverables:
- >-
Add workload_ref with required rapp_id and name and optional deployable to
every workload-applicable lane.
- >-
Add an explicit applicability representation that distinguishes
not-applicable from an unresolved or invalid workload reference.
- Validate every supplied reference through Repo Manager exact resolution.
- Preserve native typed identity for lanes that do not represent workloads.
constraints:
- Do not copy workload classification, criticality, readiness, or placement into the catalog.
- Do not infer workload identity from path_template, owner_repo, or repository names.
- An absent pointer must not ambiguously mean both unknown and not-applicable.
acceptance:
- Every workload-applicable lane resolves exactly or reports unknown with a reason.
- Every non-workload lane is explicitly not-applicable.
- Catalog validation fails on malformed, ambiguous, or undeclared references.
- Existing lane identity and routing authority remain owned by ops-warden.
verification:
- make test
- make lint
- >-
uv run --project /home/worsch/repo-manager rmgr workload index --root /home/worsch