Pragma · Documentation Engineering

Documentation engineering, applied to diligence, authority, drift, and authorization.

Documentation engineering, applied to

Diligence.

Next step
  1. 01Run Specshift on your docs
  2. 02How the FedRAMP wedge works
  3. 03Read the methodology

Section 01

Engineering.
Not narrative.

Compliance documentation, treated as code. Versioned, tested, re-evaluated on every pull request. Pragma replaces the consultancy "writing pass" with a build pipeline that survives audit because it was always engineered to.

  • OSCAL-native
  • Diff-able SSPs in CI
  • Drift gates on every PR
  • Senior engineers, not writers

Section 02

Engagements.

  1. 01
    SSP Sprint
    Lump sum, 50/50 split.
    ~$100K
    6–8 weeks
    OSCAL-native SSP rebuild. We take a draft SSP from whatever state it is in and return a versioned, OSCAL-compliant artifact checked into your repository.
  2. 02
    ATO Acceleration
    40/30/30, net-30/60/90.
    $300–500K
    Milestone-based
    Full authorization push. Covers all documentation engineering from initial OSCAL build through 3PAO assessment, with Pragma engineers embedded in your CI pipeline.
  3. 03
    Continuous ConMon
    Monthly, net-30.
    $20K/month
    Retainer
    Drift suite runs in your CI on every PR. Monthly deviation report with scored findings. The SSP stays current; your authorization does not rot.

Section 03 · Specshift Suites

Full documentation →

The meter.

Your docs have a retrieval score. You just don't know it yet.
01retrieval

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

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?

Section 04

Tools.

01

Specshift OSS

The eval engine. MIT-licensed. Run it from the CLI on any docs URL and get a scored report. No login required.

Open
02

Specshift Cloud

Hosted eval at scale. Source-available. SBOM, signed builds, OSCAL components. The FedRAMP-aware methodology variant runs here.

Open
03

Leaderboard

Public ranking of how well documentation explains itself to LLMs. Methodology v1.0 with limitations.md. Disputes are tamper-evident.

Open
04

Try Eval

Drop a docs URL. Get a scorecard, a public report URL, and an SVG badge for your README. CARL-attested on every PR.

Open

Section 05

Talk to an engineer.

We reply within one business day. Tell us your authorization timeline and the documentation you have today. We will tell you whether the work is a Sprint, an Acceleration, or a ConMon retainer.

Next step
  1. 05Contact Pragma
  2. 06Run Specshift first