Skip to main content

Document Control Registry

Purpose: Tracks the classification and lifecycle status of all documentation across the ChurchWiseAI portfolio. Agents consult this to know which docs to trust.

Last audited: 2026-03-25


Trust Hierarchy (CLAUDE.md Rule 15)

  1. C:\dev\knowledge\ (canonical) — ALWAYS trust
  2. Per-codebase CLAUDE.md — trust for code-level context
  3. C:\dev\knowledge\drafts\ — read but verify (proposals, not facts)
  4. Any other .md file — check knowledge/ first
  5. C:\dev\knowledge\archive\ — do NOT use for current decisions

Three Zones

ZoneLocationStatus
CanonicalC:\dev\knowledge\Source of truth. Verified, current, trusted.
WorkingC:\dev\knowledge\drafts\In-progress. Not yet approved.
ArchiveC:\dev\knowledge\archive\Superseded. Read-only historical reference.

Archived Documents (2026-03-25)

Original LocationReasonSuperseded By
C:\dev\PIVOT_PLAN.mdOutdated pivot plan, wrong prices, references Railwayknowledge/narrative/strategy.md
C:\dev\PLATFORM_STRATEGY.mdReferences 4 voice agents (now 2), Phase 1 completeknowledge/narrative/strategy.md
C:\dev\GEMINI.mdReferences Railway/ElevenLabs, stale pricing, wrong church countsC:\dev\CLAUDE.md
churchwiseai-web/docs/internal/OPERATIONS_GUIDE.mdReferences Railway infrastructureknowledge/architecture/system-overview.md (pending)
churchwiseai-web/docs/DEPLOYMENT_RUNBOOK.mdLists Railway service URLsknowledge/runbooks/deployment/ (pending)
churchwiseai-web/docs/GO_LIVE_CHECKLIST.mdReferences Railway servicesknowledge/runbooks/ (pending)
churchwiseai-web/docs/GO_LIVE_ORDER.mdTactical details outdated (Feb 2026)knowledge/narrative/strategy.md
churchwiseai-web/docs/GO_LIVE_AUDIT_PLAN_2026-02-27.mdOne month old, references old stateAGENT_QUALITY_PRINCIPLES.md + QA_CHECKLIST.md

Root-Level Files (C:\dev)

Only these files belong at root:

FileStatusPurpose
CLAUDE.mdCANONICALAgent briefing (will slim after knowledge/ populated)
DECISION_LOG.mdCANONICALAppend-only decision journal
FOUNDER_ACTIONS.mdCANONICALAction items for founder
FEATURE_REGISTRY.mdCANONICALFeature ownership map
AGENT_QUALITY_PRINCIPLES.mdCANONICAL35 quality rules from 165 bugs
QA_CHECKLIST.mdCANONICALPre-completion QA checklist
PRICING.mdCANONICALStripe source of truth (derived from knowledge/data/pricing.yaml)
INSTITUTIONAL_KNOWLEDGE.mdCANONICALCompiled narrative briefing
REMOTION_STRATEGY.mdCANONICALVideo generation reference
TEST_URLS.mdCANONICALAdmin URLs and test configs
GO_LIVE_CHECKLIST.mdCANONICALLaunch readiness (root copy)
AGENT_BRIEFING_KNOWLEDGE_SYSTEM.mdWORKINGActive project context
TESTING_PROMPT_CROSS_SOURCE_CONSISTENCY.mdWORKINGTesting guidance for knowledge system
VOICE_HOSTING_STRATEGY.mdWORKINGLive architecture decision (Cartesia fallback)
VOICE_ROUTING_HANDOFF.mdWORKINGIn-progress bug fix

Per-Codebase Docs

churchwiseai-web/

FileStatusNotes
CLAUDE.mdCANONICALProject-specific agent briefing
CHATBOT_UX_ARCHITECTURE.mdCANONICALAbsorb to knowledge/products/chatbot/ux-model.md in Phase 2
DESIGN_PRINCIPLES.mdCANONICALKeep until design skill supersedes
AGENTIC_TOOLS_CATALOG.mdCANONICALAbsorb to knowledge/data/tools.yaml
BACKLOG.mdCANONICALProduct backlog
docs/PRODUCT_VISION.mdCANONICALFoundational strategy
docs/MASTER_VISION.mdCANONICALFounder's playbook
docs/REVENUE_STRATEGY.mdCANONICALRevenue plan
docs/MARKETING_STRATEGY.mdCANONICALGTM philosophy
docs/WRITING_PRINCIPLES.mdCANONICALBlog voice guide
docs/USE_CASE_CATALOG.mdCANONICALDemo pain points
docs/SERVICE_INVENTORY.mdCANONICALThird-party services
docs/internal/database-tables.mdCANONICALSchema reference
docs/QA_CHECKLIST.mdCANONICAL515 QA tests
docs/PRODUCT_BACKLOG.mdCANONICALFeature ideas
docs/superpowers/specs/*.mdCANONICALApproved design specs
docs/superpowers/plans/*.mdCANONICALImplementation plans
voice-agent-line/DEPLOY.mdCANONICALLiveKit voice agent deployment guide
voice-agent-line/AGENT_AUDIT.mdCANONICALVoice agent tool matrix
VOICE_LINE_MIGRATION_PLAN.mdSTALECompleted migration — archive next pass
IMPLEMENTATION_PLAN.mdUNKNOWNCheck status — archive if done

pewsearch/

FileStatusNotes
CLAUDE.mdCANONICALFixed church count 2026-03-25
BACKLOG.mdCANONICALFeature backlog
ENRICHMENT_PLAYBOOK.mdCANONICALDirectory building guide
docs/PRO_WEBSITE.mdCANONICAL692-line product spec
docs/ADMIN_DASHBOARD.mdCANONICALAdmin reference
docs/API_REFERENCE.mdCANONICALAPI endpoints
docs/ARCHITECTURE.mdCANONICALFixed church count 2026-03-25
docs/ROLE_WORKFLOWS.mdCANONICALRBAC matrix
data_quality_report.mdSTALE1 month old — archive next pass
PRO_WEBSITE_PLAN.mdSTALEStub pointing to old plan file
web/API_TEST_MATRIX.mdSTALE8 days old, no follow-up
web/E2E_TEST_PLAN.mdSTALE1 month old
web/TRAINING_TAB_PLAN.mdABSORBMove to docs/ with status header

sermon-illustrations/

FileStatusNotes
CLAUDE.mdCANONICALAccurate
BACKLOG.mdCANONICALFeature backlog
internal/shared-database-contract.mdCANONICALCritical cross-project safety
internal/content-pipeline.mdCANONICALIllustration flow
internal/content-rules.mdCANONICALTheological content rules
internal/image-style-research.mdCANONICALImage generation guidance
internal/README.mdCANONICALIndex for internal docs
internal/scripts.mdSTALEIncomplete — only 1 of ~5 scripts documented
README.mdSTALEGeneric Next.js boilerplate
GEMINI.mdSTALEPoints to non-existent file
E2E_TEST_PLAN.mdSTALE1 month old

Future Cleanup (Phase 1-6 Absorption)

As knowledge/ docs are written in later phases, these codebase docs will be absorbed:

Codebase DocWill Be Absorbed IntoPhase
CHATBOT_UX_ARCHITECTURE.mdknowledge/products/chatbot/ux-model.md2
AGENTIC_TOOLS_CATALOG.mdknowledge/data/tools.yaml (already exists)2
docs/PRODUCT_VISION.mdknowledge/narrative/vision.md (enrich)1
docs/SERVICE_INVENTORY.mdknowledge/integrations/*.md5
docs/internal/database-tables.mdknowledge/architecture/database-schema.md1
ENRICHMENT_PLAYBOOK.mdknowledge/runbooks/content-ops/data-enrichment.md6

Draft → Canonical Promotion Checklist

A knowledge/drafts/ file becomes canonical when it passes ALL of the following gates. Run this checklist before moving a file from drafts/ to its target location.

Gate 1: Content verification

  • Every factual claim verified against current code (check code-files: frontmatter)
  • Every DB table reference checked against actual Supabase schema
  • Every price/dollar figure matches knowledge/data/pricing.yaml
  • Every code path confirmed to still exist (grep or file-check)
  • No "TBD", "TODO", or placeholder text remains
  • No actual secrets — only env var NAMES, never values

Gate 2: Frontmatter completeness

  • title: — clear, descriptive document title
  • description: — one-line summary (used in INDEX.md)
  • parent: — path to parent doc or README
  • tags: — at least 2 relevant tags
  • last-verified: — today's date in YYYY-MM-DD format
  • code-files: — all referenced source files listed (or empty list if none)
  • db-tables: — all referenced tables listed (or empty list if none)

Gate 3: Navigation

  • Breadcrumb at top: [Knowledge](../INDEX.md) > [Category](README.md) > **This Doc**
  • "See Also" section at bottom with parent, related, and runbook links
  • Parent doc updated: add this file to its children: list

Gate 4: Automation verification

  • Run pnpm test — all 10 test files pass
  • Run pnpm derive knowledge:docs — no broken links reported
  • Run pnpm derive --check — no drift detected

Gate 5: Review

  • Reviewed as "senior QA engineer" — edge cases, error paths, accuracy
  • If doc references any feature: manually tested or verified it works
  • Description field useful enough for INDEX.md navigation (not "a doc about X")

After promotion

  1. Move file from drafts/ to canonical location
  2. Update DOCUMENT_CONTROL.md with new entry
  3. Run pnpm derive knowledge:docs to regenerate INDEX.md
  4. Add 1-line entry to DECISION_LOG.md: promoted drafts/X.md to canonical

Plan File Hygiene

Active plans live in ~/.claude/plans/. Naming convention: YYYY-MM-DD-description.md

Cleanup rule: Plans older than 60 days with no active reference in any knowledge/ doc or CLAUDE.md should be deleted. When completing a project:

  1. Archive any working drafts in knowledge/drafts/ that are no longer active
  2. Move handoff docs to knowledge/drafts/ if they have ongoing value
  3. Remove stale implementation plans from ~/.claude/plans/