PLANNED OPERATED SERVICE

Live Adoption Assistant

Answer current questions with evidence and route unknown or stale ones so each correction becomes reusable knowledge.

01 · THE SITUATION

“Three weeks after go-live, a client asks a familiar project question in its approved work channel and the original FDE is about to be pulled back.”

Post-go-live questions repeatedly return to the original implementation team because no current, owned answer path exists.

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
  • events/question-208.jsonA real adoption question entering through an approved work channel.
  • outputs/answers.json + outputs/decisions.jsonEvidence available for a grounded response.
  • outputs/freshness.json + outputs/coverage-boundary.mdThe gates that decide whether an answer is safe to serve.
  • outputs/handover/transition-record.jsonThe role responsible when current evidence cannot answer.

03 · WHAT THE FDE DOES

operated serviceIllustrative planned interaction

Answer with evidence or route to the owner

Planned operated service — illustrative; not production support or ITSM.

  1. 01Check the question against current evidence and freshness state.
  2. 02Answer known current questions with citations.
  3. 03Route unknown or stale questions with a draft and preserve the approved correction for reuse.

04 · WHAT GETS PRODUCED

outputs/live-answer.jsonIllustrative fixture

Answer, provenance, and escalation record

artifact
outputs/live-answer.json
verification
review required

A channel-ready result that either cites current evidence or records the owner routing and pending correction.

05 · WORK AVOIDED

A difficult question is answered once and the confirmed result becomes reusable instead of repeatedly reaching you.

06 · CREDIBILITY BOUNDARY

What this cannot know or do.

  • The assistant supports adoption knowledge only; it does not triage incidents, observe production, operate ITSM, or provide application 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.