Service inventory
Named components, owners, versions, dependencies, data classes and approved purposes.
Operations & support
Production begins when ownership becomes routine.
A private model is not an operating model. The service boundary must name who watches, approves, restores, communicates and decides—under ordinary conditions and failure.
Six operating practices
Change control
Versioned changes, regression evidence, approver, maintenance path, rollback and decision receipt.
Incident handling
Classification, containment, evidence preservation, escalation, communication and learning.
Backup and restore
Named objects, owners, copies, restore sequence, index rebuild, test record and exceptions.
Evidence review
Access, model, retrieval, refusal, security and change records reviewed at an agreed cadence.
Exit readiness
Export, handover, deletion or return, key transition, dependency removal and acceptance.
Support is contracted, not implied
| Question | Written answer required |
|---|---|
| Coverage | service hours, channels, language, geography and exclusions |
| Priority | impact definition, client obligations and escalation route |
| Target | response or restoration objective and measurement method |
| Dependency | client, hosting, hardware, software and upstream responsibilities |
| Evidence | tickets, timeline, decisions, changes and closure record |
Current public boundary: ANULUM does not advertise 24/7 coverage, guaranteed availability, response times, RTO or RPO. Any such commitment requires a service-specific assessment and signed terms.
Continuity
Recovery is a demonstrated sequence.
“Backed up” says little about whether a usable system can return. The recovery record identifies exact data, indexes, configurations, models, keys and dependencies; the restore test records elapsed time, loss window, failures and owner acceptance.