Watchtower governance package

ZX-WTWR-01 · version 1.0.0 · normative review candidate

This package defines the production end-state for ZAYAZ Watchtower, grounded in the four supplied public briefs and inspected canonical ZAYAZ documentation. It is an architecture/schema deliverable, not a deployed monitoring service.

Start here

• content/architecture/watchtower/ZX-WTWR-01.mdx — normative manual, 60 stable requirements, lifecycle/permission tables, source conformance, threat model and ten Appendix G use cases.
• schemas/watchtower/1.0.0/ — all 14 requested object contracts, five supporting object contracts and shared definitions, using JSON Schema Draft 2020-12.
• schema-catalog.json — exact schema identities and paths.
• api/watchtower.openapi.json — proposed OpenAPI 3.1 integration fragment; no operative remediation/send routes.
• governance/requirements.json and governance/verification-matrix.csv — requirement-to-source and acceptance-test traceability.
• governance/source-register.json — source hashes, pinned repository inspection and limitations.
• governance/ADMISSION.md — concrete registry, API and deployment admission work.
• examples/watchtower/ — synthetic schema specimens and branch variants, explicitly not production records.
• validation/watchtower/ — repeatable offline contract validator and recorded results.

Validate

From this package directory, use Python 3.11 or later:

python3 -m venv .venv
.venv/bin/pip install -r validation/watchtower/requirements.txt
.venv/bin/python validation/watchtower/validate.py

Once dependencies are installed, validation resolves schemas locally without network calls. JSON Schema proves shape, not identity or authority. The semantic checks exercise selected deterministic contract rules; IAM, real grants, trusted receipt resolution, FOGE integration, Docusaurus and runtime acceptance remain separate gates documented in the admission checklist.

Key decisions

Watchers cannot write records or perform triage; a separate deterministic recorder admits their non-operative responses. Natural persons cannot be evaluative finding subjects. Tenant scope uses canonical eco_number. Sentinels use EXACT replay and Observers RECORDED verification. TCCP is derived, WOF observes work snapshots, and consequence graphs preserve unresolved branches. Remediation is prepared by separately governed services; FOGE uses PREP/FOGE-REC, and a human must separately confirm the exact operative change or supplier send.

Status is review, because authored normative contracts do not create repository registration, deployment approval or independent attestation. The package contains no MVP exception to its controls.

Validation at delivery

353 local contract checks passed. The final manual compiled with @mdx-js/mdx 3.1.1, YAML frontmatter and GFM with zero warnings. The detailed reports are included under validation/watchtower/. The package's manifest.sha256.json records exact file hashes for integrity checking.