ed/manual_slop
Private
Public Access
0
0
Fork 0
Code Activity

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

Browse Source
This commit is contained in:
ed
2026-07-02 23:46:16 -04:00
parent e9a19523d6
commit 71e01dfee7
18 changed files with 91 additions and 82 deletions
Download Patch File Download Diff File Expand all files Collapse all files
conductor/directives/boundary_layer_exception/meta.md
+10
View File
@@ -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)
conductor/directives/boundary_layer_exception/v1.md
-9
View 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()`.