EM-TEC-10 · Subject model · W2
Operational change and on-call duty
Change request, approval decision, window, execution, rollback and on-call schedule. Person assignment and release are delegated to their own models.
Partially published; research continues
Claude: complete-frozen-study; Grok: prompt-ready-awaiting-action-time-confirmation.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- OperationalChange
- ChangeWindow
- ChangeExecution
- RollbackPlan
- DutyRoster
- EscalationRule
Deep research questions
- When does a release not require an immediate change?
- How to reconcile windows across time zones?
- How to verify on-call duty when an assignment changes?
Verifiable invariants
- A window is not a permission by itself
- Execution references an approved revision
- On-call duty does not extend IAM automatically
End-to-end acceptance scenario
A change with two windows, a failed rollout and an on-call handover preserves authorization and rollback evidence.
Negative case
A person on the on-call schedule receives all administrative rights.
Approaches to compare
- AISMM/WM-SFT and ArchiMate: product, system and architecture
- CSDM: business application, service and runtime instance
- SPDX/OpenTelemetry/Google SRE: delivery, observation and reliability; choose by boundary
Candidates in the live catalogue
The boundary and the reuse / extension / new model route are not chosen yet.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.