First-time incident reviewer
Understand the repository role before using templates or boundary checks.
Open START_HEREEntry for boundary checks, incident review, evidence preservation, and post-incident stabilization.
Understand the repository role before using templates or boundary checks.
Open START_HEREUse the minimum working route for an AI-related incident, near miss, or boundary concern.
Open First 3 FilesUse a controlled reading path when the repository feels too large.
Open Reading OrderApply the boundary question to AI incidents, oversight failure, and post-incident review.
Open Incident Review GuideSeparate public facts, authority paths, evidence gaps, and unresolved conclusions before using a public case as a governance example.
Open Mapping GuideReview capability exposure, access control, automation, and refusal capacity before irreversible execution pathways become available.
Open Pre-Incident Review NoteCheck who decides, when irreversibility is judged, and what evidence is required.
Open CriteriaIf evidence is absent or unverifiable, do not infer effective refusal existed.
Open Absence Rule CheckClassify the review result after checking irreversibility, evidence, and refusal authority.
Open ClassificationUse downloadable or editable forms when the review needs a structured record.
Open Forms IndexUse this for post-incident stabilization, containment, evidence preservation, and recovery tracking.
Open Stabilization ChecklistConnect LUMINA-30 to governance, standards, incident-response, and oversight contexts without claiming endorsement.
Open External Use RoutesThe Markdown files are retained for text preservation, search discoverability, existing links, source review, and comparison. For reading and navigation, prefer the HTML pages.