Shared Responsibility Matrix
One table, every responsibility the platform touches, exactly one owner per cell. GCH = GovConHouse. You = the customer’s organization (and its signing officials).
Rows about CMMC, SPRS, and the SSP, POA&M, SAP and SAR documents describe the compliance modules, which are switched off for pilot accounts. Rows about drafting and citations apply when AI drafting is on, which it is not in production today. Who owns each task does not change.
| Responsibility | GCH | You | Government | Assessor |
|---|---|---|---|---|
| Hold certifications for the platform itself | No (holds none) | No | n/a | n/a |
| Hold YOUR certifications (CMMC and others) | No | Yes | n/a | n/a |
| Compute CMMC control status from your evidence | Yes | No | n/a | n/a |
| Verify that your evidence is true | No | Yes | n/a | Yes |
| Keep your compliance data separate from other customers’ | Yes | No | n/a | n/a |
| Compute your SPRS score (DoD methodology) | Yes | No | n/a | n/a |
| Affirm and submit your SPRS score | No | Yes | Receives | n/a |
| Draft SSP/POA&M/SAP/SAR package documents | Yes | No | n/a | n/a |
| Complete and validate the SSP narrative | No | Yes | n/a | May review |
| Grant an Authority to Operate | No | No | Yes | n/a |
| Perform the security assessment | No | No | n/a | Yes |
| Decide what is CUI and its categories | Assists | Yes | Defines | n/a |
| Encrypt CUI fields and uploaded evidence at rest | No. Off in the pilot and not offered as a control today (see below) | Yes. You own CUI handling. Do not upload CUI to the pilot | n/a | n/a |
| Encrypt connections (in transit) | Yes | No | n/a | n/a |
| Decide what to upload (including any CUI) | No | Yes | n/a | n/a |
| Keep FAR/DFARS clause citations real in generated text | Yes (checked against the clause catalog) | No | n/a | n/a |
| Review generated proposals before they go anywhere | No | Yes | n/a | n/a |
| Flag risky passages in solicitation text | Yes | No | n/a | n/a |
| Report security incidents to the government | No | Yes | Receives | n/a |
| Sign flow-down clauses to your subcontractors | No | Yes | n/a | n/a |
| Make ITAR/export-control determinations | No (screens only) | Yes | Regulates | n/a |
| Back up the platform’s own infrastructure | Yes (hosted); operator (self-host) | No | n/a | n/a |
| Keep the immutable audit trail | Yes | No | n/a | n/a |
Encryption at rest, exactly
Section titled “Encryption at rest, exactly”The pilot must not hold CUI. Field encryption is off and is not offered as a control today. Do not count on encryption at rest for anything you upload. You own CUI handling.
The code can encrypt two kinds of data when an operator sets a key:
- Uploaded evidence files, with Fernet, when
FERNET_KEYis set. Files written before a key existed stay readable (they are plaintext, and the platform does not pretend otherwise). - CUI-marked contract fields, at the application layer, when
CUI_ENCRYPTION_KEYis set (64-char hex). On the hosted pilot that key is not set, so these fields would be stored as plaintext. The platform logs that state.
A key being supported in code is not a promise that your data is encrypted. Where a key is not set, the platform stores plaintext and says so. It never claims encryption it did not perform.
The two sentences that matter
Section titled “The two sentences that matter”- GovConHouse prepares, computes, logs, and labels. It never signs, submits, or certifies anything on your behalf.
- You review, sign, and submit. The government, or its recognized assessor, evaluates.
Full version with notes and mechanism references for every row lives in
the repository at docs/audits/SHARED_RESPONSIBILITY_MATRIX_2026-09-29.md.