PLANNED OPERATED SERVICE

Client Deployment Control Tower

Aggregate post-implementation responsibility across delivered systems and make returning work visible before it becomes an escalation.

01 · THE SITUATION

“A practice leader owns many delivered systems but cannot see where stale knowledge, unanswered questions, or missing owners are pulling engineers back.”

Practice leaders cannot see which completed engagements still generate stale knowledge, unanswered questions, and ownerless review work.

REPOSITORY → ACTION → ARTIFACT → OUTCOME

Watch the work move.

02 · WHAT IT READS

acme-support-agent/fictional fixture
  • src/
    • agent/orchestrator.py
  • prompts/
    • refund-triage.md
  • tools/
    • refund_api.py
  • evals/
    • probes/refund-routing.yaml
  • config/
    • routing.toml
  • docs/
    • runbook.md
  • outputs/freshness.jsonPer-system knowledge state without raw customer code.
  • outputs/live-answer.jsonUnanswered questions and confirmation work by system.
  • outputs/gaps.jsonNewly uncovered or observation-limited system surfaces.
  • outputs/handover/transition-record.jsonThe role accountable for each open responsibility.

03 · WHAT THE FDE DOES

operated serviceIllustrative planned interaction

Review the deployment portfolio

Planned Fleet Console — illustrative; no live customer systems are connected.

  1. 01Aggregate normalized knowledge and responsibility status across connected systems.
  2. 02Surface growing, stale, or ownerless queues without exposing raw customer code.
  3. 03Drill into the selected acme-support-agent responsibility trail.

04 · WHAT GETS PRODUCED

outputs/fleet.jsonIllustrative fixture

Portfolio governance grid

artifact
outputs/fleet.json
verification
review required

A portfolio view of freshness, open questions, coverage, sensor state, and role-based ownership.

05 · WORK AVOIDED

Leaders can see where completed engagements still consume delivery capacity and assign ownership before escalation.

06 · CREDIBILITY BOUNDARY

What this cannot know or do.

  • The Control Tower shows governance metadata only; it is not observability, production-health monitoring, incident response, ITSM, billing truth, or support.
  • This service is not observability, incident response, ITSM, production support, or application maintenance.

07 · NEXT STEP

See where operation begins.

The commercial model follows responsibility—operate, transfer, or govern—without fabricated pricing.