Sample Trust Report

Potential knowledge issues, with the evidence to investigate them.

This sample uses fictional documents and findings.

Documents in the sample: 2322 cited by findings · Confluence, Google Drive, GitHub, Markdown
Sample analysis date: Sep 18, 2026Fixed date in the sample data
Findings: 8 potential issuesacross 12 checked claims
By issue type: 3 conflicting guidance2 possibly outdated3 unclear authority4 no issue found

Most important finding: Who approves a production release? The runbook requires VP approval for every deployment, while the release policy specifies Director approval for standard releases.

Findings identify potential issues. Document owners confirm which guidance applies.

Findings

Conflicting guidanceNeeds owner review4 cited sources

Who approves a production release?

The runbook requires VP approval for every deployment, while the release policy specifies Director approval for standard releases.

Primary evidence

Source · Engineering Runbook v3

Platform: Google Drive
Owner: Developer Productivity; Updated Jan 14, 2025
Authority: Medium (recorded)

“All production deployments require VP approval.”

Verbatim excerpt. The sample holds no surrounding document text.

Source · Release Policy 2026

Platform: Confluence
Owner: Platform Engineering; Updated Sep 2, 2026
Authority: High (recorded)

“Standard releases require Director-level approval.”

Verbatim excerpt. The sample holds no surrounding document text.

Supporting evidence

Platform Operations Guide
Platform
Confluence
Owner
Production Operations
Updated Aug 21, 2026
Authority
High (recorded)
“VP approval is required for Tier-1 or high-risk production changes.”
Strata note: The Operations Guide helps explain the distinction between standard and high-risk changes.
docs/deploy/checklist.md
Platform
GitHub
Owner
Platform Engineering
Updated Jul 30, 2026
Authority
Medium (recorded)
“Get Director sign-off in the release ticket before promoting to prod.”
Strata note: The checklist provides supporting operational guidance about approval.

How the guidance changed

Jan 14, 2025Engineering Runbook v3 publishedStates that all production deployments require VP approval.Source: Engineering Runbook v3 · Documented in the sample
May 3, 2026Platform Operations policy changedKey changeDirector approval allowed for standard releases. The change was agreed in the platform leadership review and recorded in the operations guide; the runbook was not updated.Source: Platform Operations Guide · Documented in the sample
Aug 21, 2026Platform Operations Guide updatedVP approval limited to Tier-1 and high-risk changes. The guide now defines the risk tiers explicitly.Source: Platform Operations Guide · Documented in the sample
Sep 2, 2026Release Policy 2026 publishedPublished by Platform Engineering. Its text consolidates the operations guide and the deployment checklist. Whether it governs standard releases is not confirmed in the sample.Source: Release Policy 2026 · Documented in the sample

The guidance evolved over 2026 while the runbook's blanket requirement stayed in circulation unchanged.

Interpretation and uncertainty

What the evidence suggests

The newer guidance distinguishes standard releases from high-risk changes. The older runbook applies one requirement to all deployments. This suggests the runbook may need updating, subject to confirmation by the policy owner.

What still needs confirmation

Directly observable: the two excerpts state different approvers for overlapping situations.
Possible explanation: the approval rule was split by risk tier after the runbook was written, and the runbook was not revised.
Unresolved: which document governs standard releases, and whether the runbook's blanket rule was ever formally withdrawn.

Source comparison

Source	Relevant scope	Recorded authority	Contribution	Remaining uncertainty
Engineering Runbook v3	All production deployments	Medium (recorded)	States the blanket VP requirement.	Whether it has been superseded.
Release Policy 2026	Standard releases	High (recorded)	States Director approval for standard releases.	Whether it governs, and how 'standard' is defined.
Platform Operations Guide	Tier-1 and high-risk changes	High (recorded)	Describes the high-risk exception.	How tiers are assigned in practice.
docs/deploy/checklist.md	Release ticket procedure	Medium (recorded)	Operational step that assumes Director sign-off.	Whether it reflects the governing policy.

Engineering Runbook v3
Scope
All production deployments
Authority
Medium (recorded)
Contribution
States the blanket VP requirement.
Uncertainty
Whether it has been superseded.
Release Policy 2026
Scope
Standard releases
Authority
High (recorded)
Contribution
States Director approval for standard releases.
Uncertainty
Whether it governs, and how 'standard' is defined.
Platform Operations Guide
Scope
Tier-1 and high-risk changes
Authority
High (recorded)
Contribution
Describes the high-risk exception.
Uncertainty
How tiers are assigned in practice.
docs/deploy/checklist.md
Scope
Release ticket procedure
Authority
Medium (recorded)
Contribution
Operational step that assumes Director sign-off.
Uncertainty
Whether it reflects the governing policy.

Recorded authority is metadata from the sample and does not mean a source governs. Recency is not treated as authority.

Why this could affect an AI answer

Illustrative examples written for this sample. Strata did not observe these answers and does not rewrite answers or change retrieval.

Illustrative answer risk · illustrative

“An assistant relying on the older runbook could tell users that every production release requires VP approval.”

Evidence-aware example answer · illustrative

“Standard releases appear to require Director-level approval under Release Policy 2026, with VP approval reserved for Tier-1 or high-risk changes. Engineering Runbook v3 still states a blanket VP requirement, and the policy owner has not confirmed which rule governs.”

Recommended actions

Ask the policy owner to confirm the governing rule and its scope.Suggested team, from source ownership: Platform Engineering
Update the blanket approval wording in the runbook if it has been superseded.Suggested team, from source ownership: Developer Productivity
Link operational guidance to the confirmed governing policy.Suggested team, from source ownership: Production Operations
Review related documents for the same inconsistency.

Suggestions for the team to carry out. Nothing here has been done, and Strata does not perform these steps.

About this sample

Acme Robotics and every document, owner, date, and finding here are fictional. The report demonstrates the format, not a customer result.
Excerpts are verbatim from the sample records. Strata notes, interpretations, and suggested actions are editorial and are labeled as such.
Recorded authority, owner, and date are metadata from the sample. They do not decide which guidance applies; document owners do.
Pilot scans include human review.

Ready to check your knowledge?

Join the waitlist or explore a hands-on pilot with your documents.

Request early access

No documents or repository access needed to get started.