OPERA_RUNS/README.md

Bytes: 2119 | SHA-256: 558c5d5df4ec234419304f4585695a07967026824b71bd13ade5cf9e2f2fba27 | Source: OPERA_RUNS/README.md

Page Sections

Version: 0.1.0-OPERA-RUNS-LOCAL-OUTPUT-ROOT line 3
Status: line 4
Authority: line 6
Class: line 8
Mutation Policy: line 10
I. PURPOSE line 16
OPERA_RUNS is the canonical local destination for OPERA outputs produced line 19
in this environment. line 20
This folder replaces the prior root-level run folder: line 22
OPERA_RUN_2026-04-30_b8f751159174 line 25
II. TAXONOMY line 32
Use this folder pattern: line 35
Where: line 41
OPERA_ID: line 44
YYYY-MM-DD: line 48
RUN_ID: line 51
Recommended run subfolders: line 55
00_INPUT line 58
01_CONTEXT line 59
02_EXECUTION line 60
03_OUTPUT line 61
04_VALIDATION line 62
05_REPORTS line 63
III. LOCATION LAW line 68
Outputs generated by OPERAE in this environment belong here unless a line 71
specific OPERA artifact declares a stricter local run path. line 72
SIGMA_SATOR kernels are deployment wrappers and must not become run line 74
output folders. line 75
Run outputs are development-only by default. line 77
Promotion requires explicit review and version-controlled movement into line 79
the appropriate canonical or deployment-visible location. line 80

============================================================ OPERA_RUNS — LOCAL OPERA OUTPUT ROOT Version: 0.1.0-OPERA-RUNS-LOCAL-OUTPUT-ROOT Status: ACTIVE / DEVELOPMENT-ONLY / NON-DEPLOYABLE Authority: USER / HUMAN DEVELOPER AUTHORITY Class: AGLA / LOCAL_RUNTIME_OUTPUTS / OPERA_RUNS Mutation Policy: VERSION-CONTROLLED INDEX; RUN CONTENT MAY BE LOCAL UNTIL PROMOTED ============================================================ ============================================================ I. PURPOSE ============================================================ OPERA_RUNS is the canonical local destination for OPERA outputs produced in this environment. This folder replaces the prior root-level run folder: ```text OPERA_RUN_2026-04-30_b8f751159174 ``` Future runs must not create new root-level OPERA_RUN_* folders. ============================================================ II. TAXONOMY ============================================================ Use this folder pattern: ```text OPERA_RUNS/<OPERA_ID>/<YYYY-MM-DD>/<RUN_ID>/ ``` Where: ```text OPERA_ID: canonical OPERA identifier, e.g. OPERA_G, OPERA_RADIX, OPERA_Q_MNEMONICA. YYYY-MM-DD: run date. RUN_ID: RUN_<YYYY-MM-DD>_<short-id> ``` Recommended run subfolders: ```text 00_INPUT 01_CONTEXT 02_EXECUTION 03_OUTPUT 04_VALIDATION 05_REPORTS ``` ============================================================ III. LOCATION LAW ============================================================ Outputs generated by OPERAE in this environment belong here unless a specific OPERA artifact declares a stricter local run path. SIGMA_SATOR kernels are deployment wrappers and must not become run output folders. Run outputs are development-only by default. Promotion requires explicit review and version-controlled movement into the appropriate canonical or deployment-visible location. ============================================================ END — OPERA_RUNS ============================================================