analyze-constraints-readiness
Purpose
Assess feasibility and readiness by identifying constraints, resources, dependencies, bottlenecks, and maturation gates.
Input contract
mode_contracts:
obstacle-triage: &readiness_input
required: [candidate_or_plan, readiness_dimensions]
optional: [resource_estimates, dependencies, assumptions, target_gates]
constraints: [evidence_must_be_attached_to_each_scored_dimension]
readiness-assessment: *readiness_input
resource-envelope: *readiness_input
causal-constraint-analysis: *readiness_input
maturation-path: *readiness_input
Execution protocol
Do not perform called SOP operations inline; each loaded SOP owns its contract and thresholds.
- Define candidate, dimensions, hard constraints, and target gates. You MUST load skill
classify-constraint to classify each declared constraint.
- Select
obstacle-triage, readiness-assessment, resource-envelope, causal-constraint-analysis, or maturation-path.
- You MUST load skill
score-object to score the selected dimensions with evidence. You MUST load skill identify-bottleneck to identify binding constraints and dependencies.
- You MUST load skill
assess-removability to test whether binding constraints can be removed. You MUST load skill design-mitigation to design removal or mitigation paths and return a readiness conclusion.
If several feasible responses must be balanced as a joint set, consider portfolio-optimization. If the target goal remains too broad to assess, consider decompose-research-goal. If external change dominates present readiness, consider analyze-future-scenarios. If several candidate paths are ready for comparative selection, rank-candidates may be the better next tactic.
Mode branches
obstacle-triage: rapidly enumerate and severity-rank the obstacles that could block the target, preserving evidence status for each one. You MUST load skill identify-obstacles to enumerate the obstacles. You MUST load skill list-undesirable-effects to retain their observed consequences.
readiness-assessment: score the required readiness dimensions with supporting evidence and identify the dimensions that keep the target from being ready. You MUST load skill assess-readiness-dimension to assess every required dimension.
resource-envelope: estimate time, cost, and personnel bounds from analogies, then flag low-confidence estimates for investigation. You MUST load skill quantify-resource-gap to quantify the gap. You MUST load skill identify-critical-chain to expose the binding resource sequence.
causal-constraint-analysis: trace how constraints interact through dependencies and conflicts to identify the binding cause rather than only its symptoms. You MUST load skill trace-causal-chain to trace constraint propagation. You MUST load skill extract-core-conflict to isolate the core conflict. You MUST load skill challenge-assumption to test the assumptions that sustain it.
maturation-path: sequence stage gates and milestones that move the target from current readiness to the declared implementation threshold. You MUST load skill project-future-reality to project the proposed path. You MUST load skill apply-stage-gate to apply its stage gates.
Output contract
mode_contracts:
obstacle-triage: &constraint_output
produces: [constraint_register, bottlenecks, mitigation_paths]
delta_fields: [findings, decisions, uncertainties, open_questions, recommended_jumps]
readiness-assessment:
produces: [readiness_profile, bottlenecks]
delta_fields: [findings, decisions, uncertainties, open_questions, recommended_jumps]
resource-envelope:
produces: [resource_envelope, bottlenecks, mitigation_paths]
delta_fields: [findings, decisions, uncertainties, open_questions, recommended_jumps]
causal-constraint-analysis: *constraint_output
maturation-path:
produces: [readiness_profile, resource_envelope, stage_gates, mitigation_paths]
delta_fields: [findings, decisions, uncertainties, open_questions, recommended_jumps]
Thresholds and quality gates
Feasibility, maturity, constraint, resource, and maturation gates use declared dimension/evidence/constraint coverage ratios; record numerator, denominator, batch increment, stopping reason, and source references.
Preserve structural requirements: at least one hard constraint, one removal path per removable constraint, explicit stage gates, and a binding-constraint rule relative to the observed score distribution.
Feasibility dimensions >=5; blockers >=3 per candidate where source protocol applies.
Maturity diagnosis: >=5 dimensions, >=2 evidence items per dimension, >=1 bottleneck.
Constraint identification: >=3 constraints per candidate; >=1 hard constraint; >=1 removal path per removable constraint.
Resource envelope: >=3 dimensions (time, cost, personnel) and >=2 analogies per estimate.
Maturation path: >=3 stage gates and >=2 milestones per stage.
Binding constraint threshold: sensitivity score >2* median.
Failure and counterexamples
Do not label a candidate ready with missing evidence, unclassified hard constraints, or an unbounded resource estimate. A conflict with no manageable injection remains blocked.
Provenance map
26 architecture old entries; readiness, feasibility, resource, obstacle, dependency, sensitivity, and maturation families are merged by mode. Missing aliases are listed in log.
Legacy context checkpoint / Delta notes
Append dimension scores/evidence, constraint IDs, bottleneck rationale, resources, gates, and unresolved conflicts.
Preserved source criteria ledger
| source |
source line |
kind |
source criterion |
| feasibility-assessment |
42 |
numeric-table |
\ |
| feasibility-assessment |
75 |
numeric |
\ |
| feasibility-assessment |
76 |
numeric |
\ |
| feasibility-assessment |
77 |
numeric |
\ |
| feasibility-assessment |
78 |
numeric |
\ |
| maturity-diagnosis |
23 |
numeric |
\ |
| maturity-diagnosis |
24 |
numeric |
\ |
| maturity-diagnosis |
25 |
numeric |
\ |
| maturity-diagnosis |
53 |
textual |
1. Identify relevant dimensions for the candidate (minimum: technical, market, regulatory, resource, organizational) |
| maturity-diagnosis |
64 |
numeric |
overall_readiness: <1-9 TRL scale> |
| constraint-identification |
23 |
numeric |
\ |
| constraint-identification |
24 |
numeric |
\ |
| constraint-identification |
25 |
numeric |
\ |
| constraint-identification |
58 |
numeric |
4. For constraints with removability score > 0.3, design removal-path |
| resource-envelope-estimation |
24 |
numeric |
\ |
| resource-envelope-estimation |
25 |
numeric |
\ |
| resource-envelope-estimation |
26 |
numeric |
\ |
| resource-envelope-estimation |
58 |
numeric |
3. Identify >= 2 analogous projects and extract their actual resource consumption |
| resource-envelope-estimation |
61 |
numeric |
6. Flag any estimates with confidence < 0.5 for further investigation |
| comparative-feasibility-ranking |
16 |
textual |
Purpose: Produce a defensible ranking of candidates by feasibility. Uses multi-dimensional radar charts to visualize relative strengths and a weighted feasibility index to collapse multiple dimensions into a single comparable score. |
| comparative-feasibility-ranking |
27 |
numeric |
\ |
| comparative-feasibility-ranking |
28 |
numeric |
\ |
| comparative-feasibility-ranking |
29 |
numeric-table |
\ |
| comparative-feasibility-ranking |
58 |
numeric |
2. Normalize scores to a common scale (1-9 recommended) |
| maturation-pathway-design |
27 |
numeric |
\ |
| maturation-pathway-design |
28 |
numeric |
\ |
| maturation-pathway-design |
29 |
numeric-table |
\ |
| maturation-pathway-design |
37 |
textual |
\ |
| maturation-pathway-design |
62 |
textual |
2. Define target readiness required for implementation |
| maturation-pathway-design |
76 |
textual |
target_readiness: |
| multi-dimensional-readiness-scan |
23 |
textual |
3. Bottleneck Identification - Analyze the radar for dimensions significantly below the mean or below required thresholds. Deploy bottleneck-identification SOP on the radar data. |
| multi-dimensional-readiness-scan |
29 |
numeric-table |
\ |
| multi-dimensional-readiness-scan |
30 |
numeric-table |
\ |
| multi-dimensional-readiness-scan |
31 |
numeric-table |
\ |
| multi-dimensional-readiness-scan |
39 |
numeric |
- Each dimension should have at least 2 evidence items supporting the score |
| multi-dimensional-readiness-scan |
41 |
textual |
## Minimum Yield |
| multi-dimensional-readiness-scan |
43 |
numeric |
- Complete radar with >= 5 dimensions scored |
| constraint-drilling |
26 |
numeric |
4. Removal Path Design - For constraints with removability > 0.3, design concrete steps to remove or mitigate them. Deploy removal-path SOP for each removable constraint. |
| constraint-drilling |
32 |
numeric-table |
\ |
| constraint-drilling |
33 |
numeric-table |
\ |
| constraint-drilling |
34 |
numeric-table |
\ |
| constraint-drilling |
35 |
numeric-table |
\ |
| constraint-drilling |
42 |
numeric |
- Stage 4 only runs for constraints with removability score > 0.3 |
| constraint-drilling |
45 |
textual |
## Minimum Yield |
| constraint-drilling |
47 |
numeric |
- Classified constraint list with >= 3 constraints identified |
| constraint-drilling |
49 |
numeric |
- Removal paths for all constraints scoring removability > 0.3 |
| staged-gate-evaluation |
19 |
textual |
1. Gate Criteria Definition - Define what must be true for a candidate to pass each gate. Deploy gate-criteria-definition SOP for each stage gate. |
| staged-gate-evaluation |
29 |
numeric-table |
\ |
| staged-gate-evaluation |
30 |
numeric-table |
\ |
| staged-gate-evaluation |
31 |
numeric-table |
\ |
| staged-gate-evaluation |
35 |
numeric |
- Stage 1 should define >= 3 gates (e.g., concept feasibility, technical feasibility, implementation readiness) |
| staged-gate-evaluation |
42 |
textual |
## Minimum Yield |
| constraint-analysis |
44 |
textual |
## HARD-GATE |
| constraint-analysis |
46 |
textual |
Before entering this campaign, the following must be true: |
| constraint-analysis |
78 |
textual |
## Budget Gate |
| constraint-analysis |
94 |
textual |
## Minimum Yield |
| constraint-analysis |
97 |
numeric |
- At least 1 binding constraint identified and characterized |
| constraint-analysis |
100 |
numeric |
- No unresolved conflicts between top-3 constraints |
| resource-constraint |
63 |
textual |
## Budget Gate |
| assumption-constraint |
55 |
numeric |
- Top-5 fragile assumptions with validation paths |
| assumption-constraint |
58 |
textual |
## Budget Gate |
| dependency-constraint |
60 |
textual |
## Budget Gate |
| conflict-resolution |
66 |
textual |
## Budget Gate |
| constraint-tree-building |
25 |
textual |
- Minimum 5 UDEs for a meaningful tree |
| constraint-tree-building |
42 |
numeric |
- When to escalate: If >10 UDEs found, prioritize top-5 by severity before tracing |
| constraint-tree-building |
43 |
textual |
- Quality gate: Every causal link must have a BECAUSE clause (the underlying assumption) |
| sensitivity-ranking |
25 |
textual |
- Express gaps in comparable units where possible |
| sensitivity-ranking |
43 |
numeric |
- When to skip: If only 1-2 constraints exist, ranking is trivial |
| sensitivity-ranking |
44 |
numeric |
- Threshold: Constraints with sensitivity score >2* the median are "binding" |
| constraint-breaking |
26 |
textual |
- If constraint is not a dilemma, reframe: "We need X" vs "We cannot have X because Y" |
| constraint-breaking |
29 |
numeric |
- Input: all assumptions from the EC (typically 8-15 assumptions across 4 arrows) |
| constraint-breaking |
35 |
textual |
- Injection must be: specific, actionable, within our control, and testable |
| constraint-breaking |
36 |
numeric |
- Generate 2-3 candidate injections |
| constraint-breaking |
43 |
textual |
- What conditions (prerequisites) must hold? |
Context checkpoint / Delta notes
Append dimension scores/evidence, constraint IDs, bottleneck rationale, resources, gates, and unresolved conflicts.
| constraint-breaking | 54 | numeric | - Success criterion: At least one injection that resolves the conflict with <=2 manageable side effects |
1---2name: analyze-constraints-readiness3description: "Characterize what blocks a research target: readiness dimensions, obstacles, bottlenecks, resource gaps, causal constraints, dependencies, conflicts, removability, and mitigation pathways. Depth selects lightweight triage, readiness assessment, or causal/TOC-style constraint analysis."4metadata:5 source: https://skillmd.com/skills/yogsoth-ai/analyze-constraints-readiness6---78# analyze-constraints-readiness910## Purpose1112Assess feasibility and readiness by identifying constraints, resources, dependencies, bottlenecks, and maturation gates.1314## Input contract1516```yaml17mode_contracts:18 obstacle-triage: &readiness_input19 required: [candidate_or_plan, readiness_dimensions]20 optional: [resource_estimates, dependencies, assumptions, target_gates]21 constraints: [evidence_must_be_attached_to_each_scored_dimension]22 readiness-assessment: *readiness_input23 resource-envelope: *readiness_input24 causal-constraint-analysis: *readiness_input25 maturation-path: *readiness_input26```2728## Execution protocol2930Do not perform called SOP operations inline; each loaded SOP owns its contract and thresholds.31321. Define candidate, dimensions, hard constraints, and target gates. You MUST load skill `classify-constraint` to classify each declared constraint.332. Select `obstacle-triage`, `readiness-assessment`, `resource-envelope`, `causal-constraint-analysis`, or `maturation-path`.343. You MUST load skill `score-object` to score the selected dimensions with evidence. You MUST load skill `identify-bottleneck` to identify binding constraints and dependencies.354. You MUST load skill `assess-removability` to test whether binding constraints can be removed. You MUST load skill `design-mitigation` to design removal or mitigation paths and return a readiness conclusion.36 If several feasible responses must be balanced as a joint set, consider `portfolio-optimization`. If the target goal remains too broad to assess, consider `decompose-research-goal`. If external change dominates present readiness, consider `analyze-future-scenarios`. If several candidate paths are ready for comparative selection, `rank-candidates` may be the better next tactic.3738## Mode branches3940- `obstacle-triage`: rapidly enumerate and severity-rank the obstacles that could block the target, preserving evidence status for each one. You MUST load skill `identify-obstacles` to enumerate the obstacles. You MUST load skill `list-undesirable-effects` to retain their observed consequences.41- `readiness-assessment`: score the required readiness dimensions with supporting evidence and identify the dimensions that keep the target from being ready. You MUST load skill `assess-readiness-dimension` to assess every required dimension.42- `resource-envelope`: estimate time, cost, and personnel bounds from analogies, then flag low-confidence estimates for investigation. You MUST load skill `quantify-resource-gap` to quantify the gap. You MUST load skill `identify-critical-chain` to expose the binding resource sequence.43- `causal-constraint-analysis`: trace how constraints interact through dependencies and conflicts to identify the binding cause rather than only its symptoms. You MUST load skill `trace-causal-chain` to trace constraint propagation. You MUST load skill `extract-core-conflict` to isolate the core conflict. You MUST load skill `challenge-assumption` to test the assumptions that sustain it.44- `maturation-path`: sequence stage gates and milestones that move the target from current readiness to the declared implementation threshold. You MUST load skill `project-future-reality` to project the proposed path. You MUST load skill `apply-stage-gate` to apply its stage gates.4546## Output contract4748```yaml49mode_contracts:50 obstacle-triage: &constraint_output51 produces: [constraint_register, bottlenecks, mitigation_paths]52 delta_fields: [findings, decisions, uncertainties, open_questions, recommended_jumps]53 readiness-assessment:54 produces: [readiness_profile, bottlenecks]55 delta_fields: [findings, decisions, uncertainties, open_questions, recommended_jumps]56 resource-envelope:57 produces: [resource_envelope, bottlenecks, mitigation_paths]58 delta_fields: [findings, decisions, uncertainties, open_questions, recommended_jumps]59 causal-constraint-analysis: *constraint_output60 maturation-path:61 produces: [readiness_profile, resource_envelope, stage_gates, mitigation_paths]62 delta_fields: [findings, decisions, uncertainties, open_questions, recommended_jumps]63```6465## Thresholds and quality gates6667- Feasibility, maturity, constraint, resource, and maturation gates use declared dimension/evidence/constraint coverage ratios; record numerator, denominator, batch increment, stopping reason, and source references.68- Preserve structural requirements: at least one hard constraint, one removal path per removable constraint, explicit stage gates, and a binding-constraint rule relative to the observed score distribution.6970- Feasibility dimensions >=5; blockers >=3 per candidate where source protocol applies.71- Maturity diagnosis: >=5 dimensions, >=2 evidence items per dimension, >=1 bottleneck.72- Constraint identification: >=3 constraints per candidate; >=1 hard constraint; >=1 removal path per removable constraint.73- Resource envelope: >=3 dimensions (time, cost, personnel) and >=2 analogies per estimate.74- Maturation path: >=3 stage gates and >=2 milestones per stage.75- Binding constraint threshold: sensitivity score >2* median.7677## Failure and counterexamples7879Do not label a candidate ready with missing evidence, unclassified hard constraints, or an unbounded resource estimate. A conflict with no manageable injection remains blocked.8081## Provenance map828326 architecture `old` entries; readiness, feasibility, resource, obstacle, dependency, sensitivity, and maturation families are merged by mode. Missing aliases are listed in log.8485## Legacy context checkpoint / Delta notes8687Append dimension scores/evidence, constraint IDs, bottleneck rationale, resources, gates, and unresolved conflicts.8889## Preserved source criteria ledger9091| source | source line | kind | source criterion |92|---|---:|---|---|93| feasibility-assessment | 42 | numeric-table | \\| maturity-diagnosis \\| Assess current readiness using TRL 9-level, NASSS 7-dimension, and Innovation Readiness Level frameworks \\| |94| feasibility-assessment | 75 | numeric | \\| Dimensions assessed \\| >= 5 (technical, market, regulatory, resource, organizational) \\| |95| feasibility-assessment | 76 | numeric | \\| Blockers identified \\| >= 3 per candidate \\| |96| feasibility-assessment | 77 | numeric | \\| Estimate precision \\| from +/-30% to +/-10% through iteration \\| |97| feasibility-assessment | 78 | numeric | \\| Gates evaluated \\| >= 3 stage gates \\| |98| maturity-diagnosis | 23 | numeric | \\| Dimensions scored \\| >= 5 \\| |99| maturity-diagnosis | 24 | numeric | \\| Evidence items per dimension \\| >= 2 \\| |100| maturity-diagnosis | 25 | numeric | \\| Bottlenecks identified \\| >= 1 \\| |101| maturity-diagnosis | 53 | textual | 1. Identify relevant dimensions for the candidate (minimum: technical, market, regulatory, resource, organizational) |102| maturity-diagnosis | 64 | numeric | overall_readiness: <1-9 TRL scale> |103| constraint-identification | 23 | numeric | \\| Constraints identified \\| >= 3 per candidate \\| |104| constraint-identification | 24 | numeric | \\| Hard constraints classified \\| >= 1 \\| |105| constraint-identification | 25 | numeric | \\| Removal paths designed \\| >= 1 per removable constraint \\| |106| constraint-identification | 58 | numeric | 4. For constraints with removability score > 0.3, design `removal-path` |107| resource-envelope-estimation | 24 | numeric | \\| Estimate dimensions \\| >= 3 (time, cost, personnel) \\| |108| resource-envelope-estimation | 25 | numeric | \\| Precision range \\| +/-30% initial, +/-10% refined \\| |109| resource-envelope-estimation | 26 | numeric | \\| Reference analogies \\| >= 2 per estimate \\| |110| resource-envelope-estimation | 58 | numeric | 3. Identify >= 2 analogous projects and extract their actual resource consumption |111| resource-envelope-estimation | 61 | numeric | 6. Flag any estimates with confidence < 0.5 for further investigation |112| comparative-feasibility-ranking | 16 | textual | **Purpose:** Produce a defensible ranking of candidates by feasibility. Uses multi-dimensional radar charts to visualize relative strengths and a weighted feasibility index to collapse multiple dimensions into a single comparable score. |113| comparative-feasibility-ranking | 27 | numeric | \\| Candidates compared \\| >= 2 \\| |114| comparative-feasibility-ranking | 28 | numeric | \\| Dimensions in radar \\| >= 5 \\| |115| comparative-feasibility-ranking | 29 | numeric-table | \\| Weight justifications \\| 1 per dimension \\| |116| comparative-feasibility-ranking | 58 | numeric | 2. Normalize scores to a common scale (1-9 recommended) |117| maturation-pathway-design | 27 | numeric | \\| Stage gates defined \\| >= 3 \\| |118| maturation-pathway-design | 28 | numeric | \\| Milestones per stage \\| >= 2 \\| |119| maturation-pathway-design | 29 | numeric-table | \\| Resource estimates per stage \\| 1 per stage \\| |120| maturation-pathway-design | 37 | textual | \\| target_readiness \\| object \\| Required maturity for implementation \\| |121| maturation-pathway-design | 62 | textual | 2. Define target readiness required for implementation |122| maturation-pathway-design | 76 | textual | target_readiness: <required score> |123| multi-dimensional-readiness-scan | 23 | textual | 3. **Bottleneck Identification** - Analyze the radar for dimensions significantly below the mean or below required thresholds. Deploy `bottleneck-identification` SOP on the radar data. |124| multi-dimensional-readiness-scan | 29 | numeric-table | \\| dimension-assessment \\| 1 \\| Score a single readiness dimension \\| |125| multi-dimensional-readiness-scan | 30 | numeric-table | \\| radar-synthesis \\| 2 \\| Combine scores into radar chart data \\| |126| multi-dimensional-readiness-scan | 31 | numeric-table | \\| bottleneck-identification \\| 3 \\| Identify limiting dimensions \\| |127| multi-dimensional-readiness-scan | 39 | numeric | - Each dimension should have at least 2 evidence items supporting the score |128| multi-dimensional-readiness-scan | 41 | textual | ## Minimum Yield |129| multi-dimensional-readiness-scan | 43 | numeric | - Complete radar with >= 5 dimensions scored |130| constraint-drilling | 26 | numeric | 4. **Removal Path Design** - For constraints with removability > 0.3, design concrete steps to remove or mitigate them. Deploy `removal-path` SOP for each removable constraint. |131| constraint-drilling | 32 | numeric-table | \\| constraint-identification-sop \\| 1 \\| Discover constraints using structured methods \\| |132| constraint-drilling | 33 | numeric-table | \\| constraint-classification \\| 2 \\| Categorize constraints by type \\| |133| constraint-drilling | 34 | numeric-table | \\| removability-assessment \\| 3 \\| Score removability of each constraint \\| |134| constraint-drilling | 35 | numeric-table | \\| removal-path \\| 4 \\| Design removal steps and timeline \\| |135| constraint-drilling | 42 | numeric | - Stage 4 only runs for constraints with removability score > 0.3 |136| constraint-drilling | 45 | textual | ## Minimum Yield |137| constraint-drilling | 47 | numeric | - Classified constraint list with >= 3 constraints identified |138| constraint-drilling | 49 | numeric | - Removal paths for all constraints scoring removability > 0.3 |139| staged-gate-evaluation | 19 | textual | 1. **Gate Criteria Definition** - Define what must be true for a candidate to pass each gate. Deploy `gate-criteria-definition` SOP for each stage gate. |140| staged-gate-evaluation | 29 | numeric-table | \\| gate-criteria-definition \\| 1 \\| Define criteria and pass thresholds \\| |141| staged-gate-evaluation | 30 | numeric-table | \\| gate-judgment \\| 2 \\| Evaluate and render verdict \\| |142| staged-gate-evaluation | 31 | numeric-table | \\| feasibility-synthesis \\| 3 \\| Synthesize into final recommendation \\| |143| staged-gate-evaluation | 35 | numeric | - Stage 1 should define >= 3 gates (e.g., concept feasibility, technical feasibility, implementation readiness) |144| staged-gate-evaluation | 42 | textual | ## Minimum Yield |145| constraint-analysis | 44 | textual | ## HARD-GATE |146| constraint-analysis | 46 | textual | Before entering this campaign, the following must be true: |147| constraint-analysis | 78 | textual | ## Budget Gate |148| constraint-analysis | 94 | textual | ## Minimum Yield |149| constraint-analysis | 97 | numeric | - At least 1 binding constraint identified and characterized |150| constraint-analysis | 100 | numeric | - No unresolved conflicts between top-3 constraints |151| resource-constraint | 63 | textual | ## Budget Gate |152| assumption-constraint | 55 | numeric | - Top-5 fragile assumptions with validation paths |153| assumption-constraint | 58 | textual | ## Budget Gate |154| dependency-constraint | 60 | textual | ## Budget Gate |155| conflict-resolution | 66 | textual | ## Budget Gate |156| constraint-tree-building | 25 | textual | - Minimum 5 UDEs for a meaningful tree |157| constraint-tree-building | 42 | numeric | - **When to escalate**: If >10 UDEs found, prioritize top-5 by severity before tracing |158| constraint-tree-building | 43 | textual | - **Quality gate**: Every causal link must have a BECAUSE clause (the underlying assumption) |159| sensitivity-ranking | 25 | textual | - Express gaps in comparable units where possible |160| sensitivity-ranking | 43 | numeric | - **When to skip**: If only 1-2 constraints exist, ranking is trivial |161| sensitivity-ranking | 44 | numeric | - **Threshold**: Constraints with sensitivity score >2* the median are "binding" |162| constraint-breaking | 26 | textual | - If constraint is not a dilemma, reframe: "We need X" vs "We cannot have X because Y" |163| constraint-breaking | 29 | numeric | - Input: all assumptions from the EC (typically 8-15 assumptions across 4 arrows) |164| constraint-breaking | 35 | textual | - Injection must be: specific, actionable, within our control, and testable |165| constraint-breaking | 36 | numeric | - Generate 2-3 candidate injections |166| constraint-breaking | 43 | textual | - What conditions (prerequisites) must hold? |167168## Context checkpoint / Delta notes169170Append dimension scores/evidence, constraint IDs, bottleneck rationale, resources, gates, and unresolved conflicts.171| constraint-breaking | 54 | numeric | - **Success criterion**: At least one injection that resolves the conflict with <=2 manageable side effects |