# Zen Mesh — Webhook Operations

> Zen Mesh helps teams receive, validate, observe, and operate webhooks across Stripe, GitHub, and custom sources. Current readiness is DEMO only (local/mock/sandbox and limited cloud-demo scope — not customer-ready or production-live).

Version: 1.0.0 · Last-Updated: 2026-05-29T22:00:00Z · Product scope: webhook ingestion, validation, delivery visibility, and security operations (evidence-first federated operational runtime/trust platform).

Non-claims and proof scope are authoritative — see the Non-Claims and Wedge Evidence links below before inferring production readiness.

## Core

- [AI evidence index](https://www.zen-mesh.io/evidence): Human-readable map of llms.txt, JSON manifests, and non-claims
- [Website](https://www.zen-mesh.io): Public product site and buyer-facing overview
- [Documentation](https://docs.zen-mesh.io): Human and AI-oriented docs hub
- [Source repository](https://github.com/zenmesh/zen-platform): Product, contracts, and internal evidence source of truth
- [Contact](mailto:zen@zen-mesh.io): Public contact (not a security incident channel)

## Wedge evidence (high signal)

- [Wedge claim map](https://docs.zen-mesh.io/ai/evidence/v1/wedge-claim-map.json): Scoped capability claims for the webhook wedge
- [Wedge non-claims](https://docs.zen-mesh.io/ai/evidence/v1/wedge-non-claims.json): What the wedge does not claim
- [Wedge overview](https://docs.zen-mesh.io/docs/ai/wedge-overview): Narrative wedge summary for reviewers

## Platform evidence

- [Capability manifest](https://docs.zen-mesh.io/ai/evidence/v1/manifest.json): Machine-readable capability and proof_status registry
- [Compliance map](https://docs.zen-mesh.io/ai/evidence/v1/compliance-map.json): Internal readiness mapping (not certification)
- [Non-claims registry](https://docs.zen-mesh.io/ai/evidence/v1/non-claims.json): Global non-claims for AI and reviewer use
- [AI overview](https://docs.zen-mesh.io/docs/ai/overview): How to read Zen evidence artifacts
- [Verification guide](https://docs.zen-mesh.io/docs/ai/verification): How claims are verified in-repo

## Getting started

- [Quick start](https://docs.zen-mesh.io/docs/getting-started/quick-start): Sandbox-oriented setup
- [Installation](https://docs.zen-mesh.io/docs/getting-started/installation): Install paths for evaluation

## V1 governance (2026-05-30)

- Not production-live, not customer-ready, not demo-ready as global platform readiness
- Canonical failure-stop: canonical script failure requires STOP — ad hoc runtime is not accepted evidence
- Integrity-chain authority: accepted deploy/UI/completion evidence artifacts require hash-chain inclusion; comparison is integrity-only — not authentication, not identity proof, not encryption, not replay prevention
- Planes management UI (T1): not product-pass; management-console boring-readiness not complete
- Runtime sandbox delivery validation: relay-path proof is mandatory for demo scope; see manifest proof_status for direct/egress/relay receipts — not a platform go-live claim
- Runtime workload identity (SVID) rotation: operational proof not complete on mainline
- DeliveryPolicy TLS/trust-chain controls: policy-driven delivery controls at L2 deferred — not PASS
- [Non-claims registry](https://docs.zen-mesh.io/ai/evidence/v1/non-claims.json)

## Narrative context (not proof)

- [Narrative context registry](https://www.zen-mesh.io/ai/narrative-context.json): Blog/editorial URLs classified narrative_context — not accepted_evidence or manifest proof
- [Webhook delivery evidence (blog)](https://www.zen-mesh.io/blogs/webhook-delivery-evidence/): Why verifiable delivery evidence matters — editorial; proof remains in manifest/hash-chain receipts
- [Webhooks behind firewalls (blog)](https://www.zen-mesh.io/blogs/webhooks-behind-firewalls/): Architecture narrative — not proof

## Optional

- [Public surface traceability](https://www.zen-mesh.io/ai/public-surface-traceability.json): Changelog for public terminology and AI discovery improvements (capability language only)
- [Public terminology taxonomy](https://www.zen-mesh.io/ai/public-terminology-taxonomy.json): Internal-ref → public capability map; regression gate for customer copy
- [Terminology guide (human)](https://www.zen-mesh.io/docs/public-terminology-taxonomy): How to write public copy without internal task IDs
- [Full AI context](https://www.zen-mesh.io/llms-full.txt): Expanded curated context (community convention; not part of the core llms.txt spec)
- [Docs llms.txt](https://docs.zen-mesh.io/llms.txt): Docs-site entry point for LLM crawlers