SILVER
ISP Incident Outcome Report
A clear, defensible view of what happened and what action remains.
MTC-first timeline
Everyone reads the same event order even when local time zones, teams or systems differ.
When did Raven see the signal, when was a decision needed, and when did action happen?
Known / estimated / assumed / unknown separation
The reader can see what is proven and what is not proven without trusting a black box.
Can I trust this report, and what should I not overinterpret?
Human decision owner
The report makes clear that Raven prepares the decision surface; a human remains responsible for action.
Who decided, and did the system execute anything automatically?
Manager and technician notes
Notes captured in the application become part of the final evidence artifact.
Can the team explain what was done without reconstructing it from chat and memory?
Local service context
A regional ISP sees the affected area, service and customer context instead of a generic alarm list.
Is this actually my customer's problem, or only a technical symptom?
Clear next action
The manager sees what must happen next after closure or before export.
What should the team do next?
Not included: financial simulation, audit defense, cross-client comparison
GOLD
ISP Incident Value Report
A value view of the incident: cost, timing, team availability and alternatives.
MTC-first timeline
Everyone reads the same event order even when local time zones, teams or systems differ.
When did Raven see the signal, when was a decision needed, and when did action happen?
Known / estimated / assumed / unknown separation
The reader can see what is proven and what is not proven without trusting a black box.
Can I trust this report, and what should I not overinterpret?
Human decision owner
The report makes clear that Raven prepares the decision surface; a human remains responsible for action.
Who decided, and did the system execute anything automatically?
Manager and technician notes
Notes captured in the application become part of the final evidence artifact.
Can the team explain what was done without reconstructing it from chat and memory?
Local service context
A regional ISP sees the affected area, service and customer context instead of a generic alarm list.
Is this actually my customer's problem, or only a technical symptom?
Clear next action
The manager sees what must happen next after closure or before export.
What should the team do next?
Cost of waiting
The ISP can discuss minutes as money, customer trust and service exposure.
What did waiting probably cost, and what is only an estimate?
Technician timing value
The report shows how ETA, repair estimate and team availability shaped the decision.
Would sending the team earlier have reduced exposure?
Alternative scenario comparison
The manager sees why acting now, waiting or rerouting produced different consequences.
What would likely happen if we chose another operational path?
B2B/SLA/churn context
Where approved, the report connects service quality to penalties, churn risk and reputation.
Could this incident affect retention, penalties or local trust?
Not included: multi-step strategy, guaranteed savings, legal conclusion
PLATINUM
ISP Decision Defense Report
A management-grade incident report that defends the human decision and preserves learning boundaries.
MTC-first timeline
Everyone reads the same event order even when local time zones, teams or systems differ.
When did Raven see the signal, when was a decision needed, and when did action happen?
Known / estimated / assumed / unknown separation
The reader can see what is proven and what is not proven without trusting a black box.
Can I trust this report, and what should I not overinterpret?
Human decision owner
The report makes clear that Raven prepares the decision surface; a human remains responsible for action.
Who decided, and did the system execute anything automatically?
Manager and technician notes
Notes captured in the application become part of the final evidence artifact.
Can the team explain what was done without reconstructing it from chat and memory?
Local service context
A regional ISP sees the affected area, service and customer context instead of a generic alarm list.
Is this actually my customer's problem, or only a technical symptom?
Clear next action
The manager sees what must happen next after closure or before export.
What should the team do next?
Cost of waiting
The ISP can discuss minutes as money, customer trust and service exposure.
What did waiting probably cost, and what is only an estimate?
Technician timing value
The report shows how ETA, repair estimate and team availability shaped the decision.
Would sending the team earlier have reduced exposure?
Alternative scenario comparison
The manager sees why acting now, waiting or rerouting produced different consequences.
What would likely happen if we chose another operational path?
B2B/SLA/churn context
Where approved, the report connects service quality to penalties, churn risk and reputation.
Could this incident affect retention, penalties or local trust?
Decision defense
The manager can later defend why the decision was reasonable at the time it was made.
Can I defend this decision after the incident?
Audit-ready export
The organization receives a board/customer-dispute appendix with an audit trail.
Can this be shown to management, B2B customer or audit without rewriting it?
Stress reduction through defensibility
The report reduces manager and team stress by making the decision evidence explicit.
Will the team feel safer making fast decisions?
Safe learning extract
Raven may improve from approved abstractions without exposing customer identity or raw reports.
Can the system improve without leaking my data?
Boundary: synthetic public-safe values only. No customer data, no operator identity and no MTZ method disclosure. Not included: legal opinion, statutory audit, customer identity disclosure