Organizes runtime, model, teleodynamic, compiler, and governance reports into bounded research tracks without converting proposals into implementation claims.
Tracks in scope
- Small-model runtime and artifact architecture.
- Teleodynamic and resource-bounded control systems.
- TinyLM-16M as a reference workload.
- Standard ML compiler and virtual-machine design as a case study.
- Rust-oriented architecture and enterprise governance.
Outputs
Research can become documentation, a guide, an evidence schema, a benchmark method, a roadmap item, or a correction. It does not become support merely by being published.
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?