============================================================ AGLA_LIBER_CLASS_LAW Ars Generalis Applied — Dataset Authority Class Law Version: 0.1.0-LIBER-CLASS-LAW Status: DRAFT — ROOT CLASS LAW CANDIDATE Authority: LOCAL / AGLA_P&D_LAB Class: AGLA / ROOT CLASS LAW / LIBER Scope: • define LIBER as root class for AGLA-admitted datasets • distinguish LIBER from SOURCE, OPERA, ROTA, TENET, AREPO, SATOR, SYSTEM_INDEX, and execution artifacts • define LIBER species and admissibility modes • define LIBER ARS, LIBER ARS NATIVUS, LIBER EX, LIBER EX X, LIBER EX OPERA, and LIBER EX OPERAE • define EX LIBER module behavior • define ROTA EX LIBER as temporary ROTA overlay • define object-mode and informant-mode use • define LIBER ARS minimal and complete coverage thresholds • prevent unresolved recursion between root classes Mutation Policy: VERSION-CONTROLLED ONLY ============================================================ ============================================================ I. ROOT PURPOSE ============================================================ LIBER is the AGLA root class for named datasets allowed to inform, support, preserve, or become the object of AGLA operations. A dataset may be called LIBER when: 1. it is explicitly named as LIBER; 2. it has a declared scope; 3. it has a traceable origin or internal generation status; 4. it is admitted into AGLA discourse as structured data; 5. it may be used as object of analysis; 6. it may inform execution only if it belongs to an admitted informant species. LIBER is not merely a source. LIBER is not automatically an OPERA. LIBER is not automatically canonical. LIBER is the namespace for datasets that may be handled by AGLA without confusing dataset, source, operation, and artifact law. ============================================================ II. ROOT DEFINITION ============================================================ LIBER := a named AGLA-admitted dataset with declared scope and traceable status capable of being analyzed by OPERA and, when qualified, capable of informing OPERA execution. Compact formula: LIBER = named admitted dataset. Expanded formula: LIBER = dataset + name + scope + trace + allowed use + prohibited use + admissibility status. ============================================================ III. NON-IDENTITY LAWS ============================================================ LIBER must not be collapsed into adjacent classes. The following distinctions are mandatory: LIBER ≠ SOURCE LIBER ≠ OPERA LIBER ≠ ROTA LIBER ≠ ROTAS LIBER ≠ TENET LIBER ≠ AREPO LIBER ≠ SATOR LIBER ≠ SYSTEM_INDEX LIBER ≠ EXECUTION LIBER ≠ CANON BY DEFAULT Interpretation: SOURCE supplies raw or semi-raw material. LIBER stores admitted dataset content. TENET defines doctrine. AREPO gates admissibility. OPERA executes procedure. ROTAS defines the structural class; ROTA instances carry structural traversal and display. SATOR mediates user-facing execution and reporting. SYSTEM_INDEX registers binding and routing status. LIBER may support these classes but does not replace them. ============================================================ IV. ROOT CLASS PARALLELISM ============================================================ LIBER is a root class. AREPO is also a root class. Therefore: AREPO LIBER is prohibited as a root artifact name. Reason: It risks creating unresolved recursion by implying that LIBER is subordinate to AREPO as if LIBER were merely an object internal to AREPO. Correct pattern: AREPO EX LIBER Interpretation: AREPO EX LIBER is not “the AREPO of LIBER as root class.” AREPO EX LIBER is the admissibility module governing LIBER-modulated execution. Root classes remain parallel: TENET AREPO OPERA ROTAS as class governance for ROTA overlays SATOR LIBER EX LIBER is a module, not a root class. ============================================================ V. LIBER CLASS POSITION ============================================================ LIBER sits between SOURCE and executable AGLA artifacts. In repository structure, canonical or promoted LIBER artifacts should live in: 90_STACK_LIBER The older DATA lane name is not canonical for admitted LIBER artifacts. Artifacts moved from DATA into 90_STACK_LIBER must update their declared class, authority lane, and index identifiers to LIBER language while preserving source provenance. Canonical flow: SOURCE ↓ parsing / extraction / consolidation LIBER ↓ admissive use TENET / AREPO / OPERA / ROTAS / SATOR / APPLICATIO / MACHINA Therefore: SOURCE may feed LIBER. LIBER may feed artifacts. OPERA may generate LIBER. LIBER may preserve OPERA results. LIBER may provide temporary ROTA slot fillings. LIBER may not execute by itself. ============================================================ VI. NAMING LAW ============================================================ A dataset becomes LIBER only by explicit naming. Valid patterns: LIBER LIBER AGLA LIBER ARS LIBER ARS NATIVUS LIBER EX LIBER EX OPERA LIBER EX OPERAE Examples: LIBER TAROT AGLA LIBER ASTROLOGIAE AGLA LIBER RUNARUM TAROT AGLA LIBER APPLICATIO_S_EM LIBER ARS TAROT LIBER ARS NATIVUS EVACUATIO FIGURAE TERTIAE LIBER EX OPERA Q — COMPUTATIO LIBER EX OPERAE RADIX — ALEPH Invalid by default: notes source summary PDF chat output index dataset Such material may become LIBER only by explicit naming or promotion. ============================================================ VII. PRIMARY SPECIES ============================================================ LIBER has the following primary species: 1. LIBER 2. LIBER ARS 3. LIBER ARS NATIVUS 4. LIBER EX 4.1 LIBER EX X 4.2 LIBER EX OPERA 4.3 LIBER EX OPERAE Taxonomic diagram: LIBER ├── LIBER ARS │ └── LIBER ARS NATIVUS └── LIBER EX ├── LIBER EX X ├── LIBER EX OPERA │ ├── LIBER EX OPERA Q │ ├── LIBER EX OPERA A │ ├── LIBER EX OPERA T │ ├── LIBER EX OPERA S │ ├── LIBER EX OPERA F │ ├── LIBER EX OPERA G │ ├── LIBER EX OPERA H │ └── etc. └── LIBER EX OPERAE ============================================================ VIII. GENERAL LIBER ============================================================ LIBER := any explicitly named AGLA-admitted dataset. A general LIBER may be: • exploratory • provisional • consolidated • domain-specific • source-derived • doctrine-dominant • game-facing • comparative • pre-stack • pre-formalization • partially AGLA-reduced A general LIBER may contain: • extracted data • consolidated premises • doctrine-like summaries • operator mappings • tables • matrices • source reductions • OPERA outputs • comparative datasets • symbolic carrier sets • domain-specific material • historical traces • unresolved but marked contradictions By default: LIBER may be OPERA object. LIBER may not be OPERA informant unless qualified. ============================================================ IX. LIBER ARS ============================================================ LIBER ARS := a LIBER whose contents have been minimally reduced into AGLA-operational form by verified coverage of OPERA A, OPERA Q, OPERA T, and OPERA S. LIBER ARS is stronger than ordinary LIBER. It is not merely a source summary. It is an AGLA-addressable dataset. Minimum formula: LIBER ARS_MIN = A + Q + T + S Meaning: A gives contracted principles. Q gives interrogative fields. T gives relations. S gives subjects / substrates. A LIBER may be called LIBER ARS only if it contains minimal pre-processed coverage of: • OPERA A • OPERA Q • OPERA T • OPERA S ------------------------------------------------------------ IX.1 OPERA A COVERAGE ------------------------------------------------------------ Required: • A dignity set • contracted meanings for B–K or declared equivalent scope • domain-specific A-values • statement of contraction from canonical A principles Example structure: AB_canonical: Bonitas AB_LIBER_X: domain-specific contracted Bonitas generated, stabilized, or verified through OPERA A. ------------------------------------------------------------ IX.2 OPERA Q COVERAGE ------------------------------------------------------------ Required: • Q questions relevant to the domain • question modes or species • admissible formulations • prior answers or question-fields where available • uncertainty markers where unresolved Purpose: OPERA Q EX LIBER should transcribe, verify, and complete existing Q material rather than restart from zero. ------------------------------------------------------------ IX.3 OPERA T COVERAGE ------------------------------------------------------------ Required: • T relations among contracted A dignities • relevant T cameras or relation matrices • declared relation types: - difference - concordance - contrariety - beginning - middle - end - majority - equality - minority • domain-specific interpretation of those relations Purpose: OPERA G, OPERA F, and OPERA H may use already-processed relational data instead of recomputing every relation. ------------------------------------------------------------ IX.4 OPERA S COVERAGE ------------------------------------------------------------ Required: • domain subjects • S/K substrate positions • admissible object classes • subject-carrier mapping • scope of application Purpose: combinatory operations can identify what kinds of things are being operated on, not merely what principles are present. ============================================================ X. COMPLETE LIBER ARS ============================================================ A LIBER ARS becomes complete when, beyond minimal A/Q/T/S coverage, it also includes: • evacuated 36 chambers • listed TABULA Complete formula: LIBER ARS_COMPLETE = A + Q + T + S + CAMERA_36_EVACUATIO + TABULA Interpretation: A/Q/T/S gives the minimal operator substrate. The evacuated 36 chambers provide already-articulated pairwise combinatory content. TABULA provides the listed combinatory traversal or reference structure needed for systematic recomposition. Status levels: ORDINARY LIBER PARTIAL LIBER ARS LIBER ARS CANDIDATE LIBER ARS_MIN COMPLETE LIBER ARS_COMPLETE ============================================================ XI. PARTIAL LIBER ARS ============================================================ A LIBER may be partially reducible to LIBER ARS without being formally promoted. Definitions: ------------------------------------------------------------ ORDINARY LIBER WITH ARS-COMPATIBLE SECTIONS ------------------------------------------------------------ A LIBER containing some AGLA-reduced sections but not written or verified under LIBER ARS law. ------------------------------------------------------------ PARTIAL LIBER ARS ------------------------------------------------------------ A LIBER containing some but not all A/Q/T/S coverage. ------------------------------------------------------------ LIBER ARS CANDIDATE ------------------------------------------------------------ A LIBER that appears to contain enough material for promotion but has not passed formal verification. ------------------------------------------------------------ LIBER ARS_MIN COMPLETE ------------------------------------------------------------ A LIBER with verified A/Q/T/S coverage. ------------------------------------------------------------ LIBER ARS_COMPLETE ------------------------------------------------------------ A LIBER with verified A/Q/T/S coverage, evacuated 36 chambers, and listed TABULA. ============================================================ XII. LIBER ARS NATIVUS ============================================================ LIBER ARS NATIVUS := a LIBER ARS whose contents are native to AGLA operation and consist of preprocessed operator-compatible data required or useful for executing one or more OPERAE, but unsuitable for inclusion inside TENET, ROTAS, OPERA, AREPO, or SATOR artifacts. Formula: LIBER ARS NATIVUS = native AGLA data + operator-compatible preprocessing + non-executable dataset status + consumability by registered OPERAE ------------------------------------------------------------ XII.1 PURPOSE ------------------------------------------------------------ Some datasets are not external extractions. They are native to AGLA. However, placing them directly inside TENET, ROTAS, OPERA, AREPO, or SATOR would clutter those artifacts and violate class separation. LIBER ARS NATIVUS stores native operative data. It does not define: • doctrine • execution procedure • admissibility law • mediation law • canonical ROTA structure ------------------------------------------------------------ XII.2 EXAMPLE ------------------------------------------------------------ A complete preprocessed Evacuatio dataset for Figura Tertia may belong to: LIBER ARS NATIVUS EVACUATIO FIGURAE TERTIAE because it contains: • 36/36 camerae • 12 statements per camera • deterministic chamber closure • complete Figura Tertia evacuation • ROTA-consistent T-pair assignment This data is useful for OPERA G. But it is not: • TENET G • ROTA G • OPERA G • AREPO G • SATOR G ------------------------------------------------------------ XII.3 NON-EXECUTION LAW ------------------------------------------------------------ LIBER ARS NATIVUS is non-executable. It may be consumed by OPERA. It may inform OPERA execution. It may fill ROTA EX LIBER slots. But it may not execute. Formula: LIBER ARS NATIVUS ≠ OPERA LIBER ARS NATIVUS → consumable by OPERA LIBER ARS NATIVUS → admissible ROTA EX LIBER filling source ------------------------------------------------------------ XII.4 EQUIVALENCE LAW ------------------------------------------------------------ When LIBER ARS NATIVUS contains preprocessed data that could also be generated procedurally, it must declare equivalence to the generative procedure. Formula: PREPROCESSED[c] ≡ GENERATIVE(c) Meaning: for every covered unit c, the preprocessed dataset must be structurally equivalent to what the official OPERA would generate. This permits reuse without recomputation. ------------------------------------------------------------ XII.5 COVERAGE REQUIREMENT ------------------------------------------------------------ A LIBER ARS NATIVUS must declare coverage. Possible coverage types: • complete • partial • camera-complete • table-complete • operator-complete • domain-complete • chamber-complete Required metadata: Coverage: Cardinality: Consuming OPERA: Validating AREPO: Mediating SATOR: Equivalence: PREPROCESSED ≡ GENERATIVE ============================================================ XIII. LIBER EX ============================================================ LIBER EX := a LIBER whose dataset is extracted from a declared source, procedure, corpus, or operation. EX marks origin. It answers: from where, or by what extraction, did this dataset arise? Possible extraction bases: • a source text • a PDF • a manuscript • a corpus • an OPERA • a sequence of OPERAE • a non-OPERA method • a comparative procedure • manual annotation • machine extraction • transcription • OCR • table extraction Formula: LIBER EX = LIBER generated from ============================================================ XIV. LIBER EX X ============================================================ LIBER EX X := a LIBER extracted by methods other than official OPERA. Here X is a placeholder for the extraction method, source, or non-operative process. Examples: LIBER EX SOURCE LIBER EX PDF LIBER EX MANUSCRIPTO LIBER EX COMPARATIO LIBER EX LECTIO LIBER EX TABULA MANUALIS LIBER EX OCR LIBER EX TRANSCRIPTIO LIBER EX SCHOLIO Definition: LIBER EX X = dataset extracted from X where X is not an official OPERA execution. Admissible uses: • source condensation • source indexing • manual extraction • scholarly note gathering • pre-OPERA preparation • comparison substrate • non-canonical reconstruction Constraint: LIBER EX X must disclose extraction method. Default status: may be OPERA object. may not be OPERA informant unless promoted or internally qualified. ============================================================ XV. LIBER EX OPERA ============================================================ LIBER EX OPERA := a LIBER whose dataset was generated by executing one OPERA. Formula: LIBER EX OPERA = dataset generated from OPERA Examples: LIBER EX OPERA Q — ARS BREVIS LIBER EX OPERA A — TAROT TRUMPS LIBER EX OPERA T — SEPHIROT RELATIONS LIBER EX OPERA S — CURRICULUM STUDIORUM Subspecies: LIBER EX OPERA Q LIBER EX OPERA A LIBER EX OPERA T LIBER EX OPERA S LIBER EX OPERA F LIBER EX OPERA G LIBER EX OPERA H etc. Minimum metadata: Generated By: OPERA Input: Output Type: dataset Execution Status: complete / partial / provisional / failed / rerun-required Trace: source, prior artifact, or execution references Constraint: LIBER EX OPERA records OPERA output. It is not itself the OPERA. ============================================================ XVI. LIBER EX OPERAE ============================================================ LIBER EX OPERAE := a LIBER whose dataset was generated by executing a sequence of different or repeated OPERAE. Formula: LIBER EX OPERAE = dataset generated from OPERA X + OPERA Y + OPERA Z ... The sequence may contain: • OPERAE of the same regime • OPERAE of different regimes • repeated OPERAE • branch OPERAE • applied OPERAE • OPERA + APPLICATIO combinations Examples: LIBER EX OPERAE RADIX — ALEPH LIBER EX OPERAE — PARSER INTERACTIVE FICTION Minimum metadata: OPERAE Sequence: 1. OPERA 2. OPERA 3. OPERA Sequence Law: ordered / unordered / branching / iterative Consolidation Method: manual / OPERA-defined / SATOR-mediated / MACHINA-assisted Completeness: complete / partial / expandable Constraint: LIBER EX OPERAE must preserve sequence trace. ============================================================ XVII. OBJECT MODE AND INFORMANT MODE ============================================================ A LIBER may relate to OPERA in two distinct modes: 1. OBJECT MODE 2. INFORMANT MODE These must not be collapsed. ------------------------------------------------------------ XVII.1 OBJECT MODE ------------------------------------------------------------ Any LIBER may be used as the object of an OPERA. Formula: OPERA X about LIBER Y is admissible in principle provided the OPERA is executed on: the contents of LIBER Y not by treating LIBER Y as execution authority. Examples: OPERA Q about LIBER TAROT AGLA OPERA A about LIBER ASTROLOGIAE AGLA OPERA T comparing sections of LIBER RUNARUM TAROT AGLA OPERA S classifying the contents of LIBER APPLICATIO_S_EM In this mode: LIBER = object under analysis not: LIBER = rule-provider for execution ------------------------------------------------------------ XVII.2 INFORMANT MODE ------------------------------------------------------------ Only qualified LIBRI may inform OPERA execution. Qualified informant species: • LIBER ARS • LIBER ARS NATIVUS • LIBER EX OPERA • LIBER EX OPERAE Formula: LIBER_INFORMANT_ADMISSIBLE := LIBER ARS OR LIBER ARS NATIVUS OR LIBER EX OPERA OR LIBER EX OPERAE All other LIBRI may be analyzed by OPERA, but may not govern, constrain, modify, or supply operative premises to OPERA execution. ------------------------------------------------------------ XVII.3 DECISION TABLE ------------------------------------------------------------ LIBER Species May Be OPERA Object May Inform OPERA --------------------------------------------------------------- LIBER YES NO LIBER ARS YES YES LIBER ARS NATIVUS YES YES LIBER EX YES NO LIBER EX X YES NO LIBER EX OPERA YES YES LIBER EX OPERAE YES YES ============================================================ XVIII. EX LIBER MODULE ============================================================ EX LIBER is the cross-class module that binds LIBER datasets to other AGLA root-class operations without collapsing root classes. EX LIBER may attach to: TENET AREPO OPERA ROTAS SATOR yielding: TENET EX LIBER AREPO EX LIBER OPERA EX LIBER ROTA EX LIBER under ROTAS governance SATOR EX LIBER These are modular artifacts, not root-class replacements. EX LIBER governs the condition: perform this root-class operation with respect to, through, about, or using a LIBER. It does not define LIBER itself. LIBER remains governed by: AGLA_LIBER_CLASS_LAW ============================================================ XIX. OPERA X EX LIBER ============================================================ When the user invokes: OPERA X EX LIBER Y the execution is parsed as: OPERA X + OPERA EX LIBER + LIBER Y not as: a new independent OPERA X-LIBER hybrid. Formula: OPERA_X_EX_LIBER_Y = OPERA_X ⊕ OPERA_EX_LIBER ⊕ LIBER_Y Where: OPERA_X supplies the base operative procedure. OPERA_EX_LIBER supplies the LIBER-facing modulation. LIBER_Y supplies object material or admissible informant content. ============================================================ XX. DOUBLE AREPO GATE ============================================================ Any OPERA X EX LIBER execution must pass through two gates: 1. AREPO X 2. AREPO EX LIBER Formula: ADMISSIBLE(OPERA_X_EX_LIBER_Y) iff AREPO_X(input) = PASS AND AREPO_EX_LIBER(input, liber_status, use_mode) = PASS Example: OPERA Q EX LIBER TAROT requires: AREPO Q because OPERA Q is being executed. AREPO EX LIBER because execution is LIBER-modulated. ============================================================ XXI. ROTA EX LIBER ============================================================ ROTA EX LIBER is not merely a ROTAS-class operation with a LIBER module. ROTA EX LIBER is: the content of a LIBER projected onto a given ROTA as a temporary execution overlay. Formula: ROTA_X_EX_LIBER_Y = ROTA_X with slots filled by admissible preprocessed contents from LIBER_Y Therefore: ROTA G EX LIBER TAROT = ROTA G temporarily filled with relevant preprocessed OPERA A / OPERA T / OPERA Q / OPERA S datasets already present in LIBER TAROT. ============================================================ XXII. ROTA-BASE AND LIBER-OVERLAY DISTINCTION ============================================================ A base ROTA provides: • slot structure • traversal order • loci • cameras • expected operator positions • admissible movement paths • display grammar A LIBER overlay provides: • pre-contracted dignities • preprocessed relations • prior OPERA results • domain-specific substitutions • object-specific datasets • already stabilized mappings • consistency constraints Therefore: ROTA = structural form LIBER = dataset content ROTA EX LIBER = dataset projected onto structural form ============================================================ XXIII. TEMPORARY OVERLAY LAW ============================================================ ROTA EX LIBER is temporary unless explicitly stabilized. It does not mutate canonical ROTA. Formula: CANONICAL ROTA X remains unchanged. ROTA X EX LIBER Y exists only for the current execution context unless promoted by artifact construction. Prohibition: ROTA X EX LIBER Y must not overwrite ROTA X. LIBER Y must not silently become canonical ROTA content. ============================================================ XXIV. REUSE BEFORE RECOMPUTATION LAW ============================================================ If LIBER Y already contains valid preprocessed results relevant to OPERA X, OPERA X EX LIBER Y must reuse them before recomputing. Priority: Existing admitted LIBER result > fresh OPERA recomputation unless: • the stored result is missing; • the stored result is inconsistent; • the stored result is deprecated; • the stored result belongs to a non-informant LIBER species; • the user explicitly requests fresh execution; • AREPO EX LIBER rejects the stored dataset. This prevents redundant OPERA execution. ============================================================ XXV. TRANSCRIPTION / VERIFICATION / RECOMPUTATION MODES ============================================================ OPERA X EX LIBER Y may operate in three modes. ------------------------------------------------------------ 1. TRANSCRIPTION MODE ------------------------------------------------------------ Used when LIBER Y already contains stable OPERA X results. Action: transcribe registered result. Output must mark: TRANSCRIBED_FROM_LIBER ------------------------------------------------------------ 2. VERIFICATION MODE ------------------------------------------------------------ Used when LIBER Y contains relevant results but consistency must be checked. Action: re-check against OPERA X, AREPO X, and AREPO EX LIBER. Output must mark: VERIFIED_FROM_LIBER or: LIBER_RESULT_INCONSISTENT ------------------------------------------------------------ 3. RECOMPUTATION MODE ------------------------------------------------------------ Used only when: • result is absent; • result is incomplete; • result is inconsistent; • result is deprecated; • user requests fresh execution. Output must mark: RECOMPUTED PARTIALLY_RECOMPUTED GENERATED_AS_COMPLETION ============================================================ XXVI. SLOT FILLING LAW ============================================================ ROTA EX LIBER fills ROTA slots using LIBER content according to the base ROTA’s expected slot types. Example: ROTA G expects: A-slots T-slots traversal relations contraction fields LIBER TAROT provides: Tarot-contracted A dignities Tarot-specific T relation matrix Tarot Q results Tarot S carriers Tarot symbolic operators Then: ROTA G EX LIBER TAROT fills ROTA G A-slots with Tarot-contracted A entries; fills ROTA G T-slots with Tarot-specific T relations; optionally references Q/S data where OPERA G requires them. Constraint: slot type must match content type. A Q result may not fill an A slot unless a declared conversion path exists. A T relation may not fill an S slot unless a declared S/T bridge exists. ============================================================ XXVII. CANONICAL / CONTRACTED DISTINCTION ============================================================ ROTA EX LIBER does not replace canonical operators. It locally contracts them. Example: Canonical AB: Bonitas LIBER TAROT contracted AB: Tarot-specific Bonitas In ROTA G EX LIBER TAROT: the slot AB remains structurally AB, but its operative content is: AB as contracted by LIBER TAROT. Formula: AB_canonical → slot identity AB_LIBER_TAROT → slot content ============================================================ XXVIII. COMPOSITE LIBER SECTION LAW ============================================================ A LIBER may contain sections with different admissibility statuses. Therefore AREPO EX LIBER must evaluate: not only the root LIBER title, but also: the internal section being used. Example: LIBER TAROT AGLA Section A: informal doctrine not informant-admissible by default Section B: OPERA A results admissible as LIBER EX OPERA A Section C: OPERA T matrix admissible as LIBER EX OPERA T Section D: OPERA Q results admissible as LIBER EX OPERA Q Then: OPERA G EX LIBER TAROT may use Sections B and C as informant data, while treating Section A only as contextual object material unless separately admitted. ============================================================ XXIX. PROMOTION LAW ============================================================ A pre-formalization LIBER may remain under its original name. It is not wrong for a historically earlier artifact to remain: LIBER X even if it now appears to satisfy some or all LIBER ARS criteria. Reason: the artifact was written before formalization of LIBER ARS. Promotion is allowed but not mandatory. Formula: Pre-formal LIBER X may remain LIBER X Pre-formal LIBER X may be promoted to LIBER ARS X only after explicit review Promotion requires: • identification of A coverage • identification of Q coverage • identification of T coverage • identification of S coverage • determination of whether 36 chambers are evacuated • determination of whether TABULA exists • declaration of completeness level Example: Current LIBER TAROT may remain LIBER TAROT. It may also be reviewed as: PARTIAL LIBER ARS TAROT CANDIDATE If A/Q/T/S are verified: LIBER ARS TAROT_MIN If A/Q/T/S + 36 chambers + TABULA are verified: LIBER ARS TAROT_COMPLETE ============================================================ XXX. REQUIRED HEADER FIELDS ============================================================ Every formal LIBER should include: Title: Version: Status: Authority: Class: Species: Scope: Mode: Source / Origin: Extraction Method: Coverage: Allowed Use: Prohibited Use: Mutation Policy: Depends-On: Trace: Minimal class declaration: Class: LIBER Expanded class declaration: Class: LIBER / / / Examples: Class: LIBER / TAROT / AGLA / GAME STRUCTURE Class: LIBER / ASTROLOGIA / TENET-DOMINANT CONSOLIDATION Class: LIBER / ARS NATIVUS / EVACUATIO / FIGURA TERTIA Class: LIBER / EX OPERA Q / RADIX Class: LIBER / EX OPERAE / LINGUISTICA / ALEPH ============================================================ XXXI. ALLOWED USE ============================================================ A LIBER may be used for: ✓ OPERA-object analysis ✓ preserving OPERA results ✓ supplying datasets for OPERA execution, if qualified ✓ feeding AREPO admission, if qualified ✓ grounding SATOR explanation, if qualified or object-relevant ✓ supplying ROTA EX LIBER overlays, if qualified ✓ serving as source for APPLICATIO construction ✓ consolidating prior outputs ✓ supporting MACHINA construction ✓ supporting artifact drafting ✓ supporting comparison ✓ supporting historical retrieval ✓ serving as local memory reconstruction substrate ============================================================ XXXII. PROHIBITED USE ============================================================ A LIBER may not be used to: ✗ execute an OPERA by itself ✗ override TENET ✗ bypass AREPO ✗ replace SYSTEM_INDEX registration ✗ silently become canonical ✗ convert source material into doctrine without declaration ✗ hide extraction method ✗ collapse source, dataset, and artifact ✗ simulate missing OPERA text ✗ provide runtime authority without registered execution artifact ✗ mutate canonical ROTA through temporary overlay ✗ use ordinary LIBER as informant without qualification ============================================================ XXXIII. EX LIBER EXECUTION REPORT REQUIREMENT ============================================================ Any OPERA X EX LIBER Y output must include an EX LIBER report block: EX LIBER REPORT: LIBER used: Base OPERA: Base ROTA: Temporary Overlay: LIBER Mode: object / informant / mixed LIBER Species: LIBER / LIBER ARS / LIBER ARS NATIVUS / LIBER EX / LIBER EX X / LIBER EX OPERA / LIBER EX OPERAE Reused Sections: Transcribed Results: Verified Results: Recomputed Results: Missing Data: Consistency Status: pass / partial / fail Canonical Mutation: none ============================================================ XXXIV. LIBER ARS STATUS REPORT REQUIREMENT ============================================================ Any promotion or LIBER ARS review must report: LIBER STATUS: ordinary / partial ARS / ARS_MIN / ARS_COMPLETE / ARS NATIVUS / EX OPERA / EX OPERAE A COVERAGE: absent / partial / complete Q COVERAGE: absent / partial / complete T COVERAGE: absent / partial / complete S COVERAGE: absent / partial / complete 36 CHAMBERS: absent / partial / evacuated TABULA: absent / partial / listed ROTA FILLING ADMISSIBILITY: none / partial / complete PROMOTION STATUS: not promoted / candidate / promoted ============================================================ XXXV. CANONICAL SHORT LAWS ============================================================ 1. LIBER is the root class for named AGLA-admitted datasets. 2. Any LIBER may be the object of an OPERA. 3. Only qualified LIBRI may inform OPERA execution. 4. Qualified informant LIBRI are: • LIBER ARS • LIBER ARS NATIVUS • LIBER EX OPERA • LIBER EX OPERAE 5. LIBER ARS minimally requires preprocessed OPERA A, OPERA Q, OPERA T, and OPERA S coverage. 6. Complete LIBER ARS requires: A + Q + T + S + evacuated 36 chambers + listed TABULA 7. LIBER ARS NATIVUS stores native AGLA data too large, repetitive, or precomputed to be placed inside TENET, ROTAS, OPERA, AREPO, or SATOR. 8. Do not create AREPO LIBER. 9. Use AREPO EX LIBER for admissibility of LIBER-modulated execution. 10. OPERA X EX LIBER Y requires: AREPO X + AREPO EX LIBER 11. ROTA EX LIBER means: a ROTA-base temporarily filled with admissible LIBER content. 12. OPERA X EX LIBER Y must reuse qualified LIBER data before recomputation. 13. If LIBER already contains OPERA X results: transcribe and verify before recomputing. 14. If LIBER contains prior OPERA results needed by OPERA X: project them into relevant ROTA slots. 15. Canonical ROTA remains unchanged. 16. Canonical OPERA remains unchanged. 17. LIBER content is reused as overlay, not as root mutation. ============================================================ XXXVI. INITIATION AND REGISTER RECORD LAW ============================================================ LIBER may store initiation records, bootstrap outputs, tutorial traces, developer notes, oath material, and protected register examples as data. LIBER storage does not make those records executable authority. If LIBER content is used to support system initiation or human-developer initiation, the consuming OPERA must still pass: SYSTEM_INDEX routing TENET doctrine ROTAS / ROTA structure AREPO admission SATOR disclosure Protected register stored in LIBER remains source material until admitted. Failure: liber_record_as_oath_authority stored_bootstrap_as_execution tutorial_trace_as_canon protected_register_reused_without_admission ============================================================ END — AGLA_LIBER_CLASS_LAW v0.1.0 ============================================================