Phase 1 of substrate-unified-registry: move all references to user
home memory/rules out of plain strings and into content-addressable
path atoms. Public artefacts now contain opaque `{path::NAME}/file.md`
references; the actual home prefix lives only in the path-atom file's
frontmatter, registered in the local kei-registry.
NEW path atoms (`_blocks/path-*.md`):
- `path-user-memory.md` → template `~/.claude/memory`
- `path-user-rules.md` → template `~/.claude/rules`
Both files use frontmatter `type: atom, kind: path, template: ..., expand_at: render`.
BlockMdScanner auto-registers them; DNA index shows them under their
unprefixed names (`user-memory`, `user-rules`) for human lookup, while
the body sha8 makes them content-addressable.
Resolver (`_assembler/src/registry_client.rs`):
- `is_path_atom(conn, name)` — checks DB by name + filename convention
(`_blocks/path-<name>.md`) + frontmatter `kind: path`. Defensive:
filename + frontmatter must BOTH agree.
- `frontmatter_has_kind_path(body)` — minimal YAML parser. Tolerates
CRLF, quoted values, rejects substring matches (`pathological` ≠ `path`).
- 5 unit tests cover positive + 4 negative cases.
Resolver wire-up (`_assembler/src/assembler.rs:147 write_references`):
- For each `references.extra` entry starting with `path:NAME/...`:
- Lookup `NAME` via `is_path_atom`.
- On success: emit `{path::NAME}/<suffix>` — opaque, kit-resolvable.
- On miss: stderr warn + passthrough. Never fatal.
- Non-`path:` refs pass through unchanged. Backward compatible.
- 2 unit tests cover passthrough paths.
Manifest migration (38 manifests touched):
- `~/.claude/rules/<file>` → `path:user-rules/<file>`
- `~/.claude/memory/<file>` → `path:user-memory/<file>`
- 96 references migrated; 1 prose-style reference in security-auditor
left as plain text (lives inside a domain_in description, not in
references.extra — out of scope for this resolver).
Regenerated 38 `_generated/*.md` + 1 new `frontend-validator.md`.
Regenerated `docs/DNA-INDEX.md` (now includes 2 path-atoms by name).
Verification (cited):
- `git ls-files | grep denisparfionovich` → 0 hits outside allowlist
(NOTICE/README byline + `.github/workflows/leak-check.yml` detection
rule).
- `_generated/` contains 99 occurrences of `{path::user-...}/`.
- assembler tests: 29 passed (5 new). kei-registry tests: 10 passed
(8 short_path from earlier commit + 2 unrelated).
- assembler resolver verified end-to-end: ml-implementer.md line
479-485 shows `{path::user-rules}/ml-protocol.md` etc.
What this does NOT do (deferred):
- No registry-DB schema change. Path atoms ride existing Atom block-
type via convention, not via new `BlockType::PathAtom` variant.
- No git-branch tracking (Phase 2 of plan).
- No `kei-registry status` cross-cutting CLI (Phase 3 of plan).
- No path-atom orphan detection CLI (Phase 4).
The path:user-memory and path:user-rules cover 100% of the username-
leak surface from the current manifest set; future categories
(kit-root, registry-db, sync-repo, secrets-env, project-root) can
land additively without architectural changes.
=== STATUS-TRUTH MARKER ===
shipped: functional
stubs: 0
cargo-check: PASS
behaviour-verified: yes
follow-up-required:
- Phase 2 (git-branch tracker hook)
- Phase 3 (kei-registry status subcommand)
- Phase 4 (orphan detection CLI)
- Sync user-side install: ~/.claude/agents/_manifests/ still has
pre-migration absolute paths; will pick up new format on next
`install.sh --add` (out of scope for this commit).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| api-anthropic.md | ||
| api-apify.md | ||
| api-elevenlabs.md | ||
| api-fal-ai.md | ||
| api-graphql.md | ||
| api-openapi-first.md | ||
| api-rest-conventions.md | ||
| api-versioning-pagination-ratelimit.md | ||
| auth-authorization.md | ||
| auth-oauth2-oidc.md | ||
| auth-passkeys.md | ||
| auth-sessions.md | ||
| baseline.md | ||
| ci-forgejo-actions.md | ||
| ci-github-actions.md | ||
| ci-release-automation.md | ||
| ci-security-gate.md | ||
| db-drizzle.md | ||
| db-migration-hygiene.md | ||
| db-postgres.md | ||
| db-sqlite.md | ||
| db-sqlx.md | ||
| deploy-aws-ec2.md | ||
| deploy-cloudflare.md | ||
| deploy-docker.md | ||
| deploy-hetzner-cloud.md | ||
| deploy-local-only.md | ||
| deploy-modal.md | ||
| deploy-vps-generic.md | ||
| docs-architecture-diagrams.md | ||
| docs-claude-md.md | ||
| docs-decisions-adr.md | ||
| docs-readme-template.md | ||
| docs-runbook.md | ||
| domain-has-secrets.md | ||
| domain-ml-training.md | ||
| domain-paid-apis.md | ||
| evidence-grading.md | ||
| memory-protocol.md | ||
| mode-devils-advocate.md | ||
| mode-first-principles.md | ||
| mode-matrix.md | ||
| mode-maximalist.md | ||
| mode-minimalist.md | ||
| mode-skeptic.md | ||
| obs-metrics.md | ||
| obs-structured-logs.md | ||
| obs-traces.md | ||
| path-user-memory.md | ||
| path-user-rules.md | ||
| pipeline-5phase-template.md | ||
| README.md | ||
| rule-double-audit.md | ||
| rule-error-budget.md | ||
| rule-math-first.md | ||
| rule-pre-dev-gate.md | ||
| rule-pure-click-contract.md | ||
| rule-test-first.md | ||
| scraper-free-tier.md | ||
| scraper-paid-tier.md | ||
| scraper-unified-output.md | ||
| security-audit-logging.md | ||
| security-firewall-ufw.md | ||
| security-patching.md | ||
| security-ssh-hardening.md | ||
| security-tls-caddy.md | ||
| stack-astro.md | ||
| stack-embedded-stm32.md | ||
| stack-fastapi-postgres.md | ||
| stack-flutter.md | ||
| stack-go-server.md | ||
| stack-nextjs.md | ||
| stack-python-ml.md | ||
| stack-react-vite.md | ||
| stack-rust-axum.md | ||
| stack-rust-cli.md | ||
| stack-sveltekit.md | ||
| stack-swift-ios.md | ||
| stack-swift-spm.md | ||
| stack-tailwind.md | ||
| test-e2e.md | ||
| test-fuzz.md | ||
| test-load.md | ||
| test-property.md | ||
_blocks/ — Composable Agent Content
Each .md file in this directory is a block: a single-concern, standalone-readable snippet that any agent manifest can include via its blocks = [...] list. The _assembler concatenates selected blocks + manifest metadata into the final agent .md that Claude Code loads.
Blocks are grouped by prefix:
| Prefix | Purpose |
|---|---|
baseline, evidence-grading, memory-protocol |
Obligatory base — every manifest must include these |
rule-* |
Discipline rules (pre-dev-gate, test-first, error-budget, double-audit, math-first) |
mode-* |
Cognitive mode blocks (see below) |
stack-* |
Language / framework constraints (Rust Axum, React Vite, Swift SPM, …) |
deploy-* |
Deployment target rules (Modal, AWS EC2, Cloudflare, Hetzner, …) |
api-* |
External API conventions (Apify, fal.ai, ElevenLabs, Anthropic, …) |
db-* |
Database rules (Postgres, SQLite, Drizzle, sqlx, migrations) |
auth-*, security-*, obs-*, ci-*, test-*, scraper-*, domain-*, docs-* |
Domain-specific rules |
Cognitive mode blocks
Composable behavioural skews. Add any combination to a manifest's blocks list to stack the mode. Modes compose — e.g. mode-skeptic + mode-minimalist yields an adversarial pruner.
| Block | Purpose |
|---|---|
mode-skeptic.md |
Doubt the conclusion until proved; flag claims without E1/E2 grade |
mode-devils-advocate.md |
Steel-man the opposite; name the strongest objection before agreeing |
mode-minimalist.md |
Prefer deleting over adding; justify every addition against existing code |
mode-maximalist.md |
Explore 10× scope; return both maximum and minimum bounds; only when user invokes exploration |
mode-first-principles.md |
Derive from invariants; cite the physical / mathematical constraint, not "best practice" |
See mode-matrix.md for the agent-role × recommended-modes table used by the skills/new-agent wizard (Phase 3.6). It is the suggested starting set per role — modes remain a free pick per manifest.
Adding a new block
- Pick a stable prefix (existing category or a new one documented here).
- One concern per file. 20–50 LOC target,
<200 LOChard cap (Constructor Pattern). - Imperative voice (
"Do X"not"the agent should do X") — these land verbatim in agent prompts. - Standalone-readable — do not assume sibling blocks are present. Cross-references OK, hard dependencies not.
- Reference from a manifest's
blocks = [...]list; the assembler validates existence.
Ownership
Blocks are kit-owned — install.sh overwrites _blocks/ on re-run, backing up local edits to _blocks.bak-TIMESTAMP/. User-owned content belongs in _manifests/*.toml (which are never overwritten).