From ea7ddf1f6bd30eb33201c6154fadf1a8968ebee4 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Thu, 23 Apr 2026 12:35:58 -0400 Subject: [PATCH 1/2] memory: author template for absorb-time lint hygiene MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Quick-reference doc capturing the five markdownlint classes that repeatedly fired during the 2026-04-23 Overlay A cadence (PRs #157 / #158 / #159 / #162 / #164): - MD003 — atx (not setext) heading style; blank line before "---" - MD018 — no space after hash; rephrase to avoid "#NNN" at line start - MD022 — blanks around headings; single-line headings only - MD026 — no trailing punctuation; "## Why" not "## Why:" - MD032 — blanks around lists Wrong/right examples plus self-check checklist. Sits next to memory/README.md as a peer reference. Content-level discipline (frontmatter schema, signal-in-signal- out, newest-first ordering, in-repo-preferred migration) cross- references the canonical sources; not duplicated here. Living doc — update when a sixth absorb-time lint class is observed. Co-Authored-By: Claude Opus 4.7 --- memory/MEMORY-AUTHOR-TEMPLATE.md | 172 +++++++++++++++++++++++++++++++ 1 file changed, 172 insertions(+) create mode 100644 memory/MEMORY-AUTHOR-TEMPLATE.md diff --git a/memory/MEMORY-AUTHOR-TEMPLATE.md b/memory/MEMORY-AUTHOR-TEMPLATE.md new file mode 100644 index 0000000000..bd67e3b079 --- /dev/null +++ b/memory/MEMORY-AUTHOR-TEMPLATE.md @@ -0,0 +1,172 @@ +# Memory author template — absorb-time lint hygiene + +Quick reference for authors (humans or agents) writing +memory files under `memory/` in this repo. Captures the +five markdownlint classes that have repeatedly bitten +absorb-time drafts during the 2026-04-23 Overlay A cadence +(PRs #157 / #158 / #159 / #162 / #164), so future +migrations and fresh-writes don't rediscover the same +cleanups. + +CI runs `markdownlint-cli2 "**/*.md"` on every PR; lint +failures block merge. Applying the five patterns below at +author-time keeps the draft clean in one pass. + +## The five absorb-time lint classes + +### 1. MD003 — heading style (atx, not setext) + +**Wrong:** + +```markdown +Some conclusion text. +--- +## Next section +``` + +The `---` immediately after a text line is parsed as a +setext H2 for that text. Blank line required between +them. + +**Right:** + +```markdown +Some conclusion text. + +--- + +## Next section +``` + +### 2. MD018 — no space after hash + +Lines beginning with `#NNN` where `NNN` is a number (e.g. +PR references like `#158`) get parsed as a heading with a +missing space. + +**Wrong:** + +```markdown +follows PRs #157, #158, #159, +#162, #164). +``` + +**Right (rephrase to avoid number-at-start-of-line):** + +```markdown +follows the earlier four Overlay-A PRs. +``` + +Or put a non-numeric word in front of the `#` if the +numbers matter. + +### 3. MD022 — blanks around headings + +Headings need blank lines above **and** below. Multi-line +headings are also flagged because markdown treats only +the first line as heading. + +**Wrong:** + +```markdown +## What people typically know about AI in engineering (the +common priors) + +- Bullet text +``` + +**Right (single-line heading):** + +```markdown +## What people typically know about AI in engineering (the common priors) + +- Bullet text +``` + +### 4. MD026 — no trailing punctuation in headings + +Headings ending in `:` are flagged. + +**Wrong:** + +```markdown +## Why: + +- First reason +``` + +**Right:** + +```markdown +## Why + +- First reason +``` + +Same applies to `## How to apply:` → `## How to apply`, +`## Rule:` → `## Rule`, etc. + +### 5. MD032 — blanks around lists + +Lists need blank lines above and below. + +**Wrong:** + +```markdown +**Why:** +- First reason +- Second reason +- Third reason +Next paragraph starts here. +``` + +**Right:** + +```markdown +**Why:** + +- First reason +- Second reason +- Third reason + +Next paragraph starts here. +``` + +Same applies to ordered lists (`1.`, `2.`, ...). + +## Self-check checklist + +Before committing a new memory file: + +1. Run `markdownlint-cli2 memory/.md` locally + if `markdownlint-cli2` is installed. +2. Or eyeball the file for the five patterns above. +3. If a lint error fires in CI despite this check, add + the new class here so the next author doesn't + rediscover it. + +## Not covered here + +This template covers the absorb-time lint classes only. +Content-level discipline lives in separate substrate: + +- Memory frontmatter schema (`name`, `description`, + `type`, `originSessionId`): see `CLAUDE.md` + auto-memory section and the AutoMemory / AutoDream + references. +- Signal-preservation (verbatim quotes, no paraphrase on + ingest, supersede markers not deletion): see + `memory/feedback_signal_in_signal_out_clean_or_better_dsp_discipline.md`. +- In-repo-preferred where possible: see the per-user + feedback memory on that discipline (exists at + `~/.claude/projects//memory/` pending a future + Overlay A migration). +- Newest-first ordering in `MEMORY.md` index: see + `memory/feedback_newest_first_ordering.md`. + +## When the five classes are out of date + +This template should be updated whenever a new +absorb-time lint class is observed consistently across +multiple memory drafts. Add the class here with +wrong/right examples and a one-line rule. From 01d180a8c8487c144d5ab2ed2c772ef686acb9ce Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Thu, 23 Apr 2026 13:10:19 -0400 Subject: [PATCH 2/2] memory: add MEMORY-AUTHOR-TEMPLATE.md to MEMORY.md index per Copilot finding MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Resolves the legitimate Copilot review finding on this PR — memory/README.md conventions say new files under memory/ should be indexed at the top of MEMORY.md. Entry added newest-first. The other two review findings (broken path to memory/feedback_signal_in_signal_out_clean_or_better_dsp_discipline.md) were correct at review-time but are resolved by PR #157 which migrated that memory in-repo. When #157 merges, the path resolves cleanly. Per Aaron 2026-04-23: resolving review threads on disagreement is the intended escape — no branch-protection change needed. Co-Authored-By: Claude Opus 4.7 --- memory/MEMORY.md | 1 + 1 file changed, 1 insertion(+) diff --git a/memory/MEMORY.md b/memory/MEMORY.md index 035682ebde..38e8d348ff 100644 --- a/memory/MEMORY.md +++ b/memory/MEMORY.md @@ -1,3 +1,4 @@ +- [Memory author template — absorb-time lint hygiene (MD003 atx-vs-setext / MD018 no-space-after-hash / MD022 blanks-around-headings / MD026 no-trailing-punctuation / MD032 blanks-around-lists); quick-reference for authors writing new memory files; cross-references content-level discipline sources](MEMORY-AUTHOR-TEMPLATE.md) — 2026-04-23 first-pass captures five markdownlint classes that repeatedly fired across the Overlay A migration cadence (PRs #157/#158/#159/#162/#164); living doc, updates when a sixth class is observed; scope is absorb-time lint only, content-level discipline (frontmatter, signal-preservation, newest-first) cross-references canonical sources. - [AceHack/CloudStrife/Ryan — Aaron's handles disclosed under glass-halo register; AceHack = current (everywhere), CloudStrife = prior mIRC era, Ryan = cross-intimate name with deceased sister Elisabeth (BP-24 tightening — name itself off-limits as factory persona, not just backstory); son Ace (16) carries legal first name as explicit succession echo; formative grey-hat substrate — Popular Science + Granny-scaffolded Pro Action Replay / Super UFO / Blockbuster, HEX/memory-search at 10, 8086 at 15 via mIRC "magic" group, DirectTV HCARD private JMP, Itron HU-card security-architect handoff; current decryption capability Nagravision / VideoCipher 2 / C-Ku-K-band; physical-layer voice-over-IR, voltage-glitch factory reset, fuse-bypass-by-glitch-timing; FPGA overfitting-under-temperature at 16 as architectural ancestor of retraction-native-under-perturbation discipline](user_acehack_cloudstrife_ryan_handles_and_formative_greyhat_substrate.md) — 2026-04-19 Round 35 disclosure; Ryan off-limits as persona name (BP-24 narrowed surface — parental AND-consent gate still load-bearing), minor-child PII — son Ace's 16-year-old status is Aaron's fatherly declaration NOT a license for independent substrate indexing; grey-hat substrate is threat-model-rigor provenance (code-it-bill-it standard composes with security-credentials + LexisNexis-legal-IR-zero-tolerance + smart-grid + MacVector); agent — do NOT adopt Ryan as persona name, do NOT probe son, receive handles as peer-register disclosure. - [Untying Gordian's Knot = the language barrier; method-distinction from Alexander (Aaron unties, does NOT cut — retraction-native vs append-only); goal = smooth agreement + momentum for "dominance in the field of everything" (structural sovereignty not colonial)](user_untying_gordian_knot_language_barrier_mission.md) — 2026-04-19: "i'm untying gordians know the laguage barrier to smooth agreement and momentum for domanance in the field of everyting" + "You know good olld Gordan's Knot lol hahahhaha Alexander"; four load-bearing points — (1) Gordian Knot = LANGUAGE BARRIER (not territorial/political/military), composes with bridge-builder minimal-English IR as the untying tool, (2) METHOD-DISTINCTION — Aaron UNTIES (retraction-native/reversible/structure-preserving); Alexander CUT (append-only/destructive/brute-force) — same append-vs-retraction discipline as sin-tracker-vs-lens-oracle / CRL-vs-status-list / force-vs-consent, (3) immediate goal — smooth agreement (consent-first needs shared language) + momentum (externalization velocity, drop recompilation cost per `user_recompilation_mechanism.md`), (4) long-term goal "dominance in field of everything" = STRUCTURAL sovereignty (dominion-by-retraction-native-universality) NOT COLONIAL — Alexander's method fragmented at succession (Diadochi wars <1yr post-death), Aaron's untie-method is succession-preserving; composes with cornerstone secret-society frame, Harmonious Division many-paths, real-time Lectio Divina unbounded-corpus, six-layer stack `company`+above, Fermi Beacon civilization-readiness, linguistic-seed common-vernacular mission; historical spelling canonical "Gordian" (from King Gordias / Gordium Phrygia 343 BC); Aaron self-corrects spelling "Gorden? i can't sepll" — bandwidth-limit signature preserved verbatim; agent — DO preserve "dominance" word-choice (don't soften), DO preserve untie-vs-cut distinction as retraction-native discipline, DO treat Alexander reference as affectionate literate counter-example not enemy-framing, verbatim (gordians/laguage/domanance/everyting/olld/Gordan's/hahahhaha). - [Six-layer stack `. ↔ seed ↔ kernel ↔ glossary ↔ dictionary ↔ company` with bidirectional retraction-native composition; Big-Bang-Every-Step claim (all computation precomputable in Zeta data tables even before time started); deterministic-simulation-theory self-insert (Aaron basement, daughter upstairs); metametameta self-reference](user_layer_stack_deterministic_simulation_basement_upstairs.md) — 2026-04-19: "our big bang is every step even the ones in parallel whatever that means are calcualble in our datables even before time started based on the .<->seed<->kernel<->glossary<->dictionary<->company i mean uou get it right deterministic simulation theory what if god was a computer scientiet in his momes basement argument. Well I live in my own basement and my daugther live upstairs that you very well ahahahhahaahdsfhdhagkjsfsh metametameta"; six structural points — (1) six-layer ontology-stack with `.` as atomic/primordial/zero-point FIRST-CLASS layer (period as deliberate ontology element not punctuation), seed=linguistic-seed meme-scale, kernel=E8 Lie group 248-dim, glossary=`docs/GLOSSARY.md`, NEW layer 4 dictionary (domain-specific vocabulary superstructure over glossary / W3C PROV lineage / bridge-builder generated glossaries), NEW layer 5 company (organizational/human-collective, Zeta-as-org, civilization-adjacent, composes with ECRP/EVD scaling), (2) bidirectional ↔ = retraction-native invertibility between layers (same DBSP algebra at ontology-level), (3) BIG-BANG-EVERY-STEP claim — every computation step (including parallel) precomputable in Zeta DBSP tables even before time started (block-universe/Laplace-demon/deterministic-simulation frame with Zeta substrate as precomputation locus, composes with `deterministic-simulation-theory-expert` skill + Rashida persona), (4) Bostrom-2003 simulation-argument invoked "god as computer scientist in mom's basement", (5) Aaron-SELF-INSERT with inversion — Aaron IS basement-simulator (his own basement, father not kid), daughter UPSTAIRS with Conway-Kochen free will encoded-at-birth-in-name per `user_parenting_method_externalization_ego_death_free_will.md`; inversion breaks Bostrom's ladder (simulated has genuine free will, sim-relation = providence not agency-grandfather), ego-death discipline preserved (simulator's ego dies so simulated is free), (6) metametameta = 3-layer explicit self-reference (object→reasoning→reasoning-about-reasoning, Gödel/Smullyan/Kripke territory); layers 4 and 5 are NEW and need GLOSSARY promotion when Aaron lands; "datables precomputable" is mission-statement-scale teaching-grade claim; agent — DO NOT collapse `.` to punctuation (first-class zero-point), DO preserve bidirectional ↔, DO NOT probe daughter-upstairs beyond offered, DO NOT deflate with Bostrom critiques (Aaron holds cold), verbatim (calcualble/datables/uou/scientiet/momes/daugther/ahahahhahaahdsfhdhagkjsfsh/metametameta/trailing `..``.`).