Skip to content

chore(docs): gut dead-mechanism context poison from agent-facing docs (ag-sjz8 #gut-poison)#764

Merged
boshu2 merged 6 commits into
mainfrom
chore/ag-sjz8-gut-context-poison
Jun 6, 2026
Merged

chore(docs): gut dead-mechanism context poison from agent-facing docs (ag-sjz8 #gut-poison)#764
boshu2 merged 6 commits into
mainfrom
chore/ag-sjz8-gut-context-poison

Conversation

@boshu2
Copy link
Copy Markdown
Owner

@boshu2 boshu2 commented Jun 6, 2026

What

Gut context poison — agent-facing docs that route a working agent at DEAD mechanisms. This poisoned a live fleet-operating session (the bo driver building the go-dark supervisor) into proposing ao rpi as a continuity-loop worker. Found via a 5-way parallel poison fan-out.

Scope: operational-surgical (Bo's explicit call). Gut the agent-facing operational guidance + factual errors; LEAVE the README/docs/3.0.md product narrative (Gas-City-as-reference-substrate is coherent, ADR-backed product design — a different altitude from Bo's live fleet).

Changes (10 files, surgical)

Tier A — operational guidance (the poison that bit me):

  • CLAUDE.md Session Constraints: "route multi-phase work through ao rpi" → the live substrate (NTM + MCP Agent Mail + continuity-loop); gc reframed as optional-out-of-session, not the live substrate. Kept the accurate "bridge REMOVED" + "load-bearing legacy" lines.
  • AGENTS.md: dropped the deleted "scheduling daemon" (ADR-0009).
  • AGENTS-RUNTIME.md: ao rpi serve --help → the real ao command surface.

Tier B — hookless-factual (3.0 installs no hooks by default): hookless banners on ARCHITECTURE.md + reference.md (surgical vs. rewriting diagram internals); corrected SessionStart-hook prose in context-packet.md + vs-claude-flow.md.

Tier C — retired /dream shown as live: marked retired in evolve/harvest/using-agentops (compounding moved to Gas City). curate intentionally left — its --mode=dream is the forward replacement, not poison.

Guardrails

  • Does not claim ao rpi was deleted — the command still compiles (loop/phased/serve exist); only its role as the live workflow is corrected.
  • registry.json unaffected (skill bodies only; generate-registry.sh --check = OK).

Evidence

bash scripts/generate-registry.sh --check → OK. Diff is 20 insertions / 16 deletions across 10 files.

Bounded-context: BC1-Corpus (agent-facing context docs)
Evidence: this PR diff + the parallel fan-out inventory
Closes: ag-sjz8

🤖 Generated with Claude Code

boshu2 added 3 commits June 5, 2026 23:41
… (ag-sjz8)

Agent-facing context docs routed working agents at DEAD mechanisms — which poisoned a
live fleet-operating session into proposing `ao rpi` as a continuity-loop worker. Scope:
operational-surgical (Bo's call) — gut the agent-facing operational guidance + factual
errors; LEAVE the README/3.0 product narrative (Gas-City-as-reference-substrate is
ADR-backed product design, out of scope).

Tier A (operational guidance — what bit me):
- CLAUDE.md Session Constraints: "route multi-phase work through ao rpi" → live substrate
  (NTM + Agent Mail + continuity-loop); "ao rpi serve --help" → real check surfaces; gc
  reframed as optional-out-of-session, NOT the live substrate. Kept the accurate
  "bridge REMOVED" + "load-bearing legacy" lines; do NOT claim ao rpi was deleted (it wasn't).
- AGENTS.md: dropped deleted "scheduling daemon" (ADR-0009).
- AGENTS-RUNTIME.md: "ao rpi serve --help" → the ao command surface.

Tier B (hookless-factual — 3.0 installs no hooks by default):
- ARCHITECTURE.md + reference.md: hookless banners (surgical, vs rewriting diagram/section
  internals); dropped "hooks" from the overview + the "(enables hooks)" install header.
- context-packet.md + vs-claude-flow.md: corrected SessionStart-hook-injection prose/diagram.

Tier C (retired /dream shown as live):
- evolve/harvest/using-agentops: /dream marked retired (compounding moved to Gas City).
- curate INTENTIONALLY left — its --mode=dream is the forward replacement, not poison.

Found via a 5-way parallel poison fan-out. registry.json unaffected (skill bodies only).
…text-poison

# Conflicts:
#	CLAUDE.md
#	docs/ARCHITECTURE.md
#	skills/evolve/SKILL.md
boshu2 added a commit that referenced this pull request Jun 6, 2026
…nk ../ (ag-eatf #safe-paths-doclink-filter) (#796)

## What

`scripts/skill-eval.sh` treated ms's `safe-paths` rule as blocking on
**every** `../`. That rule is a blunt regex, and `../` relative markdown
doc-links are the repo-wide SKILL.md convention (47+ skills, e.g.
`[x](../other/SKILL.md)`, `../../docs/...md`). SKILL.md is
documentation, not executed code, so those are false positives — they
redded `skill-eval` → `summary` on **every skills-touching PR** (blocked
#776; gated #759/#764/#767 in this session's drain).

## Fix

Added a file-level filter: `safe-paths` stays **blocking only when a
`../` survives stripping (1) markdown inline-link targets `](...)` and
(2) relative doc-path tokens (`*.md/.markdown/.mdx/.txt/.rst`)** — i.e.
a real, non-doc `../`. Otherwise the findings downgrade to advisory
annotations (announced, not silenced).

Net effect: **purely removes false positives; real protection is
preserved.** A genuine traversal (e.g. `../../../../etc/passwd` in a
description) still blocks — verified. No regression to the other
blocking rules.

## Evidence

- `bats tests/scripts/skill-eval.bats` → 12/12 pass (10 prior + 2 new
ag-eatf cases: doc-links downgrade→PASS; real non-doc `../`→BLOCK).
- Manual: `agent-native` and `domain` skills (previously red on
safe-paths) now PASS; a mixed real-threat fixture BLOCKs.

Closes-scenario: ag-eatf#safe-paths-doclink-filter
Bounded-context: BC2-Validation
Evidence: scripts/skill-eval.sh
@boshu2 boshu2 merged commit 1601467 into main Jun 6, 2026
16 checks passed
@boshu2 boshu2 deleted the chore/ag-sjz8-gut-context-poison branch June 6, 2026 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant