For client-owned systems after launch
Colony Operations
Keep the launched capability healthy and usable.
Maintain evaluations, training, runbooks, controlled improvements, model and cost review, and recovery readiness inside an explicit support and exit boundary.
Plan Post-Launch SupportWorking chamber
Inspect the engagement.
A bounded post-launch service for system health, evaluations, controlled improvements, model and cost review, training, and recovery readiness.
Fit conditions
- A client-owned system is launched and has a named operational owner.
- The team wants help maintaining evaluations, training, recovery, and controlled improvements.
- Support should accelerate internal capability rather than become the lock that keeps it alive.
What is engineered
- System-health and evaluation review cadence
- Controlled worker, workflow, integration, and context updates
- Model, cost, incident, and recovery review
- Runbook maintenance, office hours, and role-specific training
- Explicit response, capacity, escalation, and exit boundaries
Authority and evidence
Support keeps the capability healthy, not captive.
Who or what decides
- The client retains administrative control and approval of consequential changes.
- Change controls and evaluations determine whether an update can enter production.
- Support access remains scoped, revocable, and documented.
How the work is verified
- Health and evaluation results are recorded against named operating expectations.
- Changes leave reviewable tests, receipts, decisions, and rollback paths.
- Training, runbooks, access, recovery readiness, and open risks remain inspectable.
Ownership schedule
Know what crosses the handoff.
Included
- The agreed health, evaluation, training, maintenance, and recovery cadence
- Controlled improvements within explicit capacity
Excluded
- Unlimited implementation or emergency response
- Hidden provider dependence
- Fractional Architect roadmap and strategy ownership as the primary responsibility
Transferred or client-controlled
- Updated runbooks, evaluations, training materials, health records, and client-specific changes
- A viable operating and exit path at every renewal boundary
Retained by Analytical Ants
- Reusable support methods, generalized tooling, and internal production systems
- Rights explicitly identified before support work begins
Available support
- Renewal through a bounded support schedule
- Separate architecture or delivery work only when independently approved
Relevant proof
Operating evidence shows whether support is working.
Evaluation results, health reviews, controlled-change receipts, maintained runbooks, training records, and recovery checks are the proof category. The service does not rely on invented uptime, savings, or customer outcomes.
Next useful step
Define the operating boundary.
Share the launched system, named owner, current evaluations, support needs, and the exit path your team must preserve.