Pragma · Documentation

Docs.

Pragma is documentation engineering for regulated software. We rebuild SSPs as OSCAL — versioned, diff-able, continuously evaluated against your codebase on every PR. This index covers the public methodology, getting-started guides, and the Specshift OSS evaluator.

Specshift methodology

The public methodology describes the four scoring suites — retrieval, agent, structure, and drift — and the rules that make every score reproducible. Methodology version is pinned in every Specshift report. The limitations.md companion documents what v1.0 does not measure.

Read the methodology →

Specshift OSS — first 15 minutes

Paste a docs URL into /eval and Specshift runs all four suites against it right now — no install required. The CLI below is not yet published to npm.

1
Run it now
Paste a URL into /eval. The scorecard — overall score, per-suite breakdown, every test — renders inline in the response. No login, no install.
2
Read the methodology
Understand what each sub-score means and what to fix first.
3
CLI — not yet published
npx @wentzel/specshift run https://docs.example.com --methodology=v1 is the CLI surface once it ships. Not yet published to npm — /eval is the working way to run Specshift today.

Try the hosted eval →

Platform overview

Four scoring suites measure what matters for regulated documentation. Each suite has a public spec and a public limitations document.

01retrieval

Can a vector index answer realistic developer questions from these docs?

02agent

Can a tool-use agent complete a representative task using only these docs?

03structure

Are the docs organised so a model can navigate without context overflow?

04drift

Do the docs describe the platform's actual current behaviour?

Full Specshift overview →

Knowledge base

The Pragma knowledge base covers OSCAL authoring, FedRAMP control mapping, SSP Sprint methodology, and Specshift CLI reference. Knowledge base articles are published alongside engagements and updated each quarter.

Knowledge base content is in active development as part of the 2026 launch. Anchor-customer-facing articles are published before each SOW signs.

Request early access to the KB →

Dispute a methodology score or file an RFC? Contact us. Disputes are tracked publicly under PRAG/06.

Docs.

Specshift methodology

Read the methodology →

Specshift OSS — first 15 minutes

Paste a docs URL into /eval and Specshift runs all four suites against it right now — no install required. The CLI below is not yet published to npm.

1
Run it now
Paste a URL into /eval. The scorecard — overall score, per-suite breakdown, every test — renders inline in the response. No login, no install.
2
Read the methodology
Understand what each sub-score means and what to fix first.
3
CLI — not yet published
npx @wentzel/specshift run https://docs.example.com --methodology=v1 is the CLI surface once it ships. Not yet published to npm — /eval is the working way to run Specshift today.