Constraint Identification

Purpose: Systematically discover what could prevent a candidate from being implemented. Uses Theory of Constraints to find bottlenecks, TRIZ to surface contradictions, and Pre-mortem to anticipate failures before they occur.

When to use:

• A candidate looks promising but you need to stress-test its viability
• Stakeholders want to know what could go wrong before committing
• You need a structured inventory of blockers with severity and removability assessments

Budget

State Ledger

Available Tactics

Available SOPs

Execution Guidance

1. Deploy constraint-identification-sop to discover all constraints using TOC, TRIZ, and Pre-mortem
2. Feed discovered constraints to constraint-classification to sort them
3. For each non-trivial constraint, run removability-assessment
4. For constraints with removability score > 0.3, design removal-path
5. Aggregate findings into state ledger

Output Format

constraint_analysis:
  candidate: <name>
  total_constraints: N
  hard_constraints:
    - {constraint, severity, rationale}
  soft_constraints:
    - {constraint, severity, workaround_sketch}
  assumptions:
    - {assumption, risk_if_false, validation_method}
  removal_paths:
    - {constraint, removability: 0.X, steps: [...], timeline, resources}
  showstopper_verdict: <yes/no>
  showstopper_reason: <if yes>