Decisions

  • Pending: Replace “Claude” with “AI” or “the assistant” or something else?

User Tasks


Summary

Remove Claude-specific language from vault docs and templates so the system reads as model-agnostic.

Problem / Motivation

The LLM Portability principle in CLAUDE.md says vault content should be plain Markdown with no model-specific markup. Currently, many docs and templates reference “Claude” or “Claude Code” by name where they mean “the AI assistant.” This couples the vault’s documentation to a specific provider.

Proposed Solution

Audit and rewrite references in three tiers:

  1. Templates (quick) — generic wording in reusable templates
  2. System docs (medium) — architecture, glossary, workflow rewritten to describe a generic agent runtime, noting Claude Code as current implementation
  3. Dashboards & logs (minor) — scattered references in descriptions

Personal knowledge files (thoughts.md, learning-topics.md) and external docs (external/) are excluded — those describe real experiences with Claude Code and stay as-is.


Open Questions

1. Replacement terminology

Question: What should “Claude” become in generic contexts?

OptionDescription
A) “the assistant”Natural, clear, model-agnostic
B) “the AI”Shorter but slightly cold
C) “Opus”The system’s own name — but Opus is the system, not the LLM

Recommendation: Option A for prose (“the assistant creates proposals”), keep “Opus” for the system itself.

Decision:


Phase Overview

PhaseDescriptionStatus
Phase 1Templates & quick-notes
Phase 2System docs (architecture, glossary, workflow)
Phase 3Dashboards & logs (minor cleanup)

Phase 1: Templates & quick-notes —

Goal: Make reusable templates vendor-neutral.

FileWhat to changeOwnerStatus
vault/_templates/proposal.md:3source: claude-codesource: ai-assistantopus
vault/_templates/dashboard.md:15”Updated by Claude after relevant changes.” → genericopus
vault/90_inbox/quick-notes.md:8”Claude picks this up each session.” → genericopus

Phase 2: System docs —

Goal: Rewrite core docs to describe a generic agent runtime with Claude Code as current implementation.

FileWhat to changeOwnerStatus
vault/00_system/docs/architecture.md”Claude Code CLI as its runtime” → generic runtime description, note current implopus
vault/00_system/docs/glossary.md”Infrastructure (Claude Code)” section → generic termsopus
vault/00_system/docs/workflow.md”Claude figures out”, “Claude creates proposals” → “the assistant”opus

Phase 3: Dashboards & logs —

Goal: Clean up scattered references in dashboards and decision logs.

FileWhat to changeOwnerStatus
vault/00_system/logs/decision-log.md”How should Claude suggest improvements” → genericopus
vault/00_system/dashboards/*.mdMinor description tweaks where “Claude” is used genericallyopus

Test

Manual tests

TestExpectedOwnerActualLast
Grep for “Claude” in vault (excl. external/, features/, ideas/, knowledge/personal/)Only hits in .claude/ paths or proper nounsopuspending-

AI-verified tests

ScenarioExpected behaviorVerification method

E2E tests

ScenarioAssertion

Integration tests

ComponentCoverage

Unit tests

ComponentTestsCoverage

History

DateEventDetails
2026-03-12CreatedAudit of Claude-specific references in vault

References

  • LLM Portability section in CLAUDE.md
  • vault/10_features/01_ideas/model-agnostic-architecture.md