-
Notifications
You must be signed in to change notification settings - Fork 1
Bind immutable model lifecycle sources at startup #257
Copy link
Copy link
Closed
Labels
area:operator-consoleread-only console + narrator (Bragi)read-only console + narrator (Bragi)area:rule-catalogcatalog-as-code: collection, governance, discovery loopcatalog-as-code: collection, governance, discovery loopcompletedAll exit criteria are satisfied; no residual work remains.All exit criteria are satisfied; no residual work remains.priority:p1Next: planned for the current or next iterationNext: planned for the current or next iterationshadow-modeshadow -> enforce promotion / shadow validationshadow -> enforce promotion / shadow validationtype:taskImplementation unit that supports a story or stands aloneImplementation unit that supports a story or stands alone
Description
Activity
Metadata
Metadata
Assignees
Labels
area:operator-consoleread-only console + narrator (Bragi)read-only console + narrator (Bragi)area:rule-catalogcatalog-as-code: collection, governance, discovery loopcatalog-as-code: collection, governance, discovery loopcompletedAll exit criteria are satisfied; no residual work remains.All exit criteria are satisfied; no residual work remains.priority:p1Next: planned for the current or next iterationNext: planned for the current or next iterationshadow-modeshadow -> enforce promotion / shadow validationshadow -> enforce promotion / shadow validationtype:taskImplementation unit that supports a story or stands aloneImplementation unit that supports a story or stands alone
Projects
- StatusShow more project fieldsDone
Problem
Model lifecycle reconciliation can produce proposal-only evidence and deterministic expired-unmerged review decisions, and the Operator service has a bounded asynchronous Key Vault source adapter. The active startup path still consumes file or inline JSON without one shared immutable source revision, so lifecycle holds cannot yet prove parity with the model mapping bound by Core and Operator.
Scope
Complete the authority-free model lifecycle source and review path. This issue does not authorize model mapping changes, PR merge, provider activation, or managed-resource execution.
Exit criteria
Validation
Focused unit, integration, Ruff, strict mypy, roadmap, localization, punctuation, and link checks must pass for the exact committed paths. Governed Azure or GitHub runtime evidence must target a pushed SHA.