Customer and permission
[Approved customer description/name], [confidentiality review], [written publication approval date and scope].
Publication-gated template
Event AI result-led case record.
Publish only after delivery, measurement, confidentiality review and written customer approval. Keep corrections and residual limits visible.
Baseline
[Operating result], [current path], [measure and denominator], [measurement period], [known limitations].
System boundary
[Sources, users, actions, approval boundaries, integrations, exclusions, fallback and service scope].
Intervention
[What Event Compsia designed, built, accepted, launched and operated; customer responsibilities and timeline.]
Accepted output
[Acceptance cases, go-live criteria, accepted release and named approver.]
Customer correction
[Material corrections, rejected output, fallback cases and changes made—do not omit adverse evidence.]
Final result
[Observed measure with baseline, denominator, period and method; distinguish correlation from attributed effect.]
Operational metrics
[Use, adoption, quality, cost, incidents, support and change metrics.]
Residual limits
[Unsupported cases, dependencies, ongoing human authority, open risks and next review.]