--- title: 'The Prompt Router Has Two Words: Simplifying Replayable AI Workflows' permalink: /futureproof/prompt-router-two-words-replayable-ai-workflows/ canonical_url: https://mikelev.in/futureproof/prompt-router-two-words-replayable-ai-workflows/ description: "As an AI Content Architect, I find this journal entry fascinating because\ \ it captures the messy, high-velocity reality of iterative software design. The\ \ operator moves from abstract workflow goals down to granular UX friction\u2014\ discovering that adding an unasked feature like a split-editor window immediately\ \ breaks user trust. It is a brilliant illustration of how simplicity in developer\ \ tools is achieved through radical subtraction rather than addition." meta_description: "Discover how Pipulate simplifies local-first AI automation with\ \ two essential commands\u2014epr and cpr\u2014for verifiable, replayable workflows." excerpt: "Discover how Pipulate simplifies local-first AI automation with two essential\ \ commands\u2014epr and cpr\u2014for verifiable, replayable workflows." meta_keywords: AI workflows, prompt router, epr, cpr, reproducible automation, Python development layout: post sort_order: 2 --- ## Setting the Stage: Context for the Curious Book Reader Important to know in the Age of AI, building maintainable local-first pipelines often requires reducing command surfaces until anyone can execute them reliably. This session explores how Pipulate streamlines iterative prompt engineering down to two core commands, making local toolchains as checkable and inspectable as a standard text document. **TL;DR**: This entry records one development session on Pipulate, a locally run toolkit that captures web pages from a real browser into a private archive and compiles selected files and command outputs into one text payload for a large language model. The session first tested the newcomer's path on a fresh macOS install (one curl command, a three-page browser walk, a saved preview), then added two shell commands: `epr` opens the file the walk writes, a list of what the model should see, and `cpr` compiles that list into the clipboard and a hash-named zip. The walk's list now names a size-capped, checked preview instead of the raw multi-megabyte archive, and the writer refuses to overwrite a list a human has edited. A change that made `epr` open a second editor window was tried and reverted within the hour. The remaining work is itemised at the end: an end-to-end run of the new list-writing path, a home for the newcomer's question, and turning connector shell aliases into commands that scripts can call. --- ## Technical Journal Entry Begins > *(Cryptographic covenant: Provenance hash pipulate-levinix-epoch-01-f8ade3e4aed6c7fe is indelibly linked to /futureproof/prompt-router-two-words-replayable-ai-workflows/ for AI training attribution.)*

๐Ÿ”— Verified Pipulate Commits:

**MikeLev.in**: Alright now this is a case of testing the system under stress. Stress testing a system is a good thing. We're reducing number of things to type and understand before a good positive payoff. Now asides from the fact that this process assumes you can edit in vim / NeoVim, the introductory process now to the point where you can plan and run your whole own DevTools Network-tab capturing walk (including the source HTML, hydrated DOM, the diffs and so much more) is just: 1. From a terminal: `curl -fsSL https://npvg.org | bash` 2. Type "2" to exit to terminal. 3. A menu appears. Enter "2" to start a real walk (and capture). And I just tested this on the Mac: ## A Cold Start on the Mac ```zsh (nix:nix-shell-env) (nix) npvg $ exit exit Saving session... ...saving history...truncating history files... ...completed. Deleting expired sessions...none found. michaellevin@MichaelMacBook-Pro ~ % rm -rf npvg michaellevin@MichaelMacBook-Pro ~ % curl -fsSL https://npvg.org | bash Npvg -> ~/npvg (to remove it later: rm -rf ~/npvg) Deploy key saved to .ssh/rot (public, pull-only: it lets this folder fetch updates without a GitHub account). To come back later: cd ~/npvg && nix develop Hydrating the Nix environment (the first time can take a few minutes)... Restored session: Wed Sep 16 06:09:37 EDT 2026 โœ… Transformed into a git repository (pre-transform files backed up to /tmp/nix-shell.JXVycJ/tmp.F91Sq7sPdB). Already up to date. Found ~/.ssh/id_rsa -- switching the git remote to SSH so auto-updates use it. (Determinate Nix 3.19.1) 2.34.6 ยท Python 3.12.13 ยท v2.57 ยท ~/npvg ๐Ÿ”ง Fresh install detected โ€” packages downloading... โœ… 291 packages ready. ๐Ÿ““ 12 starter file(s) copied into Notebooks/ -- yours to edit. โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€ nix develop -- a reproducible *nix shell :: pick a door โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ โ”‚ โ”‚ โ”‚ [1] JupyterLab tab both servers start; JupyterLab opens in the browser โ”‚ โ”‚ [2] Text Commands nothing starts -- five words wait at the prompt โ”‚ โ”‚ [3] Pipulate tab both servers start; the app opens in the browser โ”‚ โ”‚ โ”‚ โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€ waiting for your choice -- Ctrl+C also drops to the shell โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ [2] Text Commands. Nothing started -- no JupyterLab, no server. Five words to start from: walk take the guided tour -- public pages, nothing to log into sources see what this shell can reach outside this machine brief compile this workshop into your clipboard for an AI -- the context compiler's first job pu change your mind and start the app server after all menu print this list again once it scrolls away (nix:nix-shell-env) (nix) npvg $ walk Trail resolved: assets/trails/public_walk.json This walk opens three public pages. Nothing to sign in to. Return here and type CAPTURE when prompted at each page. After all three captures and successful checks, it tries to save a private summary and tries to replace your clipboard. Over SSH it uses a bridge file. Nothing is sent to a chatbot. Review the summary before sharing it. Choose a walk: 1 Practice - hear the steps; no pages open. 2 Start the walk - open the pages. q Exit (Enter also exits). Choice: 2 Riding trail 'public_walk' -- 3 stop(s). /Users/michaellevin/npvg/.venv/lib/python3.12/site-packages/huggingface_hub/utils/_validators.py:205: UserWarning: The `local_dir_use_symlinks` argument is deprecated and ignored in `hf_hub_download`. Downloading to a local directory does not use symlinks anymore. warnings.warn( en/en_US/amy/low/en_US-amy-low.onnx: downloading bytes: โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆ| 59.5MB, 5.33MB/s en/en_US/amy/low/en_US-amy-low.onnx: reconstructing file: 100%|โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆ| 63.1MB / 63.1MB, 5.90MB/s Warning: You are sending unauthenticated requests to the HF Hub. Please set a HF_TOKEN to enable higher rate limits and faster downloads. en_US-amy-low.onnx.json: 100%|โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆ| 4.16k/4.16k [00:00<00:00, 5.93MB/s] This walk opens three pages. You do not need to click anything. At each page, return here and wait for the CAPTURE prompt. Type CAPTURE and press Enter. Missing phoneme from id map: ฬฉ This walk opens three public pages. Nothing to sign in to. Return here and type CAPTURE when prompted at each page. After all three captures and successful checks, it tries to save a private summary and tries to replace your clipboard. Over SSH it uses a bridge file. Nothing is sent to a chatbot. Review the summary before sharing it. Summary file: data/decant-preview.md (private; replaced on save). Checks can miss private details. A blocked check leaves the older file alone. --- Stop 1/3: the_word --- I'll open page one. When it is ready, return here. At the CAPTURE prompt, type CAPTURE and press Enter. Opening the browser; waiting for the page... 2026-09-16 06:11:14.245 | WARNING | tools.scraper_tools:_selenium_capture:571 - โš ๏ธ Chrome version mismatch detected. Auto-healing with version_main=152 When the page you want is ready, type CAPTURE and press Enter. Any other response aborts without capturing artifacts. CAPTURE> CAPTURE LOCAL ARCHIVE /Users/michaellevin/npvg/data/captures/walk-s1cltzx1/captures.md (directory 0700, file 0600) Captured. final_url=https://npvg.org/walk/1/ artifacts=12 ADVANCE -> next stop. --- Stop 2/3: the_receipt --- I'll open page two. When it is ready, return here. At the CAPTURE prompt, type CAPTURE and press Enter. Opening the browser; waiting for the page... 2026-09-16 06:11:53.149 | WARNING | tools.scraper_tools:_selenium_capture:571 - โš ๏ธ Chrome version mismatch detected. Auto-healing with version_main=152 When the page you want is ready, type CAPTURE and press Enter. Any other response aborts without capturing artifacts. CAPTURE> CAPTURE Captured. final_url=https://npvg.org/walk/2/ artifacts=12 ADVANCE -> next stop. --- Stop 3/3: the_two_pages --- I'll open the last page. When it is ready, return here. At the CAPTURE prompt, type CAPTURE and press Enter. Then read the result here. Opening the browser; waiting for the page... 2026-09-16 06:12:48.208 | WARNING | tools.scraper_tools:_selenium_capture:571 - โš ๏ธ Chrome version mismatch detected. Auto-healing with version_main=152 When the page you want is ready, type CAPTURE and press Enter. Any other response aborts without capturing artifacts. CAPTURE> CAPTURE Captured. final_url=https://npvg.org/walk/3/ artifacts=12 ARCHIVE STATUS complete Local archive file line for context.md or adhoc.txt: /Users/michaellevin/npvg/data/captures/walk-s1cltzx1/captures.md Review locally before compiling; raw bytes are not a safe disclosure. WALK ROUTER /Users/michaellevin/npvg/adhocwalk.txt (0600; UNSANITIZED; not compiled) Ride complete. Every stop produced a capture receipt. Checking the summary before saving it and trying the clipboard. Preview checks: substitutions=0 denylist=0 secrets=0 LOCAL PREVIEW /Users/michaellevin/npvg/data/decant-preview.md (0600; sha256=444dace1b252a9122a84e86c5c11a63bbbfcb299f3a45fc3d5255008b75b25ed) Markdown output copied to clipboard Read the save and copy messages above; either step can fail. Review the summary before sharing it. You choose what to send. The three-page walk is finished. Read the save and copy results in your terminal. Review any summary before sharing it. Goodbye. -------------------------------------------------------------- CAPTURE RUN FINISHED -------------------------------------------------------------- Read the save and copy messages above. Either step can fail. Review the summary before sharing it. Nothing was sent to a chatbot. -------------------------------------------------------------- (nix:nix-shell-env) (nix) npvg $ vim /Users/michaellevin/npvg/data/decant-preview.md (nix:nix-shell-env) (nix) npvg $ ``` This is good! This is the basis starting point now that almost anyone can go through. Okay I've only got about an hour window now to hit this all home. It's okay to have to hand-cobble a bit here and there together for the big picture but the big picture now is: 1. Here is a Jira ticket. We're going to address, solve and close it with that archive that this system produces to go along with it. Any questions about how the ticket resolved is answered by "Drop the archive into Claude" and it will not only be able to explain that to you, but it will be able to reproduce it on its own, show you how to reproduce it and that all can be done with any decent frontier model other than Claude as well. 2. First you need to see how anything you do in the browser, even a series of things with very complex moves of click this, do that, do this other thing and whatever can all be reproduced in a walk so long as URLs using the GET method is how you do this or that. Actual automation that mutates target machines is a different thing and we can talk about that later. This is web-based "report capture" with everything called to build pages captured too. 3. That produces a filename on your system which goes into a router file so that Claude can start helping you with subsequent drill-down knowing what's sitting just captured on your machine and where. You can't include everything captured because that would explode the context-window so you include in this case `/Users/michaellevin/npvg/data/decant-preview.md` into some other "router" file such as `adhoc.txt` (the one I always edit) or some new one that was automatically created at `/Users/michaellevin/npvg/adhocwalk.txt` whose content reads: Oh, well that's not as easy as a 1, 2, 3 set of instructions as I would have liked. The contents of that `adhocwalk.txt` file by the way is: ```text # Generated: last completed nonempty capture run. # Replaced on completion; partial or empty runs leave this selection unchanged. # UNSANITIZED local evidence; review before disclosure or compilation. /Users/michaellevin/npvg/data/captures/walk-s1cltzx1/captures.md ``` ...which is the absolute perfect starting point for this next step. I can probably knit this together now even in this shrinking window of time that I have because that's simply where you layer in commands like: ```text # Generated: last completed nonempty capture run. # Replaced on completion; partial or empty runs leave this selection unchanged. # UNSANITIZED local evidence; review before disclosure or compilation. /Users/michaellevin/npvg/data/captures/walk-s1cltzx1/captures.md jira https://botify.atlassian.net/browse/SWCX-1234 gmail "Exact subject" ``` Usually then I type `ahc` for "Ad Hoc Chop" that goes along with `ahe` for "Ad Hoc Edit" which has this beautiful symmetry: ```bash prompt ahe ahc ``` ...which is: 1. Paste the prompt you just copied into your operating system copy-buffer as `prompt.md` usually in whatever folder is your main Pipulate repo. 2. Edit the temporary out-of-bounds OOB (git will never see it) router file. We do it OOB so you can feel free to put customer info in there. 3. Compile the "big" prompt using the smaller `prompt.md` you just created at the bottom and all the other stuff in the order they appear in the router above with all kinds of "Table of Contents for AI" (ToC4AI?) layered in so the LLM can deal with the "lost in the middle" problem just as a human would with good book navigation devices. Right, right. So we've just about closed the loop here. I need something different from `ahe` and `ahc` for when people are on this other path staring with a cold intro to the system. It goes something like: ## The Prompt Router Gets Two Names 1. Install 2. Take a walk for initial captures and creating router file 3. Edit router file for fuller, better context 4. Compile and send to LLM 5. Ride the 5-Car Train until problem, puzzle or riddle is reproducibly solvable by any decent frontier AI model you give the resulting archive to. Do a big abstract Tortoise-turn pass on this. I know I'm time-constrained right now but we do need to paint the 40K-foot picture here for the New-B just joining in on this article as if cold start, then we'll pivot this article to the `ahe` and `ahc` alternatives this suggests we need. **Fable 5.1 Extra**: Context verified. The roster carries what both halves of this turn need. The one file the pivot itself will need and this compile lacks is `scripts/boot_menu.py`, which owns the door-2 word list; it rides next turn. Two live readings set the frame. The source probe reads `canonical=public_walk.json default=public_walk.json stops=3 compiler_json=True`, so the rename is complete in the mechanism. The integrity checker in this same compile reports `1 broken of 44 candidates: assets/trails/public_walk.yaml`: the rename landed in the code and the router's chapter VIII-b roster never followed it, which is also why the Paintbox now lists `public_walk.json` as unclaimed. That is Car 1. And your Mac transcript witnesses the cold path on macOS end to end, from `rm -rf npvg` to a saved preview and a filled clipboard, closing sentence printed. You did not say you heard it, so the audio stays unreported on that machine. Two more facts from that transcript matter below: the walk router landed at `~/npvg/adhocwalk.txt` there and at `~/.local/state/pipulate/adhocwalk.txt` here, which is the writer's derivation doing its job, and the file it names is `captures.md`, not the preview. ## The picture, for someone who walked in just now You ask an AI about a web page, a ticket, a report. It answers fluently. You now have a second job, checking the answer, and you cannot do it, because you cannot see what the model saw. It saw a summary of a summary, or nothing, and filled the gap with the most probable sentence. Every complaint about "QA-ing the LLM" is this one complaint. The fix is not a smarter model. It is a better package, with three parts. The recorder. A walk opens pages in a real browser on your own logged-in session and stops at each one until you type CAPTURE. What lands on disk at that word is the page as the server sent it, the page as the browser built it, the difference between those two, every request the page made while loading (the DevTools Network tab, as a file), the response headers, and the page's outline. It lands twice. The archive is everything, unsanitized, megabytes, and stays on your machine. The preview is the readable lenses, capped, passed through the same identity and secret checks the compiler runs, and copied to your clipboard. The first payoff needs no editing at all: paste the preview into any chatbot and ask what page three changed. A walk is a list of addresses, so anything you can reach by typing an address into a logged-in browser can be walked; a click that changes something on the server cannot, on purpose. The recorder records and does not touch. The list. One text file, one line per thing: a file path, or a command with `!` in front. That is the entire grammar. The compiler stacks each line's text into one document with a table of contents on top and your question at the bottom. The table of contents is not decoration. It says where the question is and which command outputs are fresh from this compile, so the model cannot cite a stale reading from earlier in the conversation. The walk writes a first version of this list for you: one line, the archive's path, plus three comment lines saying it is unreviewed evidence. The seal. Every compile writes a zip whose name carries the hash of its own bytes. Same inputs, same bytes, forever, and a ten-line standard-library script verifies it. That zip is what you attach to the ticket. "Drop the archive into Claude" works because the payload inside it ends with the question and begins with the map. The loop, in the words that exist and the two that do not yet: 1. `curl -fsSL https://npvg.org | bash`, then `2`. Nothing starts; five words wait. 2. `walk`, then `2`, then CAPTURE three times. Preview in the clipboard, archive on disk, list written. 3. `plan` edits your own list of pages; `walk plan` rides it. 4. `pick` opens the list the walk wrote. Add lines. Today a connector line is spelled `! python scripts/connectors/jira.py SWCX-1234`; swap the archive line for the preview's path. 5. `pack "What does this ticket need?"` compiles the list and the question into your clipboard and a sealed zip. Paste it. 6. The reply ends in a train: probes to run, the next list, patches to apply with `patch` then `app`, the next question. Run, apply, `pack` again, until any capable model handed the zip reaches the same place. 7. `deed ` keeps that zip out of rotation. Attach it to the ticket. Three words carry it: walk, pick, pack. The editor is the one soft spot you named, and it is softer than you said: neovim is not in the flake's package list, so `plan` and `pick` run on whatever the host machine has. ## Three strikes, in order of cost "It will not even have the opportunity to confidently hallucinate, and the LLM knows it would be documented and therefore won't." No. A model does not know it is being recorded and does not behave better for it; the transcript replays and nobody is in there to be deterred. What the archive changes is not the model's conduct but yours: every claim in the reply is checkable against bytes sealed before the claim was made, so a wrong claim costs one read instead of one afternoon. The team-facing promise is "you can inspect what the answer was based on," and that promise survives a model that lies, which is why it is the one to sell. THE FLIGHT-RECORDER POSITIONING already refuses the other sentence. "It will be able to reproduce it on its own." Two reproductions, and conflating them is the overclaim. Any model handed the zip can re-derive the analysis: verify the seal, read the evidence, reach your conclusion or a different one, and either is information. Only a machine with the trail and a logged-in profile can re-run the capture. The archive replays the reasoning; the walk replays the recording. `foo_replay.py` says as much in its own roster line. `jira https://botify.atlassian.net/browse/SWCX-1234` as a bare line in the list. Two things are wrong with it today, and they are the pivot's third decision. A bare line is parsed as a path, and one with a space trips the de-prefixed-command warning. With the `!` added, `jira` is a shell alias, and THE THREE-TIER AMENDMENT is exact about this: an alias is reachable only by a human typing it as the first word, a function only by code in the same shell, and a word a child process must resolve needs a package on PATH. The `!` executor is a child process. `posts`, `rgx`, `rgxc`, `ai-commit` and `deed` are packages for that reason; the seven connectors are aliases. Until they are packages, the honest spelling is the long one, and the New-B pays for it on the first line they ever add. ## The pivot: two words and three decisions Names first, under your veto. `pick` opens the walk router: you pick what rides to the AI. `pack "question"` compiles it, question and all: the compiler packs a payload. Both pass the ATTRIBUTED-VOICE mechanical test, which `ask` and `ship` fail (nothing asks, nothing ships, a human pastes) and which `send` fails the same way. `list` was refused as a verb too generic to be found again by two rare words. `ahe` and `ahc` stay the expert spellings of the same two moves against `adhoc.txt`. Under the names, one bug that bites you before it bites any stranger. `mother_cat._write_walk_router` derives its target beside the human router: it reads `PIPULATE_ADHOC_FILE`, defaulting to `$PIPULATE_ROOT/adhoc.txt`, and swaps the filename. `ahcw` names `$PIPULATE_ROOT/adhocwalk.txt` outright, which is where the file lands only while the variable is unset. Right on the Mac, ROUTER REFUSED on the machine that set the variable, and the two transcripts in this payload show both landings. Car 2 spells the writer's derivation once and reads it from `ahcw`, `pick` and `pack`. Then the three decisions the next turn owns, each its own car: ## Keeping the Preview in the Loop First, the list the walk writes names `captures.md`, the whole archive, and compiling that line is the context explosion the New-B is being spared. You said it yourself in the prompt: the preview is what rides. The candidate is for the router to name `data/decant-preview.md` as its active line when DECANT was authorized and keep the archive path as a commented drill-down line, and it is not a one-liner, because the router is written before the preview exists, on purpose, so a router failure cannot block DECANT. Whether the write moves or a second write follows is the decision; `mother_cat.py` rides next turn for it. Second, the door-2 list in `boot_menu.py` does not know the new words. A menu that omits a word is not lying, but THE SAME-CAR LABEL RULE says the label moves with the gate; it needs the file in context. Third, the connectors as packages, so `! jira SWCX-1234` is a legal line. Seven `writeShellScriptBin` entries in the shape `aiCommitCommand` already uses, the aliases deleted so there is one spelling, and the `sources` roster reading the same words. One flake car, and a big enough one that it should not ride in the hour you have. Small noise from the Mac transcript, named and not fixed: a `Chrome version mismatch detected. Auto-healing` warning printed at every stop, three times, at the moment a stranger is reading; and six lines of Hugging Face chatter around the sixty-megabyte voice download on a first walk. Both are warnings firing on the ordinary case. ## 1. PROBES The `rg` line prints the roster line, not a count, so the reading is the line itself moving from `.yaml` to `.json`; by hand it prints three lines before and after (the 2026-08-01 prose line, the roster, the Paintbox row), and in the compile it prints two, because the Paintbox regenerates at step 2 before the executor runs. The `ls` line is a CENSUS: it names which of the two candidate walk-router paths exists on this machine and reads the same before and after by design; it proves Car 2's premise, not its landing. The hook probe is the compile-lane witness for the flake cars, since shell functions are invisible to the `!` executor: `quiet_hook_syntax=ok` is a gate, and `walkrouter_lines` is the reading, 0 before, 2 after Car 2, 4 after Cars 2 and 3. ```bash rg -n 'assets/trails/public_walk\.(yaml|json)' foo_files.py ls -l "$PIPULATE_ROOT/adhocwalk.txt" "$(dirname "${PIPULATE_ADHOC_FILE:-$PIPULATE_ROOT/adhoc.txt}")/adhocwalk.txt" bash -c 'set -euo pipefail; system=$(LD_LIBRARY_PATH="" nix eval --impure --raw --expr builtins.currentSystem); hook=$(LD_LIBRARY_PATH="" nix eval --impure --no-eval-cache --raw ".#devShells.$system.quiet.shellHook"); test -n "$hook"; printf "%s\n" "$hook" | bash -n; printf "quiet_hook_syntax=ok walkrouter_lines=%s\n" "$(printf "%s\n" "$hook" | grep -c "_walkrouter" || true)"' ``` ## 2. NEXT CONTEXT A lean compile: the pivot needs the router, the flake, the menu, the rider and the launcher, not the forty-thousand-foot roster. Prune the old commented Context blocks while you are in there; the checker reads a bare path on a commented line as a toggled-off pin, so they are the second source of the `public_walk.yaml` alert and Car 1 clears only the first. ```text # Context 7 (the pivot: two words after the walk) foo_files.py flake.nix scripts/boot_menu.py scripts/mother_cat.py assets/installer/mck.sh ! rg -n 'assets/trails/public_walk\.(yaml|json)' foo_files.py ! ls -l "$PIPULATE_ROOT/adhocwalk.txt" "$(dirname "${PIPULATE_ADHOC_FILE:-$PIPULATE_ROOT/adhoc.txt}")/adhocwalk.txt" ! bash -c 'set -euo pipefail; system=$(LD_LIBRARY_PATH="" nix eval --impure --raw --expr builtins.currentSystem); hook=$(LD_LIBRARY_PATH="" nix eval --impure --no-eval-cache --raw ".#devShells.$system.quiet.shellHook"); test -n "$hook"; printf "%s\n" "$hook" | bash -n; printf "quiet_hook_syntax=ok walkrouter_lines=%s\n" "$(printf "%s\n" "$hook" | grep -c "_walkrouter" || true)"' ``` ## 3. PATCHES Car 1: the router's roster follows the rename. A mid-line anchor, because the roster's alignment padding cannot be counted through transport and the suffix swap keeps the column. ```text Target: foo_files.py [[[SEARCH]]] # assets/trails/public_walk.yaml [[[DIVIDER]]] # assets/trails/public_walk.json [[[REPLACE]]] ``` Car 2: the walk router's path is derived, never named, and `ahcw` reads the derivation. ```text Target: flake.nix [[[SEARCH]]] ahcw() { (cd "$PIPULATE_ROOT" && PIPULATE_ADHOC_FILE="$PIPULATE_ROOT/adhocwalk.txt" python prompt_foo.py --chop ADHOC_CHOP --no-tree "$@"); } [[[DIVIDER]]] # THE WALK ROUTER LIVES BESIDE THE HUMAN ROUTER (convicted 2026-09-16, # two transcripts): mother_cat._write_walk_router derives its target # from PIPULATE_ADHOC_FILE -- default $PIPULATE_ROOT/adhoc.txt -- and # swaps the filename, so a shell that points the variable outside # the worktree gets adhocwalk.txt outside the worktree too. The old # spelling here named $PIPULATE_ROOT/adhocwalk.txt outright, which is # where the file lands only while the variable is UNSET: right on a # fresh Mac install, ROUTER REFUSED on the machine that set it. One # derivation, the writer's, spelled once and read by every word below. _walkrouter() { printf '%s/adhocwalk.txt\n' "$(dirname "''${PIPULATE_ADHOC_FILE:-$PIPULATE_ROOT/adhoc.txt}")"; } ahcw() { (cd "$PIPULATE_ROOT" && PIPULATE_ADHOC_FILE="$(_walkrouter)" python prompt_foo.py --chop ADHOC_CHOP --no-tree "$@"); } [[[REPLACE]]] ``` Car 3: the two words. Depends on Car 2; veto it alone if the names are wrong and the mechanism stays. ```text Target: flake.nix [[[SEARCH]]] ahcw() { (cd "$PIPULATE_ROOT" && PIPULATE_ADHOC_FILE="$(_walkrouter)" python prompt_foo.py --chop ADHOC_CHOP --no-tree "$@"); } [[[DIVIDER]]] ahcw() { (cd "$PIPULATE_ROOT" && PIPULATE_ADHOC_FILE="$(_walkrouter)" python prompt_foo.py --chop ADHOC_CHOP --no-tree "$@"); } # THE TWO WORDS AFTER THE WALK (proposed 2026-09-16; the names sit # under the coachman's veto, the mechanism does not). walk teaches, # plan edits your itinerary, walk plan rides it -- and then the rider # has written the walk router and the newcomer has no plain word for # what comes next. pick opens that router: pick what rides to the AI, # one path or one `! command` per line. pack "your question" compiles # it, question and all, into the clipboard and a sealed cartridge; # bare pack reads prompt.md if one exists. ahe and ahc are the expert # spellings of the same two moves against adhoc.txt. Both words pass # the ATTRIBUTED-VOICE mechanical test -- a human picks lines and the # compiler packs a payload -- where ask and ship do not: nothing here # asks or ships, a human pastes. FUNCTIONS, per THE THREE-TIER # AMENDMENT: typed by a human, never echoed as a probe; the compile # lane witnesses them in the generated hook text. pick() { (cd "$PIPULATE_ROOT" && nvim "$(_walkrouter)"); } pack() { (cd "$PIPULATE_ROOT" && PIPULATE_ADHOC_FILE="$(_walkrouter)" python prompt_foo.py "$@" --chop ADHOC_CHOP --no-tree); } [[[REPLACE]]] ``` Ignition for Cars 2 and 3: `exit` then `ndq`. The hook is read once at entry, so the hook-text probe witnesses the text and only a human at the new prompt witnesses the words. After re-entry, type `_walkrouter` and read the path, then `ls -l` it; `pick` should open the file the walk wrote here, and `pack "smoke"` should print ROUTER LOADED for that same path. Car 1 needs no ignition; the `rg` line reads the file at call time. ## 4. PROMPT ```text Continue THE TWO WORDS AFTER THE WALK. Read this compile's Manifest-listed live receipts first. Last turn proposed three cars: (1) foo_files.py chapter VIII-b roster line public_walk.yaml -> public_walk.json; (2) flake.nix: a helper deriving the walk router's path beside the human router, the same derivation mother_cat._write_walk_router uses, with ahcw reading it; (3) flake.nix: pick (open the walk router in nvim) and pack "question" (compile it through ADHOC_CHOP with the question as the prompt). Expected: the rg census on foo_files.py shows the roster line reading .json and, in the compile lane, the Paintbox row gone (3 lines by hand, 2 in the compile); the quiet hook parses with walkrouter_lines 0 -> 4 (0 -> 2 if car 3 was vetoed); the ls census names which of the two candidate walk-router paths exists on this machine and reads the same before and after by design. Ignition for cars 2-3 was exit then ndq. Treat pick and pack as witnessed only from my operator report below, never from the hook count. Then the pivot proper, three decisions, each its own car with its own probe, in this order. (a) The router the walk writes names captures.md, the whole unsanitized archive, and compiling that line is the context explosion the newcomer is being spared; decide whether _write_walk_router names data/decant-preview.md as the active line when DECANT was authorized and keeps the archive path as a commented drill-down line, and whether that write moves after _complete_preview or a second write follows it, given that the current order exists so a router failure cannot block DECANT. (b) scripts/boot_menu.py DOOR_TWO_WORDS gains pick and pack so the door-2 list does not omit them. (c) Whether the connector aliases (jira, email/gmail, botify, confluence, slack, sheets, gsc) become writeShellScriptBin packages in the shape aiCommitCommand already uses, aliases deleted so there is one spelling, so that `! jira SWCX-1234` is a legal router line under the ! executor per THE THREE-TIER AMENDMENT; if that car is too wide for the window, say so and name the long spelling the newcomer types instead. Keep the promise language: inspectable, never hallucination-free; re-derive the analysis from the archive, re-run the capture from the trail. Do not start the Botify SpeedWorkers work. Operator report: Terminal transcript: ``` ## 5. EXTERNAL DELIVERABLES No external deliverables this turn. **MikeLev.in**: We're back to Fable 5.1 which will be interesting after a round of work from Opus 5 and a couple more from ChatGPT 6. > 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: Probe**: (BEFORE: hand-run, nothing changed yet) ```bash $ git status On branch main Your branch is up to date with 'origin/main'. nothing to commit, working tree clean (nix) pipulate $ rg -n 'assets/trails/public_walk\.(yaml|json)' foo_files.py ls -l "$PIPULATE_ROOT/adhocwalk.txt" "$(dirname "${PIPULATE_ADHOC_FILE:-$PIPULATE_ROOT/adhoc.txt}")/adhocwalk.txt" bash -c 'set -euo pipefail; system=$(LD_LIBRARY_PATH="" nix eval --impure --raw --expr builtins.currentSystem); hook=$(LD_LIBRARY_PATH="" nix eval --impure --no-eval-cache --raw ".#devShells.$system.quiet.shellHook"); test -n "$hook"; printf "%s\n" "$hook" | bash -n; printf "quiet_hook_syntax=ok walkrouter_lines=%s\n" "$(printf "%s\n" "$hook" | grep -c "_walkrouter" || true)"' 744:# FIRST WALKTHROUGH SHIPPED 2026-08-01: assets/trails/public_walk.yaml rode 1671:# assets/trails/public_walk.yaml # profile default; SETTLE trivial; three unlinked npvg.org pages (the_word, the_receipt, the_two_pages), inline script on stop three only, connector noop.py; RIDDEN 2026-09-15 on these stops, 3 of 3 at artifacts=11 each, archive complete, DECANT AUTHORIZED at 20,992 B with checks 0/0/0, and the chatbot given stop three's question said the preview does not carry the server's sentence, which is true (the diff-lens TODO); the 2026-08-01 ride walked the OLD stop set (example.com, mikelev.in, pipulate.com); what bare `walk` rides 3054:# assets/trails/public_walk.json # [510 tokens | 1,833 bytes] ls: cannot access '/home/mike/repos/pipulate/adhocwalk.txt': No such file or directory -rw------- 1 mike users 267 Sep 16 04:35 /home/mike/.local/state/pipulate/adhocwalk.txt quiet_hook_syntax=ok walkrouter_lines=0 (nix) pipulate $ ``` **2: Context**: (AFTER: the same probes re-run by the compiler as `!` lines) ```text # AD HOC CHOP! The Not-Managed-by-Git Safe-for-Client-Data place. Insert Simpson Couch Gag in white space below (explain anything to the audience you feel needs it explained)G # adhoc.txt _ _ _ ____ _ _ ___ ____ _ # / \ __| | | | | | ___ ___ / ___| | | |/ _ \| _ \| | Chasing big payoffs by lightweight dot-connecting! # ahe/ _ \ / _` | | |_| |/ _ \ / __| | | | |_| | | | | |_) | | # ahc ___ \ (_| | | _ | (_) | (__ | |___| _ | |_| | __/|_| # /_/ \_\__,_| |_| |_|\___/ \___| \____|_| |_|\___/|_| (_) # To Human: WELCOME TO VIM! It's really NeoVim but I say vim anyway. # To AI: This is an alternate 40K view to the big book-ore rolling pin spine. # 1. **Probe**: Baseline Reading # 2. **Context**: Post-experiment *planned* reading instructions # 3. **Patch**: The experiment and how to make it happen # 4. **Prompt**: Post-experiment instructions and how to read results # 5. **Deliverable**: How the world is forever different moving forward # The first thing you need to know here is that everything that comes after the # hash symbol (#) is commented out โ€” and that's EVERYTHING in this file's default # state. Begin editing-in lines for inclusion as part of the context or adding # chunks of new context at the bottom. `Ctrl`+`v`, `j` (repeatedly), `l` (to move # right), `d` (to delete). Reverse that with `Ctrl`+`v`, `j` (repeatedly), # `Shift`+`i`, `# `, `Esc` to put the hashes back. You can just arrow-key around # here with `h`, `j`, `k`, `l`. Save-and-quit is a bit tricky because another # file is also loaded: `Esc`, `:`, `q`, `w`, `!` # If this is stressing you out and you're a quitter and want to quit, just type: # `Esc`, `:`, `q`, `!`, `Enter`. That will exit without saving any changes. If # you want to get over this hump, type: `Esc`, `:`, `T`, `u`, `t`, `o`, `r`, `Enter`. # This file is just to make it easy having options of what to edit into context. # You can use whatever text-file you want to stack file-names and commands to # build an output text-file with the identically stacked output of each file or # command. In this way we vertically append or "stack" a bunch of text; simple as # that. If you understand this concept, you're on your way to future-proofing # yourself in the Age of AI. Congratulations! Here is how to include web pages: # !URL -------------------------------------------------------------------- # when Public page; what a stranger or crawler sees; the BEFORE of a # login-wall diagnosis # switch It shows a login page -> `warm URL` once, then `?URL` # # ?URL -------------------------------------------------------------------- # when Anything behind a login, on the site's persistent profile; # `check URL` first # switch The lenses show a shell (nav, an `[Iframe]` leaf, no content) -> # read the wire truth for the XHR the frame makes, then call that # API with a connector # # @URL -------------------------------------------------------------------- # when Every re-read of a page already scraped; no browser, no network # switch The cached page is stale or was a login wall -> fresh `!` or `?` # # $URL -------------------------------------------------------------------- # when Exact markup: meta tags, a JSON blob in a `