[Preset]: Add Model Routing Governance v0.1.4

[hindermath]

Preset ID

model-routing-governance

Preset Name

Model Routing Governance

Version

0.1.4

Description

Maps provider-neutral Spec Kit roles to validated harness-local runner profiles without storing model availability, credentials, or machine-specific selections in Git.

Author

Thorsten Hindermann

Repository URL

https://github.com/hindermath/spec-kit-preset-model-routing-governance

Download URL

https://github.com/hindermath/spec-kit-preset-model-routing-governance/archive/refs/tags/v0.1.4.zip

Documentation URL

https://github.com/hindermath/spec-kit-preset-model-routing-governance/blob/v0.1.4/README.md

License

MIT

Required Spec Kit Version

=0.8.3

Required Extensions (optional)

None

Templates Provided

• model-routing-governance-model-routing - portable command-to-role declarations
• model-routing-agent-guidance-addendum-template - provider-neutral discovery and selection guidance
• model-routing-policy-template - adapter, evidence, and fail-closed selection policy
• model-routing-profiles-template - local, non-versioned runner-profile example

Commands Provided

• speckit.model-routing-status - inspects harness, model, role, and profile status without changing files
• speckit.model-routing-refresh - refreshes an explicitly authorized local fail-closed model-to-role binding

Number of Scripts (optional)

2

Tags

model-routing, agents, governance, provider-neutral, cross-platform

Key Features

Hi @mnriem, thank you for your earlier guidance on optional, stackable Spec Kit presets.

• Keeps repository policy provider-neutral: commands declare workload roles and constraints, while each machine resolves those roles through a local, ignored runner profile.
• Detects models exposed by the active harness through explicit adapters and fails closed when discovery is unavailable, ambiguous, stale, or incompatible with policy.
• Separates read-only status from an explicitly authorized refresh. Neither command grants execution, provider, credential, billing, admin, or remote-delivery authority.
• Stores normalized hashes and freshness evidence without committing credentials, concrete local availability, or machine-specific selections.
• Supports deterministic Bash and PowerShell discovery with equivalent status classes and exit behavior.
• Composes at optional priority 61 after Agent Parity Governance and before Intake Authoring, Intake Review, Intake Sequencing, Autonomous Run, and Parallel Autonomous Run.
• Integrates with Autonomous Run Governance v0.3.6 and Parallel Autonomous Run Governance v0.2.6, so orchestration can request provider-neutral roles while preserving each command's authority and convergence boundaries.
• Passed positive and negative discovery fixtures, LF/CRLF and UTF-8 handling, policy and stale-state checks, Bash/PowerShell parity, and exact twelve-preset composition.
• Was installed and validated in 33 registered Level-1/Level-2 repositories. Every target passed the exact preset matrix, both discovery implementations, diff checks, secret checks, and command/skill uniqueness; all 33 rollout PRs were merged with zero actionable review threads.
• Provider failures were not counted as successful review: 193 jobs were proven to have executed zero steps, and four external reviews returned no usable result.
• The versioned ZIP SHA-256 is c9e04d29983a12743b1f465cd1d44e647076bd5edd19e4e439919de7b1c1aed7.
• Detailed field evidence is available at https://github.com/hindermath/home-baseline/blob/main/docs/field-validation/model-routing-fleet-2026-08-09.md.

Maintainer feedback on the provider-neutral role boundary, local-profile design, command names, metadata, and community-catalog suitability would be appreciated. The preset is opt-in and does not change Spec Kit core behavior.

Testing Checklist

• Preset installs successfully via specify preset add
• Template resolution works correctly after installation
• Documentation is complete and accurate
• Tested on at least one real project

Submission Requirements

• Valid preset.yml manifest included
• Linked README explains how to use this preset and includes the exact versioned specify preset add --from ... install command
• LICENSE file included
• GitHub release created with version tag
• Preset ID follows naming conventions

[hindermath]

The issue body follows every field of the current preset_submission.yml template. The template still references the no-longer-existing needs-triage label, while contributor permissions do not allow me to add preset-submission directly. Could a maintainer please apply preset-submission so the catalog validation workflow can run? Thank you.