wayfinder: resolve TeamBot public-evidence boundary (#321)

[ojfbot]

Resolves wayfinder #321 on the map fde-operating-presence. Grilled via /grill-with-docs (4 questions, operator-answered).

The ruling

Day-job material enters public FDE artifacts only as de-identified engineering patterns, and only where they pass the stranger test: a reader with no prior knowledge of the operator's employment cannot identify the employer, the internal system, or the team. Re-identification by someone who already knows the operator is explicitly accepted, not defended against. Attributed publishing is out of scope fleet-wide and does not become available by seeking sign-off.

Enforced by construction, not by discipline — a denylist lint sourced from gitignored personal-knowledge/. The rationale is evidential rather than theoretical: the one documented breach of this boundary was committed by an automated session that merged employer-naming material to public main 39 minutes after the governing ticket opened. Agents are the population writing to these repos and they do not read policy before merging. Discipline has one observed failure here and zero observed successes.

The denylist cannot live in the public repo — a list of the terms being protected is itself the disclosure it prevents. personal-knowledge/ is gitignored with zero tracked files and is the one boundary that held cleanly through this entire episode.

What this PR does

• Scrubs HEAD. Employer name went from 3 lines across 2 files to 0 occurrences in tracked files. The load-bearing one was decisions/wayfinder/fde-operating-presence.md:19-20, the single place that bound system nickname → employer → strategic framing. The 9 bare-alias files are left in place: unbound, they pass the stranger test, and the lint will sweep them.
• Creates decisions/open-unknowns.md — the grill's durable artifact, and the first in this repo.
• Tends the map — gist appended to ## Decisions so far, TeamBot public-evidence boundary #321 marked closed, Positioning narrative + venue map #328 flagged as partly invalidated, and the TeamBot-pattern-flow fog graduated to a ticket (Sanitized pattern-flow loop #342) now that the boundary makes its question statable.

What this PR does NOT do

• No history rewrite. 10 commits still carry the strings (earliest 2026-06-25). Deferred deliberately: force-pushing main against ~23 live agent sessions and 3 worktrees is a larger risk than a history exposure that 0 forks and 0 stars say nobody currently holds. Logged as a deferred decision.
• No lint. That is a delivery, not a decision — it belongs on a roadmap, not on the map (two-ledger rule).
• No ADRs written. Three stubs are drafted for you to run through /adr new: employer-evidence-boundary, boundary-enforced-by-construction, staged-history-remediation.

The assumption this rests on

Recorded plainly in the ledger rather than buried: the ruling was made without either party reading the actual employment agreement or publication policy. If that policy requires pre-approval for any work-derived publication, this ruling is void and the boundary collapses to employer-indifferent. Worth reading before the first pattern-level artifact publishes, not after.

Unrelated live hazard, flagged not fixed

core-library/public/graph/selfco.json — 1.5 MB, untracked, not gitignored, in a public repo, carrying a protected term in a node title. One git add -A publishes it. Different repo, so out of scope here; it wants a one-line .gitignore entry.

🤖 Generated with Claude Code

[github-actions]

Skill Audit — PR #343

Skills used during development

• /frame-standup
• /wayfinder

Recommended skills (based on diff analysis)

• /investigate — PR references bug fix — was root cause analyzed?

Coverage

• /investigate was not used but is recommended

---

Generated by skill-audit

[ojfbot]

Follow-up pushed (8ae7ce6), plus a fix in a sibling repo.

Fixed: core-library@ccbf853 gitignores public/graph/ wholesale — the generated vault graph can no longer be committed to that public repo. Pushed directly to core-library/main (unprotected) rather than via PR, since a safety fix sitting in an open PR protects nothing.

Resolved: the employment-agreement assumption — operator-confirmed. Struck through in the ledger rather than deleted, so a future reader can see it closed by confirmation rather than by document review.

Newly open, and larger than the one just closed: core-library serves the vault graph at runtime. apps/web/src/main.ts:82 fetches /graph/selfco.json, and the vault-ingest Vite plugin regenerates it into publicDir on every build. The repo has no vercel.json, .vercel, or netlify.toml — not being deployed is the only thing containing this. Deploy it and the build republishes the entire private vault graph to a public URL, with .gitignore powerless to stop it. Under adr:boundary-enforced-by-construction that wants a build-time guard (de-identify at ingest, local-only fetch gate, or exclude protected nodes), so deploying core-library is effectively blocked until it's decided.