Skip to content

Charter: Node Manifest Specification

Purpose

Define the normative, per-node manifest contract that describes what a single platform is allowed and obliged to do for a bounded time window, on behalf of named tenants, under explicit constraints and evidence expectations.

Scope

  • A machine-readable schema for the Node Manifest (JSON Schema 2020-12).
  • A reference TypeScript binding that mirrors the schema precisely.
  • Human-readable documentation that explains intent, semantics, and versioning.
  • Examples that exercise the schema and demonstrate intended usage.
  • A strict versioning policy for the manifest schema (semver, current schemaVersion 0.2.0).
  • The v0.2.0 line includes profile and contracts identifiers to name compile-time bundles.

Non-scope

  • Autonomy, navigation, or control system implementations.
  • C2 user interfaces, mission planning tools, or tasking workflows.
  • Multi-node or fleet-level intent and coordination.
  • External policy catalogs, lens definitions, or cryptographic references.
  • Runtime scheduling, optimization, or resource allocation algorithms.

Canonical Decisions

  • JSON is the wire format for manifests.
  • JSON Schema 2020-12 is the normative specification.
  • TypeScript is the reference binding language for v0.
  • The current schemaVersion is 0.2.0 and is part of a pre-stable v0 line.