Project Case Management Handbook Epic

User Journey

The Project Case Management bounded context enables case-based project management for knowledge work using CMMN (Case Management Model and Notation). It provides discretionary workflows, artifact pipeline (Cognitive → Intellectual → Information Products → Intellectual Capital), PM-Agent orchestration, and provenance gating through TransitionTokens and IFL (Internal Federated Ledger) to transform project management from a constraint into an enabler.

Jobs to be Done & EARS Requirements

Job: Create and Configure Case

User Story: As a project manager, I want to create a case using CMMN primitives (Case, Stage, Task, Sentry, Milestone, CaseFile), so that I can manage knowledge work with discretionary, event-driven workflows.

EARS Requirement:

• While managing projects, when a CreateCase command is received with case template and context, the project case management context shall:
  1. Create Case aggregate root with unique case ID, name, and template reference
  2. Initialize CaseFile with artifact collection and empty lineage
  3. Configure Stages with entry/exit sentries for discretionary activation
  4. Define Tasks as mandatory or discretionary work units
  5. Set Sentries with event-driven activation criteria (on-event, if-condition)
  6. Establish Milestones for progression tracking
  7. Enforce case template constraints and invariants
  8. Return case ID with initial stage status

Job: Execute Discretionary Task Activation

User Story: As a case worker, I want tasks to activate based on events rather than fixed schedules, so that work adapts to reality.

EARS Requirement:

• While a case is active, when sentry conditions are satisfied, the project case management context shall:
  1. Evaluate Sentry conditions (event triggers, state predicates)
  2. Activate associated Task if sentry evaluates to true
  3. Support parallel stage execution (no forced sequencing) (FR-001)
  4. Allow stage skipping if sentries never fire with explicit authorization and audit trail
  5. Emit task activation event with case ID, task ID, timestamp
  6. Update case status with active task count

Job: Orchestrate via PM-Agent

User Story: As a team member, I want PM-Agent to orchestrate hybrid human-AI teams, so that routine coordination is automated and humans focus on judgment.

EARS Requirement:

• While a case is active, when orchestration is required, the project case management context shall:
  1. PM-Agent Assignment:
     • Analyze task requirements (skills, complexity, context)
     • Match tasks to agents (human or AI) based on capabilities
     • Consider workload, expertise, and authority rules (SDS-031)
  2. Knowledge Base Integration:
     • Query Knowledge Graph for relevant context and artifacts
     • Retrieve Intellectual Capital for reuse
     • Access Semantic Memory for case history patterns
  3. Task Execution:
     • Dispatch tasks to assigned agents
     • Monitor task progress and status
     • Handle task failures with escalation logic
     • Emit task completion events
  4. Authority Enforcement:
     • Check SDS-031 authority rules before privileged actions
     • Require human approval for high-impact operations
     • Log all orchestration decisions for audit

Job: Progress Artifacts Through Pipeline

User Story: As a knowledge worker, I want my work products to progress through the artifact pipeline (Cognitive → Intellectual → Information Products → Intellectual Capital), so that knowledge becomes organizational assets.

EARS Requirement:

• While working on a case, when an artifact is created or modified, the project case management context shall:
  1. Cognitive Artifacts (Notes, sketches):
     • Capture mental load reduction artifacts
     • Store with minimal metadata (creator, timestamp, case context)
     • Enable quick capture and retrieval
  2. Intellectual Artifacts (Specs, SOPs):
     • Synthesize cognitive artifacts into structured knowledge
     • Validate completeness and quality
     • Add semantic annotations and concept links
  3. Information Products (Software, campaigns):
     • Build market-valued deliverables
     • Apply appropriate quality gates and testing
     • Package for deployment or delivery
  4. Intellectual Capital (Enterprise assets):
     • Capitalize artifacts for reuse across organization
     • Apply Exchange Rate Policies for valuation
     • Store in Knowledge Graph with semantic indexing

Job: Enforce Provenance with TransitionTokens

User Story: As a governance officer, I want all artifacts to have immutable lineage through TransitionTokens, so that “teleportation” is prevented and trust is maintained.

EARS Requirement:

• While artifacts progress through pipeline, when state transition occurs, the project case management context shall:
  1. Generate TransitionToken:
     • Create unique token ID for each state change
     • Include: from-state, to-state, artifact-id, actor-id, timestamp, previousHash
     • Calculate SHA256 hash of token content + previousHash for integrity
  2. Validate Lineage:
     • Reject artifact transitions without valid source token
     • Enforce “No teleportation” — every artifact must have traceable origin
     • Verify token chain integrity (previousHash linkage)
  3. Store in IFL (Internal Federated Ledger):
     • Append token to immutable append-only log
     • Include artifact hash for content verification
     • Enable retrospective lineage queries
  4. Return Transition Result:
     • Success with new token ID
     • Failure with reason (missing lineage, invalid hash, unauthorized actor)

Job: Complete Case Milestone

User Story: As a case manager, I want to track and complete milestones, so that case progression is measured and reported.

EARS Requirement:

• While a case is active, when milestone conditions are satisfied, the project case management context shall:
  1. Evaluate milestone completion criteria
  2. Check all required tasks are completed
  3. Validate required artifacts exist in CaseFile
  4. Verify artifact lineage is complete (no gaps in TransitionTokens)
  5. Mark milestone as completed with timestamp
  6. Emit milestone completion event
  7. Trigger evaluation of subsequent stage sentries

Job: Generate Capital Valuation

User Story: As an executive, I want to measure Intellectual Capital formation, so that I can track knowledge asset growth over time.

EARS Requirement:

• While cases complete, when Intellectual Capital is created, the project case management context shall:
  1. Apply Exchange Rate Policies to value artifacts:
     • Cognitive → Intellectual: Synthesis effort multiplier
     • Intellectual → Information Product: Quality gate multiplier
     • Information Product → Capital: Reuse potential multiplier
  2. Calculate total capital value per case:
     • Sum valuations of all capitalized artifacts
     • Include depreciation for aging assets
     • Track appreciation for high-reuse artifacts
  3. Store valuation in Knowledge Graph:
     • Link to case and artifact entities
     • Enable temporal queries for capital growth
     • Support reporting by project, domain, time range

Job: Close Case and Archive Artifacts

User Story: As a case manager, I want to close a case and archive artifacts, so that the case lifecycle is complete and knowledge is preserved.

EARS Requirement:

• While a case is active, when CloseCase command is received, the project case management context shall:
  1. Validate all mandatory stages are completed
  2. Verify all required milestones are achieved
  3. Confirm all artifacts have complete TransitionToken lineage
  4. Capitalize eligible artifacts as Intellectual Capital
  5. Archive CaseFile with read-only access
  6. Generate case completion report with:
     • Duration, tasks completed, artifacts created
     • Capital formation summary
     • Lessons learned and improvement opportunities
  7. Emit case closed event

Domain Entities Summary

Root Aggregates

• Case: Aggregate root representing a project case with ID, name, template, stages, tasks, sentries, milestones, and CaseFile
• Artifact: Work product with ID, type (Cognitive/Intellectual/Information/Capital), content, lineage, and valuation
• TransitionToken: Immutable state change record with from-state, to-state, artifact reference, actor, timestamp, previousHash, and SHA256 hash

Contained Entities (within Case)

• Task: Work unit with ID, name, type (mandatory/discretionary), status, assignment, and completion criteria
• Stage: Discretionary phase with entry/exit sentries, tasks, and parallel execution support

Value Objects

• Sentry: Event-driven activation criteria with event type, condition predicate, and associated task
• Milestone: Completion condition with criteria, status, and timestamp
• CaseFile: Artifact collection with lineage tracking and metadata
• ExchangeRatePolicy: Valuation rules for artifact transformations

Policy Rules

• NoTeleportation: Every artifact must have complete TransitionToken lineage
• SentryGatedActivation: Tasks activate only when sentry conditions are satisfied
• MilestoneCompletion: Milestones complete only when all required tasks and artifacts are done
• CapitalizationEligibility: Only artifacts with complete lineage can become Intellectual Capital

Integration Points

• PM-Agent: Orchestrates hybrid human-AI teams with task assignment and monitoring
• Knowledge Graph: Stores Intellectual Capital with semantic indexing and retrieval
• Agent Society Context: Provides authority rules (SDS-031) for task permissions
• IFL (Internal Federated Ledger): Immutable append-only log for TransitionTokens
• Semantic Memory Context: Provides case history patterns for PM-Agent decision-making
• Cognitive Extension Context: Generates cognitive artifacts and supports synthesis

Success Metrics

• PM Coordination Time Reduction: 75% (from 40% to 10% of PM capacity)
• Artifact Reuse Rate: >60% (up from ~5% baseline)
• Case Completion Rate: >90% of cases close with all milestones achieved
• Capital Formation: Increase Intellectual Capital value by 10% QoQ using knowledge-index score (baseline: 2025-01-01 = 62); review quarterly and adjust if growth <5%

Non-Functional Requirements

• NFR-002: Sentry evaluation completes in <1 second for event-driven activation
• NFR-003: TransitionToken generation is deterministic and cryptographically verifiable
• NFR-004: Case archive preserves complete artifact lineage indefinitely