map-validity-envelope
Purpose
Map where a claim, method, or design remains valid by defining axes, probing values, detecting breakpoints, and constructing a multidimensional validity envelope.
Input contract
mode_contracts:
systematic-perturbation: &validity_input
required: [claim_or_method, validity_target, analysis_dimensions]
optional: [baseline_conditions, critical_case_rule, perturbation_budget]
constraints: [axes_values_outcome_measure_and_breakpoint_rule_must_be_explicit]
boundary-value-stress: *validity_input
critical-case: *validity_input
Execution protocol
Do not perform called SOP operations inline; each loaded SOP owns its contract and thresholds.
- You MUST load skill
define-analysis-dimensionsto define the validity axes. You MUST load skillenumerate-dimension-valuesto enumerate representative and boundary values. - Apply the probes required by the selected mode and retain their evidence.
- You MUST load skill
detect-breakpointto locate validity transitions. You MUST load skillconstruct-validity-envelopeto construct the supported envelope. - You MUST load skill
analyze-scaling-regimeto analyze scale-dependent regime changes. If global effect decomposition is needed beyond the envelope, considersensitivity-analysis. If the resulting boundary claim lacks a reachable falsifier, considerfalsifiability-audit. Deviation: usecritical-casewhen a decisive case can replace broad probing; otherwise usesystematic-perturbationorboundary-value-stressaccording to the declared mode and evidence.
Output contract
mode_contracts:
systematic-perturbation:
produces: [dimension_schema, perturbation_records, breakpoints, validity_envelope]
delta_fields: [findings, evidence_updates, uncertainties, decisions, open_questions]
boundary-value-stress:
produces: [dimension_schema, perturbation_records, breakpoints, validity_envelope, critical_case_report]
delta_fields: [findings, evidence_updates, uncertainties, decisions, open_questions]
critical-case:
produces: [breakpoints, validity_envelope, critical_case_report]
delta_fields: [findings, evidence_updates, uncertainties, decisions, open_questions]
Thresholds and quality gates
- Breakpoints require an explicit outcome criterion and before/after evidence.
- Envelope claims must state untested regions and uncertainty.
Failure and counterexamples
Do not infer an envelope from a single favorable case. Mark extrapolation outside sampled axes as unsupported.
Provenance map
- concept: validity-envelope-mapping [strategy]
- resolved: systematic-perturbation
- resolved: variation-axis-definition
- resolved: controlled-perturbation
- concept: validity-envelope-construction [sop]
- resolved: adversarial-stress-testing
- concept: validity-envelope-mapping [stress strategy]
- resolved: parameter-space-mapping
- resolved: extreme-value-generation
- resolved: breakpoint-detection
- intermediate: Pass5/validity-envelope-analysis
- intermediate: Pass5/boundary-stress-test
Preserved source criteria ledger
| source | source line | kind | source criterion |
|---|---|---|---|
| v4 architecture | modes/calls | structural | Actual modes are systematic-perturbation, boundary-value-stress, critical-case; alias labels are not used. |
Context checkpoint / Delta notes
Append axes, values, perturbations, breakpoints, envelope, critical cases, scaling findings, and untested regions.
Mode branches
systematic-perturbation: broad controlled variation across declared axes. You MUST load skillapply-perturbationto vary the declared axes systematically.boundary-value-stress: emphasize boundary, pathological, and adversarial values. You MUST load skillapply-perturbationto probe boundary and pathological values.critical-case: select inference-maximizing cases and document selection logic. You MUST load skillselect-critical-caseto select and justify the decisive cases.
