The Precedent handbook
Compliance
What a Precedent workspace records that an auditor can use as evidence, mapped to SOC 2 trust services criteria and ISO/IEC 27001:2022 Annex A control families. Precedent is a decision record. It is not a risk register or a GRC platform.
Security and platform teams working to SOC 2 or ISO 27001 have to show that consequential engineering decisions were approved by the right people, that departures from a standard were time-boxed, and that the record was not rewritten afterwards. Precedent records that as part of writing decisions down. Your GRC platform keeps the control set, the risk register and the audit workflow; Precedent holds the decision trail behind them.
What Precedent evidences
| Evidence | What is recorded | Described in |
|---|---|---|
| Approval trail | Who asked for approval on a draft, when, and each Area's rule as it stood then. Each approval and request for changes, with its note and the content it applies to, and each dismissal with its reason. When the draft was decided, and whose approvals counted. | Approve decisions |
| Exception expiry | Each exception's departs-from link, compensating controls and expiry date. It shows as Expired from the next day, and the owner is reminded 30 and 7 days before and on the date. Reaffirming with a new date records the old and the new date. | Record an exception |
| Pull request check | A comment on each pull request listing the decisions that apply to the Areas it touches. The check fails on an expired exception in a checked Area, or on a superseded decision the pull request cites. | GitHub Actions |
| Revision history | A change to a decided decision saves a new revision with a change note once its Areas' approvals are in; until then it waits as a proposed change and the decision does not change. Earlier revisions and the event log stay readable, and a superseded or reversed decision keeps its original record. | Inbox and reviews |
| Signed audit export | Every decision event and assistant tool call in a date range, with the people and assistants named, signed with Ed25519 over the exact bytes. Anyone holding the file can verify it against the deployment's public key. Each export is itself logged. | Workspace settings |
| Retention and legal hold | Decided, superseded and reversed decisions are never purged. A retention policy deletes archived decisions and trims operational logs after a set window. A workspace or per-decision legal hold stops that. Each run is logged and appears in the audit export. | Workspace settings |
| Single sign-on and access | Sign-in through your OpenID Connect or SAML identity provider, with provisioning by email domain and optional enforcement. Groups grant Viewer, Member, Maintainer or Area administrator on each Area, and every list, search, assistant tool and export applies the same visibility. | Workspace settings |
SOC 2 trust services criteria
| Criteria | Relevant evidence |
|---|---|
| CC1.3 Structures, authorities and responsibilities | Every decision has an owner. Each Area's rule for approvals, the groups with access to it and the recorded approvals show who may approve and who approved. |
| CC4.1 Ongoing and separate evaluations | Review dates, overdue review items and the outcome history show that decisions are revisited and what each review concluded. The pull request check evaluates each change against recorded exceptions. |
| CC5.3 Policies and procedures | Policies are decisions with an owner, an effective date and a review date or condition. Exceptions to them name the policy, the compensating controls and the expiry date. |
| CC6.1 to CC6.3 Logical access | Single sign-on, provisioning by email domain, roles per Area, and revocable assistant connections. |
| CC7.2 Monitoring | The audit export lists every decision event and assistant tool call with the person and assistant, for review alongside your other logs. |
| CC8.1 Change management | Approvals recorded against the content they apply to, before a draft is decided and before a change to a decided decision applies; change notes on every revision of a decided decision; and the pull request check. |
| C1.2 Disposal of confidential information | The retention policy and its logged runs, and legal hold when records must be kept. |
ISO 27001 Annex A control families
| Annex A theme and controls | Relevant evidence |
|---|---|
| Organizational, 5.1 Policies for information security | Policy decisions with an owner and a review date or condition, and reminders to the owner before a review date. |
| Organizational, 5.2 and 5.3 Roles, responsibilities and segregation of duties | Owners and Maintainer groups. Where an Area's rule excludes the owner, and for every Exception, a decision needs approval from someone other than its owner and the person who asked for approval. |
| Organizational, 5.15 to 5.18 Access control, identity and access rights | Groups and roles per Area, single sign-on with optional enforcement, and revocable assistant connections. |
| Organizational, 5.33 Protection of records | Revision history, the signed audit export, and legal hold. |
| Organizational, 5.36 Compliance with policies, rules and standards | Exceptions with an expiry date and the standard they depart from, warnings to assistants about expired exceptions, and the pull request check. |
| Technological, 8.10 Information deletion | The retention policy and its logged runs. |
| Technological, 8.15 Logging | The signed audit export of decision events and assistant tool calls. |
| Technological, 8.32 Change management | Approvals before a draft is decided, change notes, and the pull request check. |
What Precedent is not
Precedent is not a risk register or a GRC platform. It does not hold your control set, score or rate risks, test controls, collect evidence from other systems, or run an audit. An exception records that a departure from a standard was approved, with its compensating controls and expiry date; the risk assessment behind it belongs in your risk register, and the exception can link to it as evidence.
Prepare evidence for an audit
- As a workspace administrator, open Settings → Data, choose the audit period under Audit export and download the signed file.
- Verify it offline against the public key at
/.well-known/precedent-audit-key.jsonon your deployment. Keep the file and its signature together. - In Settings → General, export decisions of the Exception or Rule Type as JSON, with their revisions, events, evidence and links.
- Open the decision pages your auditor asks about with them. Each shows its approvals and requests for changes, its revisions and its event log.