Import release documentation standards from marrbox-platform

[virtualian]

Summary

Four new MARR standards were created in marrbox-platform/.claude/marr/standards/ that govern release documentation. These are user and project agnostic and should be imported into the MARR standard library for use across all projects.

Standards to Import

Standard	File	Governs
Service Definition	prj-service-definition-standard.md	User-focused specs: capabilities, acceptance criteria, user roles
Technical Architecture	prj-technical-architecture-standard.md	Architect-focused specs: components, interfaces, technology decisions
Detailed Systems Design	prj-detailed-systems-design-standard.md	Admin-focused specs: deployment, configuration, monitoring, procedures
Implementation Plan	prj-implementation-plan-standard.md	PM-focused specs: phased tasks, dependencies, risks, success criteria

Design Features

• Cross-referencing set: each standard references the other three with explicit file paths
• Content delineation: explicit boundary rules prevent duplication (content belongs in exactly one document)
• Coherence gates: mandatory verification checks when any document in the set is updated
• Mermaid diagram mandates: each standard specifies which Mermaid diagram types are required (C4Context, C4Container, C4Deployment, flowchart+classDef, gantt, sequence, stateDiagram-v2, journey)
• Dual audience: primary audience is agentic LLMs, secondary is human AI engineers
• Rollback boundary: operational rollback (Systems Design) vs build-sequence rollback (Implementation Plan) explicitly delineated
• C4Context ownership: Service Definition is sole authority; Technical Architecture references it

Source

marrbox-platform repo, branch 10-reimplement-marrbox-inference-stack, directory .claude/marr/standards/

Relationship to Existing Standards

• Complements plan-execution-standard (which governs HOW agents execute plans; the new Implementation Plan standard governs the plan DOCUMENT content)
• Follows prj-writing-prompts-standard conventions (WHAT/WHY not HOW, no code, imperative language)