EvidenceOps / Maintenance

The website is a maintained system, not a finished brochure.

EvidenceOps watches facts, sources, dependencies, accessibility, security, search eligibility, and platform policy—then changes only what can be supported and reversed.

Ledger source implemented · public API and executors unavailable
01

Maintenance loop

OBSERVE

Source and system watch

Detect substantive source, claim, crawler, dependency, availability, and search-console changes.

INSPECT

Independent review

Build the evidence dossier, check contradictions, and use a separate model family plus deterministic gates.

RELEASE

Preview and rollback

A future execution connector may promote only approved risk classes after full tests and must retain a signed receipt plus a working reversal path.

02

Eligible for future bounded automation

  • Approved factual synchronization
  • Broken internal-link repair
  • Sitemap and feed regeneration
  • Asset optimization within budgets
  • Translation parity for approved claims
  • Allowlisted dependency patches after full regression
03

Approval always required

  • Founder, customer, outcome, pricing, or comparative claims
  • Legal, privacy, compliance, or certification language
  • Google Business Profile and review actions
  • DNS, authentication, WAF, secrets, or authorization
  • Deletion, migration, major redirect, or irreversible action
04

Current release boundary

The repository implements policy classification, tenant membership, job state, approval, expiry, audit events, and receipt storage, while the public Worker blocks the operations routes before application or database access. It does not execute website changes. A future private host and connector must pass independent security review and release gates before any automated deployment claim becomes current.

Next mission

Inspect the measurement protocol

Maintenance is accountable only when outcomes and regressions are measured separately.

Read the method