v1.5.0: Introduce cross-cutting concepts for system-wide rules

[kikaineko]

Summary

Introduces cross-cutting concepts (横断概念) as a first-class mechanism for managing business rules that affect multiple capabilities. This addresses the challenge of rules like "restricted users cannot post comments" that span multiple capabilities but are owned by a single capability.

The core insight: rules are unstable units (can be split/merged by rewording), but concepts are stable (the same concept regardless of phrasing). Therefore, obligations are attached to concepts (nouns), not rules (sentences).

Key Changes

Business Rules Guide

• Added comprehensive "横断概念とは何か" section defining:
  • Judgment test (3 questions: otherness, universality, necessity) to identify cross-cutting concepts
  • Declaration format: 1 concept = 1 line with <!-- cross-concept --> marker in owner's BR
  • Conformance format: all capabilities must declare attitude (applicable/non-applicable with reason) toward all declared concepts
  • Responsibility split: owner declares concept + defines it; each capability specifies effects in their own rules + conformance section
  • Delayed migration for existing BR files (introduced when updating, not retroactively)

BR Structure

• Added Section 4 "横断概念" with subsections "宣言" (Declaration) and "適合" (Conformance)
• Updated documentation structure guidance to clarify that two-party dependencies belong in boundaries, not cross-cutting concepts
• Updated example business_rules.md with ORD-05 (restricted user cannot post comments) as conformance example

Skill Updates

/miko.new-cap:

• Step 6b: Added mandatory full-capability BR survey via Sonnet sub-agent (not just adjacent capabilities)
• Step 6c: Added mandatory cross-cutting concept conformance judgment (grep declared concepts → confirm with user → record in conformance section)
• Step 11: Conformance section now required in generated BR (with "特になし" if no concepts declared)
• Step 12: Updated completion report to include conformance judgment counts and escalation candidates

/miko.propose:

• Step 9: Changed other-capability impact survey from optional to mandatory (unless explicitly skipped by user)
• Updated cross-capability impact guide to include cross-concept considerations:
  • Changes to declared concept definitions affect all conforming capabilities
  • New concept declarations require conformance from all capabilities
  • Escalation candidates (states meeting judgment test) reported separately

/miko.harae & /miko.new-harae:

• Added mechanical verification step (not inference) for cross-concept coverage:
  • Detects missing conformance section
  • Detects missing conformance entries for declared concepts
  • Detects unresolved 要判定 entries
  • Detects broken rule ID references in conformance
• Implemented in both棚卸 (inventory) and proposal verification modes

Delayed migration skills (/miko.quick-impl, /miko.catchup, /miko.quick-catchup, /miko.speckit.implement):

• When updating business_rules.md, introduce cross-concept section if missing (only exception to "don't restructure existing BR" principle)
• Follow migration procedure from guide

Documentation

• Updated business_rules_driven_development.md with "解決済みの論点" section explaining:
  • Design decision rationale
  • Two-layer enforcement (mechanical grep + sub-agent discovery)
  • Rejected alternatives (glossary management, rule-level markers, central registry, discovery-only)
• Updated harae_guide.md with mechanical verification procedure
• Updated cross_capability_impact_guide.md with cross-concept impact patterns

Version

• Bumped to v1.5.0 (2026-09-05)

Implementation Details

Concept List Derivation:

grep -n 'cross-concept' miko/*/business_rules.md

No central registry file maintained — list is derived on-demand to avoid sync drift between source and index.

Conformance Enforcement:

• Layer 1 (Mechanical): `ha

https://claude.ai/code/session_019MrZz6XvUK3g1xUVTnGnRH