aoa-session-self-diagnose

It is a bounded summary that classifies drift, friction, and ownership confusion from reviewed session artifacts into symptom and probable cause categories while preserving unknowns. The packet relies on explicit citation of repository evidence refs to maintain read-only integrity.

Analyze session drift by classifying drift types, symptoms, and probable causes from the reviewed transcript into a bounded diagnosis packet with owner-layer hints. Emit bounded receipts that follow stats-event-envelope rules to preserve unknowns without silent repair.

No, this diagnosis process applies strictly to reviewed non-live session artifacts, harvest packets, and postmortems. It requires read-only access to repository evidence and references, ensuring diagnosis is completed before any repair or automation attempt.

Yes, tracing proof gaps requires read-only access to repository evidence and references. The diagnosis process demands explicit citation of evidence refs to validate owner-layer hints and generate bounded receipts without mutating the system.

The best way to separate symptoms from probable causes is to convert reviewed session evidence into a bounded diagnosis packet. This approach classifies drift and friction while explicitly preserving unknowns before attempting any automation.

Session reviews fail to produce automation readiness when blurred ownership and repeated friction block honest repair. Converting reviewed evidence into a bounded diagnosis packet with explicit evidence refs separates symptoms from causes and clarifies owner-layer hints.