Maps activate, deactivate, reserve, replace, retire, split, merge, and no-op to explicit resource and evidence conditions without anthropomorphic claims.
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.
Operator vocabulary
- Activate
- Make an installed compatible role available for the current task.
- Deactivate
- Remove a role from the active set while retaining its artifact.
- Reserve
- Keep a slot or budget available without assigning a model.
- Replace
- Swap a role implementation after validation and rollback preparation.
- Retire
- Remove a stale or unjustified artifact from the supported registry.
- Split or merge
- Change role boundaries only with evaluation showing reduced confusion or duplication.
- No-op
- Preserve the current structure when no candidate improves local viability.
Claim boundary
These operators can implement a resource-aware controller. Calling them teleodynamic additionally requires the declared two-timescale, endogenous-resource, local-objective, halt, and phase 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?