MeshGuard Editorial and Evidence Policy
Reviewed: July 28, 2026

MeshGuard distinguishes product facts, reference results, customer results,
external facts, scenarios, proposals, technical guides, and opinion.

AUTHORS

- DB Hurley: category theses, founder perspective, and technical strategy.
- Nick Brachet: engineering notes, implementation analysis, and benchmarks.
- Jim Crowley: non-technical essays, operator guidance, and business explainers.

MeshGuard Editorial and automated bylines are not used for public articles.

EVIDENCE RULES

- Product facts name a released version or commit and the relevant configuration.
- Reference results disclose the runner, workload, denominator, failures,
  environment, raw or sanitized results, and limitations.
- Customer results require an approved attribution or anonymization,
  measurement method, time window, denominator, and publication consent.
- External claims link to a primary source and include absolute dates.
- Hypothetical examples are labeled Scenario or Illustrative scenario.
- Proposals and targets are never presented as achieved results.
- Opinion has a named author and enough reasoning for readers to evaluate it.

MeshGuard does not publish unnamed enterprise anecdotes, precise loss figures,
adoption percentages, or incident counts without reviewable evidence.
Composite examples must be labeled and must not imply a real customer.

SECURITY AND COMPLIANCE BOUNDARY

MeshGuard can govern only requests routed through configured enforcement
points. Policy packs and audit records can support a compliance program; they
do not by themselves make a deployment compliant. Terms such as immutable,
tamper-evident, prevents, and guarantees require evidence for the exact
property claimed.

PUBLICATION CONTROL

Blog publication is fail-closed. A source entry must name an approved author,
declare an evidence class, record a review date, and carry status "published."
All other entries are withheld from blog routes, feeds, related posts, the
sitemap, and llms.txt.

Public claim register:
https://meshguard.app/api/blog/audit.json