SOC2 WS-8 evidence
Change Control Evidence
Last updated: 2026-07-27 UTC. Applies to the AI Control Plane repository.
ACP production changes are protected by GitHub branch protection, required CI checks, signed commits, linear history, semver-tagged CD, governed release approvals, and post-deploy verification. We state our operating model plainly: IntelXview is currently a single-maintainer engineering organisation, so the primary safeguards at this stage are the automated controls, governed releases and the evidence trail — mandatory peer review is not claimed and will be introduced as the engineering team grows. This page is a buyer-safe evidence summary, not a SOC2 report.
Live Enforcement
| Control | Status | Evidence |
|---|---|---|
| Peer review | Roadmapped | IntelXview is currently a single-maintainer engineering organisation; mandatory peer review is deliberately not claimed and will be introduced as the team grows |
| Automated cross-review | Operating | every code change is assessed before merge, with findings recorded in the pull request; where a single-maintainer admin override is used, the absence of an independent GitHub approval is explicitly disclosed |
| Evidence publication approval | Enabled | public evidence updates require a named human approval bound to the reviewed commit (docs-evidence-gates required check) |
| Required status checks | Enabled | openapi-validate, opa-tests, pdp-regression, backend, frontend, pytest, ws1-e2e-proof, docs-evidence-gates |
| Signed commits | Enabled | required_signatures=true |
| Linear history | Enabled | required_linear_history=true |
| Admin enforcement | Enabled, with disclosed override | enforce_admins=true; administrator override is used to complete merges because a sole maintainer cannot supply the required approving review — see Boundary |
| Force pushes and deletions | Blocked | allow_force_pushes=false, allow_deletions=false |
| Merge strategy | Squash only | merge commits and rebase merges disabled |
Required Checks
openapi-validate- OpenAPI schema validationopa-tests- OPA policy testspdp-regression- PDP regression packbackend- backend compile and local regression packfrontend- frontend buildpytest- backend test suitews1-e2e-proof- end-to-end proof smokedocs-evidence-gates- evidence publication gates (freshness, paths, secrets, links, named approval)
Source Artifacts
.github/CODEOWNERSCONTRIBUTING.mdSECURITY_CHANGELOG.mddocs/compliance/change-control-enforcement.mddocs/compliance/soc2-gap-assessment.md
Boundary
This page records operational enforcement for change control. It does not claim a completed SOC2 examination or external audit opinion.
Disclosure — single-maintainer admin override. IntelXview is a single-maintainer engineering organisation. Branch protection requires one approving review, and a sole maintainer cannot approve their own pull request, so merges are completed with an administrator override. The practical consequence, stated plainly: merged pull requests carry no independent GitHub approval object, and a reader checking the GitHub API will find none. Assessment of each code change does happen before merge — by a separate automated reviewer, with findings and any declined findings written into the pull request body — but that record is prose in the PR, not a machine-checkable approval. Treat it accordingly. This resolves when the team grows beyond one maintainer, alongside the peer-review row above.