statements ยท statement-BATCH-2026-003-030
source-BATCH-2026-003-002
Recovery requires explicit revocation, knowledge of intended state, tested restoration paths, and mechanisms that do not depend on the component already known to be compromised.
Statement context
- Statement type
- recommendation
- Exact source locator
- Chapter 9 > Use an Explicit Revocation Mechanism; Know Your Intended State, Down to the Bytes
- Source date
- 2020-04-08
- Role at source time
- Named book author or chapter contributor
- Evidence character
- Recovery guidance
- Scope
- Compromise recovery
Indexed source: Building Secure and Reliable Systems: Best Practices for Designing, Implementing, and Maintaining Systems
Evidence lineage and transparency
| Relationship field | Linked identifiers |
|---|---|
| topic ids | topic-ai-agents, topic-ai-governance, topic-cybersecurity, topic-non-human-identity, topic-enterprise-infrastructure |
Machine review: ready for human review. Human review: approved. Workflow: published.
Complete structured record
- statement id
- statement-BATCH-2026-003-030
- source id
- source-BATCH-2026-003-002
- person id
- Unknown
- institutional author
- Aaron Joyner, Jon McCune, and Vitaliy Shipitsyn, with Constantinos Neophytou, Jessie Yang, and Kristina Bennett
- book edition id
- book-edition-BATCH-2026-002-007
- speaker role at source time
- Named book author or chapter contributor
- organization at source time
- Unknown
- statement type
- recommendation
- neutral paraphrase
- Recovery requires explicit revocation, knowledge of intended state, tested restoration paths, and mechanisms that do not depend on the component already known to be compromised.
- direct quote
- Unknown
- direct quote rights note
- No direct quotation used; original OEII paraphrase only.
- exact locator
- Chapter 9 > Use an Explicit Revocation Mechanism; Know Your Intended State, Down to the Bytes
- locator type
- chapter_section
- source date
- 2020-04-08
- topic ids
- topic-ai-agents, topic-ai-governance, topic-cybersecurity, topic-non-human-identity, topic-enterprise-infrastructure
- executive role context
- CISO, CIO, CTO, CEO, General Counsel, Board Director
- industry context
- Technology, Financial services, Healthcare, Public sector, Critical infrastructure
- geographic context
- Primarily United States and global technology operations
- evidence character
- Recovery guidance
- factual verification status
- Verified against the exact locator in the complete edition
- statement scope
- Compromise recovery
- uncertainty
- Unknown
- extraction method
- Manual semantic extraction after complete-edition reading, followed by locator replay and separate review pass
- machine extraction confidence
- 0.94
- independent agent review status
- See statement-review.csv and double-review-sample.json
- publication status
- published
- workflow status
- published
- machine review status
- ready_for_human_review
- human review status
- approved
- reviewed by
- Murray Newlands
- reviewed at
- 2026-08-16T23:17:22Z
Provenance and revision history
{
"provenance": [
{
"source_url": "https://google.github.io/building-secure-and-reliable-systems/raw/ch09.html#use_an_explicit_revocation_mechanism",
"accessed_at": "2026-08-15",
"retrieval_method": "Complete exact edition retrieved from an official public source and reviewed in full",
"exact_locator": "Chapter 9 > Use an Explicit Revocation Mechanism; Know Your Intended State, Down to the Bytes",
"content_hash": "6bf5050c08be0bced81767ac14bd9b3303e34b3efb667806b3c9e9d6b0ed8cf1",
"batch_id": "BATCH-2026-003",
"prompt_id": "OEII-BOOK-DEEP-ANALYSIS",
"prompt_version": "2.0",
"notes": "Locator replayed; paraphrase checked for attribution and scope"
}
],
"revision_history": [
{
"changed_at": "2026-08-16T23:17:22Z",
"changed_by": "Murray Newlands",
"summary": "Approved for the governed-identities pilot release under the exact scope, exclusions, rights treatment, and limitations recorded in issue #18.",
"batch_id": "BATCH-2026-003"
}
]
}