zmeta-spec

KO | EN

gitlite — search

#javascript #python #hacktoberfest #react #ai #typescript #llm #go #golang #android #machine-learning #rust #deep-learning #linux

(★ 14)

ZMeta v1.0: A transport-agnostic, event-based metadata standard for resilient ISR, supporting degraded and denied environments, multi-sensor fusion, and operator-facing state.

zmeta-spec 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# ZMeta Specification (v1.0 Locked, current release v1.1.20)

ZMeta is a free, open, transport-agnostic semantic standard for resilient ISR.
It defines one honest event model that heterogeneous sensors, analytics,
gateways, TAK clients, and mission systems can share without silently changing
what the data means. A sensor is adapted to ZMeta once and then interoperates
with everything else ZMeta maps, which removes the need for N×N point-to-point
bridges.

![ZMeta at a glance: sensors collect, an edge adapter translates to OBSERVATION events, which become INFERENCE, FUSION, STATE, and COMMAND events, with a retask loop back to collection and SYSTEM events across every stage.](https://raw.githubusercontent.com/JTC-byte/zmeta-spec/main/docs/img/c1-zmeta-at-a-glance.svg)

### What ZMeta provides

- **Integration cost scales with the number of sources.** Ten sensors and five
  consumers require fifty point-to-point bridges, or fifteen adapters to a
  single contract. Writing an adapter against `adapters/AUTHORING.md` is a
  single-sitting task, and the repository ships worked references to copy.
- **Honesty is machine-checked.** Uncertainty, provenance, lineage, and timing
  quality travel with the data and are validated against policy. Degraded,
  stale, or externally promoted data cannot be made to look clean, so the
  consumer adjudicates truth rather than a black box.
- **Degraded links are a design case.** Three export profiles thin data for
  bandwidth without changing meaning, and a Profile L state event fits within
  a tactical packet budget. The size comparison below shows the encodings.
- **Each layer keeps its own authority.** A line of bearing is not a track,
  and a track is not sufficient basis for a command. Those distinctions are
  machine-checkable, which is what makes automated retasking auditable.
- **No lock-in to a vendor, a transport, or this project.** Apache-2.0
  licensing, a locked v1.0 kernel, and a governed change process. See
  `IP_POLICY.md`.

### The semantic pipeline

Each transition is a deliberate, evidence-bearing promotion: data moves to a
higher-authority lane only when lineage, timing, and confidence support it.

```mermaid
flowchart LR
 Obs["OBSERVATION_EVENT measured facts"]
 Inf["INFERENCE_EVENT AI / analytic claim"]
 Fus["FUSION_EVENT track identity"]
 St["STATE_EVENT operator-facing track"]
 Cmd["COMMAND_EVENT bounded mission intent"]
 Sys["SYSTEM_EVENT health, timing, link, TASK_ACK"]

### Encoding size on a tactical link

![Bar chart comparing the byte size of one Profile L STATE_EVENT encoded as JSON, CBOR, compact CBOR, and protobuf.](https://raw.githubusercontent.com/JTC-byte/zmeta-spec/main/docs/img/b3-encoding-sizes.svg)

The chart shows the same Profile L `STATE_EVENT` in four wire formats. All four
decode back to the identical canonical JSON. Encoding does not create
authority: a compact packet is valid only if the decoded event passes the same
schema, policy, and conformance checks that a JSON event does.

[`docs/zmeta_professional_overview.md`](docs/zmeta_professional_overview.md)
covers the whole stack in one document: architecture, the six event families,
adapters, gateway deployment, risk adjudication, AI provenance, and worked
operational scenarios including RF detection through automated retasking,
multi-node geolocation, and GPS-denied operation. Start there if you are
evaluating ZMeta rather than building against it.

## ZMeta In The Field

The reference stack is extracted from fielded deployments. The ingress adapters
marked "Production" in `adapters/README.md` came from:

- a hosted EO/CV integration deployment: fixed-camera detections build a full
  local `OBSERVATION -> INFERENCE -> FUSION -> STATE` chain on the edge,
  publish only validated `STATE_EVENT`s to a hosted control plane, render on
  a live operator map, and project to TAK/ATAK as honest CoT through a
  governed egress path;
- mobile RF direction-finding deployments: KrakenSDR coherent DoA, Moth
  RF-over-MAVLink, and SignalHunter PSD-sweep sensors feeding RF
  `OBSERVATION_EVENT` lines of bearing into downstream fusion.

Deployment reports are the standard's primary evidence stream, covering what
mapped cleanly and what did not. The promotion evidence bar is defined in
`spec/extension-registry.md`. Open a deployment field report issue to
contribute one.

## What ZMeta Is
- A semantic contract
- A JSON schema
- A policy-driven enforcement model
- A reference gateway and adapters

## What ZMeta Is Not
- Not a transport
- Not a C2 system
- Not a video container
- Not a replacement for MISB

ZMeta does not replace CoT, MAVLink, JREAP, MISB, or vendor sensor formats. It
gives them a shared vocabulary for what was observed, what was inferred, what
was fused, what an operator should see, and what mission intent is being
requested.

## Design Goals
- Honesty under uncertainty
- Graceful degradation
- Operator trust
- Interoperability across vendors and transports

## See It Work In Ten Minutes

Prereq: Python 3.11+ (no Docker needed for this path).

> **Windows users:** enable long-path support once before cloning, with
> `git config --global core.longpaths true`. Without it, a clone into an
> already-deep directory can fail checkout with `Filename too long`, which is
> the Windows 260-character path limit. The symptom looks like a corrupt
> clone, but the cause is the path length.

```
python -m pip install -r requirements.txt

# terminal 1: reference gateway (schema + policy enforcement)
python tools/run_gateway.py --profile H

# terminal 2: watch validated output arrive
python tools/udp_receiver.py --host 127.0.0.1 --port 5556

# terminal 3: replay a real OBSERVATION -> INFERENCE -> FUSION -> STATE chain
python tools/replay.py --file examples/zmeta-examples-1.0.jsonl --host 127.0.0.1 --port 5555
```

Then validate events of your own against the locked contract:

```
python tools/validate.py --file <your-events>.jsonl --profile H --strict
```

### Prerequisites and the fuller walkthrough

The path above needs only Python 3.11+. For the Docker gateway, encodings, and
CoT emission, install the dev extras and follow the full walkthrough:

```
python -m pip install -r requirements-dev.txt
```

Windows Docker note: Docker Desktop requires virtualization + WSL2 enabled. If
Docker is not available, run the gateway directly with Python as shown above.

See `spec/quickstart.md` for the runnable gateway + UDP replay walkthrough, and
`docs/zmeta_two_node_quickstart.md` to deploy sensor-edge-to-COP across two
nodes.

## Start Here By Role

- **Building an adapter** (your sensor or format -> ZMeta): read
  `adapters/AUTHORING.md`, then copy the worked exercise in
  `adapters/ingress/example-vendor/` and the worked chains in
  `examples/zmeta-examples-1.0.jsonl` (RF) and
  `examples/zmeta-eo-chain-examples.jsonl` (EO).
- **Integrating or deploying**: `spec/installation-guide.md` for a
  step-by-step install, `spec/quickstart.md` for the developer walkthrough,
  and the Deployment Checklist below for drift-locked production setups.
- **Evaluating the standard**: start with
  [`docs/zmeta_professional_overview.md`](docs/zmeta_professional_overview.md),
  the single document that explains the whole stack with diagrams and worked
  scenarios, then `spec/semantics-contract.md` (normative),
  `spec/profile-compatibility.md`, and `CONFORMANCE.md`.
- **Building UIs or consumers**: `spec/field-dictionary.md`; encoding
  guidance in `spec/compact-binary-mapping.md` and
  `spec/protobuf-encoding.md`.
- **Contributing, agents, and maintainers**: `AGENTS.md` and
  `docs/zmeta_change_governance.md` before changing governed artifacts;
  `CONTRIBUTING.md` for contribution terms.
- **Industry reviewers**: `IP_POLICY.md`, `CONFORMANCE.md`, `TRADEMARK.md`,
  and `docs/zmeta_defensive_publication.md` before relying on compatibility,
  contribution, or public-sharing claims.
- **Downstream clone users**: read the downstream clone limits in `AGENTS.md`
  and `docs/zmeta_change_governance.md` before altering schema, semantics,
  policy authority, or event vocabulary.

## Current Release

- Current release: `v1.1.20`
- Release notes and assets: <https://github.com/JTC-byte/zmeta-spec/releases/tag/v1.1.20>
- Release focus: the audit-closure cut. A position with no vertical is
 sayable on the v1.1.0 branch (`dimensionality: "2D"`, `quality.geo_status:
 VERTICAL_UNAVAILABLE`), and AIS and barometric-only ADS-B now emit it end
 to end through the track projector to 2-D `FUSION_EVENT`/`STATE_EVENT`
 pairs. The v1.1.0 `utcDateTime` pattern enforces structural calendar
 shape, and the gateway gains a warn-only `event.ts` plausibility window.
 The locked v1.0 contract and schema are restored byte-exact to the
 2026-05-07 lockdown-audit baseline, with a dated provenance note and hash
 anchors on both. SAPIENT boundary defects found by the first
 independent-implementation interop run are closed, including a z-less
 2-D `DetectionReport` confirmed on the wire by that harness. The release
 signer now hashes text assets on line-ending-normalized content;
 `docs/release_checksum_errata.md` records the 16 wrong checksum entries
 the old behavior produced across 15 published tags, with published files
 left as published. The ADS-B NACp ellipse moves to
 `payload.geo.error_ellipse_m` with formal member spellings. This release's
 one breaking change: `policy/producer-authority.yaml` drops the
 `state-projector-*` wildcard producer authorization, so a deployment that
 relied on it to authorize a state projector must rename or add a named
 producer stanza.
 Governed artifacts changed in this release, relative to zmeta-v1.1.19: conformance/adapter-harness/must-pass.jsonl, conformance/bad-events/must-fail.jsonl, conformance/profile-precision/must-fail.jsonl, conformance/profile-precision/must-pass.jsonl, policy/producer-authority.yaml, policy/profile-precision.yaml, schema/zmeta-event-1.1.0.schema.json, spec/compact-binary-mapping.md, spec/extension-registry.yaml, spec/semantics-contract.md.
 The locked v1.0 kernel is unchanged. The contract changes are the lock
 provenance note and the v1.1 lane's A1-02 sections; the v1.1.0 schema
 gains the declared-dimensionality form, the VERTICAL_UNAVAILABLE token
 with its coherence arms, and a structural timestamp shape, all of which
 producers opt into; the registry adopts ERROR_ELLIPSE_M and
 GEO_DIMENSIONALITY as formal v1.1.0 vocabulary.
- Normative contract: v1.0 locked semantic contract, canonical version-discriminated
 JSON schema, v1.0 JSON schema, and policy pack.
- Experimental extension: `schema/zmeta-event-1.1.0.schema.json` is provided for proposed
 compatibility testing only; v1.1.0-only fields are not part of the locked v1.0 contract.

## v1.1.20 Integration Notes

- **One breaking change.** `policy/producer-authority.yaml` drops the
  `state-projector-*` wildcard producer authorization. It let any producer
  matching the glob emit `STATE_EVENT`s with no external-promotion evidence
  and no named identity, and no reference component used it. A deployment
  that authorized a state projector under the wildcard must rename its
  producer or add a named producer stanza, the same shape
  `configs/policy-variants/producer-authority.strict.yaml` already uses.
- **The MAVLink command translator fails closed on risk-flagged commands by
  default.** A `COMMAND_EVENT` carrying gateway risk-adjudication records is
  refused rather than translated into a clean intent. The explicit
  `allow_flagged` opt-in translates it, with the records stamped into the
  MissionIntent, so a soft-flagged command can no longer become a clean one
  by default.
- **v1.1.0 gains opt-in geo fields; absent-dimensionality v1.0 events are
  unaffected.** A v1.1.0 event may declare `dimensionality: "2D"` with
  `quality.geo_status: VERTICAL_UNAVAILABLE` to say a horizontal-only
  position honestly, and may carry `payload.geo.error_ellipse_m` with the
  formal member spellings. Both stamp a conditional `zmeta_version: "1.1.0"`
  only on the events that carry them. A v1.0 event with no declared
  dimensionality validates and behaves exactly as before this release.
- **A new warn-only gateway timestamp window.** The gateway counts an
  `event.ts` more than `ts_plausibility_horizon_ms` (default 24 hours, 0
  disables) before or after wall-clock now as `EVENT_TS_IMPLAUSIBLE`, with
  direction, delta, and horizon in the warning details. It never rejects an
  event and never escalates under `strict_validation`, the same as the
  existing `warn_datagram_bytes` observability warning. The v1.1.0
  `utcDateTime` pattern separately enforces structural calendar shape (year
  1970-2999, month 01-12, and so on), which is a shape gate, not a calendar
  or plausibility check.
- **Formerly-accepted shapes now refuse.** AIS message 27's not-available
  sentinels (speed 63, course 511) are refused instead of carried as motion
  data; an AIS speed or course value outside the field's real range (a
  negative speed, a course over 360) is refused as corruption; an AIS
  `rxtime` that does not parse as fourteen calendar digits, or an epoch
  `timestamp` before 2000-01-01 or outside datetime range, refuses the
  message instead of borrowing another clock. JREAP now distinguishes a
  declared 2-D geo from the ambiguous no-token shape, which refuses instead
  of being exported as an assumed dimensionality. The v1.1.0 schema's
  coherence rules refuse a `2D` declaration paired with `alt_m` and refuse
  `geo_status: UNAVAILABLE` beside a present geo; the SAPIENT and CoT
  egress adapters refuse the same 2-D-with-`alt_m` contradiction at their
  own boundaries instead of exporting a laundered `z`.
- **Published checksums for pre-v1.1.20 tags are known wrong for text
  assets, and were not rewritten.** `docs/release_checksum_errata.md`
  records the 16 wrong entries across 15 published tags and the corrected
  values. The release signer now normalizes line endings before hashing
  text assets, so v1.1.20 onward is correct at source.
- `tools/check_compat.py` gains the `v1.1.20` target; current-facing docs
  re-baseline to the v1.1.20 release manifest.

Integration notes for earlier releases (v1.1.11 through v1.1.19, except
v1.1.17, whose section was overwritten by the v1.1.18 cut and never
archived) are in
[`CHANGELOG.md`](CHANGELOG.md), alongside the full change history for
each version. The v1.1.19 section is archived verbatim under CHANGELOG's
[1.1.19] entry.

## Repository Structure
- `spec/` Core specification and normative text.
- `schema/` JSON schema definitions for ZMeta artifacts.
- `examples/` Sample payloads and usage patterns.
- `conformance/` Must-pass/must-fail regression corpus.
- `policy/` Policy language and enforcement guidance.
- `export/` Derived, non-authoritative projections of governed artifacts.
  Currently `export/policy/*.json`, a verbatim JSON rendering of
  `policy/*.yaml` for consumers that cannot read YAML. Generated and
  hash-pinned; never edited by hand. See `export/README.md`.
- `gateway/` Reference gateway implementation and tests.
- `adapters/` Ingress and egress adapter patterns and templates.
- `tools/` Utilities for validation and development workflows.
- `docs/` Advisory guidance plus maintainer process records. See
  `docs/README.md` for which is which.
- `AGENTS.md`, `docs/zmeta_change_governance.md` Human and AI agent change
  governance, process limits, documentation requirements, and release workflow.

## Adapters

Reference adapters show how to translate between ZMeta and external systems.
See `adapters/README.md` for ingress templates, mapping packs, and egress
projections, and `adapters/AUTHORING.md` for the step-by-step authoring guide.

Adapter semantic mapping:
- Native sensor measurements map to `OBSERVATION_EVENT`.
- Classifier or detector output maps to `INFERENCE_EVENT`.
- Track association and identity creation map to `FUSION_EVENT`.
- Operator display projection maps to `STATE_EVENT`.
- Mission tasking maps to `COMMAND_EVENT` only through deconfliction.
- Health, timing, link, validation, and task acknowledgement reports map to `SYSTEM_EVENT`.

ZMeta is strict about semantic invariants and flexible through ignorable,
namespaced, non-semantic extensions. Extensions must not redefine core event
meaning, authority boundaries, units, lineage, profile behavior, or command
safety.

## Schemas and Examples

Use `schema/zmeta-event.schema.json` as the canonical validation entry point.
It dispatches by `zmeta_version` and prevents v1.1.0 vocabulary from validating
under a v1.0 event. Version-specific wrappers are retained for integrations that
need a fixed target:
- `schema/zmeta-event-1.0.schema.json`
- `schema/zmeta-event-1.1.0.schema.json`

Runnable examples live in `examples/`:
- `zmeta-examples-1.0.jsonl`: RF observation, inference, fusion, and state projection.
- `zmeta-eo-chain-examples.jsonl`: worked EO full chain with genuine chained lineage.
- `zmeta-profile-L-examples.jsonl`: Profile L state/system/command examples.
- `zmeta-command-examples.jsonl`: GOTO and TASK_ACK lifecycle.
- `zmeta-v1.1-examples.jsonl`: SENSOR_STATUS, PLATFORM_STATUS, data_ref/data_refs,
  error_ellipse_m, and v1.1.0 tasking examples.

Intentionally invalid examples live in `conformance/must-fail.jsonl`; valid
regression fixtures live in `conformance/must-pass.jsonl`.

## Tools

Quick helpers for local validation and UDP replay:

```
python tools/run_gateway.py --profile H
python tools/udp_receiver.py
python tools/udp_sender.py --file examples/zmeta-command-examples.jsonl
python tools/replay.py --file examples/zmeta-command-examples.jsonl --delay-ms 200
python tools/check_compat.py legacy-events.jsonl --target v1.1.20
python tools/validate.py --file examples/zmeta-command-examples.jsonl --profile L
python tools/check_adapter.py --events my-adapter-output.jsonl --fixtures my-fixtures.jsonl
python tools/validate_conformance.py --strict
python tools/validate_release_manifest.py --manifest release/zmeta-release-manifest.yaml
python tools/validate_release_package.py --manifest release/zmeta-release-manifest.yaml --templates-only
python tools/compute_contract_hash.py
python tools/export_policy_json.py --check
python tools/test_gateway_live.py
python tools/test_workflow_end_to_end.py
```

End-to-end workflow variants:
```
python tools/test_workflow_end_to_end.py --profile M
python tools/test_workflow_end_to_end.py --profile L
python tools/test_workflow_end_to_end.py --profile M --expect COMMAND_EVENT,SYSTEM_EVENT
```

`tools/test_gateway_live.py` exercises live UDP forwarding, COMMAND dedupe, and CoT emission.

Makefile targets run the same commands with `python` directly; ensure dependencies are installed
(`python -m pip install -r gateway/requirements.txt -r requirements-dev.txt`).

## Versioning
- v1.0.x = clarifications and fixes
- v1.1+ = proposed backward-compatible extensions until explicitly locked
- v2.0 = breaking changes

See `spec/versioning.md` for the full policy.

## Installation and Packaging

See `spec/installation-guide.md` for a deterministic install guide, gateway wizard,
and mapping pack installs for drone and sensor configs.

Timing quality metadata (`time_source`, `sync_state`, `est_error_ms`,
`last_sync_ts`) is required by the semantic contract for operational events.
Gateway `event.t_receive` / `event.t_publish` stamps are separate latency and
AAR fields added by the reference gateway when configured.
Adapter fallback timing (`UNKNOWN` / `UNSYNCED`) is intentionally degraded and
should be replaced by source-provided GPS/NTP/PTP timing or periodic
`TIME_STATUS` as soon as a deployment can expose it.

Deployment helpers:
- Config templates: `configs/edge-config.json`, `configs/gateway-config.json`
- Docker Compose: `deploy/edge/docker-compose.yml`, `deploy/gateway/docker-compose.yml`
- Bundle builders:
    - `python release/build_mvp_packages.py --version v1.1.20` produces `zmeta-edge-v1.1.20.zip` and `zmeta-gateway-v1.1.20.zip`
    - `python release/build_release_bundle.py --version 1.1.20` produces `zmeta-v1.1.20-dist.zip`
    - `python tools/build_release_package.py --manifest release/zmeta-release-manifest.yaml --output-dir release/package-v1.1.20 --release-id zmeta-v1.1.20 --release-state formal_release --no-signatures --release-notes release/RELEASE_NOTES_v1.1.20.md` builds formal package metadata without creating signatures. `--release-notes` is mandatory for `formal_release`: omit it and the unpopulated notes template is copied verbatim, which `tools/validate_release_package.py` refuses with `RELEASE_PACKAGE_NOTES_PLACEHOLDER`.
    - `python release/sign_release_artifacts.py --version v1.1.20 --write-checksums --sign --target all` signs release assets with detached PGP signatures when an approved signing key is available.

## Deployment Checklist (Compact)

Use this to lock down schema, policy, and semantic-contract drift and verify a clean deployment:

1. Compute schema, policy, semantic-contract, and combined contract hashes: `python tools/compute_contract_hash.py`
1. Set `require_contract_hash` (and optionally `require_schema_hash`/`require_policy_hash`) in config.
1. If adopting a policy variant into the active `policy/` directory, recompute and update the deployment hash gates.
1. Validate the governed release baseline: `python tools/validate_release_manifest.py --manifest release/zmeta-release-manifest.yaml`
1. Validate formal release package templates or generated package output before distribution.
1. Run self-test: `python tools/run_gateway.py --profile H --self-test`
1. Run conformance: `python tools/validate_conformance.py --strict --profile-projection --extension-registry --conformance-classes --encoding-negative --precision-policy --release-manifest --release-package --bad-events --adapter-harness`
1. Verify consumer risk posture where needed: `python tools/filter_risk.py --input gateway-output.jsonl --preset command --fail-on-drop`
1. Start gateway with strict mode (optional): `python tools/run_gateway.py --config configs/gateway-config.json --strict-validation`
1. Verify metrics and drops in logs (enable `metrics_log_path` if needed).

Before publishing changes to the repository itself, follow
`docs/zmeta_change_governance.md`; release publication additionally requires
`RELEASE_CHECKLIST.md`.

## Normative vs Reference

Normative (contract): `spec/semantics-contract.md`, `schema/zmeta-event.schema.json`, `schema/zmeta-event-1.0.schema.json`, `policy/*.yaml`, `spec/versioning.md`
Reference: `gateway/*`, `tools/*`, `adapters/*`, `examples/*`

Normative files define compliance. Reference components exist to accelerate adoption.

## Industry Sharing And IP Posture

ZMeta is published under Apache License 2.0 as an open specification and
reference stack. For broad industry conversations, cite the public repository,
a tagged release, release notes, release manifest hashes, conformance evidence,
and `docs/zmeta_defensive_publication.md`. Avoid privately disclosing
unpublished roadmap concepts, future vocabulary, or deployment-specific
mappings before they are public or covered by an appropriate agreement.

`IP_POLICY.md`, `CONTRIBUTING.md`, `CONFORMANCE.md`, and `TRADEMARK.md` define
the project's advisory posture for contributor authority, private dialects,
conformance claims, and use of the ZMeta name. These documents are project
governance, not legal advice or a formal standards-body patent policy.

zmeta-spec

zmeta-spec 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

zmeta-spec

zmeta-spec 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README