Defines sparse routing, confidence, eligibility, top-k activation, hysteresis, cooldowns, and explicit abstention or no-op behavior.
Architecture guide: this topic defines a modular tiny-model planning contract. It does not claim that model artifacts exist, are compatible, or execute on this WordPress site.
Eligibility before ranking
Remove candidates that fail license, dependency, schema, backend, memory, or policy checks before scoring task relevance. A highly relevant but incompatible model is not an eligible action.
Selection record
- Candidate roles and excluded reasons.
- Router inputs, confidence, and calibration.
- Top-k, threshold, tie-break, and fallback.
- Current active set, incremental cost, and hysteresis.
- Selected action and no-op margin.
Stability controls
Use cooldowns, minimum residence times, and replace thresholds to prevent rapid load/unload oscillation. These are engineering stabilizers and must be logged separately from teleodynamic evidence.
Scope
This starter page defines the questions, boundaries, evidence, and failure modes that should be recorded before a capability is presented as supported.
Engineering considerations
- Identify the source, version, target environment, and owner.
- Separate observed values from estimates and externally reported values.
- Record trade-offs, unsupported cases, and fallback behavior.
- Link performance statements to a compatible benchmark methodology.
Verification questions
- What exact artifact, revision, backend, and environment were reviewed?
- Which assumptions could change the result?
- Which data should be retained so another engineer can reproduce the conclusion?