Skip to main content
Parmana states what it claims in docs/CLAIMS.md. Every claim there is scoped to its evidence: the code that implements it, the tests that check it, and what it explicitly does not cover. This site mirrors that file and never overrides it. When the two disagree, CLAIMS.md is authoritative and the site is wrong.

​
How to read a claim

  • The heading states the claim. A heading marked (Scoped) holds only within the boundary its text states.
  • Evidence lists the code and tests. A claim is written in the present tense only when code and tests back it.
  • Dated updates record changes. When a claim is narrowed, corrected or extended, a dated Update paragraph is added rather than the original text being rewritten, so the history stays readable.
  • What is not claimed is stated too. See Limitations, and section 5 of CLAIMS.md.
Gaps that were found, and how each was closed or narrowed, are in docs/VERIFICATION-GAPS.md. Open work is in docs/REMAINING-WORK.md.

​
Core claims

Run any listed test after npm ci and npm run build with npx vitest run <path>. Every test also runs in npm test. Each claim’s full text, scope and remaining limits are in the CLAIMS.md section named in the middle column. Read it before relying on the one line summary here.

​
Claims about live deployments

Statements about the hosted sandbox and production (sections 2.51, 3.8, 3.9 and 3.18 of CLAIMS.md) describe what was checked on a stated date, against a stated deployment. They are evidence that the code ran there on that date, not a continuous guarantee. Sections marked Historical describe connectors that have since been removed.

​
Changing a claim

A claim changes only together with its evidence, in the same pull request: CLAIMS.md first, then this site. See CONTRIBUTING.md and Contributing to this documentation.