docs: adopt practical domain modeling

[DecisionNerd]

Summary

• replace the former light DDD framing with practical domain modeling across product docs, lifecycle guidance, architecture, skills, templates, and package copy
• model DocSlime using its actual concepts, relationships, rules, workflows, lifecycle states, and responsibility boundaries
• add generated-template and normative-surface regression coverage while preserving historical critique observations with clarification

Verification

• npm run format:markdown
• npm run check:markdown
• cargo fmt --check
• cargo test
• cargo clippy --all-targets -- -D warnings
• npm ci
• npm run build (16 pages; rendered line-break guard passed)
• throwaway repository scaffold inspection
• git diff --check
• final terminology audit (only two clarified historical critique references remain)

Note

Replace DDD terminology with practical domain modeling across docs and templates

• Renames and rewrites sections across docs, templates, and agent skills to replace Domain-Driven Design framing (bounded contexts, ubiquitous language) with a lighter "domain modeling" approach centered on concepts, relationships, constraints, workflows, and lifecycle states.
• Updates the lifecycle diagram and narrative across docs/index.md, docs/lifecycle.md, and docs/PRODUCT.md to a problem → model → decisions → implementation → verification loop.
• Adds a test in tests/cli.rs that fails if generated or normative repository files contain deprecated terminology (e.g. DDD, bounded context, ubiquitous language) and asserts domain-modeling phrasing and diagrams are present in key output files.
• Updates docs/REQUIREMENTS.md FR-14 and NFR-8 and the docs/engineering/ARCHITECTURE.md section to enumerate explicit modeling elements rather than DDD abstractions.

^{Macroscope summarized ff4b612.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docslime	Ready	Preview, Comment	Jul 14, 2026 8:30pm

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 08133405-59be-4269-8be2-b71749274b4b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/domain-modeling-methodology

---

_{Comment @coderabbitai help to get the list of available commands.}