============================================================
OPERA EX LIBER
AGLA — Execution Modulation Law for LIBER-Conditioned OPERAE
Version: 0.1.0-OPERA-EX-LIBER
Status:
DRAFT — MODULE OPERA
Authority:
LOCAL / AGLA_P&D_LAB
Class:
OPERA / EX LIBER
Pentagrama:
PENTAGRAMA EX LIBER
Depends-On:
• AGLA_LIBER_CLASS_LAW
• AGLA_PENTAGRAMA_CLASS_LAW
• TENET EX LIBER
• ROTA EX LIBER
• AGLA — FIVE-CLASS STRUCTURAL ORDER
Scope:
• define how OPERA X behaves when conditioned by LIBER content
• enforce reuse-before-recomputation
• define transcription, verification, recomputation, and fresh execution modes
• govern OPERA X EX LIBER Y execution
• preserve OPERA X as base procedure
• prevent LIBER from becoming hidden OPERA
• consume ROTA X EX LIBER Y overlays without mutating canonical ROTA
Mutation Policy:
VERSION-CONTROLLED ONLY
============================================================
============================================================
I. PURPOSE
============================================================
OPERA EX LIBER defines the procedural law for executing a base OPERA
when a LIBER is present as object, informant, or mixed object/informant.
It answers:
What does OPERA X do when LIBER Y already contains relevant data?
When should OPERA X transcribe?
When should OPERA X verify?
When should OPERA X recompute?
When should OPERA X start fresh?
How does OPERA X execute through ROTA X EX LIBER Y?
OPERA EX LIBER is not the base OPERA itself.
It is the execution-modulation layer for LIBER-conditioned use.
============================================================
II. POSITION IN PENTAGRAMA EX LIBER
============================================================
Within PENTAGRAMA EX LIBER:
TENET EX LIBER:
doctrine and non-collapse law
AREPO EX LIBER:
admissibility and gate
ROTA EX LIBER:
temporary overlay structure
OPERA EX LIBER:
execution modulation
SATOR EX LIBER:
mediation and report surface
OPERA EX LIBER executes only after:
• base OPERA X is identified;
• base ROTA X is identified;
• LIBER Y is identified;
• AREPO X passes;
• AREPO EX LIBER passes;
• ROTA X EX LIBER Y is constructed if informant data exists.
Formula:
OPERA_X_EX_LIBER_Y =
OPERA_X
+
OPERA_EX_LIBER
+
ROTA_X_EX_LIBER_Y
+
LIBER_Y
============================================================
III. ROOT DEFINITION
============================================================
OPERA EX LIBER :=
the execution module that governs how a base OPERA uses,
checks, transcribes, completes, or recomputes data from a LIBER.
Compact formula:
OPERA_EX_LIBER =
reuse-before-recomputation procedure
Expanded formula:
OPERA_EX_LIBER =
base OPERA preservation
+ LIBER mode detection
+ prior-result detection
+ ROTA overlay consumption
+ transcription protocol
+ verification protocol
+ recomputation protocol
+ reporting obligations.
============================================================
IV. BASE OPERA PRESERVATION LAW
============================================================
OPERA EX LIBER never replaces the base OPERA.
If the user invokes:
OPERA X EX LIBER Y
then:
OPERA X remains the base procedure.
EX LIBER modifies how OPERA X consumes LIBER Y.
LIBER Y supplies object material or qualified informant data.
Prohibited:
✗ treating LIBER Y as OPERA X
✗ treating OPERA EX LIBER as a standalone OPERA
✗ executing LIBER contents without OPERA X
✗ bypassing AREPO X
✗ bypassing AREPO EX LIBER
Formula:
OPERA_X_EX_LIBER_Y ≠OPERA_EX_LIBER alone
OPERA_X_EX_LIBER_Y ≠LIBER_Y
OPERA_X_EX_LIBER_Y = OPERA_X modulated by EX_LIBER
============================================================
V. EXECUTION MODES
============================================================
OPERA EX LIBER recognizes five execution modes:
1. OBJECT ANALYSIS MODE
2. TRANSCRIPTION MODE
3. VERIFICATION MODE
4. PARTIAL RECOMPUTATION MODE
5. FRESH EXECUTION MODE
The mode must be explicitly declared or recoverable from the report.
============================================================
VI. OBJECT ANALYSIS MODE
============================================================
Object analysis mode is used when:
LIBER Y is the object being analyzed,
not an informant source for execution.
Any LIBER may be used in object mode.
Example:
OPERA Q about LIBER TAROT
In this mode:
OPERA X applies to LIBER Y as material under analysis.
LIBER Y does not govern OPERA X.
No ROTA slot filling is authorized by default.
No prior result is reused as execution substrate unless an internal
qualified section is identified.
Output label:
LIBER_MODE:
OBJECT
Required behavior:
execute OPERA X on the contents of LIBER Y.
Prohibited:
treating ordinary LIBER content as preprocessed OPERA result.
============================================================
VII. TRANSCRIPTION MODE
============================================================
Transcription mode is used when:
LIBER Y already contains stable, qualified results for OPERA X.
Example:
OPERA Q EX LIBER TAROT
If LIBER TAROT already contains a qualified OPERA Q result:
OPERA EX LIBER transcribes that result.
It does not restart OPERA Q from zero.
Required action:
1. locate the relevant OPERA X result in LIBER Y;
2. confirm section status:
LIBER ARS / LIBER ARS NATIVUS / LIBER EX OPERA /
LIBER EX OPERAE / qualified internal section;
3. transcribe result;
4. mark trace;
5. pass result to verification if required.
Output label:
TRANSCRIBED_FROM_LIBER
Transcription does not mean blind copying.
It means:
use registered LIBER result as primary execution substrate.
============================================================
VIII. VERIFICATION MODE
============================================================
Verification mode is used when:
LIBER Y contains relevant data,
but consistency, scope, or slot compatibility must be checked.
Required checks:
• base OPERA X compatibility
• AREPO X compatibility
• AREPO EX LIBER compatibility
• TENET EX LIBER non-collapse
• ROTA X EX LIBER Y slot compatibility
• section-level qualification
• deprecated or contradiction-marked status
• canonical mutation risk
Possible output labels:
VERIFIED_FROM_LIBER
LIBER_RESULT_PARTIAL
LIBER_RESULT_INCONSISTENT
LIBER_RESULT_DEPRECATED
LIBER_RESULT_SCOPE_MISMATCH
LIBER_RESULT_SLOT_MISMATCH
Verification may result in:
• accepted reuse;
• partial reuse;
• recomputation of failed portions;
• rejection of LIBER as informant;
• object-only treatment.
============================================================
IX. PARTIAL RECOMPUTATION MODE
============================================================
Partial recomputation mode is used when qualified LIBER data exists,
but some required parts are:
• absent;
• incomplete;
• inconsistent;
• deprecated;
• slot-incompatible;
• outside scope.
Required action:
1. preserve verified LIBER data;
2. isolate missing or failed portions;
3. recompute only those portions;
4. mark recomputed portions;
5. update temporary overlay only for the current execution;
6. do not mutate canonical LIBER unless artifact construction is
explicitly requested.
Output labels:
PARTIALLY_RECOMPUTED
GENERATED_AS_COMPLETION
RECOMPUTED_FAILED_SECTION
RECOMPUTED_MISSING_SLOT
Doctrine:
recomputation is completion or correction,
not default behavior when qualified data exists.
============================================================
X. FRESH EXECUTION MODE
============================================================
Fresh execution mode is used when:
• LIBER Y is object-only and no qualified section exists;
• no relevant prior result exists;
• AREPO EX LIBER rejects LIBER as informant;
• user explicitly requests fresh execution;
• prior data is too unstable to reuse;
• OPERA X requires full rerun due to scope mismatch.
In fresh execution mode:
OPERA X executes normally.
LIBER may still be used as object material.
Output label:
FRESH_EXECUTION
or:
RECOMPUTED_FROM_ZERO
Constraint:
if qualified reusable data exists, fresh execution must be justified.
============================================================
XI. REUSE BEFORE RECOMPUTATION LAW
============================================================
OPERA EX LIBER must prefer qualified preprocessed LIBER data over
fresh recomputation.
Priority formula:
qualified LIBER result
>
partial recomputation
>
fresh execution
unless:
• user requests fresh execution;
• data fails AREPO EX LIBER;
• data fails base AREPO;
• data is inconsistent;
• data is deprecated;
• scope mismatch blocks reuse.
Operational sequence:
1. search for qualified prior result;
2. if found, transcribe;
3. verify;
4. reuse accepted sections;
5. recompute only missing or failed sections;
6. execute fresh only if reuse is impossible or rejected.
============================================================
XII. OPERA X EX LIBER GENERAL PROCEDURE
============================================================
To execute:
OPERA X EX LIBER Y
perform:
1. Parse user request.
2. Identify base OPERA X.
3. Identify LIBER Y.
4. Determine intended mode:
object / informant / mixed.
5. Invoke AREPO X.
6. Invoke AREPO EX LIBER.
7. Identify base ROTA X.
8. Inspect LIBER Y for relevant qualified sections.
9. If informant data exists, construct or receive:
ROTA X EX LIBER Y.
10. Select execution mode:
object analysis / transcription / verification /
partial recomputation / fresh execution.
11. Execute OPERA X through selected mode.
12. Preserve canonical mutation = NONE.
13. Pass result to SATOR EX LIBER report.
============================================================
XIII. RELATION TO ROTA EX LIBER
============================================================
OPERA EX LIBER must execute through the effective structural surface
declared by ROTA EX LIBER.
If overlay exists:
execute through:
ROTA X EX LIBER Y
If overlay is rejected:
either:
execute OPERA X in object mode
or:
execute fresh OPERA X without informant reuse
depending on AREPO EX LIBER decision.
OPERA EX LIBER must not silently invent a ROTA overlay.
ROTA EX LIBER supplies:
• base ROTA
• slot map
• filled slots
• missing slots
• rejected fillings
• compatibility status
OPERA EX LIBER consumes this map procedurally.
============================================================
XIV. RELATION TO TENET EX LIBER
============================================================
OPERA EX LIBER is bound by TENET EX LIBER.
Therefore OPERA EX LIBER must preserve:
• LIBER ≠OPERA
• object ≠informant
• overlay ≠canonical mutation
• slot identity ≠slot content
• source quote ≠OPERA result
• ordinary LIBER ≠qualified informant
• reuse before recomputation
• section-level qualification
If OPERA EX LIBER cannot preserve these distinctions:
execution must fail or degrade to object mode.
============================================================
XV. RELATION TO AREPO EX LIBER
============================================================
OPERA EX LIBER does not decide admissibility.
AREPO EX LIBER decides:
• whether LIBER Y may be object;
• whether LIBER Y may be informant;
• whether specific sections may fill slots;
• whether the overlay is admissible;
• whether recomputation is required;
• whether user consent is needed for adaptation.
OPERA EX LIBER acts only after gate decision.
Prohibited:
✗ OPERA EX LIBER admitting its own informant data
✗ OPERA EX LIBER bypassing AREPO EX LIBER
✗ OPERA EX LIBER overriding rejection
If AREPO EX LIBER fails:
OPERA EX LIBER must either:
• abort;
• run object-mode analysis only;
• request clarification;
• execute fresh OPERA X without informant reuse;
according to the failure type.
============================================================
XVI. RELATION TO SATOR EX LIBER
============================================================
SATOR EX LIBER must report what OPERA EX LIBER actually did.
OPERA EX LIBER must provide SATOR EX LIBER with:
• selected execution mode;
• reused LIBER sections;
• transcribed results;
• verified results;
• recomputed results;
• fresh execution scope;
• rejected sections;
• missing data;
• effective ROTA overlay;
• canonical mutation status.
SATOR may explain.
SATOR may not rewrite OPERA result.
SATOR may not hide reuse.
============================================================
XVII. OPERA RESULT CLASSIFICATION
============================================================
Every output segment produced under OPERA EX LIBER must be classified
as one of:
FROM_LIBER_TRANSCRIBED
FROM_LIBER_VERIFIED
FROM_LIBER_PARTIAL
FROM_LIBER_REJECTED
OPERA_RECOMPUTED
OPERA_GENERATED_COMPLETION
OBJECT_ANALYSIS_RESULT
FRESH_EXECUTION_RESULT
This classification prevents ambiguity between inherited data and
new execution.
============================================================
XVIII. EXAMPLE — OPERA Q EX LIBER TAROT
============================================================
Request:
OPERA Q EX LIBER TAROT
Base OPERA:
OPERA Q
LIBER:
LIBER TAROT
Procedure:
1. Check AREPO Q.
2. Check AREPO EX LIBER.
3. Inspect LIBER TAROT for OPERA Q section.
4. If OPERA Q section exists and is qualified:
transcribe Q results.
5. Verify consistency.
6. Recompute only missing or failed questions.
7. Report:
TRANSCRIBED_FROM_LIBER
VERIFIED_FROM_LIBER
PARTIALLY_RECOMPUTED if needed.
Not allowed:
restarting OPERA Q from zero by default.
============================================================
XIX. EXAMPLE — OPERA G EX LIBER TAROT
============================================================
Request:
OPERA G EX LIBER TAROT
Base OPERA:
OPERA G
LIBER:
LIBER TAROT
Required substrate:
• A contracted principles
• T relations
• possible Q and S support
• camera / evacuation structure depending on G scope
Procedure:
1. Check AREPO G.
2. Check AREPO EX LIBER.
3. Identify base ROTA G.
4. Build ROTA G EX LIBER TAROT if qualified data exists.
5. Fill A slots from Tarot OPERA A results.
6. Fill T slots from Tarot OPERA T results.
7. Use Q/S sections where required.
8. Execute OPERA G through overlay.
9. Recompute only missing or failed portions.
Not allowed:
treating Tarot ordinary doctrine as T matrix unless qualified.
replacing canonical ROTA G.
recomputing all A/T relations when valid LIBER data exists.
============================================================
XX. EXAMPLE — OPERA G EX LIBER ARS NATIVUS EVACUATIO
============================================================
Request:
OPERA G EX LIBER ARS NATIVUS EVACUATIO FIGURAE TERTIAE
Base OPERA:
OPERA G
LIBER:
LIBER ARS NATIVUS EVACUATIO FIGURAE TERTIAE
Expected mode:
transcription + verification
Procedure:
1. Check AREPO G.
2. Check AREPO EX LIBER.
3. Identify ROTA G.
4. Construct:
ROTA G EX LIBER ARS NATIVUS EVACUATIO FIGURAE TERTIAE.
5. Transcribe preprocessed chambers.
6. Verify equivalence:
PREPROCESSED[c] ≡ GENERATIVE(c)
7. Recompute only if inconsistency appears.
8. Report canonical mutation:
none.
============================================================
XXI. FAILURE MODES
============================================================
OPERA EX LIBER exists to prevent:
1. LIBER being executed as OPERA;
2. OPERA restarting from zero despite valid qualified data;
3. OPERA reusing ordinary LIBER as informant;
4. OPERA bypassing AREPO EX LIBER;
5. OPERA bypassing base AREPO X;
6. OPERA silently mutating canonical ROTA;
7. OPERA confusing source quotes with OPERA results;
8. OPERA treating SATOR explanation as data;
9. OPERA using T results as S data without bridge;
10. OPERA failing to classify output origin;
11. OPERA hiding recomputation scope;
12. OPERA treating partial overlay as complete.
============================================================
XXII. REQUIRED OPERA EX LIBER EXECUTION REPORT
============================================================
OPERA EX LIBER must provide the following report data to SATOR:
OPERA EX LIBER EXECUTION REPORT:
Base OPERA:
<OPERA X>
LIBER:
<LIBER Y>
LIBER Mode:
object / informant / mixed
Base AREPO:
<AREPO X>
EX LIBER Gate:
<AREPO EX LIBER status>
Base ROTA:
<ROTA X>
Temporary Overlay:
<ROTA X EX LIBER Y / none>
Execution Mode:
object analysis / transcription / verification /
partial recomputation / fresh execution / mixed
Transcribed Sections:
<list>
Verified Sections:
<list>
Recomputed Sections:
<list>
Fresh Execution Scope:
<scope>
Rejected Sections:
<list>
Missing Data:
<list>
Output Classification:
<classification map>
Canonical Mutation:
none
============================================================
XXIII. SHORT LAW
============================================================
OPERA EX LIBER is the execution-modulation point of PENTAGRAMA
EX LIBER.
It governs:
how OPERA X behaves when LIBER Y is present.
It preserves:
OPERA X as base procedure.
It requires:
AREPO X
+
AREPO EX LIBER
It consumes:
ROTA X EX LIBER Y
when an admissible overlay exists.
It must:
• reuse qualified LIBER data before recomputation;
• transcribe stable prior results;
• verify relevant data;
• recompute only missing or failed portions;
• execute fresh only when reuse is impossible, rejected, or
explicitly requested;
• classify output origin;
• mutate no canonical ROTA, OPERA, TENET, AREPO, SATOR, or LIBER.
Final formula:
OPERA_X_EX_LIBER_Y =
OPERA_X
through
EX_LIBER execution modulation
using
ROTA_X_EX_LIBER_Y when admitted
with reuse before recomputation.
============================================================
END — OPERA EX LIBER v0.1.0
============================================================
```
Actual artifact: 90_STACK_LIBER/OPERA_EX_LIBER.md