Treats tokenizer, base revision, tensor layout, input/output schema, quantization, backend, and license relationships as a resolved graph rather than informal tags.
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.
Graph nodes
Represent models, adapters, tokenizers, preprocessors, schemas, runtimes, backends, licenses, datasets, and benchmark records as versioned nodes.
Graph edges
- Requires exact revision.
- Compatible with verified range.
- Conflicts with.
- Derived from.
- Replaces or deprecates.
- Measured by.
Resolution
Resolve the graph before download or activation. Cycles, missing revisions, license conflicts, unsupported operators, or ambiguous tokenizers must produce a visible failure rather than best-effort execution.
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?