Carbon · Documentation engine for regulated software
Submission-ready documents in days, not months.
Carbon turns eight intake answers and the documents you already have into a signed, traceable package: PRD, SRD, threat model, compliance evidence and risk register. It runs in your environment, on your LLM.
See how it works →The old way
Documentation still ships last.
In regulated software, that means the product doesn't ship either. Your ALM tool stores what someone already wrote. Nothing in your stack writes the package the reviewer actually asks for.
Manual authoring
- Wk 1–3
Kickoff. Template debates. Who owns the threat model?
- Wk 4–7
Three or four authors, each with their own vocabulary.
- Wk 8–10
The PRD and SRD disagree on three numbers. Reconciliation begins.
- Wk 11–12
Compliance asks for evidence that doesn't exist yet.
- Wk 13+
The reviewer sends it back. You restart from week eight.
With Carbon
5 business days
- Day 1
Eight intake answers from your product owner, compliance lead and security architect.
- Day 2
Your PDFs, notes and existing requirements become a constraint log.
- Day 3
Eight agents author every artifact in parallel.
- Day 4
Every requirement is scored against EARS patterns and INCOSE rules.
- Day 5
A signed, hash-chained bundle, approved at the final gate.
Why it holds up in review
Written by agents. Checked by rules. Signed by people.
/01
Deterministic scoring
RQS grades every requirement with EARS pattern detection and INCOSE rule checks. No model grades its own work.
/02
Every claim sourced
Each statement links back to an intake answer or an uploaded document. Nothing appears without a source.
/03
Five named gates
A named reviewer approves every phase, so problems surface at gate two, not week twelve.
/04
Tamper-evident
The audit log is hash-chained. One command detects any edit made after export.
Carbon
The package a reviewer can sign.
Six questions and your template go in. Five gated phases run in your environment. What comes out is a hash-chained bundle, and a log of who approved it.
In customer trials. Not general availability. No public pricing.
-
5
Phases, each briefed before it runs
-
0.90
Score target. Export stops under 0.70
-
8
Artifact types in one signed bundle
-
5 days
Reference runs, from a 13-week cycle
Six parts of the product
Open any container.
01 · Pipeline
Brief before. Gate after.
-
01 · G1
Intent
Always on
-
02 · G2
Ingest
Always on
-
03 · G3
Swarm
Always on
-
04 · G4
Audit
Always on
-
05 · G5
Export
Always on
02 · Artifacts
Your template is the container.
- BRD / PRD / SRD
- Threat model
- Evidence
- Traceability
- Risk register
- Architecture
- Wireframes
- Audit trail
Open artifacts
03 · Quality scoring
Rules, not a second opinion.
0.90
Document target. Audience changes the weights.
- Export freely ≥ 0.95
- Warn at sign-off < 0.90
- Stop unless overridden < 0.70
Open quality scoring
04 · Observability
Nothing in the run is silent.
- BRIEF · what, why, duration
- CONF · hold under 0.70
- LOG · hash-chained signatures
Open observability
05 · Governance
You sign. It does not ship itself.
-
Standard
5 gates · default
-
Thorough
5 gates · deeper review
Open governance
06 · Security model
The package stays in the building.
- Your VPC. Your model.
- Projects do not see each other.
- SOC 2, ISO 27001, BAA: not claimed.
Open security model
The bundle
Eight artifact types. One signed package.
- BRD / PRD / SRDBusiness, product and software requirements. The SRD is EARS-scored.
- Threat modelSTRIDE security architecture and threat analysis.
- EvidenceFramework-specific evidence, generated with the requirements instead of hunted down at week 12.
- TraceabilityA matrix linking stakeholder need to requirement to constraint.
- Risk registerRisks and mitigations, merged across every framework you select.
- ArchitectureSystem diagrams, emitted from the same run.
- Audit trailA hash-chained log of who approved what, when and why.
What Carbon is not
-
Not an ALM
Jira, DOORS, Jama, and Polarion stay. Carbon writes the package they store.
-
Not a GRC tool
It does not prove controls operate. It produces the specification and the trace.
-
Not a chatbot
Documents are the deliverable. No application code. No unattended submission.