Introduces the research tracks documentation area and links its component topics.
Reading this section
Each track is a bounded research lens. A track may produce architecture guidance, terminology, evidence requirements, or roadmap entries without implying a released runtime.
Promotion rule
Move a claim beyond Research only when the exact artifact, source revision, environment, method, owner, and limitations have been reviewed.
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?