Skip to main content

epochly-relay-schemas

Canonical control-plane schemas for the Relay agent reliability OS.

This package owns the canonical schema source-of-truth and the W1.5 codegen pipeline.

Source-of-truth file (W1.5)

raw/openapi.yaml is a single OpenAPI 3.1 document carrying every persisted control-plane envelope under components.schemas. The W1.5 codegen pipeline consumes this file via:

  • datamodel-code-generator -> packages/sdk-python/relay/_generated/ (Pydantic v2 BaseModel subclasses with extra='forbid')
  • openapi-typescript -> packages/sdk-typescript/src/_generated/ (TypeScript type aliases + named re-exports)

Regenerate via:

uv run python packages/schemas/scripts/codegen.py

Drift check (VAL-W1-035):

uv run python scripts/check-codegen-drift.py

Two-layer architecture

The W1.5 generated layer carries the BASE canonical models (one Pydantic class per envelope; one TS type alias per envelope) with the extra='forbid' discipline. The hand-authored W1.1-W1.4 modules under packages/schemas/python/relay_schemas/envelopes.py and packages/schemas/typescript/src/envelopes.ts add the RICH validation layer:

  • Cross-field invariants (accepted_requires_evidence, raw_capture_requires_dpa_and_approver, dry_run_never_resolves).
  • RFC 3339 timezone-offset enforcement (VAL-W1-017, VAL-W1-024).
  • StrictBool rejection of string coercion (VAL-W1-023, VAL-W1-026).
  • Canonical-byte serializers for cross-language round-trip evidence.
  • The discriminated-union ScopeState metaclass adapter.

The generated layer and the hand-authored layer are independent: the generated classes are NOT subclassed by the hand-authored classes. Future W1.6 + cross-language fixtures consume both layers and verify them against the same JSON canonical form.

Two-layer convention (LOCKED post-W1.6, orchestrator decision 2026-05-13)

The two-layer architecture is the chosen convention for v0.1 and is not provisional. The hand-authored rich-validation layer addresses validation shapes that OpenAPI 3.1 cannot express directly (cross-field validators, StrictBool semantics, canonical-byte serializers). Folding rich validation into OpenAPI vendor extensions is OUT OF SCOPE for v0.1.

To prevent silent drift between raw/envelopes.yaml (rich-layer source) and raw/openapi.yaml (generated-layer source), the CI cross-YAML alignment check at packages/schemas/python/tests/test_yaml_alignment.py enforces:

  • Both YAMLs enumerate exactly the same envelope names.
  • Each shared envelope's schema_version Literal is identical across the two sources.
  • Each shared envelope's closed enums (status, action, draft_kind, etc.) carry identical member sets across the two sources.

The alignment check runs under the tier-1 plumbing marker (-m plumbing) on every commit. A failure means a drift has been introduced and one of the two YAMLs needs amendment to restore parity.

When a new canonical envelope is introduced (W2+ milestones), it lands in BOTH YAMLs in the same commit, with the alignment check verifying parity before merge.

Layout

  • raw/openapi.yaml - canonical OpenAPI 3.1 source-of-truth (W1.5).
  • raw/envelopes.yaml - W1.1-W1.4 custom-format YAML; lock-in documentation companion only (not a codegen source).
  • raw/relay-error-codes.yaml - canonical RELAY-* error code registry.
  • raw/owner-email-deny.yaml - canonical group-email deny prefixes (W1.4).
  • python/relay_schemas/ - W1.1-W1.4 hand-authored rich-validation envelopes.
  • typescript/src/ - W1.1-W1.4 hand-authored TS runtime guards.
  • sql/ - W1.1-W1.4 SQL DDL migrations (FK targets and CHECK constraints).
  • scripts/codegen.py - W1.5 codegen orchestrator (this file's home).
  • scripts/gen_error_codes.py - W1.4 error-codes generator (called by W1.5).
  • python/tests/ - W1 contract assertion tests (pytest, tier-1 plumbing).

Versioning

Per CLAUDE.md keystone invariant #10: every canonical envelope carries a schema_version field pinned to a string literal. Engines refuse unknown versions on write. The W1.5 codegen pipeline emits a RelayUnknownSchemaVersionError helper (Python + TS) that callers use via parse_envelope(...) / parseEnvelope(...) to surface forward-compat failures with a stable error type (VAL-W1-036).

License

Apache 2.0. See repository root LICENSE.

Metadata

Release files for epochly-relay-schemas 0.1.20

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for epochly-relay-schemas 0.1.20
File Size Uploaded
epochly_relay_schemas-0.1.20.tar.gz 159.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for epochly-relay-schemas 0.1.20
File Interpreter ABI Platform
epochly_relay_schemas-0.1.20-py3-none-any.whl Python 3 none any Details

Total release size: 199.7 kB

Release files / epochly_relay_schemas-0.1.20.tar.gz

Download URL epochly_relay_schemas-0.1.20.tar.gz
Size 159.4 kB
Tags Source
SHA-256 checksum
How to use checksums
2f537c6f05752d5b9c9fb5ffae88cfef9b023df8ee2a708379c0a2a55520b120
BLAKE2b-256 checksum
How to use checksums
070b204e0b7660fd8c2674ff6e371cd4e90763a3d671e0ba2de030469fbc5b5e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 28, 2026.

Transparency log

Release files / epochly_relay_schemas-0.1.20-py3-none-any.whl

Download URL epochly_relay_schemas-0.1.20-py3-none-any.whl
Size 40.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d33161a76474dca5fd9ba401d6da9fd855b1fcd006ba905963f0db72c479ceec
BLAKE2b-256 checksum
How to use checksums
4c991474b24aeec7ac7c677ebbbcaef906c6054f9ebb9095652a494efe620ee1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 28, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.20 This release

2 release files

0.1.18

2 release files

0.1.16

2 release files

0.1.15

2 release files

0.1.14

2 release files

0.1.13

2 release files

0.1.12

2 release files

0.1.11

2 release files

0.1.10

2 release files

0.1.9

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page