Pragma · Documentation Engineering
Documentation engineering, applied to
Diligence.
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.
- 01SSP SprintLump sum, 50/50 split.~$100K6–8 weeksOSCAL-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.
- 02ATO Acceleration40/30/30, net-30/60/90.$300–500KMilestone-basedFull authorization push. Covers all documentation engineering from initial OSCAL build through 3PAO assessment, with Pragma engineers embedded in your CI pipeline.
- 03Continuous ConMonMonthly, net-30.$20K/monthRetainerDrift 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.
Can a vector index over these docs answer realistic developer questions?
Can a tool-use agent complete a representative task using only these docs?
Are the docs organised so a model can navigate without context overflow?
Do the docs describe the platform's actual current behaviour?
Section 04
Tools.
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.