Documentation maturity and evidence
Documentation status: reference.
Every public page carries machine-readable metadata and now exposes its documentation status visibly near the page title. The status does not by itself prove implementation maturity.
| Documentation status | Meaning |
|---|---|
reference |
Stable public contract or behavior supported strongly enough to be used as reference. |
guide |
Recommended usage built from published/validated concepts. |
tutorial |
Reproducible learning path; platform-specific prerequisites must be stated. |
architecture |
Intended or partially verified architecture; check evidence before treating exact signatures/targets as certified. |
roadmap |
Planned direction, not a current guarantee. |
maintainer |
Maintainer-facing material. |
archive |
Historical context, not current guidance. |
Evidence labels for technical claims
Where useful, pages should additionally distinguish Generated API, Generated when published, vNext binding target, and Application pattern. Exact generated names remain package-dependent unless current generated output certifies them.
Canonical claims policy
The corporate claims policy is canonical on logiCells.com — Claims. This .net page is its technical-documentation implementation: evidence labels, maturity, platform certification and reproducibility are enforced here rather than redefined independently.
Claims discipline
No benchmark number without a reproducible protocol. No platform-support statement without a matrix row. No exact API signature as reference without current generated output or an unambiguous published contract.