Per user 2026-06-23 feedback on the pilot output:
1. **Decompress names AND expressions** (in prompt_template.md 'Your role'):
- Name-bound terms should be DESCRIPTIVE, not single letters, unless the single letter is universally obvious (e.g., x for input, f for function)
- Examples: p(X₁, ..., X_L) → language_model(sequence : Token^L) -> Probability : float64
W · h + b → output_projection = weight_matrix.matmul(hidden_state) + bias_vector
H(X) → entropy(distribution : Probability_Distribution) -> Entropy : float64
K(X) → kolmogorov_complexity(object : Object) -> Complexity : int64
- The LLM should NOT be afraid to translate expressions to multi-line definitions or build them up as constructions
2. **§9 Operator reference (indexed)** in report.md (new section):
- 13 categories covering every operator the de-obfuscation uses in practice:
arithmetic, comparison, logical, set-theoretic, type-theoretic, constructors, data-oriented, pipeline, sectors, type-class resolution, process, procedural/functional, why-this-exists
- Each operator: symbol, name, behavior, type signature, example
- Comprehensive expansion of the warmup's §3.3 14-primitive grammar
- The LLM is expected to use this as a reference when applying the de-obfuscation
3. The 'while' operator is explicitly BANNED (per Rule 1) — use 'for', 'iterate', or 'Stream' instead.
These 2 refinements will be propagated forward:
- prompt_template.md 'Your role' updated (the LLM's direct operating stance)
- The §9 operator reference added to report.md (the warmup's design doc; the lexicon's source)
- Phase 3 (apply) TIER2_STARTER will reference both
Per user 2026-06-23 review: the Tier 2 over-cited the user's specific implementations (Sectored Language V1, LLM session patterns, GA reinterpretations, classical Greek/Latin) as the canonical scheme, when they should be optional output conventions.
Changes:
1. report.md §3.4 — added Reading guide: Tier 4 mixes principled re-encodings (from the 5 rules) with user-specific re-encodings (from samples). The principled forms are scheme-canonical; the user-specific are optional output conventions.
2. report.md §3.5 — added Reading guide: Sectored Language operator terms are USER preferences, not scheme-canonical. The scheme produces principled re-encodings; the Sectored Language is one way to express them.
3. report.md §4.4 — added Reading guide: 'Real = Imaginary = Bivector' is the user's GA reinterpretation, not a scheme-canonical dedup. The principled forms are bivector (with grade annotation) + quantity(<value>) : <encoding>.
4. report.md §6.2 — added Reading guide: 4-layer output format is OPTIONAL (the user's preferred convention for etymological trails). The scheme's baseline is the 3-layer format.
5. prompt_template.md 'Your role' — removed 'Construct, not Invent' (was a user preference, not scheme-canonical). Added a 'Scheme-canonical vs. user-specific' bullet that makes the distinction explicit.
6. prompt_template.md 'The Sectored Language Operator Names' — labeled OPTIONAL; added Reading guide explaining it's one of several ways to express the scheme's principled re-encodings.
7. prompt_template.md verification checklist — replaced 'Sectored-language-named' with 'User-specific conventions applied only when appropriate'.
Phase 1 (lexicon child) will formalize this distinction further (e.g., moving §3.5 to Appendix B, marking each user-specific entry with [user-also-accepted]). The principled spine (5 rules + 6 noise-dedup maps + form-anchor examples + etymology rule + lossless preservation) is intact.
ed