============================================================ PENTAGRAMA EX LIBER AGLA — Modular Binding Figure for LIBER-Conditioned Execution Version: 0.1.0-PENTAGRAMA-EX-LIBER Status: DRAFT — STRUCTURAL MODULE FIGURE Authority: LOCAL / AGLA_P&D_LAB Class: AGLA / PENTAGRAMA / EX LIBER Depends-On: • AGLA_LIBER_CLASS_LAW • AGLA_PENTAGRAMA_CLASS_LAW • TENET CLASS LAW • AREPO CLASS LAW • OPERA CLASS LAW • ROTAS CLASS LAW • SATOR CLASS LAW Scope: • define the fivefold EX LIBER module structure • bind LIBER to TENET / AREPO / OPERA / ROTAS / SATOR without collapsing root classes • define how OPERA X EX LIBER executions are stabilized • define how temporary ROTA EX LIBER overlays are generated • prevent LIBER from becoming runtime authority by itself Mutation Policy: VERSION-CONTROLLED ONLY ============================================================ ============================================================ I. PURPOSE ============================================================ PENTAGRAMA EX LIBER defines the fivefold module structure by which a LIBER may enter AGLA operations without becoming an OPERA, TENET, ROTA, AREPO, SATOR, or SYSTEM_INDEX. It articulates the five EX LIBER modules: 1. TENET EX LIBER 2. AREPO EX LIBER 3. OPERA EX LIBER 4. ROTA EX LIBER 5. SATOR EX LIBER with: LIBER at the center. Core formula: LIBER enters execution through EX LIBER modules not through direct runtime authority. ============================================================ II. FIGURE ============================================================ Symbolic structure: TENET EX LIBER ▲ / \ / \ / \ SATOR EX LIBER ◄-------► AREPO EX LIBER \ / \ / \ / \ / OPERA EX LIBER ▲ │ ROTA EX LIBER Center: LIBER Interpretation: LIBER is the central dataset. The five points are the lawful class-modulated surfaces through which LIBER enters AGLA use. No point replaces LIBER. LIBER replaces no point. ============================================================ III. CENTER — LIBER ============================================================ The center of the pentagram is: LIBER Definition: a named AGLA-admitted dataset. In EX LIBER operations, LIBER may function as: 1. object 2. informant 3. mixed object/informant Object mode: any LIBER may be analyzed. Informant mode: only qualified LIBRI may inform execution: • LIBER ARS • LIBER ARS NATIVUS • LIBER EX OPERA • LIBER EX OPERAE The center supplies content. The points govern how the content enters operation. ============================================================ IV. POINT 1 — TENET EX LIBER ============================================================ TENET EX LIBER defines the doctrinal constraints for LIBER use. It answers: What may a LIBER mean inside an operation? What must not be inferred from LIBER status? What distinctions must be preserved? Core laws: LIBER ≠ SOURCE LIBER ≠ OPERA LIBER ≠ ROTA LIBER ≠ TENET LIBER ≠ AREPO LIBER ≠ SATOR LIBER ≠ SYSTEM_INDEX OBJECT ≠ INFORMANT OVERLAY ≠ CANONICAL MUTATION TENET EX LIBER preserves the doctrine that: LIBER may inform execution only when qualified. LIBER may be analyzed even when not qualified. LIBER may provide ROTA fillings only through admissible sections. LIBER does not become runtime authority by being cited. ============================================================ V. POINT 2 — AREPO EX LIBER ============================================================ AREPO EX LIBER gates LIBER-conditioned execution. It answers: May this LIBER be used in this execution? Is it being used as object, informant, or mixed? Is the relevant LIBER section qualified? Is the requested use compatible with OPERA X? Can the LIBER content fill the requested ROTA slots? AREPO EX LIBER does not replace AREPO X. Any OPERA X EX LIBER execution requires: AREPO X + AREPO EX LIBER Formula: ADMISSIBLE(OPERA_X_EX_LIBER_Y) iff AREPO_X = PASS AND AREPO_EX_LIBER = PASS AREPO EX LIBER must check: • LIBER species • internal section status • object/informant mode • coverage • provenance • consistency • slot compatibility • mutation risk • whether recomputation is required ============================================================ VI. POINT 3 — OPERA EX LIBER ============================================================ OPERA EX LIBER defines how a base OPERA operates when conditioned by a LIBER. It answers: How does OPERA X behave when LIBER data already exists? What is transcribed? What is verified? What is recomputed? What is projected into ROTA slots? OPERA EX LIBER does not replace OPERA X. Formula: OPERA_X_EX_LIBER_Y := OPERA_X + OPERA_EX_LIBER + LIBER_Y Execution priority: 1. locate relevant LIBER content 2. classify object/informant mode 3. identify base OPERA X requirements 4. identify base ROTA X 5. build ROTA X EX LIBER Y overlay if allowed 6. transcribe valid prior results 7. verify consistency 8. recompute only missing or failed portions 9. report reuse and mutation status Primary rule: reuse before recomputation. ============================================================ VII. POINT 4 — ROTA EX LIBER ============================================================ ROTA EX LIBER defines the temporary ROTA overlay produced by projecting LIBER content onto a ROTA-base. It answers: Which ROTA is being filled? Which slots are filled by LIBER? Which slots remain canonical? Which slots are missing? Which fields require recomputation? ROTA EX LIBER is not a canonical ROTA mutation. Formula: ROTA_X_EX_LIBER_Y := ROTA_X with slots temporarily filled by admissible content from LIBER_Y A base ROTA provides: • slot structure • loci • cameras • traversal order • structural grammar The LIBER overlay provides: • pre-contracted dignities • preprocessed Q results • T relation matrices • S subject mappings • evacuated chambers • TABULA listings • domain-specific substitutions • native preprocessed data ROTA EX LIBER is the principal technical reason qualified LIBRI exist. Qualified LIBRI provide temporary ROTA fillings. Canonical ROTA remains unchanged. ============================================================ VIII. POINT 5 — SATOR EX LIBER ============================================================ SATOR EX LIBER defines the user-facing mediation and report surface for EX LIBER execution. It answers: What did the assistant reuse? What was transcribed? What was verified? What was recomputed? What was only object-level material? Did canonical mutation occur? Which LIBER sections were admissible? SATOR EX LIBER must make visible: • LIBER used • LIBER species • base OPERA • base ROTA • temporary overlay • object/informant mode • reused sections • missing data • consistency status • recomputation scope • mutation status SATOR EX LIBER prevents the assistant from silently treating LIBER as runtime authority. ============================================================ IX. PENTAGRAMA ORDER ============================================================ Default operational order: 1. TENET EX LIBER preserve doctrine and distinctions 2. AREPO EX LIBER gate admissibility of LIBER use 3. ROTA EX LIBER construct temporary ROTA overlay 4. OPERA EX LIBER execute base OPERA through overlay 5. SATOR EX LIBER report, mediate, and expose status Execution formula: TENET_EX_LIBER → AREPO_EX_LIBER → ROTA_EX_LIBER → OPERA_EX_LIBER → SATOR_EX_LIBER Compact formula: Doctrine → Gate → Overlay → Execution → Report ============================================================ X. EDGE RELATIONS ============================================================ The pentagram edges define necessary relations among points. ------------------------------------------------------------ TENET EX LIBER ↔ AREPO EX LIBER ------------------------------------------------------------ TENET gives the non-collapse doctrine. AREPO tests whether the proposed use violates that doctrine. Formula: doctrine constrains gate ------------------------------------------------------------ AREPO EX LIBER ↔ ROTA EX LIBER ------------------------------------------------------------ AREPO decides whether LIBER content may fill ROTA slots. ROTA EX LIBER receives only admitted content under ROTAS governance. Formula: gate admits overlay ------------------------------------------------------------ ROTA EX LIBER ↔ OPERA EX LIBER ------------------------------------------------------------ ROTA EX LIBER supplies the temporary filled structure under ROTAS governance. OPERA executes through that structure. Formula: overlay supports execution ------------------------------------------------------------ OPERA EX LIBER ↔ SATOR EX LIBER ------------------------------------------------------------ OPERA produces or verifies results. SATOR reports which parts came from LIBER and which parts were computed. Formula: execution requires mediation ------------------------------------------------------------ SATOR EX LIBER ↔ TENET EX LIBER ------------------------------------------------------------ SATOR reports in a way that preserves doctrinal distinctions. TENET prevents explanation from becoming false authority. Formula: mediation returns to doctrine ============================================================ XI. DIAGONAL RELATIONS ============================================================ The diagonals define cross-checks. ------------------------------------------------------------ TENET EX LIBER ↔ ROTA EX LIBER ------------------------------------------------------------ Check: Does the overlay preserve canonical / contracted distinction? Failure mode: temporary ROTA filling treated as canonical ROTA mutation. ------------------------------------------------------------ TENET EX LIBER ↔ OPERA EX LIBER ------------------------------------------------------------ Check: Does OPERA reuse LIBER without letting LIBER become OPERA? Failure mode: dataset becomes hidden procedure. ------------------------------------------------------------ AREPO EX LIBER ↔ SATOR EX LIBER ------------------------------------------------------------ Check: Does the report expose why LIBER passed or failed? Failure mode: silent admissibility. ------------------------------------------------------------ AREPO EX LIBER ↔ OPERA EX LIBER ------------------------------------------------------------ Check: Does OPERA recompute only what AREPO allowed? Failure mode: OPERA starts from scratch despite valid LIBER data, or reuses data that failed gate. ------------------------------------------------------------ ROTA EX LIBER ↔ SATOR EX LIBER ------------------------------------------------------------ Check: Does SATOR expose the temporary overlay? Failure mode: user cannot distinguish canonical ROTA from overlay. ============================================================ XII. OPERA X EX LIBER EXECUTION TEMPLATE ============================================================ When user invokes: OPERA X EX LIBER Y parse: Base OPERA: OPERA X Module: EX LIBER Dataset: LIBER Y Required gates: AREPO X AREPO EX LIBER Required structure: ROTA X Potential overlay: ROTA X EX LIBER Y Required report: SATOR EX LIBER report block Execution modes: • transcription • verification • recomputation • mixed ============================================================ XIII. TRANSCRIPTION MODE ============================================================ Used when LIBER Y already contains stable results for OPERA X. Action: transcribe registered results. Required label: TRANSCRIBED_FROM_LIBER Example: OPERA Q EX LIBER TAROT If LIBER TAROT already contains OPERA Q results: do not restart OPERA Q from zero. Instead: transcribe, verify consistency, complete only missing parts. ============================================================ XIV. VERIFICATION MODE ============================================================ Used when LIBER Y contains relevant results, but consistency must be checked. Action: re-check against: • OPERA X • AREPO X • AREPO EX LIBER • TENET EX LIBER • slot compatibility Required labels: VERIFIED_FROM_LIBER LIBER_RESULT_INCONSISTENT LIBER_RESULT_PARTIAL ============================================================ XV. RECOMPUTATION MODE ============================================================ Used only when: • result is absent • result is incomplete • result is inconsistent • result is deprecated • user explicitly requests fresh execution • AREPO EX LIBER rejects reuse Required labels: RECOMPUTED PARTIALLY_RECOMPUTED GENERATED_AS_COMPLETION ============================================================ XVI. EXAMPLE — OPERA G EX LIBER TAROT ============================================================ Request: OPERA G EX LIBER TAROT Base OPERA: OPERA G Base ROTA: ROTA G Required OPERA G substrate: • A absolute principles • T relative principles • chambers / evacuation structure • traversal logic If LIBER TAROT contains: • contracted A dignities from prior OPERA A • T relations from prior OPERA T • Q fields from prior OPERA Q • S carriers from prior OPERA S then: ROTA G EX LIBER TAROT is created. The canonical ROTA G slots remain structurally G-slots. But their temporary content is supplied by LIBER TAROT. Formula: ROTA_G_SLOT_AB remains AB structurally ROTA_G_SLOT_AB_EX_LIBER_TAROT receives AB_TAROT contracted content Result: OPERA G executes through Tarot-preprocessed data instead of starting from zero. ============================================================ XVII. EXAMPLE — OPERA G EX LIBER ARS NATIVUS EVACUATIO ============================================================ Request: OPERA G EX LIBER ARS NATIVUS EVACUATIO FIGURAE TERTIAE Base OPERA: OPERA G Base ROTA: ROTA G LIBER: LIBER ARS NATIVUS EVACUATIO FIGURAE TERTIAE Use mode: informant Reason: LIBER ARS NATIVUS is qualified informant species. Overlay: ROTA G EX LIBER ARS NATIVUS EVACUATIO FIGURAE TERTIAE Function: fill Evacuatio chambers with preprocessed native data. OPERA behavior: transcribe chamber data; verify equivalence; avoid recomputation unless inconsistency is found. Canonical mutation: none. ============================================================ XVIII. FAILURE MODES ============================================================ PENTAGRAMA EX LIBER prevents the following failures: 1. LIBER treated as OPERA. 2. ordinary LIBER treated as informant. 3. source-derived material treated as preprocessed OPERA result. 4. temporary ROTA overlay treated as canonical ROTA mutation. 5. OPERA recomputed from zero despite valid LIBER data. 6. OPERA reused LIBER data without AREPO EX LIBER gate. 7. SATOR omitted reuse / verification / recomputation status. 8. LIBER ARS NATIVUS cluttered TENET or ROTA artifacts. 9. AREPO LIBER created as recursive root-class confusion. 10. EX LIBER module mistaken for independent root class. ============================================================ XIX. REQUIRED EX LIBER REPORT BLOCK ============================================================ Every OPERA X EX LIBER Y output must include: EX LIBER REPORT: LIBER: LIBER Species: Base OPERA: Base AREPO: EX LIBER Gate: AREPO EX LIBER Base ROTA: Temporary Overlay: LIBER Mode: object / informant / mixed Reused Sections: Transcribed Results: Verified Results: Recomputed Results: Missing Data: Consistency Status: pass / partial / fail Canonical Mutation: none ============================================================ XX. SHORT LAW ============================================================ PENTAGRAMA EX LIBER is the fivefold figure of LIBER-conditioned operation. It consists of: TENET EX LIBER AREPO EX LIBER ROTA EX LIBER OPERA EX LIBER SATOR EX LIBER with LIBER at the center. Its purpose is to let LIBER enter AGLA operations without collapsing dataset, doctrine, gate, procedure, structure, and mediation. Any OPERA X EX LIBER Y must: 1. preserve TENET EX LIBER distinctions; 2. pass AREPO X and AREPO EX LIBER; 3. construct ROTA X EX LIBER Y if qualified data exists; 4. execute OPERA X through OPERA EX LIBER rules; 5. report through SATOR EX LIBER; 6. reuse qualified LIBER data before recomputation; 7. mutate no canonical ROTA or OPERA. Formula: LIBER at center. Five EX LIBER points around it. Temporary overlay, not root mutation. Reuse before recomputation. Report before consolidation. ============================================================ END — PENTAGRAMA EX LIBER v0.1.0 ============================================================ ```