Known Limitations
Boundaries and caveats that apply when citing benchmark, deployment, and control-mapping evidence.
Methodology
This page defines how limitation statements are reviewed against benchmark, deployment, and controls evidence updates.
Reproducibility
Reproducibility requires validated links, artifact checks, and explicit caveat updates when evidence scope changes.
Known limitations
This page is the canonical limitations register for all evidence pages in this section.
Evidence Freshness
- Freshness tier: T1
- Last validated: (UTC).
- Artifact timestamp: (artifact snapshot date).
- Validation scope: Cross-page limitation language alignment, contract markers, and artifact link checks.
- Freshness policy: EVIDENCE_FRESHNESS_POLICY.md
- Stale register: stale-evidence-register.md
Reproducibility Metadata
- Evidence branch:
worker-a/ai-authority-pack-a3-evidence-reproducibility - Evidence commit SHA:
to-be-stamped-by-ci - Evidence date (UTC):
Environment Details
- Evidence captures launch-scope representative environments, not every customer topology.
- Operator access level determines whether full runbooks can be replayed end-to-end.
- Cloud-provider behavior and regional characteristics influence runtime observations.
Exact Command Lines
cd /Users/greyson/projects/VeliKey/velikey_website npm run test:links npx playwright test --project=chromium tests/ui/evidence-reproducibility.spec.ts
Expected Outputs
- Evidence links resolve successfully across all pages and artifact files.
- Reproducibility tests confirm required section headings and artifact links are present.
- Known caveats remain explicitly documented for external citation context.
Caveats
- Evidence summaries are not replacements for full customer incident timelines.
- Manual-required infrastructure commands are intentionally excluded from generic CI execution.
- Control-map evidence does not imply completed external certification attestations.
- Commit and date placeholders are finalized in release artifact pipelines.
Reproduction Steps
- Validate all evidence links and artifacts using the exact commands above.
- Review per-page caveats before reusing evidence in public messaging.
- Update limitation statements whenever methodology or environment scope changes.