Head of R&D — Key Questions
Documentation status: guide — see Maturity and evidence.
- Which experimental capabilities are candidates for a stable public contract?
- What test evidence is required before changing documentation status from roadmap to architecture or reference?
- Are benchmarks separated from correctness and compatibility tests?
- Can a new accelerator/backend fail safely and fall back without changing semantics?
- Are persistent-data changes migration-compatible?
- Do source-level innovations leak private types into generated SDKs?
- Are research outputs reproducible enough to become product capabilities?
- Is there a clear owner for deprecating experiments that should not become permanent maintenance burden?