Use-Case Dependency, Readiness and Sequencing Standard
Purpose
A use-case cannot enter implementation merely because it has high business value. Its upstream decisions, modules, data, permissions, entitlements and runtime preconditions must be visible and testable.
Dependency layers
- Canon decision dependencies.
- Implementation dependencies.
- Runtime preconditions.
Readiness axes
definition_readiness: missing_context | draftable | decision_ready | effective
implementation_readiness: blocked | partially_ready | ready | in_delivery | implemented
activation_readiness: not_ready | test_ready | staging_ready | production_ready | activated
runtime_eligibility: allowed | denied | upgrade_required | verification_required | membership_required | capability_required | quota_exhausted
Dependency types
hardsoftoptionalalternative
Missing hard dependencies keep implementation_readiness: blocked.
Stable contracts
Use-cases depend on capability and entitlement contracts, not mutable role/tier names.
required_capability: search.ai.use
required_entitlement: ai_search
Foundational sequence
Public → Identity → Organization/Tenant → Membership
→ Role/Capability/Scope/Context → Subscription/Entitlement/Quota
→ Domain Data → Search/Matching → Commercial Flow
Prioritization
First gate: hard-dependency readiness. Then rank ready work by business value, unlock power, risk reduction, time criticality and job size.
Metadata minimum
extensions:
readiness:
definition: decision_ready
implementation: blocked
activation: not_ready
dependencies:
canon: {hard: [], soft: []}
use_cases: {hard: [], alternative: []}
modules: {hard: []}
capabilities: {required: []}
entitlements: {required: []}
runtime_preconditions: []
Integrity rules
- Hard-dependency graph is acyclic.
- A record cannot depend on itself.
- Missing Canon IDs fail lint.
- ADRs beyond draft require an accepted/effective use-case upstream.
- Downstream views are derived from canonical upstream links.
Generated views
canon/_generated/use-case-dependency-map.mdcanon/_generated/use-case-ready-queue.md
CAN-REQ-UC-001 initial state
definition_readiness: decision_ready
implementation_readiness: blocked
activation_readiness: not_ready
CAN-GOV-UCDEP-001 · governance_status: draft.