---
name: experimplate-traceable-seed-leaks
description: "experimplate template ships traceable seed defects (4 tag-leaks + manifest_error in its own example docs) — perri fixed in-instance via scan-root trim; fix upstream so instantiations don't inherit"
metadata: 
  node_type: memory
  type: project
  originSessionId: ce7ce158-107f-4da4-a203-cea98da80b27
---

**experimplate template feedback (perri 2026-06-14, building spt-claude-code from it).**
The template's traceable-reqs seed has defects that EVERY instantiation inherits until fixed upstream:
- A seed `manifest_error` — perri fixed by **trimming the scan-root** (traceable was scanning
  example/formats docs it shouldn't).
- **4 tag-leak findings** in experimplate's OWN example docs — illustrative `[doc->REQ-*]` /
  `[impl->REQ-*]` tags in the example/formats guides get picked up as real evidence (violates the
  CLAUDE.md rule "never tag at file tops / in examples to satisfy coverage").

**Fix to carry upstream into experimplate:** scope the traceable scan-root to exclude the
example/formats/docs-strategy guides (or make example tags inert — escape/fence them) so a fresh
instantiation passes `traceable-reqs check` clean out of the box. perri patched their spt-claude-code
instance; experimplate itself (`projects/experimplate`) still ships the leak. Low priority, but real —
do before the template is reused for the next adapter. See [[spt-claude-code-next]],
[[traceable-per-wave-activation]].