Skip to content

Operations Workspace

ETIS Project Workspace

Operations Workspace

Operational readiness, scope, runbooks, support, monitoring, rollback, transition, risks.

ES-111 Project Repository Operations

Purpose

Prepare the system to be operated responsibly in the approved environment, with runbooks, support paths, monitoring, rollback, and operational boundaries.

This directory should contain the project’s actual working artifacts for this lifecycle area. The links below intentionally point to the Template Library and, where available, the completed LMU/COICP example. Create the real project files in this directory when the project is ready to populate them.

What belongs here

Artifact Project File Name Template Completed Example
Operational Readiness Overview operational_readiness_overview.md Template Completed example
Operational Scope operational_scope.md Template Completed example
Support Model support_model.md Template Completed example
Incident Response Plan incident_response_plan.md Template Completed example
Monitoring And Observability Plan monitoring_and_observability_plan.md Template Completed example
Rollback And Stop Plan rollback_and_stop_plan.md Template Completed example
User Transition Plan user_transition_plan.md Template Completed example
Operational Risk Register operational_risk_register.md Template Completed example
Operational Readiness Review operational_readiness_review.md Template Completed example
Operational Readiness Summary operational_readiness_summary.md Template Completed example

Start from templates

Working pattern

  1. Open the relevant template.
  2. Create the same-named file in docs/project-workspace/operations/.
  3. Replace template guidance with project-specific evidence.
  4. Compare the result with the LMU/COICP example when available.
  5. Record open risks, assumptions, and unresolved questions.
  6. Finish with the review or readiness artifact for this stage.

Evidence quality bar

Quality What It Means
Specific Names actual project facts, stakeholders, systems, scenarios, risks, and decisions.
Traceable Connects back to earlier stages and forward to later stages.
Reviewable Gives another reviewer enough evidence to challenge or approve the work.
Current Reflects the project’s actual state rather than old intent.
Governable Makes AI use, exceptions, risks, release posture, and limitations visible.
Workspace Rule

Create project artifacts here. Learn the artifact structure from the Template Library. Learn the completed pattern from the LMU/COICP example.

Continue to Deployment

Move forward when this stage has enough project evidence and a clear readiness decision.

Open Deployment →