Behavioral Strategy Toolkit (Specs & Templates) #

This page previews machine-readable files that make the core Behavioral Strategy decision tools easier to reuse, cite, and implement. The approved model contracts and the release status of their toolkit files are separate: v2 terminology is canonical, while the v2 files below remain release candidates.

Specs (machine-readable) #

• Behavior Fit Assessment v2 release candidate (canonical model contract; pre-release and unsupported): /tools/toolkit/behavior-fit-assessment.v2.json
• Behavior Fit Assessment v1 historical specification (deprecated and preserved verbatim): /tools/toolkit/behavior-fit-assessment.v1.json
• Four-Fit v2 release candidate (pre-release and unsupported): /tools/toolkit/four-fit-hierarchy.v2.json
• Four-Fit v1 historical specification (deprecated and preserved verbatim): /tools/toolkit/four-fit-hierarchy.v1.json

Templates (machine-readable) #

• Case write-up template (v1): /tools/toolkit/case-template.v1.yaml
• Behavior selection v2 release candidate (pre-release and unsupported): /tools/toolkit/behavior-selection-template.v2.yaml
• Behavior selection v1 historical template (deprecated and preserved verbatim): /tools/toolkit/behavior-selection-template.v1.yaml
• Behavior measurement spec template (v1): /tools/toolkit/measurement-spec-template.v1.yaml

Examples (inputs -> outputs) #

• Behavior Fit Assessment scoring example: /tools/toolkit/examples/bfa-scoring.example.json
• Measurement spec example: /tools/toolkit/examples/measurement-spec.example.yaml

Versioning and evidence posture #

• Release status: The v2 files are release candidates, not a formal U7 toolkit release. They have no named maintainer, support commitment, release manifest, or recorded usability review. Use them for inspection and testing; do not represent them as a supported release.
• These are practitioner specs, not validated measurement instruments. Calibrate thresholds by domain and link quantitative claims to the Evidence Ledger or mark them as examples.
• Versioned files are immutable. Changed schemas or meanings receive a new versioned filename so existing citations and integrations do not silently drift.
• BFA v1.x records that use Identity Fit remain historical v1.x records. Do not silently relabel or compare those scores with BFA v2.0; rescore from the underlying evidence using the v2.0 definitions and anchors.