Document type
Guides
Documents, 10
Every document of this type
Each with its area and its purpose; a document that states no purpose gets a line naming its type and area. A title in a corpus area opens the document's page, which holds the record and, where the document has them, its outline, frameworks, and related documents; a title in the Library area is a library specification with no page and opens its source on GitHub. The full text of every document is read on GitHub.
- AI Adversarial Test ReferenceAIThis annex provides the adversarial test case library, red team methodology, and tooling guidance supporting the AI and Agentic Development Security Standard ยงยง21 to 23. Test cases must be maintained quarterly per ADTEST-SEC-01.
- AI Board Oversight GuideAIThis guide supports the board, or the equivalent governing body, in exercising oversight of the organization's use of artificial intelligence. It sets out what directors are accountable for, what they need to understand, what to ask management, what warning signs to watch for, and what they should expect to receive.
- AI Security Technical Implementation GuideAIThis guide contains implementation patterns, code examples, CI/CD configurations, and reference architectures supporting the AI and Agentic Development Security Standard. This is a technical reference, not a policy document. Requirements are stated in the parent standard.
Adopter documents, 7
The 7 adopter documents of this type, under docs/ and outside the corpus taxonomy; each entry is read from the leading metadata block of its file at build time. Each title opens the document's page, which holds the record and, where the document has them, its outline and related documents.
- Adopter Decision TreeAdopter documentsA structured navigator for adopting organizations: "I have these characteristics; which library documents should I read first, in what order?" It is a controlled reference artefact that complements docs/adopter-guide.md: the adopter guide gives general adoption principles; this document gives a sequenced reading order.
- Adopter GuideAdopter documentsThis guide is for organizations that want to use the GRC Documentation Library as the starting point for their own governance corpus. It is a controlled reference artefact: shorter and more prescriptive than the normative library documents, and intended to orient an adopting organization rather than to state requirements.
- Adopter PortalAdopter documentsThe adopter portal is a navigation aid for the most common adopter audiences: for each role, it lists the documents most likely to be useful to that role, drawn from the machine-readable taxonomy and grouped by document type. The full document index lives in governance/register-document-index-and-classification.md; term definitions and acronym expansions are in the governance/register-glossary.md.
- Adopting the Library Across a Group or Multi-Entity StructureAdopter documentsThe docs/adopter-guide.md and its worked example docs/worked-example-adoption.md show a single organization adopting the library. A group, holding company, or multi-entity structure has a further decision the single-entity guidance does not address: how to adopt the library across several legal entities that share governance but differ in jurisdiction, sector, and regulatory exposure. This guide adds that topology layer. It composes the corpus's existing group-scope precedents, the jurisdiction-annex layering model, and the versioning policy by cross-reference; it does not restate the single-entity adoption mechanics, for which the adopter guide governs.
- Reference-Acquisition ManifestAdopter documentsA public bibliography of the citation-source reference base the GRC Library corpus draws on: the trusted, citation-grade sources (standards, frameworks, legislation, programs) the corpus cites as ground truth. It lists bibliographic metadata only, title, version, issuer, upstream URL, and acquisition class, so a fork adopting the library can acquire the sources it needs. It carries NO source text.
- Worked Example: Adopting the Library into a Running ProgrammeAdopter documentsThis walkthrough follows one fictional organization from cloning the library through its first year of operating a governance programme, showing the file-by-file decisions an adopter makes at each stage. It is the companion to docs/worked-example.md, which walks the opposite direction (converting a draft into a library artefact): that example is for contributors, this one is for adopters. It does not restate the adopter tooling. It references docs/template-quickstart.md, docs/template-startup-roadmap.md, docs/template-implementation-roadmap.md, docs/decision-tree.md, and docs/adopter-guide.md at each step, and shows how they fit together for a single concrete adopter.
- Worked Example: Converting a Draft into a CC BY-SA 4.0 ArtefactAdopter documentsThis walkthrough shows how a draft becomes a library-canonical artefact in this library. The example traces a hypothetical short procedure from rough notes through to a committed file. It is for adopters and contributors who want to see the ingestion specification applied end to end. This example covers ingestion (getting a new artefact into the library); for the reverse direction, following one adopter from clone through a staged programme, see the companion docs/worked-example-adoption.md.
With script, All Documents, filtered to Guides, lists the 3 of this page's 10 documents that sit in a corpus area, and its text filter narrows them further.