Engine and Support Matrix
Authoritative support snapshot for what the current Licklider release supports across methods, figures, and implementation maturity.
This section is the public support snapshot for the current Licklider release.
Use it to answer three different kinds of questions:
- Which statistical methods are supported today, and which ones are only partially covered?
- Which figure families are first-class public surfaces versus specialized or conditional workflows?
- Which implementations are currently active product paths, and which ones should be treated as legacy, transitional, or non-authoritative?
Child pages
Supported Methods Matrix
The current method coverage snapshot for statistical tests, model families, and analysis capabilities that users can expect in the current release.
Figure Support Matrix
The current support snapshot for figure families, including which surfaces are strong current support and which ones remain specialized or conditional.
Active vs Legacy Implementations
Guidance for reading the current product surface conservatively when multiple historical implementations, route paths, or documentation layers coexist.
How to use this section
Read this section as a release-facing boundary document, not as an exhaustive internal inventory.
- "Supported" means the product currently exposes the surface as part of the intended user-facing experience.
- "Partial" means some core paths are present, but surrounding coverage or edge handling is still narrower than the mature contract.
- "Legacy" means the codebase may still contain related paths or historical behavior, but those paths should not automatically be treated as the current public contract.
Start here
- Start with Supported Methods Matrix.
- Continue to Figure Support Matrix.
- Use Active vs Legacy Implementations when you need to interpret support claims conservatively.