Describes a resident base plus compact adapters, exact compatibility requirements, activation modes, interference risks, and rollback.
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.
Compatibility is exact
An adapter is not compatible merely because two models share a family name. Verify base revision, layer names, dimensions, rank, target modules, tokenizer, precision, merge mode, and runtime kernel support.
Activation modes
- Hot-swapped single adapter.
- Weighted adapter fusion.
- Token- or layer-level routing.
- Offline merge into a derived artifact.
Risks
Adapter interference, stale base revisions, irreversible in-place mutation, incorrect unmerge, and cumulative numerical drift require fixtures and rollback. Keep the immutable base and derived artifacts distinguishable.
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?