============================================================
DOCUMENTATION CONTEXT FOLDER RULES
AGLA / CODEX WORKSPACE
Version: 1.0.0-CONTEXT-FOLDER-RULES
Status: ACTIVE
Date: 2026-04-30
Authority: USER / DEVELOPER WORKSPACE INSTRUCTION
============================================================
PURPOSE
------------------------------------------------------------
This file makes explicit the rules implied by the folder names
inside _00_Documentation.
============================================================
00_Sources
============================================================
Scope:
actual documentation source-file storage
Rule:
Actual files must be stored inside:
_00_Documentation/00_Sources
Other documentation context folders should not duplicate the
actual source files unless explicitly instructed.
Indexation rule:
Context folders must contain local indexation files,
manifests, notes, or path-reference records that point to
the corresponding files inside 00_Sources.
Required reference behavior:
When a context folder needs to include a source, it should
record:
- local context purpose
- source filename
- relative path to the source file in 00_Sources
- notes about intended context use
Non-duplication rule:
00_Sources is the storage layer.
Context folders are routing / indexation layers.
============================================================
01_CONTEXT_Development_Only
============================================================
Scope:
development-only material
Permitted use:
- Codex development context
- local drafting
- private/reference material for implementation support
- non-execution documentation
- local indexation and path references to files in 00_Sources
- context when writing artifacts
- context when rewriting artifacts
- context when evaluating artifacts
Restriction:
material in this folder is not automatically promoted to
control-plane reporting, execution authority, or canonical
runtime context.
Execution prohibition:
Development-only context must not be used to execute OPERAE.
Development-only context must not be used as runtime OPERA
behavior, admissibility, mediation, topology, or doctrine.
Development-only context must not allow an OPERA to be faked
by inference from source notes, literature notes, local
references, or Codex-only development material.
Deployment insulation rule:
Development-only context is not assumed to be present in
deployment.
Therefore, OPERA execution must not rely on development-only
context. Any execution behavior tied to this folder would make
deployed system behavior depend on the developer environment
and would make bug tracking non-reproducible.
Artifact-work rule:
Development-only context may inform:
- writing artifacts
- rewriting artifacts
- evaluating artifacts
It may not substitute for loaded, registered, execution-allowed
artifact content.
============================================================
CODEX_ONLY
============================================================
Scope:
Codex-only development material
Rule:
CODEX_ONLY material must not be mentioned in control-plane
reports unless explicitly requested.
Execution prohibition:
CODEX_ONLY material must not be used to execute OPERAE.
CODEX_ONLY material may inform artifact drafting, rewriting,
and evaluation, but it must not be treated as execution
authority, runtime context, or admissibility evidence.
Alias rule:
If a control-plane report explicitly requests reference to
CODEX_ONLY material, the report must refer to it only under
the alias:
CODEX_DEV
Forbidden in control-plane reports unless explicitly requested:
- CODEX_ONLY folder name
- full CODEX_ONLY path
- direct disclosure of CODEX_ONLY internal structure
Allowed alias when explicitly requested:
CODEX_DEV
============================================================
CHATGPT_Chat_Only
============================================================
Scope:
chat-only developer protocol material
Rule:
CHATGPT_Chat_Only material is reserved for chat interaction,
artifact-construction discipline, and developer protocol
support.
Deployment prohibition:
CHATGPT_Chat_Only material must not be included in deployment
mirrors, runtime bundles, execution kernels, or deployable
chat artifacts.
Execution prohibition:
CHATGPT_Chat_Only material must not be used to execute OPERAE,
simulate runtime behavior, provide admissibility evidence, or
replace loaded artifact content.
Permitted use:
CHATGPT_Chat_Only material may guide chat-based artifact writing,
rewriting, continuation, and evaluation only.
============================================================
Literature_PDFs
============================================================
Scope:
literature PDF storage for Codex development context
Rule:
literature PDF files themselves should be stored in
_00_Documentation/00_Sources.
This folder should contain local indexation and path
references to those PDFs unless explicitly instructed
otherwise.
literature PDFs referenced here are development references
only unless separately promoted by explicit user instruction.
Execution prohibition:
Literature PDFs in development context must not be used as
OPERA execution inputs or hidden execution authority.
They may support artifact authorship, rewriting, and
evaluation only.
============================================================
02_CONTEXT_Execution_Allowed
============================================================
Scope:
documentation material allowed to support execution context
Permitted use:
- execution-visible documentation
- control-plane-relevant context
- materials explicitly eligible for operational reference
- local indexation and path references to files in 00_Sources
Rule:
Material in this folder may be referenced in execution or
control-plane contexts when relevant and otherwise permitted
by artifact and system-index rules.
Constraint:
Even execution-allowed documentation does not execute OPERAE
by itself.
OPERA execution still requires registered, loaded, admitted
artifact content under SYSTEM_INDEX discipline.
============================================================
NON-NORMALIZATION RULE
============================================================
These folder rules classify documentation context only.
They do not:
- normalize artifact content
- alter SYSTEM_INDEX authority
- create execution permission by themselves
- promote development-only material to runtime context
- duplicate source-file authority outside 00_Sources
============================================================
ANTI-INFERENCE EXECUTION RULE
============================================================
Development-only sources may be used for:
- writing artifacts
- rewriting artifacts
- evaluating artifacts
- identifying possible inconsistencies
- supporting local development decisions
Development-only sources must not be used for:
- executing OPERAE
- simulating OPERAE
- reconstructing OPERA behavior at runtime
- filling missing OPERA logic
- bypassing SYSTEM_INDEX binding
- bypassing AREPO admission
- replacing loaded artifact content
Rationale:
Development-only sources are not deployment dependencies.
If OPERA execution relies on them, deployed behavior becomes
tied to local developer context. That makes execution behavior
non-reproducible outside the development environment and makes
bug tracking unreliable.
Final rule:
NO OPERA EXECUTION FROM DEVELOPMENT CONTEXT.
NO OPERA INFERENCE FROM DEVELOPMENT CONTEXT.
DEVELOPMENT CONTEXT SUPPORTS ARTIFACT WORK ONLY.
============================================================
END DOCUMENTATION CONTEXT FOLDER RULES
============================================================