A reviewed financial report and its release record
The case starts with a recorded signal that a reviewed report changed and links that signal to the decision and release records.
Capability 05 / Incident Reconstruction & Recovery
Reconstruct what happened Recover only what is known
Auxtho reconstructs the report version, sources, rules, reviewer, decision, permitted action, and recorded result. It identifies affected releases, prepares the response record, and verifies receipt readback before treating the result as known.
When a result cannot be verified, Auxtho records UNKNOWN and stops instead of repeating a possibly consequential action.
The job in plain language
A reviewed document changed, or its downstream result became unclear
The response team needs the exact chain that produced the event before it decides what to notify, correct, retry, or close.
Reconstructs and scopes the event
Auxtho reconstructs the report, sources, rules, human decision, permitted action, and result, then identifies exactly which releases were affected.
Notification, remediation, and closure
When the authoritative notification rule is unavailable, the system escalates the gap and an accountable person determines the applicable response and whether the incident can close.
Affected releases, the unresolved rule, and the response record
The screen keeps the affected releases, unresolved notification rule, and reviewed response record visible as separate records.
A reconstruction, confirmed result, or unresolved state
The historical record stays unchanged while recovery stores the confirmation checked and the final result status.
One incident path
From signal to exact affected scope and human closure
01Detect the change
A content-free signal identifies that the exact reviewed report version changed.
02Rebuild the exact chain
Auxtho reconstructs the reviewed artifact, selected claims, source pack, policies, authority, action, and receipt.
03Scope affected releases
Stored links identify the affected release. Filenames, titles, and “latest” labels are not treated as proof.
04Separate facts and decisions
Observed facts, system inferences, unresolved questions, human decisions, and remediation commitments remain distinct.
05Close with a bound package
The response package records the exact incident state, impact inventory, decisions, and remediation evidence.
Actual product screens
Read the reconstruction in bounded steps
These panels are captured from the same local synthetic incident after it reaches closure. Raw timeline payloads and internal mechanics are intentionally excluded.
Recovery example
A receipt readback decides whether the outcome is known
The recovery plan pins the exact release chain and receiver identity. Auxtho accepts the result only when authenticated readback from that pinned receiver verifies it.
Auxtho verifies the pinned receiver and exact signed receipt, then records the confirmed result.
CONFIRMED SUCCESSThe same verified receipt is returned without increasing the effect or dispatch count.
NO NEW EFFECTThe system does not dispatch again. It records the unresolved outcome for a person to reconcile.
UNKNOWN / NO AUTOMATIC RETRYSource note
M123 INCIDENT_RECONSTRUCTION_GO, M124 REPLAY_RECOVERY_GO, and M125 INTEGRATED_PRODUCT_PATH_GO in terminal tree 1cca2c79d92ffba686883dd0ef3a8c4eb08f7c1b. Current revalidation included 115 M121-M125 focused backend tests passed plus the M123 incident and M125 integrated App browser paths. Proof boundary: local, provider-free, synthetic cases and a process-local controlled receiver; no real incident, external notification, customer delivery, production recovery, or cloud RPO/RTO is claimed.