Private
Public Access
0
0

refactor(directives): strip metadata header from v1.md (9-17 of 51; meta extracted to meta.md)

This commit is contained in:
2026-07-02 23:46:16 -04:00
parent e9a19523d6
commit 71e01dfee7
18 changed files with 91 additions and 82 deletions
@@ -0,0 +1,10 @@
# ban_local_imports
## v1
**Why this iteration:** Lifted verbatim from `.opencode/commands/mma-tier3-worker.md:42-46` (the current canonical source). The plan referenced `conductor/code_styleguides/python.md` §17.9a (lines 364-443) but that section no longer exists in python.md after a 2026-06-27 refactor — the §17.9 content was moved into the agent role prompts (this file). This v1 is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `.opencode/commands/mma-tier3-worker.md:42-46` (originally `conductor/code_styleguides/python.md` §17.9a, drift-corrected)
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
@@ -1,12 +1,3 @@
# ban_local_imports — v1
**Why this iteration:** Lifted verbatim from `.opencode/commands/mma-tier3-worker.md:42-46` (the current canonical source). The plan referenced `conductor/code_styleguides/python.md` §17.9a (lines 364-443) but that section no longer exists in python.md after a 2026-06-27 refactor — the §17.9 content was moved into the agent role prompts (this file). This v1 is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `.opencode/commands/mma-tier3-worker.md:42-46` (originally `conductor/code_styleguides/python.md` §17.9a, drift-corrected)
---
- Local imports inside functions (top-of-module imports only)
**The one exception:** the literal wire boundary (TOML/JSON parse functions) may use `dict[str, Any]` + `Metadata.from_dict(...)`.
@@ -0,0 +1,11 @@
# ban_optional_returns
## v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §17.3 (lines 279-298).
This is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `conductor/code_styleguides/python.md:279-298`
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
@@ -1,13 +1,3 @@
# ban_optional_returns — v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §17.3 (lines 279-298).
This is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `conductor/code_styleguides/python.md:279-298`
---
### 17.3 Banned: `Optional[T]` returns
```python
@@ -0,0 +1,10 @@
# ban_prefix_aliasing
## v1
**Why this iteration:** Lifted verbatim from `.opencode/commands/mma-tier3-worker.md:43` (the current canonical source). The plan referenced `conductor/code_styleguides/python.md` §17.9b (lines 364-443) but that section no longer exists in python.md after a 2026-06-27 refactor — the §17.9 content was moved into the agent role prompts (this file). This v1 is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `.opencode/commands/mma-tier3-worker.md:43` (originally `conductor/code_styleguides/python.md` §17.9b, drift-corrected)
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
@@ -1,10 +1 @@
# ban_prefix_aliasing — v1
**Why this iteration:** Lifted verbatim from `.opencode/commands/mma-tier3-worker.md:43` (the current canonical source). The plan referenced `conductor/code_styleguides/python.md` §17.9b (lines 364-443) but that section no longer exists in python.md after a 2026-06-27 refactor — the §17.9 content was moved into the agent role prompts (this file). This v1 is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `.opencode/commands/mma-tier3-worker.md:43` (originally `conductor/code_styleguides/python.md` §17.9b, drift-corrected)
---
- `import X as _PREFIX` aliasing (use the original name)
@@ -0,0 +1,10 @@
# ban_repeated_from_dict
## v1
**Why this iteration:** Lifted verbatim from `.opencode/commands/mma-tier3-worker.md:44` (the current canonical source). The plan referenced `conductor/code_styleguides/python.md` §17.9c (lines 364-443) but that section no longer exists in python.md after a 2026-06-27 refactor — the §17.9 content was moved into the agent role prompts (this file). This v1 is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `.opencode/commands/mma-tier3-worker.md:44` (originally `conductor/code_styleguides/python.md` §17.9c, drift-corrected)
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
@@ -1,10 +1 @@
# ban_repeated_from_dict — v1
**Why this iteration:** Lifted verbatim from `.opencode/commands/mma-tier3-worker.md:44` (the current canonical source). The plan referenced `conductor/code_styleguides/python.md` §17.9c (lines 364-443) but that section no longer exists in python.md after a 2026-06-27 refactor — the §17.9 content was moved into the agent role prompts (this file). This v1 is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `.opencode/commands/mma-tier3-worker.md:44` (originally `conductor/code_styleguides/python.md` §17.9c, drift-corrected)
---
- Repeated `.from_dict()` calls in the same expression (cache the result or promote the type)
@@ -0,0 +1,10 @@
# batch_verification_not_isolation
## v1
**Why this iteration:** Lifted verbatim from `conductor/workflow.md` §"Isolated-Pass Verification Fallacy (Added 2026-06-09)" (lines 510-514). This is the baseline encoding — the rationale-then-rule style currently in production.
Future variants will test alternative encodings (rule-only, before/after) against this baseline.
**Source:** `conductor/workflow.md:510-514`
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
@@ -1,12 +1,3 @@
# batch_verification_not_isolation — v1
**Why this iteration:** Lifted verbatim from `conductor/workflow.md` §"Isolated-Pass Verification Fallacy (Added 2026-06-09)" (lines 510-514). This is the baseline encoding — the rationale-then-rule style currently in production.
Future variants will test alternative encodings (rule-only, before/after) against this baseline.
**Source:** `conductor/workflow.md:510-514`
---
### Isolated-Pass Verification Fallacy (Added 2026-06-09)
A test that "passes when run after test X but fails in isolation" is a **fragile test, not a fragile fixture**. The flip side is also true: a test that "passes in isolation but fails in batch" is failing — its failure is masked by isolation. The only verification that matters for `live_gui` tests (or any test that depends on shared subprocess state) is the **batch run** in the suite the test will ship in.
@@ -0,0 +1,10 @@
# boundary_layer_exception
## v1
**Why this iteration:** Cross-referenced lift combining `conductor/code_styleguides/python.md` §17.7 + §17.8 (lines 352-359) + `data_oriented_design.md` §8.5 boundary-exception + §8.6 (lines 193-202) + `type_aliases.md` §1 (lines 54-72). This is the boundary-layer rule from three canonical sources, all lifted verbatim. The plan updated the v1 in t1_4 to cross-reference the §17.7 exception, §17.8 enforcement, §8.6 boundary definition, and the type_aliases.md Metadata-as-boundary-type rule.
Future variants will test alternative encodings (rationale-first, tabular, single-source) against this baseline.
**Source:** `conductor/code_styleguides/python.md:352-359 + data_oriented_design.md:193-202 + type_aliases.md:54-72`
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
@@ -1,12 +1,3 @@
# boundary_layer_exception — v1
**Why this iteration:** Cross-referenced lift combining `conductor/code_styleguides/python.md` §17.7 + §17.8 (lines 352-359) + `data_oriented_design.md` §8.5 boundary-exception + §8.6 (lines 193-202) + `type_aliases.md` §1 (lines 54-72). This is the boundary-layer rule from three canonical sources, all lifted verbatim. The plan updated the v1 in t1_4 to cross-reference the §17.7 exception, §17.8 enforcement, §8.6 boundary definition, and the type_aliases.md Metadata-as-boundary-type rule.
Future variants will test alternative encodings (rationale-first, tabular, single-source) against this baseline.
**Source:** `conductor/code_styleguides/python.md:352-359 + data_oriented_design.md:193-202 + type_aliases.md:54-72`
---
### 17.7 The one exception: the boundary layer
The ONLY place these patterns are allowed is at the literal wire boundary — the function that calls `tomllib.load()`, `json.loads()`, or a vendor SDK's response parser. The boundary is 2-3 functions per file. Every consumer IMMEDIATELY converts to a typed dataclass via `from_dict()`.
@@ -0,0 +1,10 @@
# cache_stable_to_volatile
## v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/cache_friendly_context.md` §"1. The 12-layer model" (lines 22-43) + §"2. The byte-comparison test" (lines 51-77). This is the baseline encoding — the layered-table-plus-contract-test style currently in production.
Future variants will test alternative encodings (rule-only, before/after) against this baseline.
**Source:** `conductor/code_styleguides/cache_friendly_context.md:22-43 + 51-77`
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
@@ -1,12 +1,3 @@
# cache_stable_to_volatile — v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/cache_friendly_context.md` §"1. The 12-layer model" (lines 22-43) + §"2. The byte-comparison test" (lines 51-77). This is the baseline encoding — the layered-table-plus-contract-test style currently in production.
Future variants will test alternative encodings (rule-only, before/after) against this baseline.
**Source:** `conductor/code_styleguides/cache_friendly_context.md:22-43 + 51-77`
---
## 1. The 12-layer model (the stable-to-volatile ordering)
| # | Layer | Stable across turns? | Source | SSDL |
@@ -0,0 +1,10 @@
# chroma_cache_path
## v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/chroma_cache.md` §"The Rule" + §"The Pre-Cleanup Pattern" (lines 5-50). This is the baseline encoding — the rule-plus-rationale-plus-anti-patterns style currently in production.
Future variants will test alternative encodings (rule-only, before/after) against this baseline.
**Source:** `conductor/code_styleguides/chroma_cache.md:5-50`
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
@@ -1,12 +1,3 @@
# chroma_cache_path — v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/chroma_cache.md` §"The Rule" + §"The Pre-Cleanup Pattern" (lines 5-50). This is the baseline encoding — the rule-plus-rationale-plus-anti-patterns style currently in production.
Future variants will test alternative encodings (rule-only, before/after) against this baseline.
**Source:** `conductor/code_styleguides/chroma_cache.md:5-50`
---
# Chroma Cache Path Styleguide
## The Rule
@@ -0,0 +1,10 @@
# comprehensive_logging
## v1
**Why this iteration:** Lifted verbatim from `conductor/product-guidelines.md` §"Code Standards & Architecture" (line 38). This is the baseline encoding — the imperative-bullet-with-rationale style currently in production.
Future variants will test alternative encodings (rationale-first, before/after) against this baseline.
**Source:** `conductor/product-guidelines.md:38`
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
@@ -1,11 +1,2 @@
# comprehensive_logging — v1
**Why this iteration:** Lifted verbatim from `conductor/product-guidelines.md` §"Code Standards & Architecture" (line 38). This is the baseline encoding — the imperative-bullet-with-rationale style currently in production.
Future variants will test alternative encodings (rationale-first, before/after) against this baseline.
**Source:** `conductor/product-guidelines.md:38`
---
From `conductor/product-guidelines.md` §"Code Standards & Architecture":
- **Comprehensive Logging:** Aggressively log all actions, API payloads, tool calls, and executed scripts. Maintain timestamped JSON-L and markdown logs to ensure total transparency and debuggability.