Skip to content

GNN v3.0.0 — Long-Running Orchestration

Choose a tag to compare

View all tags
@docxology docxology released this 21 Jun 01:29
· 1658 commits to main since this release
v3.0.0
6c3069e

GNN v3.0.0 — Long-Running Orchestration

GeneralizedNotationNotation v3.0.0 adds safe-by-design long-running orchestration on top of the GNN text language and 25-step processing pipeline. Every new module generates, validates, replays, or plans data only — no live infrastructure is ever mutated (no container is executed, no cluster or device is touched).

Highlights — three orchestration contracts (src/pipeline/)

  • Durable observation streams (durable_streams.py) — content-checksummed file/array StreamManifests and replayable ExecutionTraces, so an extended run can be observed, paused, and re-derived deterministically before any live sensor or device-backed stream is introduced. Cross-architecture-deterministic checksums, injective stream ids, and trace meaning re-bound to ground truth on verify.
  • Resumable run sessions (run_session.py) — RunSession manifests with atomic checkpoint/resume, status inspection, and path-escape-safe, idempotent cancellation cleanup, so an extended model-family acceptance run can be interrupted and resumed without corrupting partial state.
  • Auditable container plans (container_plan.py) — hardened plan generation (non-root, read-only rootfs, cap-drop ALL, digest-pinned images, resource limits), a static security_review (privileged / root / unpinned-image / plaintext-secret / sensitive-host-mount / host-namespace / dangerous-capability findings), rollback descriptors, and deterministic plan hashes — without ever touching a real cluster.

Additive live wiring (no change to the 25-step critical path)

  • session_acceptance.py — resumable, checkpoint-after-each model-family acceptance.
  • run_manifest.py — emit durable StreamManifests + a replayable ExecutionTrace from a completed run's output/ (verified on a real run: 105 manifests + a 25-event trace).
  • pipeline_container_plan.py — a security_review-clean container plan generated from the real input/config.yaml.
  • A strict, fail-closed acceptance gate: scripts/run_v3_orchestration_acceptance.py (--inject-defect exits non-zero).
  • Three new Model Context Protocol tools (tool total 137 to 140).

Release evidence

The standing release gates were re-run green for all 9 model families: semantic fidelity (run_semantic_fidelity_gate.py), cross-framework reliability (run_cross_framework_reliability.py, GridWorld compared across PyMDP, RxInfer, and ActiveInference.jl), and model-family acceptance (run_model_family_acceptance.py). The orchestration foundation ships without regressing the v2.0.0 reliability surface. The CI matrix is green (ruff format/check, four documentation audits, and mypy src), and the long-standing tool-version drift in the matrix was cleaned up as part of this release.

Documentation, manuscript & visualizations

  • README, AGENTS, DOCS, ARCHITECTURE, and the doc/ entry points brought current to v3.0.0; new reference page doc/pipeline/v3_orchestration.md.
  • The auto-injected manuscript gained a "Long-Running Orchestration Contracts" methods section and a new architecture figure; every quantitative value is a token resolved from the live repository.
  • Visualizations improved: a clean layered pipeline DAG and a new orchestration-architecture diagram.

Next

v4.0.0 — bounded autonomy and reviewed self-editing workflows, gated behind this orchestration work.

Full details: see CHANGELOG.md and TO-DO.md.

Assets 2
Loading