Current Version: 1.0.2
Last Updated: May 2026
Repository path: lumina30-incident-review/tools/l30-bas/practical-sheets/L30_FRM_Document_ID_System.html
License: CC0 1.0 Universal (Public Domain)
All Forms Index
Purpose
This document defines the document ID system for LUMINA-30 practical forms, sheets, templates, and checklists.
The purpose is to keep each form consistently referenceable, reviewable, updateable, and usable in incident review, audit, and boundary-evaluation contexts.
What this system is not
The L30-FRM document ID system is not a certification scheme, compliance label, safety approval, legal classification, or replacement for PCR-C or the LUMINA-30 Boundary Kernel.
L30-FRM
It is a document-control system for practical forms only.
Document ID
The stable document ID uses hyphens, not underscores, and does not include a language suffix.
Public filenames use underscores for filesystem and URL compatibility.
Stable document IDs:
L30-FRM-B01 L30-FRM-B02 L30-FRM-I01 L30-FRM-I02 L30-FRM-I03 L30-FRM-A01 L30-FRM-G01 L30-FRM-R01 L30-FRM-S01
Language rule
English files are the canonical templates and do not use a language suffix.
Localized versions should be created by copying the English canonical template and translating only the human-readable text.
Document IDs, L30-BAS codes, field structure, checkbox controls, tables, code placement, and layout should be preserved across localized versions.
Document ID
Localized files use an uppercase language suffix immediately before the file extension.
Japanese files use the _JA language suffix.
The language suffix is not part of the document ID.
The practical form body should show only the document ID and should not show language code as part of the ID.
Examples:
Document ID: L30-FRM-B01 English canonical file: L30_FRM_B01_Boundary_Check.docx Japanese localized file: L30_FRM_B01_Boundary_Check_JA.docx French localized file: L30_FRM_B01_Boundary_Check_FR.docx
Country or regional suffixes should be used only when a regional legal, institutional, or linguistic variant is necessary, such as _EN_US , _EN_GB , _ZH_TW , or _PT_BR .
Japanese localized versions may be provided as reference examples for localization. They are not required for every supporting or detailed form unless the form is intended for Japanese-language practical use.
Filename format
Public filenames do not include version numbers. English files use the default filename. Localized files use an uppercase language suffix before the file extension.
L30_FRM_[Category][Number]_[English_Title].docx L30_FRM_[Category][Number]_[English_Title].pdf L30_FRM_[Category][Number]_[English_Title]_[LANGUAGE].docx L30_FRM_[Category][Number]_[English_Title]_[LANGUAGE].pdf
Public filenames do not include version numbers. Version information is stored inside the document, footer, Git history, releases/tags, and review-candidate ZIP names.
| Component | Meaning |
|---|---|
| L30-FRM-[Category][Number] | Stable document ID shown inside the form |
| L30_FRM_[Category][Number]_[English_Title] | Public filename base using underscores |
| _[LANGUAGE] | Localized language suffix, used only in filenames and not part of the document ID |
Category codes
| Code | Category | Use |
|---|---|---|
| B | Boundary | Boundary judgment, refusal validity, pre-irreversibility checks |
| I | Incident | Incident review, post-incident records, near-miss analysis |
| A | Audit | Audit, governance review, operational readiness checks |
| G | Governance | Approval flow, institutional process, escalation governance |
| R | Responsibility | Responsibility mapping, accountability, role assignment |
| S | Stabilization | Post-incident stabilization, containment, recovery tracking |
A new category should be created only when the form has a clearly different operational purpose.
Current form register
| Document ID | Default English file base | Japanese file base | Primary use |
|---|---|---|---|
| L30-FRM-B01 | L30_FRM_B01_Boundary_Check | L30_FRM_B01_Boundary_Check_JA | Minimum boundary judgment sheet for effective human refusal before irreversibility |
| L30-FRM-B02 | L30_FRM_B02_Operational_Refusal_Preservation_Minimum | — | Minimum operational conditions for preserving reviewable human refusal authority |
| L30-FRM-I01 | L30_FRM_I01_Incident_Review_Template | L30_FRM_I01_Incident_Review_Template_JA | Incident or near-incident review record aligned with the LUMINA-30 Boundary Kernel |
| L30-FRM-I02 | L30_FRM_I02_Incident_Review_Protocol | — | Detailed post-incident review protocol |
| L30-FRM-I03 | L30_FRM_I03_Incident_Review_Protocol_Extended | — | Extended post-incident structural analysis |
| L30-FRM-A01 | L30_FRM_A01_Audit_Checklist | L30_FRM_A01_Audit_Checklist_JA | Audit checklist for pre-critical control readiness and refusal validity |
| L30-FRM-G01 | L30_FRM_G01_Governance_Review_Template | — | Governance review pattern for approval flow and escalation governance |
| L30-FRM-R01 | L30_FRM_R01_Responsibility_Accountability_Review | — | Responsibility and accountability review pattern |
| L30-FRM-S01 | L30_FRM_S01_Stabilization_Checklist | — | Stabilization, containment, and recovery-tracking checklist |
Relationship to Boundary Kernel
These forms do not replace PCR-C or the LUMINA-30 Boundary Kernel.
They operationalize the Boundary Kernel for human review, incident analysis, and audit contexts.
Boundary Kernel
They must not be used as certification marks or as claims that a system is safe.
Versioning rule
A form version changes when its content, checklist structure, judgment criteria, or practical use changes.
English and localized versions of the same form should share the same document ID and version number.
Use v1_0_1 for the first usability correction that moves fixed form dates out of the main metadata table and adds practical review fields.
Assignment rule
New IDs should be assigned conservatively.
Use a new category only when the form has a clearly different operational purpose.
Do not reuse retired IDs for different forms.
Do not assign a form ID to a theoretical paper, README, diagram, slide, or general explanatory document.
⬆ TOP