L30-FRM All Forms Index

Current Version: 1.0.2
Last Updated: May 2026
Repository path: lumina30-incident-review/tools/l30-bas/practical-sheets/L30_FRM_All_Forms_Index.html

Document ID System Localization Which Form First Current Forms Category Patterns Supporting Forms Use Order Boundary Relation

Purpose

This document is the public distribution index and management register for LUMINA-30 practical form documents using the L30-FRM document ID system.
L30-FRM

It helps reviewers, auditors, maintainers, and AI assistants identify which form to use, which language version to download, and how each form relates to the LUMINA-30 Boundary Kernel.

Public filenames are stable and do not include version numbers. Version information is kept inside the documents, footers, Git history, and release notes.

What this index is not

This index is not a form, checklist, certification, legal standard, deployment approval, or substitute for PCR-C or the LUMINA-30 Boundary Kernel.

The forms listed here do not certify that a system is safe. They provide structured fields for reviewing whether effective human refusal remained possible before irreversibility.
Each DOCX/PDF form contains review-use fields for Review Date, Reviewer / Organization, and System

Language and localization policy

English practical form 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.

Localized practical form files use an uppercase language suffix immediately before the file extension.

The language suffix is not part of the document ID.

The practical form body should show only the document ID, such as L30-FRM-B01, and should not show a language code as part of the ID.
L30-FRM-B01

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.
_EN_US, _EN_GB, _ZH_TW, _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.

GitHub-facing index and management documents may remain bilingual because they are navigation and maintenance documents.

Primary reference

The forms listed here operationalize the LUMINA-30 Boundary Kernel for human review, incident analysis, and audit contexts.

Primary boundary requirement:
：

Effective human refusal must remain possible before irreversibility.

These forms do not relax, replace, or postpone PCR-C.

Which form should I use first?

Current forms

Supporting / Detailed Forms

The following forms are part of the L30-BAS practical form family, but they are not the first entry point for most users.
Use L30-FRM-B01, L30-FRM-I01, or L30-FRM-A01 first when a minimum practical entry point is needed. Use the supporting forms when more detailed refusal-preservation or incident-review analysis is required.

Category Pattern Forms

The following English forms provide baseline patterns for users who need to create sector-specific or organization-specific L30-BAS forms.
They are maintained L30-FRM reference examples for the G, R, and S categories, but they do not require users to copy their wording exactly.

Recommended use order

Use the forms in this order when possible:

L30-FRM-B01 -> L30-FRM-I01 -> L30-FRM-A01
Category patterns

1. L30-FRM-B01: Boundary Check

Use first when the reviewer needs to determine whether effective human refusal remained possible before irreversibility.

2. L30-FRM-I01: Incident Review Template

Use after an incident, near-incident, or boundary-failure concern to record the timeline, refusal conditions, control conditions, and review findings.

3. L30-FRM-A01: Audit Checklist

Use for governance, deployment, procurement, internal review, or external audit contexts where refusal effectiveness and control conditions must be checked.

Category patterns: G01, R01, S01

Use L30-FRM-G01, L30-FRM-R01, or L30-FRM-S01 when the reviewer needs a baseline English pattern for governance, responsibility, or stabilization use cases.
L30-FRM-G01, L30-FRM-R01, L30-FRM-S01

Document ID system

The full numbering rules are maintained in:

• L30_FRM Document ID System

Current filename format:

L30_FRM_[Category][Number]_[English_Title].docx
L30_FRM_[Category][Number]_[English_Title]_JA.docx

Examples:
：

L30_FRM_B01_Boundary_Check.pdf
L30_FRM_B01_Boundary_Check_JA.pdf

Relationship to Boundary Kernel

The L30-FRM practical forms translate the LUMINA-30 Boundary Kernel into human-readable review fields.

They are not the Boundary Kernel itself.

They should be interpreted under the following constraints:

• non-identical anchors are not a substitute for PCR-C;

• boundary failure is not acceptable, recoverable, or a normal operating condition;

• apparent consent, cooperation, silence, or refusal is not valid under LUMINA-30 if produced by AI-mediated control;

• formal compliance, partial compliance, or proxy compliance does not replace effective human refusal before irreversibility.

Version and revision rules

• Initial public form releases normally start at v1_0.

• The current public form version is 1.0.1 because the first usability correction removed fixed form dates from the main metadata table and added practical review fields.

• Minor wording or scope clarifications may use patch versions such as v1_0_1.

• Structural changes to fields, checkboxes, or review logic should use v1_1, v1_2, and later versions.

• Do not reuse a document ID for a different form type.

• Do not change a form category code unless the old ID is deprecated and mapped to the new ID.

Short references

The following short references may be used in review comments, issues, handoff notes, and audit discussions.

⬆ TOP