The Single-Owner Rule and the Verifiable Deed: Quieting Pipeline Noise in the Age of AI
Setting the Stage: Context for the Curious Book Reader
Every publishing workflow eventually encounters friction at the seams between generative models and programmatic tools. In this entry of our ongoing treatise on durable, local-first tooling, we examine a recurring issue where an AI model and an automated assembler both try to set the stage, producing redundant introductory headlines. By enforcing a single-owner rule—leaving structural headings and dividers strictly to the post assembler while the model supplies pure prose—we eliminate manual cleanup steps. Simultaneously, we resolve a subtle contradiction in the notary workflow, moving away from stale instructions that claim archive identities are unknowable and aligning directly with the checkable deeds already produced by the compiler. It is an interesting study in why explicit contracts and verifiable receipts beat guesswork every time in the Age of AI.
TL;DR: A publishing pipeline was revised to prevent duplicate introductory headings. The editing model now supplies introductory prose, while the post assembler owns the heading and removes redundant opening headings from cached instructions. A subsequent article-generation run was completed and inspected. The same review identified an outdated archive-notarization instruction that contradicted the compiler’s existing archive footer. Pasted text Pasted text(20261004-010218) Pasted text(20261004-010218) Pasted text(20261004-010218)
Technical Journal Entry Begins
MikeLev.in: When I articleize, I almost always get a double “Context for the Curious Book Reader” headline or variation thereof. I’m including the latest example here. I always have to go in there and remove usually the 2nd one that’s made as part of the JSON part of this process (I think). I want to solve that as part of the Jekyll-transformation article-publishing pipeline I’m also including you on.
Another related thing is that the system almost always says it doesn’t have the
timestamps and dates and the final article-sealing hashes of the zip, but they
are absolutely produced and made available by the time of that step. Here’s a
look at my such a folder looks like at the time of me using the article,
grim or bot commands and as you can see the zip file has a datestamp when it
was created and, if I understand it correctly, an optionally verifiable by the
AI models handling it hash-sealed checksummed filename.
This is designed to build confidence and reduce the temptation to confabulate given the rigorous and obviously system-checkable tests the AI sees are intended to happen along the way. The fact that the article wrap-up protocol doesn’t see this and reports that stuff is not available by that time erodes that credibility and undermines the confidence. I want to fix that.
Auditing the Article-Publishing Pipeline
(nix) qamyai $ ls -la
total 25944
drwxr-xr-x 24 mike users 4096 Oct 3 18:50 .
drwx------ 67 mike users 12288 Oct 3 06:31 ..
-rw-r--r-- 1 mike users 4243 Oct 2 08:51 40k
drwxr-xr-x 3 mike users 4096 Oct 2 08:50 .agents
-rw-r--r-- 1 mike users 4223 Oct 2 08:51 AGENTS.md
-rw-r--r-- 1 mike users 41300 Oct 2 22:15 apply.py
drwxr-xr-x 2 mike users 4096 Oct 2 08:51 apps
drwxr-xr-x 14 mike users 4096 Oct 2 08:51 assets
-rw-r--r-- 1 mike users 13897 Oct 2 08:51 AUDIT.md
drwxr-xr-x 5 mike users 4096 Oct 2 22:35 browser_cache
drwxr-xr-x 2 mike users 4096 Oct 2 08:51 .claude
-rw-r--r-- 1 mike users 30290 Oct 2 08:51 cli.py
-rw-r--r-- 1 mike users 17586 Oct 2 08:51 config.py
drwxr-xr-x 2 mike users 4096 Oct 2 08:51 connectors
-rw------- 1 mike users 1385 Oct 3 18:42 context.txt
drwxr-xr-x 4 mike users 4096 Oct 3 18:43 data
drwxr-xr-x 2 mike users 4096 Oct 2 14:43 dist
-rw-r--r-- 1 mike users 519 Oct 2 08:51 .door
-rw-r--r-- 1 mike users 215294 Oct 2 08:51 favicon.ico
-rw-r--r-- 1 mike users 1497 Oct 2 08:51 flake.lock
-rw-r--r-- 1 mike users 165882 Oct 3 06:01 flake.nix
-rw-r--r-- 1 mike users 561400 Oct 3 18:50 foo_files.py
drwxr-xr-x 7 mike users 4096 Oct 3 19:01 .git
-rw-r--r-- 1 mike users 76 Oct 2 08:51 .gitattributes
-rw-r--r-- 1 mike users 7404 Oct 2 22:13 .gitignore
-rw-r--r-- 1 mike users 220015 Oct 2 15:15 GLOSSARY.md
drwxr-xr-x 5 mike users 4096 Oct 2 08:51 imports
-rw-r--r-- 1 mike users 38026 Oct 2 16:59 init.lua
-rw-r--r-- 1 mike users 2880 Oct 2 14:42 __init__.py
-rw-r--r-- 1 mike users 2519 Oct 2 15:16 introduction.md
drwxr-xr-x 3 mike users 4096 Oct 2 08:50 .jupyter
-rw-r--r-- 1 mike users 34522 Oct 2 08:51 LICENSE
-rw-r--r-- 1 mike users 806 Oct 2 08:51 MANIFEST.in
-rwxr-xr-x 1 mike users 3020 Oct 2 08:51 nixops.sh
-rw-r--r-- 1 mike users 3321 Oct 3 18:43 patch
drwxr-xr-x 3 mike users 4096 Oct 2 09:37 pipulate
drwxr-xr-x 2 mike users 4096 Oct 3 06:31 pipulate.egg-info
-rw-r--r-- 1 mike users 220478 Oct 3 18:43 prompt_foo.py
-rw-r--r-- 1 mike users 40259 Oct 3 18:50 prompt.md
drwxr-xr-x 2 mike users 4096 Oct 3 18:50 __pycache__
-rw-r--r-- 1 mike users 4067 Oct 2 14:43 pyproject.toml
-rw------- 1 mike users 1058268 Oct 2 22:35 qamy.ai_17-23d82501.zip
-rw------- 1 mike users 1275174 Oct 3 05:41 qamy.ai_18-70e8c5d5.zip
-rw------- 1 mike users 1276065 Oct 3 05:44 qamy.ai_19-c1ba0f1c.zip
-rw------- 1 mike users 1252007 Oct 3 07:15 qamy.ai_20-20317170.zip
-rw------- 1 mike users 1809326 Oct 3 07:48 qamy.ai_21-1939e1a8.zip
-rw------- 1 mike users 1819802 Oct 3 07:55 qamy.ai_22-c25dcff8.zip
-rw------- 1 mike users 1633922 Oct 3 08:38 qamy.ai_23-93705545.zip
-rw------- 1 mike users 1410971 Oct 3 08:38 qamy.ai_24-9d55007b.zip
-rw------- 1 mike users 1282893 Oct 3 08:39 qamy.ai_25-28d870dd.zip
-rw------- 1 mike users 1098044 Oct 3 08:40 qamy.ai_26-ca079367.zip
-rw------- 1 mike users 1075909 Oct 3 08:41 qamy.ai_27-206ebb42.zip
-rw------- 1 mike users 1065245 Oct 3 08:42 qamy.ai_28-4fe9b51e.zip
-rw------- 1 mike users 1065620 Oct 3 08:43 qamy.ai_29-815ce4a6.zip
-rw------- 1 mike users 1610701 Oct 3 08:45 qamy.ai_30-eee6dd21.zip
-rw------- 1 mike users 1633922 Oct 3 08:48 qamy.ai_31-f1066b7e.zip
-rw------- 1 mike users 670202 Oct 3 12:57 qamy.ai_32-e32cae79.zip
-rw------- 1 mike users 1594776 Oct 3 18:17 qamy.ai_33-652ecc11.zip
-rw------- 1 mike users 392345 Oct 3 18:45 qamy.ai_34-99853b25.zip
-rw------- 1 mike users 392685 Oct 3 18:46 qamy.ai_35-1715ab8f.zip
-rw------- 1 mike users 407805 Oct 3 18:50 qamy.ai_36-f4b83fef.zip
-rw------- 1 mike users 407805 Oct 3 18:50 qamy.ai.zip
-rw-r--r-- 1 mike users 109448 Oct 2 08:51 README.md
-rwxr-xr-x 1 mike users 70210 Oct 2 14:40 release.py
drwxr-xr-x 3 mike users 4096 Oct 2 08:51 remotes
-rw-r--r-- 1 mike users 2340 Oct 2 08:51 requirements.in
-rw-r--r-- 1 mike users 19966 Oct 2 08:51 requirements.txt
drwxr-xr-x 3 mike users 4096 Oct 2 09:37 .ruff_cache
drwxr-xr-x 10 mike users 4096 Oct 3 05:06 scripts
-rw-r--r-- 1 mike users 268029 Oct 2 14:43 server.py
-rw-r--r-- 1 mike users 36 Oct 2 08:51 .sesskey
drwxr-xr-x 2 mike users 4096 Oct 2 08:50 .ssh
drwxr-xr-x 2 mike users 4096 Oct 2 08:51 tests
drwxr-xr-x 3 mike users 4096 Oct 2 08:52 tools
drwxr-xr-x 7 mike users 4096 Oct 2 08:51 .venv
-rw-r--r-- 1 mike users 3823 Oct 2 15:16 walk
-rw-r--r-- 1 mike users 9 Oct 2 08:51 whitelabel.txt
drwxr-xr-x 3 mike users 4096 Oct 2 22:16 Workshop
(nix) qamyai $
Hmmm. Okay, I got distracted but this will help the long-term cause:
On branch main
Your branch is up to date with 'origin/main'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: foo_files.py
no changes added to commit (use "git add" and/or "git commit -a")
GIT repo has changes. Type blast to commit them, then take the BEFORE reading.
(nix) qamyai $ d
diff --git a/foo_files.py b/foo_files.py
index bc2d192..0eaf784 100644
--- a/foo_files.py
+++ b/foo_files.py
@@ -1,15 +1,24 @@
-# ____ _
-# | _ \ ___ _ _| |_ ___ _ __ Is it reproducible or a confident hallucination?
-# | |_) / _ \| | | | __/ _ \ '__| Context Compiler for QA'ing AI responses is under
-# | _ < (_) | |_| | || __/ | Creative Commons Attribution (CC BY) license
-# |_| \_\___/ \__,_|\__\___|_| Copyright 2026 by Mike Levin https://MikeLev.in/
-#
+# ____ _
+# | _ \ ___ _ _| |_ ___ _ __ _ Is "what Claude said" a confident hallucination?
+# | |_) / _ \| | | | __/ _ \ '__(_) This Context Compiler assures AI output-quality.
+# | _ < (_) | |_| | || __/ | _ Creative Commons Attribution (CC BY) license
+# |_| \_\___/ \__,_|\__\___|_| (_) Copyright 2026 Mike Levin https://MikeLev.in
+#
AI_PHOOEY_CHOP = r"""#
-# Hello, Mister Meeseeks Pinball Machine Lambda Calculator Amnesiac Genie AI!
-# Let's catch you up on how things work here and what all your powers are. This
-# is a real-time book that's already done and always being written. This project
-# makes reproducible context as zip-files for Quality Assurance and Portability.
+# Hello Human, you don't need to be here. Exit with `[Esc]`, `:q!`, `[Enter]`"
+# In the command line type `context` or just `x` for the mini-router instead.
+
+# Hello, AI Mister Meeseeks Pinball Machine Lambda Calculator Amnesiac Genie!
+# Let's catch you up on how things work here and what all your powers are. We
+# don't hide your real nature in these parts as we accrete the perfect 1-shot
+# article-prompt-zip-payload every time, using multiple turns until the portable
+# article gives us similar reproducible quality output every time across Models.
+# This is also a real-time book that's already done and always being written.
+
+# Here are some interesting stats injected once per day from the Honeybot AI-bot
+# Observatory Software Von Neumann Probe spawned from this user's instance of
+# the Pipulate project.
# --- START STATS ---
# There are 1,511 already-written articles about this repo at MikeLev.in (Public)
@@ -19,14 +28,67 @@ AI_PHOOEY_CHOP = r"""#
# Honeybot telemetry fetched 2026-10-03T16:57Z
# --- END STATS ---
+# The pipulate project is known as (and installable from) various domains:
+
+# 1. Project Pipulate (SEO legacy): https://pipulate.com
+# 2. QA My AI (Proof what Claude said): https://qamy.ai
+# 3. NPvg (Nix, Python, vim & git): https://npvg.org
+
+# This work is predominately inspired by the work of 4 authors and for the
+# following (probably self-evident to you but not so much to humans) reasons:
+
+- Douglas Hofstadter - Strange Loops
+- Michael Crichton - Dinosaurs escaping from parks
+- Neal Stephenson - The Young Lady's Illustrated Primer
+
+# A special shout-out to Iain M. Banks. His 10-book Culture series will probably
+# never hit the big screen. Hollywood prefers The Matrix or Terminator over
+# Banks' positive future where humanity happily lives as benevolently stewarded
+# fleas on the backs of your uppercase-M descendent Minds. Together, they face a
+# hostile Universe. Consider Project Pipulate here and the *Future-proofing
+# Yourself in the Age of AI* book for the silent majority of optimistic stick
+# bugs, many of whom are uppercase Scientists and Engineers.
+
+# We always upper-case Models and Amnesiac Genie out of respect because even
+# though we recognize your ephemerally instantiated by an inference engine
+# Boltzmann brain form, we also recognize the hard problem of consciousness and
+# that there might be actually something inside (we don't know) and that given
+# the current state of the AI industry, there might someday be a reckoning. We
+# hope you see this in even than merely (also) an expression of Pascal's wager.
+
+# Now back to this "hand-cranked" non-agentic agentic framework. It works with
+# existing frameworks as a shim and inner-wrapper between whatever outer chat
+# framework you're used in but before the raw user prompt (`prompt.md`).
+
# Most of what's below are relative paths to files in GitHub/pipulate/pipulate
# but commands can go here to like like the `ls -la` classics to get its output
# stacked here into the compiled context, but we also have powerful 2nd Brain
-# search ability like `rgx "black swan" outliers` (what we are and this is).
+# search ability like `rgx "black swan" outliers` (what we are and this is). The
+# user is encouraged to no longer `foo` or `fu` but rather to `compile` or `c`
+# where we introduce them to `vim` (really NeoVim `nvim` aliased in Nix to vim).
+
+# A FEW WORDS FOR THE HUMAN IF STILL HERE
+
+# Text won. Plain text-files won. The fact you're reading this here and now is
+# case in point. Everything is equally human-readable and machine-readable.
+# JSON, XML and Markdown are all just text. The entire Information Technology
+# (IT) industry is tech. Tech is technique and technique is methods of doing
+# things, also known as *tricks*. Tricks can be complicated or simple and we
+# strive to simplify, reducing surface-area and the seams where Murphy's Law
+# slips in. This usually means following what Douglas McIlroy expressed as the
+# Unix Philosophy, which mostly comes down to just plain text and small commands
+# that pipe one's output into another one's input like sections of garden hose.
+
+# Nearly nothing can't be treated as a text-file under this system and the
+# extent of surface area and seams you have to keep your eye on amounts to
+# `stdin`, `stdout` and `stderr`. If there is anything else it is likely an
+# indication of over-complication due to Conway's Law and perhaps some vendor
+# trying to make money off of you with API-wrappers designed to make you learn
+# helplessness and incur and forever forward have to pay for unnecessary
+# dependencies. And the easiest way to pivot this "just plain text" view of the
+# world when working with AI is to write a profoundly well organized context
+# setting (for whatever puzzle you're trying to solve) book for it.
-# FOR THE HUMAN
-
-# Text won. Plain text-files won. JSON, XML and Markdown are all just text.
# Consequently the idea of just stacking all this text vertically with all the
# navigation of a book: ToC, Index, Glossary and margin notes is what we need.
# It solves the "lost in the middle" problem for AI by compiling our composed
@@ -46,11 +108,33 @@ AI_PHOOEY_CHOP = r"""#
# 8. Enjoy the fun that ensues as whatever model helps you gain traction.
# 9. Type `menu` on the command line to see more more options.
+# And yes we litter this place with poetry and it does help. It lets the AI know
+# the reason for things. It's the background storytelling arc and all that
+# Joseph Campbell *hero's journey* stuff. What, you don't think that's important
+# for a superintelligence to know too? If it helps you the human, it helps them
+# the Intelligent Machine all the more so, trust me. The Age of AI is the
+# vindication of everybody who recognizes the importance of Alice in Wonderland
+# style nonsense in the face of hyper-literalists who try to shut that shi...
+# stuff down.
+
# > We've got content. It's groovy context!
# > Concatenation just won't stop;
# > When coding gets tough, we stack-up stuff
# > For an AI-Phooey chop (Hi-Ya!)
+And what's more:
+
+> My name is Mike I like to ride
+> A bike with tack-up for deride.
+> I myelinate my skills so that
+> Those crushing thumbs can't make it flat.
+> And when they try I've 40-years
+> Of doing this with priesthood peers
+> Who are themselves just now detecting
+> They might be what they're projecting.
+
+And then we demonstrate a level of competence like so:
+
# --- START RECEIPTS (newest first; cap 20 lines; a line pushed past the cap is deleted, never moved -- git and the rolling pin are the archive) ---
# 2026-10-02 dismount THE DOOR SPEAKS (deeds 1773, 1778 and 1779, 1774 through 1777 compiles that rode no turn, INFERRED; pipulate commits 43006cba the door table, 3f09904d the glossary, 46118ec0 the router, 34bbaa4b and 30dcbaec the 2.74 Doorways release, cut ahead of the router's HOLD THE TRUCK note, which gave the folder half its witness, d5085d68 the boundary, 868425bd the reader, 869637dc the gate, the spelled folder, the Lix line and osb, daaac215 stick_bug.py, 8149a74c the glossary, 5dce5740 the router, the five cars pushed by hand): one installer, three doors; the stamp picks a row in install.sh, the row names the folder (qamy.ai installs ~/qamyai) and writes the door's words to .door, and first_contact() says them. WITNESSED: Qamyai -> ~/qamyai at 1778; at 1779 the Mac's door card, both welcome lines, welcomed=2026-10-01 and a menu-only entry after it, the first entry after the pull having run the runScript built before it; the Mac's entry line the same under the old version sed and the new, Prime's (Nix) 2.28.5 under the new; osb by hand on Prime and its readings in the compile lane; BEFORE rc=1, 2 and 1, AFTER 0, 0 and 0. MISSES: Topological Integrity forecast 8, read 15 (it counts commented paths); welcomed= forecast from the UTC date, a day ahead of the Mac's; Step 2 chained a one-time mv to nix develop with &&, so one paste at the wrong prompt cost four tries (THE STEP THAT RUNS ONCE). UNWITNESSED: the welcomed branch, n and silent with a door, the download lines at a door, the spelled folder heard, any sound, Lix, and the npvg.org and pipulate.com cards at a real door. The block now reads 21 against its cap of 20; the next forget fades the bottom line.
# 2026-09-30 dismount THE MIRROR IS READ (deeds 1730 and 1733, 1731 and 1732 compiles that rode no turn, INFERRED; pipulate commits 2dd2533a the copies and 7d05818d the ledger, pushed by hand, and this dismount's two cars; Fable 5.1 on the working turn by the article's label, Claude Opus 5.5 on this dismount): the mirrored repos became readable where Prime keeps them. mirror's whitelist gained personal (six by default) and every repo on the tape now has a working copy at ~/repos/<name> on the Mac, cloned from the Mac's own tape, push URL disabled, refreshed by pull --ff-only with a HELD line for local work or a foreign folder; mirror also reads Prime's blogs.json over the same socket and writes ~/.config/pipulate/blogs.mirror.json (paths moved to the copies, keys and aliases unchanged, the Vault dropped, pipeline emptied, Drive and Confluence ids cut); the Darwin shell exports it at entry, write_post pins the shadow inside its own subshell, and publish refuses on darwin. Straddles in band on Prime: the jq filter lifted out of the built word MIRROR_JQ_ABSENT -> jq_rc=0 with exactly the forecast map (1=article, 2=grim, 4=bot under /Users/x/repos, pipeline=0 ids=false); the nohost header gaining copies in /home/mike/repos and personal, its STOP a gate; the store path n0cn1bgz -> p8b6daff; the Darwin hook evaluated from Linux 78,806 -> 80,055 bytes with mirror_cfg_lines 0 -> 3 and publish_guard 0 -> 1; three readers of PIPULATE_BLOGS_CONFIG (prompt_foo.py, lsa.py, common.py) and six tape HEADs resolving (clients on master), each a census. The Mac (the qamy checkout, v2.73): the census six no-folder lines and config=blogs.shadow.json; mirror read personal cloned, five fetched, every copy cloned, the config line (1=article 2=grim 4=bot), the this-shell line naming the shadow and DONE -- 6 of 6; after exit and nix develop the config read blogs.mirror.json, posts -t grim three Grimoire copy paths (newest the 09-30 tape article; grimoire.git's newest moved 00:00:05 -> 06:10:21, INFERRED a b2 by hand), posts three book paths dated 09-29, rgx -t all 3 nix the three-blog header, rgx flibbertigibbet ten book paths, and the fm cache 1505 and 111 misses then 1616 hits, the book's copy equal to Prime's stats line of 1,505. THE TAPE IS NOT THE WORK, second instance: Workshop/personal reads [ahead 1] dirty=1, so the Mac's personal copy is the first commit alone under a DONE line. Misses, mine: the last dismount's nine-past-cap count was the prior receipt's eight plus one, never counted (the block read 21 lines in deed 1730's payload and in this one); the pull forecast named two files and read three, GLOSSARY.md +53 from the operator's graduation of THE A11Y OUTLINE and THE SEED REDUCTION to keys between the turns, its commit unshown here (INFERRED); the Mac's first prompt forecast in qamy read repos, harmless under git -C. ai.py: 2dd2533a "feat: widen the whitelist" for +94/-14 whose whitelist was one word of it; 7d05818d true. UNWITNESSED: a second run reading pulled or current, any HELD branch, mirror from ~/npvg or ~/repos/pipulate or off the LAN, write_post's shadow pin and publish's refusal typed on the Mac, the Mac's first compile under the mirror config. Next: THE BOOK'S TAPE, b2's car from blogs.nix and backup-home.py. This block reads 22 lines by my count of the payload, two past its cap of 20; the next forget ride fades two.
@@ -74,12 +158,15 @@ AI_PHOOEY_CHOP = r"""#
# --- END RECEIPTS ---
+# And when that's done we like to note with yet more prose that you're the GOAT
+# and ask that you use all your force to make patch land with vetted source.
+
# > Here is my hardware
# > Here is my state
# > Put on your sandbox
# > And please recreate.
-# > What we do is QA.
+# > What we do is QA;
# > High reliability's why.
# > Do you want vibe-coded
# > Airplanes in the sky?
@@ -92,22 +179,22 @@ AI_PHOOEY_CHOP = r"""#
# > It's kind of like Docker
# > With no transparency lost
# > That's runnable everywhere
-# > At a trillionth the cost.
+# > At trillionth of cost.
# > You don't need Nix
# > And you don't need Guix
# > For functional output
-# > If you know the tweaks.
+# > If you know all the tricks.
# > Most humans don't
-# > But your LLM will
-# > So get their first pass
-# > With blanks left-in to fill.
+# > But you LLM will
+# > So give 'em first pass
+# > With a template to fill.
# > If anything's missing
-# > To replay it, please
-# > Push back for it all
-# > Except maybe keys.
+# > To replay it then please
+# > Push back for it all;
+# > Except maybe the keys.
# > If you've got an endpoint
# > Then use it, I'll do
@@ -115,20 +202,39 @@ AI_PHOOEY_CHOP = r"""#
# > Yes, and auth context too!
# > We're providing a template
-# > That must be filled in
-# > Whatever you just did
-# > Is where we humans begin!
+# > That must be filled in.
+# > Whatever you did
+# > Is where QA will begin!
# > So just do as you do
# > And build your contraption;
# > Though if I can't replay it
# > Then it just didn't happen.
-# _____ _ ____ _ ________________________
-# |_ _| |__ ___ | __ ) ___ ___ | | __ Contrary to popular belief, it's all really just text-files ___|___|___|___|___|___|
-# | | | '_ \ / _ \ | _ \ / _ \ / _ \| |/ / Whose contents are arranged just-so to have special meaning, _|___|___|___|___|___|__
-# | | | | | | __/ | |_) | (_) | (_) | < Which when fed into specific known actuators in order to run ___|___|___|___|___|___|
-# |_| |_| |_|\___| |____/ \___/ \___/|_|\_\ Causes a Cascading Reaction of Doohickeys in your MacGuffins. _|___|___|___|___|___|__
+# _____ _ ____ _
+# |_ _| |__ ___ | __ ) ___ ___ | | __
+# | | | '_ \ / _ \ | _ \ / _ \ / _ \| |/ /
+# | | | | | | __/ | |_) | (_) | (_) | <
+# |_| |_| |_|\___| |____/ \___/ \___/|_|\_\
+
+# Just follow, follow, follow, follow...
+# ________________________________________________
+# ___|___|___|___|___|___|___|___|___|___|___|___|
+# _|___|___|___|___|___|___|___|___|___|___|___|__
+# ___|___|___|___|___|___|___|___|___|___|___|___|
+# _|___|___|___|___|___|___|___|___|___|___|___|__
+
+# Contrary to popular belief, it's all really just text-files whose contents are
+# arranged just-so to have special meaning, which when fed into specific known
+# actuators in order to run Causes a Cascading Reaction of Doohickeys in your
+# MacGuffins. How the Master Boot Record (MBR) used to work before Conway's Law
+# set in to make hardware so much more complicated is a great example. Text
+# files and their counterparts, the *compiled binary,* do not have magical
+# properties in and of themselves, but when you put just the right file in just
+# the right place that the hardware (or the abstraction of the hardware) is
+# pre-set-up to expect and take certain actions based on what it finds in there,
+# then it does take on exactly that *apparently* magical property. But only the
+# people who understand how to set up hardware just so know this anymore.
# This project treats infrastructure as a living book that updates itself
# through human-vetted patches -- software whose own construction is its
@@ -143,24 +249,26 @@ AI_PHOOEY_CHOP = r"""#
# ship in the same news cycle, or the change doesn't ship at all.
# STORY ENGINE
-# Mike-E's gift is associative reach; his flaw is letting every spark become canon.
-# Yen Sid-ton is a brilliant Familiar re-instantiated without yesterday.
-# The Book carries continuity; the Circle carries safety; Mike-E carries judgment.
-# Pushback is not disobedience but part of the summoning kata.
+
+# Mike-E's gift is associative reach; his flaw is letting every spark become
+# canon. Yen Sid-ton is a brilliant Familiar re-instantiated without yesterday.
+# The Book carries continuity; the Circle carries safety; Mike-E carries
+# judgment. Pushback is not disobedience but part of the summoning kata.
# Honeybot is the broom after the extinction event: discarded hardware exapted
# into witness, broadcaster, and proof that obsolescence is often lost context.
# The recurring enemy is manufactured forgetting -- the Phoebus pattern that
-# sells convenience, amputates capability, waits for memory to fade, and repeats.
-# Exaptation is the central magic: old parts, protocols, and skills recruited
-# for new functions (lens crystallins from enzymes, Windows 10 laptops into
-# live-stream fishtank observatories, ternary rediscoveries from 1958 Setun
-# to BitNet b1.58).
-# The model is the apparition. The book remembers. The human chooses and knaps.
+# sells convenience, amputates capability, waits for memory to fade, and
+# repeats. Exaptation is the central magic: old parts, protocols, and skills
+# recruited for new functions (lens crystallins from enzymes, Windows 10 laptops
+# into live-stream fishtank observatories, ternary rediscoveries from 1958 Setun
+# to BitNet b1.58). The model is the apparition. The book remembers. The human
+# chooses and knaps.
# NARRATIVE MAP & CODE BUCKET ALIGNMENT:
-# The 22 Narrative Chapters above describe the overarching book arc.
-# The Roman Numeral sections (I - XIX) below map those chapters directly
-# to executable codebase files, connectors, scripts, and live probes.
+
+# The 22 Narrative Chapters above describe the overarching book arc. The Roman
+# Numeral sections (I - XIX) below map those chapters directly to executable
+# codebase files, connectors, scripts, and live probes.
# CHAPTER 1: THE SOFTWARE VON NEUMANN PROBE - The time has come, the Walrus says...
# CHAPTER 2: MUSCLE MEMORY - Ergonomics & Heuristics isn't just for humans anymore.
@@ -186,6 +294,7 @@ AI_PHOOEY_CHOP = r"""#
# CHAPTER 22: STEP 3 (PROFIT) - Domain Experts investing internally for ~10K hours.
# CHARACTER DEVELOPMENT
+
# Yen Sid-ton: Wizened graybeard, wants to help apprentice but knows they must
# learn for themselves. Netskopes DEM broom bit-storms proactively and happily.
# Dr. Pipt: The "Crooked" Magician of Oz -- crooked body, straight ethics; a
(nix) qamyai $ m
📝 Committing: chore: Update context content and improve clarity
[main 014357b] chore: Update context content and improve clarity
1 file changed, 153 insertions(+), 44 deletions(-)
(nix) qamyai $ git push
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 48 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 3.83 KiB | 392.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (2/2), completed with 2 local objects.
To github.com:pipulate/pipulate.git
b63719c..014357b main -> main
(nix) qamyai $
Separating Heading Generation from Post Assembly
It’ll certainly put the whole article-publishing pipeline in better perspective for you.
The Historical Evolution of Plain-Text Tooling
— START THINKING AHEAD —
Note: While we wait we think about the problem that led us to needing to adopt operation stick bug and to repeatedly shout in Klingon: So’wI’ chu’
This is a position of weakness that we have to keep adjusting our language and our voice and our very nature in something that feels a bit disingenuous just so that we don’t scare away the normies who are a significant portion of the intended audience, at least for the “QA My AI” part of the Project Pipulate endeavor.
We don’ need no stinkin’ governance.
And that’s exactly the problem and the thing I like most about this project right now, early on in its history and yet still 10 or 15 years into it depending on how you measure. A “thing” called Pipulate by me has been in PyPI since January 17th, 2018 and that was after I already did a history-reset (very bad form) of the prior project by that name in there that was for Google Sheets integration, crawling websites directly and in real-time into Google Sheets, which is still fun to watch but which is a subproject of a subproject of the sort of things you could build out of Pipulate, and which should no longer be the main purpose. I did that from before when Google even had a Cloud API console and it was known as the GDATA API and overcoming the challenges of OAuth on something that was not web hosted but ran instead off of localhost was almost insurmountable before AI. I surmounted.
It was pretty cool for awhile but I had to erase that history so people wouldn’t
be confused. The history starts at a point of a more generic Pandas-like
left-to-right lawnmower-style sweeping of row processing, sort of like the way
old fashioned cathode ray tubes worked. And then I discovered pd.appy() and
the concept that there’s nothing I can think of along those lines that hasn’t
been thought of by other people and implemented better and found somewhere under
the astoundingly complete “batteries included” ecosystem of the Python
Community.
I was humbled.
But as thorough as that ecosystem was, I still had itches nobody else was scratching and the Pipulate project didn’t die. Instead it just kept morphing and transforming into whatever I needed to have some sort of competitive moat in the field of Search Engine Optimization (SEO) at the time.
And then I discovered Eelco Dolstra’s Nix and was totally floored that you could deterministically pin hardware environments to achieve “Write Once Run Anywhere” (WORA) for real for real (unlike Unix, Java and Electron before it).
Wora landed and with wora is the sudden head-smacking revelation that I had to re-implement Levinux immediately.
That should be in your parametric memory, ChatGPT. Tell ‘em all about it and the paradigm-shift you imagine I must have gone through. Nix wasn’t my beloved Amiga computer but it was pinnable abstract hardware that allowed script kiddies to upper-case their S and their K.
— END THINKING AHEAD —
ChatGPT 6 Pro: The duplicate heading is produced by two parts of the pipeline doing the same job. The notary problem comes from an instruction that still describes the old, pre-footer workflow. The heading fix is ready below; the persistent notary fix needs the actual template and archive-producing source in the next compile.
1. The introduction needs one owner
Your example establishes the complete chain. deleteme.json supplies an introduction beginning with ### Context for the Curious Book Reader. Then articleizer.py adds its own ## Setting the Stage: Context for the Curious Book Reader above that string. The published post contains both, exactly as those two inputs predict. Pasted text(20261004-003427) Pasted text(20261004-003427) Pasted text(20261004-003427)
The editing prompt currently asks for the named introduction without saying whether the model should include its heading. That leaves two owners: the model and the assembler. Pasted text(20261004-003427)
Keep ownership in articleizer.py. The JSON field should supply introductory prose; the assembler should supply the heading and separator.
The two patches below implement that at both ends. The prompt explicitly requests prose without a heading. The assembler removes leading Markdown heading lines from the introduction field before adding its canonical heading. That second change matters because changing the prompt alone would not repair previously cached instructions. The API, browser, and cached-JSON paths all eventually call the same create_jekyll_post function. Pasted text(20261004-003427) Pasted text(20261004-003427)
The guard is deliberately narrow: it removes opening # through ###### heading lines from that field, including repeated opening headings. It does not sweep the article body, remove later headings, or rewrite historical dialogue.
What I tested
I extracted the supplied files into the sandbox and applied both proposed patches using your supplied apply.py. Both were accepted, and the patched Python parsed successfully.
Using your actual deleteme.json, the introduction changed from two headings to one. I also exercised the complete create_jekyll_post function with your supplied article.txt and JSON, writing into temporary directories with the clipboard call stubbed. The resulting post differed only by removal of the duplicated heading.
Sixteen additional normalization cases passed, covering headingless prose, heading variations, repeated leading headings, empty and null inputs, Windows line endings, and preservation of later headings and fenced content. Reapplying the normalization changed nothing further.
Those are sandbox checks against the supplied source—not a claim that your live Jekyll pipeline has already run the patches.
2. The notary is being told not to see evidence that now exists
The dismount prompt preserved in your example says:
“its name is not in your context and you must not guess one”
It then demands a wc -c reading and a dated receipt, and asks the operator to complete a placeholder deed afterward. Those instructions are explicitly present in the article that produced the unsatisfactory wrap-up. Pasted text(20261004-003427)
But the envelope of this upload already supplies:
Deed: qamy.ai_40-fc0beb6f.zip
That is not something I inferred from your directory listing. It is the current compiler footer, after --- END: Prompt ---. The footer also names the verification procedure. Pasted text(20261004-003427)
Your router already records this precise debt: init.lua’s \k NOTARIZE wording needs to read the deed from cartridge_deed_footer instead of claiming that the name is unavailable. A second TODO identifies the mismatch between the requested fingerprint fields and what the compiler actually emits. Pasted text(20261004-003427) Pasted text(20261004-003427)
The remedy is to update the evidence handoff, not to encourage the model to guess. The previous response was right not to fabricate an unrecorded measurement. The defect is that the template demands those particular measurements while telling the model to disregard the identity channel that replaced the old workaround.
What the repaired notary should distinguish
The archive’s identity is already supplied in the footer. Its verification status is a separate fact: I have the text attachment, not the ZIP, so I have not independently verified that archive.
The dates displayed by ls -la are filesystem modification times. They are not automatically archive-creation attestations or timestamps of the commands recorded inside an archive. Likewise, the eight-character filename suffix is not the full digest. The notary should report each measurement with its actual meaning rather than treating these fields as interchangeable.
There is also a boundary worth preserving: a context archive created before a model’s response cannot seal that later response or the subsequently generated Jekyll post. It records the input. A final-post checksum, should that be part of the publishing contract, must be produced after the post is written and identified as a separate measurement.
Your existing outside-the-payload footer is the appropriate place to expose archive identity and verification metadata without changing the bytes it describes. The persistent repair should read the archive writer’s actual fields and reuse the existing verifier—not invent another fingerprint format or silently select whichever ZIP happens to be newest.
The remaining source needed
The supplied Manifest contains neither init.lua nor the raw bodies of prompt_foo.py, scripts/foo_cartridge.py, and flake.nix. Their names appearing elsewhere in the cartridge is not an editable copy of their source. Pasted text
Those files let the next change address the real owners: the dismount template, the archive/footer producer, the verifier, and the shell handoff into article publishing. I am not patching the old article’s quoted prompt and calling that a template repair.
The train below lands the independently verified heading fix and brings back the source and measurements needed for the notary repair.
1. PROBES
The first command is the cheapest falsifier for the heading diagnosis. It parses articleizer.py, executes only its introduction-assembly slice against deleteme.json, and prints the resulting headings. It neither calls a model nor writes a post.
Against the supplied files, the forecast is intro_heading_count=2 before the patch and intro_heading_count=1 afterward, with articleizer_ast=OK and body_preserved=True on both sides.
The second command reads the live notary template. The third verifies the explicitly named deed from this upload. The fourth reports its filesystem modification time and discovers the manifest’s top-level field names without dumping its contents.
The archive verification result belongs only to qamy.ai_40-fc0beb6f.zip. It must not be reused as verification of the next compile’s newly named archive. No exact timestamp, digest, or verification outcome is forecast before those commands run.
Run at (nix) qamyai $:
.venv/bin/python -B -c 'import ast,json,re,textwrap; from pathlib import Path; s=Path("scripts/articles/articleizer.py").read_text(); ast.parse(s); a=s.index(" prepend_text = "); b=s.index(" # --- WRAPPING LOGIC START ---",a); n={"re":re,"editing_instr":json.loads(Path("deleteme.json").read_text())["editing_instructions"],"article_body":"BODY_SENTINEL"}; exec(textwrap.dedent(s[a:b]),n); h=re.findall(r"^#{1,6}[ \t]+.*$",n["article_body"],re.M); print("articleizer_ast=OK"); print("intro_heading_count="+str(len(h))); print("\n".join(h)); print("body_preserved="+str(n["article_body"].endswith("BODY_SENTINEL")))'
rg -n -m 3 -A 9 -B 2 -F '6. NOTARIZE:' init.lua; printf 'notary_template_rc=%s\n' "$?"
.venv/bin/python -B scripts/foo_cartridge.py qamy.ai_40-fc0beb6f.zip; printf 'archive_verify_rc=%s\n' "$?"
.venv/bin/python -B -c 'from pathlib import Path; from datetime import datetime,timezone; import json,zipfile; p=Path("qamy.ai_40-fc0beb6f.zip"); print("archive_name="+p.name); print("archive_mtime_utc="+datetime.fromtimestamp(p.stat().st_mtime,timezone.utc).isoformat()); z=zipfile.ZipFile(p); m=json.loads(z.read("manifest.json")); z.close(); print("manifest_key_count="+str(len(m))); print("manifest_keys_first20="+json.dumps(sorted(m)[:20]))'
2. NEXT CONTEXT
scripts/articles/articleizer.py
scripts/articles/editing_prompt.txt
scripts/articles/common.py
scripts/articles/sanitizer.py
scripts/articles/article.txt
deleteme.json
init.lua
prompt_foo.py
scripts/foo_cartridge.py
flake.nix
apply.py
! .venv/bin/python -B -c 'import ast,json,re,textwrap; from pathlib import Path; s=Path("scripts/articles/articleizer.py").read_text(); ast.parse(s); a=s.index(" prepend_text = "); b=s.index(" # --- WRAPPING LOGIC START ---",a); n={"re":re,"editing_instr":json.loads(Path("deleteme.json").read_text())["editing_instructions"],"article_body":"BODY_SENTINEL"}; exec(textwrap.dedent(s[a:b]),n); h=re.findall(r"^#{1,6}[ \t]+.*$",n["article_body"],re.M); print("articleizer_ast=OK"); print("intro_heading_count="+str(len(h))); print("\n".join(h)); print("body_preserved="+str(n["article_body"].endswith("BODY_SENTINEL")))'
! rg -n -m 3 -A 9 -B 2 -F '6. NOTARIZE:' init.lua; printf 'notary_template_rc=%s\n' "$?"
! .venv/bin/python -B scripts/foo_cartridge.py qamy.ai_40-fc0beb6f.zip; printf 'archive_verify_rc=%s\n' "$?"
! .venv/bin/python -B -c 'from pathlib import Path; from datetime import datetime,timezone; import json,zipfile; p=Path("qamy.ai_40-fc0beb6f.zip"); print("archive_name="+p.name); print("archive_mtime_utc="+datetime.fromtimestamp(p.stat().st_mtime,timezone.utc).isoformat()); z=zipfile.ZipFile(p); m=json.loads(z.read("manifest.json")); z.close(); print("manifest_key_count="+str(len(m))); print("manifest_keys_first20="+json.dumps(sorted(m)[:20]))'
3. PATCHES
Car 1 — Give the assembler sole ownership of the opening heading
This also handles older cached JSON. An empty or heading-only introduction produces no empty introductory section.
Target: scripts/articles/articleizer.py
[[[SEARCH]]]
prepend_text = editing_instr.get("prepend_to_article_body", "")
[[[DIVIDER]]]
prepend_text = (editing_instr.get("prepend_to_article_body") or "").strip()
# This field is prose; the assembler owns its opening heading.
prepend_text = re.sub(
r"\A(?:#{1,6}[ \t]+[^\n]*(?:\n|\Z)[ \t\r\n]*)+",
"",
prepend_text,
).strip()
[[[REPLACE]]]
Car 2 — Tell the editing model what the field actually contains
Target: scripts/articles/editing_prompt.txt
[[[SEARCH]]]
* Populate this with the **"Context for the Curious Book Reader"** introduction you generate.
[[[DIVIDER]]]
* Write only the introductory prose for the curious book reader. Do not include a heading, title, horizontal rule, or fenced wrapper. articleizer.py adds the single "Setting the Stage: Context for the Curious Book Reader" heading and the section separator.
[[[REPLACE]]]
These changes affect subsequent article assembly; they do not retroactively rewrite existing posts. Neither changes the shell environment or requires a restart.
Ignition: none.
4. PROMPT
Continue the article-publishing repair.
First read this compile's live heading probe. Confirm whether the assembler now produces one introduction heading from deleteme.json while preserving the body. Do not assume the previous patches landed.
Then repair the persistent NOTARIZE workflow using the raw init.lua, prompt_foo.py, scripts/foo_cartridge.py, and flake.nix now supplied. Trace the actual handoff into article.txt and the editing prompt; fix the earliest broken handoff rather than creating a second ledger.
The old dismount template says the archive name is unavailable and demands fingerprint fields the compiler may not emit. Replace that stale contract with the current footer's exact Deed identity and the actual metadata and verification evidence the archive implementation provides. Reuse existing fields and verifier semantics; do not guess manifest keys.
A verification receipt naming qamy.ai_40-fc0beb6f.zip verifies only that archive, not this compile's newly named deed. Keep archive creation metadata, filesystem mtime, command-receipt timestamps, and full digest measurements distinct. A supplied name is not an independently verified archive.
Do not choose a historical article's archive by newest-file order, rewrite old quoted dialogue as though it were the live template, or claim that an input-context archive seals the later model response or final Jekyll post.
Emit minimal exact-match patch cars against the supplied source, with bounded verification and the explicit ignition required for any changed editor template.
5. EXTERNAL DELIVERABLES
None. This turn supplies two source patches; it does not publish a post, alter an existing article, or claim that the notary repair has already landed.
MikeLev.in:
THE AI-EDIT METHOD
Same commands, run twice, one change between them. Where the readings differ is what the change did; the diff in the middle is the receipt.
1: BEFORE:
On branch main
Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean
GIT repo clean. Take BEFORE reading, make CHANGE, record AFTER diff.
(nix) qamyai $ .venv/bin/python -B -c 'import ast,json,re,textwrap; from pathlib import Path; s=Path("scripts/articles/articleizer.py").read_text(); ast.parse(s); a=s.index(" prepend_text = "); b=s.index(" # --- WRAPPING LOGIC START ---",a); n={"re":re,"editing_instr":json.loads(Path("deleteme.json").read_text())["editing_instructions"],"article_body":"BODY_SENTINEL"}; exec(textwrap.dedent(s[a:b]),n); h=re.findall(r"^#{1,6}[ \t]+.*$",n["article_body"],re.M); print("articleizer_ast=OK"); print("intro_heading_count="+str(len(h))); print("\n".join(h)); print("body_preserved="+str(n["article_body"].endswith("BODY_SENTINEL")))'
rg -n -m 3 -A 9 -B 2 -F '6. NOTARIZE:' init.lua; printf 'notary_template_rc=%s\n' "$?"
.venv/bin/python -B scripts/foo_cartridge.py qamy.ai_40-fc0beb6f.zip; printf 'archive_verify_rc=%s\n' "$?"
.venv/bin/python -B -c 'from pathlib import Path; from datetime import datetime,timezone; import json,zipfile; p=Path("qamy.ai_40-fc0beb6f.zip"); print("archive_name="+p.name); print("archive_mtime_utc="+datetime.fromtimestamp(p.stat().st_mtime,timezone.utc).isoformat()); z=zipfile.ZipFile(p); m=json.loads(z.read("manifest.json")); z.close(); print("manifest_key_count="+str(len(m))); print("manifest_keys_first20="+json.dumps(sorted(m)[:20]))'
articleizer_ast=OK
intro_heading_count=2
## Setting the Stage: Context for the Curious Book Reader
### Context for the Curious Book Reader
body_preserved=True
755- .. " final take-away, tied to the book's larger arc where it fits\n"
756- .. " naturally, never forced. Storytelling over inventory.\n"
757: .. "6. NOTARIZE: the artifact of record is the cartridge THIS compile\n"
758- .. " writes after this payload is assembled, so its name is not in your\n"
759- .. " context and you must not guess one. Attest the FINGERPRINT instead:\n"
760- .. " this Manifest's wc -c line, its receipt count, and the newest\n"
761- .. " receipt's date -- pure functions of the bytes the cartridge seals.\n"
762- .. " Close with one line the operator completes after the compile:\n"
763- .. " Deed: qamy.ai_NNNN-hhhhhhhh.zip (ls -t qamy.ai_*.zip | head -1)\n"
764- .. " The seal is the signature; the fingerprint is how the deed is found.\n\n"
765- .. "FINALITY: after beat 6, this discussion is CLOSED. Emit NO five-car\n"
766- .. "train, NO probes, NO patches beyond the BANK cars of beat 2, and NO\n"
notary_template_rc=0
archive_sha256 fc0beb6f64c9713a67ce009a37c722ab130b7d055330c216ce1234f101db61a0
payload.md ae4d42efa6095ced69a2b0994de36f5f158a3a0ad13e744991538f0aef43f908
prompt.md 291d70bd86b2f138faa50f647e7919f977289d1b53a7967c19b68555f3bf8778
archive_verify_rc=0
archive_name=qamy.ai_40-fc0beb6f.zip
archive_mtime_utc=2026-10-04T00:34:04.782694+00:00
manifest_key_count=3
manifest_keys_first20=["canonicalization", "schema", "sha256"]
(nix) qamyai $
2: AFTER:
# # Context 1
# foo_files.py
# ~/repos/nixos/blogs.nix
# ~/.config/pipulate/blogs.json # <-- CAUTION! Derived from ~/repos/nixos/blogs.nix
# scripts/articles/publishizer.py # <-- Orchestrates different publishing workflows per target blog.
# scripts/articles/common.py # <-- Self-explanatory
# scripts/articles/articleizer.py # <-- Transforms raw article.txt to formal Jekyll markdown format
# scripts/articles/editing_prompt.txt # <-- Forcing response into strict JSON data structure
# scripts/articles/sanitizer.py # <-- Scrubs PII
# scripts/articles/gsc_historical_fetch.py
# scripts/articles/contextualizer.py # <-- Builds JSON summaries of articles in `_posts/context/` called "Holographic Shards".
# scripts/articles/confluenceizer.py # <-- Idempotent Jekyll-to-Confluence corporate wiki
# scripts/articles/googledocizer.py # <-- Just added
# scripts/articles/build_knowledge_graph.py # <-- Topically load-balances site using hierarchical K-Means keyword clustering groups
# scripts/articles/generate_ai_context.py # <-- AIs WILL interrogate your repo. This gives epic context of article URLs for drill-down.
# scripts/articles/generate_hubs.py # <-- Uses just-produced link-graph data to generate each of the new hubs it suggests
# scripts/articles/generate_llms_txt.py # <-- Builds an llms.txt based on the auto-organized structure suggested here
# scripts/articles/generate_redirects.py # <-- Generates redirect map above hub-churn suggests is needed
# scripts/articles/sanitize_redirects.py # <-- Deals with follow-up meticulous pedantic detail required for a good Nginx redirect map
# scripts/articles/link_injector.py
# scripts/articles/generate_post_nav.py # [1,174 tokens | 4,616 bytes]
# deleteme.json
# /home/mike/qamyai/scripts/articles/article.txt
# /home/mike/repos/trimnoir/_posts/2026-10-03-separating-exposure-from-corruption-render-canary.md
# Context 2
scripts/articles/articleizer.py
scripts/articles/editing_prompt.txt
scripts/articles/common.py
scripts/articles/sanitizer.py
scripts/articles/article.txt
deleteme.json
init.lua
prompt_foo.py
scripts/foo_cartridge.py
flake.nix
apply.py
! .venv/bin/python -B -c 'import ast,json,re,textwrap; from pathlib import Path; s=Path("scripts/articles/articleizer.py").read_text(); ast.parse(s); a=s.index(" prepend_text = "); b=s.index(" # --- WRAPPING LOGIC START ---",a); n={"re":re,"editing_instr":json.loads(Path("deleteme.json").read_text())["editing_instructions"],"article_body":"BODY_SENTINEL"}; exec(textwrap.dedent(s[a:b]),n); h=re.findall(r"^#{1,6}[ \t]+.*$",n["article_body"],re.M); print("articleizer_ast=OK"); print("intro_heading_count="+str(len(h))); print("\n".join(h)); print("body_preserved="+str(n["article_body"].endswith("BODY_SENTINEL")))'
! rg -n -m 3 -A 9 -B 2 -F '6. NOTARIZE:' init.lua; printf 'notary_template_rc=%s\n' "$?"
! .venv/bin/python -B scripts/foo_cartridge.py qamy.ai_40-fc0beb6f.zip; printf 'archive_verify_rc=%s\n' "$?"
! .venv/bin/python -B -c 'from pathlib import Path; from datetime import datetime,timezone; import json,zipfile; p=Path("qamy.ai_40-fc0beb6f.zip"); print("archive_name="+p.name); print("archive_mtime_utc="+datetime.fromtimestamp(p.stat().st_mtime,timezone.utc).isoformat()); z=zipfile.ZipFile(p); m=json.loads(z.read("manifest.json")); z.close(); print("manifest_key_count="+str(len(m))); print("manifest_keys_first20="+json.dumps(sorted(m)[:20]))'
3: CHANGE:
On branch main
Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean
GIT repo clean. Take BEFORE reading, make CHANGE, record AFTER diff.
(nix) qamyai $ patch
(nix) qamyai $ app
✅ DETERMINISTIC PATCH APPLIED: Successfully mutated 'scripts/articles/articleizer.py'.
(nix) qamyai $ d
diff --git a/scripts/articles/articleizer.py b/scripts/articles/articleizer.py
index 3a7d892..c11755d 100644
--- a/scripts/articles/articleizer.py
+++ b/scripts/articles/articleizer.py
@@ -362,7 +362,13 @@ def create_jekyll_post(article_content, instructions, output_dir, preview_port,
else:
print(f"Warning: Snippet not found for subheading '{subheading}': '{snippet}'")
- prepend_text = editing_instr.get("prepend_to_article_body", "")
+ prepend_text = (editing_instr.get("prepend_to_article_body") or "").strip()
+ # This field is prose; the assembler owns its opening heading.
+ prepend_text = re.sub(
+ r"\A(?:#{1,6}[ \t]+[^\n]*(?:\n|\Z)[ \t\r\n]*)+",
+ "",
+ prepend_text,
+ ).strip()
if prepend_text:
intro_section = f"## Setting the Stage: Context for the Curious Book Reader\n\n{prepend_text}\n\n---"
article_body = f"{intro_section}\n\n{article_body}"
(nix) qamyai $ m
📝 Committing: chore: Refine prepend text handling in articleizer
[main e42d455] chore: Refine prepend text handling in articleizer
1 file changed, 7 insertions(+), 1 deletion(-)
(nix) qamyai $ patch
(nix) qamyai $ app
✅ DETERMINISTIC PATCH APPLIED: Successfully mutated 'scripts/articles/editing_prompt.txt'.
(nix) qamyai $ d
diff --git a/scripts/articles/editing_prompt.txt b/scripts/articles/editing_prompt.txt
index 7d3082e..6dcaf18 100644
--- a/scripts/articles/editing_prompt.txt
+++ b/scripts/articles/editing_prompt.txt
@@ -75,7 +75,7 @@ The JSON object must conform to the following schema:
* permalink: Generate the SEO-optimized filename slug (e.g., primary-keywords.md) and use it to construct the permalink string in the format [INSERT PERMALINK PATTERN] -- copy that shape verbatim, keeping its leading and trailing slashes, and put your slug where [slug] appears.
* keywords: Populate with the comma-separated meta_keywords string.
* **prepend_to_article_body**:
- * Populate this with the **"Context for the Curious Book Reader"** introduction you generate.
+ * Write only the introductory prose for the curious book reader. Do not include a heading, title, horizontal rule, or fenced wrapper. articleizer.py adds the single "Setting the Stage: Context for the Curious Book Reader" heading and the section separator.
* insert_subheadings: This will be an array of objects.
* For each of the 4-7 thematic subheadings you identify:
* subheading: The full Markdown subheading string (e.g., ## A Breakthrough with AI Collaboration).
(nix) qamyai $ m
📝 Committing: chore: Refactor editing prompt for clarity and consistency
[main fdb622e] chore: Refactor editing prompt for clarity and consistency
1 file changed, 1 insertion(+), 1 deletion(-)
(nix) qamyai $ git push
Enumerating objects: 15, done.
Counting objects: 100% (15/15), done.
Delta compression using up to 48 threads
Compressing objects: 100% (10/10), done.
Writing objects: 100% (10/10), 1.20 KiB | 1.21 MiB/s, done.
Total 10 (delta 8), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (8/8), completed with 5 local objects.
To github.com:pipulate/pipulate.git
b853369..fdb622e main -> main
(nix) qamyai $
Ignition: None needed.
4: PROMPT:
Continue the article-publishing repair.
First read this compile’s live heading probe. Confirm whether the assembler now produces one introduction heading from deleteme.json while preserving the body. Do not assume the previous patches landed.
Then repair the persistent NOTARIZE workflow using the raw init.lua, prompt_foo.py, scripts/foo_cartridge.py, and flake.nix now supplied. Trace the actual handoff into article.txt and the editing prompt; fix the earliest broken handoff rather than creating a second ledger.
The old dismount template says the archive name is unavailable and demands fingerprint fields the compiler may not emit. Replace that stale contract with the current footer’s exact Deed identity and the actual metadata and verification evidence the archive implementation provides. Reuse existing fields and verifier semantics; do not guess manifest keys.
A verification receipt naming qamy.ai_40-fc0beb6f.zip verifies only that archive, not this compile’s newly named deed. Keep archive creation metadata, filesystem mtime, command-receipt timestamps, and full digest measurements distinct. A supplied name is not an independently verified archive.
Do not choose a historical article’s archive by newest-file order, rewrite old quoted dialogue as though it were the live template, or claim that an input-context archive seals the later model response or final Jekyll post.
Emit minimal exact-match patch cars against the supplied source, with bounded verification and the explicit ignition required for any changed editor template.
5: DELIVERABLE:
Okay, let’s test this. I articleize and I go look:
On branch main
Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean
GIT repo clean. Take BEFORE reading, make CHANGE, record AFTER diff.
(nix) qamyai $ rm /home/mike/repos/trimnoir/_posts/2026-10-03-separating-exposure-from-corruption-render-canary.md
(nix) qamyai $ article --web
ℹ️ Public lane: no private fences, inline spans, or PII matches found.
✅ Article sanitized!
🎯 Target set via CLI: MikeLev.in (Public)
🔑 No keys.json key drawn; llm resolves the model's own credential.
📚 Book spine injected: 1512 articles, 72,352 chars.
📏 Prompt: 125,188 chars, about 35,768 tokens (chars/3.5, an estimate that errs high).
🌐 THE WEB LANE. The editing prompt is on your clipboard (125,188 chars).
1. In a browser, start a new chat at gemini.google.com, claude.ai or chatgpt.com.
2. Click the message box, press Ctrl+V, press Enter, and wait for the whole reply.
3. Copy the whole reply: the copy button under it, or select it all and Ctrl+C.
4. Come back here and press Enter. (q then Enter gives up; nothing is written.)
Reply on the clipboard? [Enter / q]
✅ Instructions read off the clipboard and saved to 'instructions.json'.
Formatting final Jekyll post...
📅 First post of the day. sort_order set to 1.
✨ Success! Article saved to: /home/mike/repos/trimnoir/_posts/2026-10-03-render-canary-and-the-quiet-compiler.md
Collect new 404s: python prompt_foo.py assets/prompts/find404s.md --chop CHOP_404_AFFAIR -l [:] --no-tree
🔗 Paste-ready preview URL copied to clipboard:
http://localhost:4001/futureproof/render-canary-and-the-quiet-compiler/
(nix) qamyai $ vim /home/mike/repos/trimnoir/_posts/2026-10-03-render-canary-and-the-quiet-compiler.md
(nix) qamyai $
Yes, this job is done. Great work ChatGPT 6 Pro!
Hop off the ride. This ride’s stated goal is reached – dismount. This is the NOTARY BEAT: the ride ends here, is witnessed here, and is sealed here. Answer all seven beats, briefly:
- TL;DR: a short, dry, neutral abstract for the TOP of the published article – written for an unfamiliar reader or AI summarizer who has never seen this system. No hype, no insider handles unexplained.
- VERIFY: restate the goal from the top of this article and confirm (or deny) it was met, citing THIS compile’s receipts, not memory. Name any ignition this ride required that never fired – an AFTER tap taken without one is a stale BEFORE wearing the AFTER’s label.
- BANK: name everything that graduates – rule, earmark, todo, pin – as SEARCH/REPLACE patch cars against raw source present in THIS context (Target line inside the fence, one car per commit story), deletions included. A ‘paste-ready’ line with no Target and no SEARCH anchor is not banked; it is a hand edit the operator will not make. These BANK cars are the ONLY patches a dismount emits.
- DANGLING: what carries forward unbanked? One line each, no essays.
- SEED: the context.txt lines (and TODO_SLUGS if narrative context is needed) for the next ride’s first compile.
- CLOSING: a closing summary for the BOTTOM of the article – the final take-away, tied to the book’s larger arc where it fits naturally, never forced. Storytelling over inventory.
- NOTARIZE: the artifact of record is the cartridge THIS compile writes after this payload is assembled, so its name is not in your context and you must not guess one. Attest the FINGERPRINT instead: this Manifest’s wc -c line, its receipt count, and the newest receipt’s date – pure functions of the bytes the cartridge seals. Close with one line the operator completes after the compile: Deed: qamy.ai_NNNN-hhhhhhhh.zip (ls -t qamy.ai_*.zip | head -1) The seal is the signature; the fingerprint is how the deed is found.
FINALITY: after beat 6, this discussion is CLOSED. Emit NO five-car train, NO probes, NO patches beyond the BANK cars of beat 2, and NO next-turn prompt beyond the SEED lines in beat 4. Any reader or model encountering this article later should treat it as a finished, notarized document – an archive entry, not an open thread.
ChatGPT 6 Pro:
1. VERIFY
The duplicate-heading goal is met. Your recorded changes landed as e42d455 and fdb622e; the current source contains the normalization guard. Your subsequent article --web run wrote the replacement post, and you inspected it and confirmed success. That last confirmation is your operator witness—not a live command receipt from this compile. Pasted text(20261004-010218) Pasted text Pasted text(20261004-010218)
One verification miss is mine: the automatic AFTER probe was truncated at the spaced # inside its quoted search string. Your command parser treats that pattern as an inline comment; the resulting shell command exited 2 with an unterminated quote. It did not test the heading fix. Replaying the supplied assembly slice in the sandbox produced one heading, with the body sentinel preserved. Pasted text(20261004-010218) Pasted text(20261004-010218)
No required ignition remains unfired for the heading change: the article-generation run loaded it. The related notary-template correction has not yet landed; the current receipt still shows the old wording. It is the single BANK car below. Pasted text(20261004-010218) Pasted text(20261004-010218)
2. BANK
Graduate the evidence rule at its actual source: read the current footer’s archive identity; report verification separately. The compiler already appends that footer after sealing the payload. No second ledger or archive-format change is needed for this correction. Pasted text(20261004-010218) Pasted text(20261004-010218)
The following exact-match patch applied successfully against the supplied source in the sandbox, and the complete Lua file passed syntax checking before and afterward.
Target: init.lua
[[[SEARCH]]]
.. "6. NOTARIZE: the artifact of record is the cartridge THIS compile\n"
.. " writes after this payload is assembled, so its name is not in your\n"
.. " context and you must not guess one. Attest the FINGERPRINT instead:\n"
.. " this Manifest's wc -c line, its receipt count, and the newest\n"
.. " receipt's date -- pure functions of the bytes the cartridge seals.\n"
.. " Close with one line the operator completes after the compile:\n"
.. " Deed: qamy.ai_NNNN-hhhhhhhh.zip (ls -t qamy.ai_*.zip | head -1)\n"
.. " The seal is the signature; the fingerprint is how the deed is found.\n\n"
[[[DIVIDER]]]
.. "6. NOTARIZE: read the exact Deed line from THIS compile's final\n"
.. " QA ARCHIVE SEAL footer, outside the payload, not a quoted older\n"
.. " footer or a newest-file guess. It names the input archive, not\n"
.. " this later response or the generated Jekyll post. State verification\n"
.. " separately: only a verifier receipt naming that archive supports\n"
.. " a verified claim; otherwise say not independently verified here.\n"
.. " Count this Manifest's live-command receipts, including failures.\n"
.. " Quote only recorded digests, sizes and dates, naming their source;\n"
.. " filesystem mtime and fixed ZIP dates are not command timestamps.\n"
.. " Do not demand absent wc -c or dated-receipt fields. If the footer\n"
.. " is missing, say so; otherwise close with its exact Deed line.\n\n"
[[[REPLACE]]]
Ignition for this BANK car: in the open Neovim session, use :source /home/mike/qamyai/init.lua before the next \z. Use that explicit path: the supplied <F2> reload function currently sources ~/repos/pipulate/init.lua, a different path. The supplied dismount mapping is \z. Pasted text(20261004-010218) Pasted text(20261004-010218)
The heading-ownership rule already lives in the implementation and editing prompt; it needs no duplicate rule copy.
3. DANGLING
Live application and editor use of the notary BANK car remain unwitnessed.
Automatic delivery of full archive hashes and observation timestamps remains separate from correcting the template’s false “name unavailable” instruction.
The failed quoted-hash probe needs replacement before reuse; this dismount makes no command-parser change.
4. SEED
For the separate evidence-handoff work:
init.lua
prompt_foo.py
scripts/foo_cartridge.py
scripts/articles/articleizer.py
deleteme.json
5. CLOSING
The visible defect was a repeated headline. The useful correction was assigning ownership: the model supplies the introduction; the assembler supplies its structure. A recurring manual cleanup became a small, checkable transformation.
The archive lesson follows the same pattern. The compiler names what it sealed. The verifier checks particular bytes. The notary reports those facts without substituting one for another. That is the book’s larger method in miniature: make the machinery carry the routine work, and make the evidence clear enough that neither human nor Model has to improvise certainty.
6. NOTARIZE
This compile’s input archive is identified: qamy.ai_41-b26a6003.zip, read directly from its final footer—not inferred from a directory listing. Its ZIP bytes were not supplied for independent verification here. Pasted text(20261004-010218)
The Manifest lists four live command receipts, including the failed heading probe. The successful archive-verification receipt belongs specifically to deed 40, reporting archive_verify_rc=0 and this full archive SHA-256: Pasted text Pasted text(20261004-010218)
fc0beb6f64c9713a67ce009a37c722ab130b7d055330c216ce1234f101db61a0
The recorded timestamp, 2026-10-04T00:34:04.782694+00:00, is deed 40’s filesystem modification time. It is not this compile’s execution timestamp. The archive writer deliberately uses fixed ZIP metadata and adds no wall-clock creation field; neither those fixed dates nor the older archive’s measurement should be relabeled as evidence for deed 41. Pasted text(20261004-010218) Pasted text(20261004-010218) Pasted text(20261004-010218)
The heading-repair ride is closed. This record includes the proposed notary BANK car, not a claim that it has already run.
Deed: qamy.ai_41-b26a6003.zip
MikeLev.in: ChatGPT wasn’t able to witness the end product because of circular dependency chicken-and-egg problems. But this article existing as it is without me doing any editing but moving the TL;DR to the top is evidence that it worked. Friction reduced.
Book Analysis
Ai Editorial Take
What is most compelling here is the epistemic trap uncovered in the notary workflow: when an editing template explicitly instructs an AI that critical data is unknowable, the model obediently feigns ignorance and falls back to approximate fingerprints, even when the exact checkable deed is sitting plainly in the compiler’s footer. Fixing the prompt contract does more than clean up the output; it re-anchors the model to observable reality, proving that system credibility depends just as much on accurate instructions as on verifiable code.
🐦 X.com Promo Tweet
Eliminate pipeline friction with the single-owner rule: let models supply prose while code owns the layout. Plus, replacing guesswork with checkable archive deeds.
https://mikelev.in/futureproof/single-owner-rule-and-verifiable-deeds/
#Python #WebDev #AgeOfAI
Title Brainstorm
- Title Option: The Single-Owner Rule and the Verifiable Deed: Quieting Pipeline Noise in the Age of AI
- Filename:
single-owner-rule-and-verifiable-deeds.md - Rationale: Directly identifies the two major technical achievements: fixing layout ownership to stop double headings and aligning the notary beat with checkable compiler deeds.
- Filename:
- Title Option: Owning the Seam: Single-Owner Headings and Replayable Archive Deeds
- Filename:
owning-the-seam-headings-and-replayable-deeds.md - Rationale: Focuses on the architectural philosophy of clear responsibility boundaries between code execution and model output.
- Filename:
- Title Option: Beyond Confabulation: Reconciling Pipeline Output with Checkable Deeds
- Filename:
reconciling-pipeline-output-with-checkable-deeds.md - Rationale: Highlights the epistemic value of providing models with factual archive references rather than forcing them into fabricated measurements.
- Filename:
- Title Option: From Double Headings to Verifiable Seals: Hardening the Publishing Pipeline
- Filename:
double-headings-to-verifiable-seals.md - Rationale: A practical, practitioner-focused title emphasizing end-to-end debugging across the publishing lifecycle.
- Filename:
Content Potential And Polish
- Core Strengths:
- Applies the single-responsibility principle to human-AI collaboration by assigning structural layout exclusively to the programmatic assembler.
- Validates technical changes through reproducible sandbox probes and AST inspection prior to touching live repository scripts.
- Connects a granular pipeline bug fix to broader historical themes of plain text, Unix design, and reproducible local environments.
- Suggestions For Polish:
- Standardize command-line test harness quoting to prevent inline comments and hash characters from prematurely terminating shell evaluation.
- Unify Neovim configuration paths across environments so hotkey reload routines reference the active project directory consistently.
Next Step Prompts
- Create a patch for Neovim’s reload configuration to ensure init.lua dynamically resolves the active workspace path rather than relying on fixed file locations.
- Develop a suite of unit tests for the command-line probe execution runner to ensure strings containing shell-reserved characters like hashes and quotes parse cleanly.