Skip to content

GNN 4.0.0 — Current-run Reliability

Choose a tag to compare

@docxology docxology released this 07 Oct 14:07
1bc3a76

GNN 4.0.0

Conceptual overview of GNN 4.0.0: Generalized Notation Notation connects generative-model specification, validation, rendering, execution and reporting with frozen selections, bounded execution, current-run evidence and FEP/GEO interchange.

GNN 4.0.0 binds model selection, source identity, artifacts and execution budgets to each pipeline invocation. It preserves the 25-step pipeline and canonical gnn.* Python namespace.

  • Collision-safe model IDs, frozen selections, current-run summaries and exclusive output ownership.
  • Strict probability/Gaussian validation, round-trippable literals and value-bound scientific evidence.
  • Shared execution deadlines, retained partial outcomes and bounded observed-process cleanup.
  • urllib3 2.8.0 security floor and lock for the chunked Deflate streaming advisory (GHSA-gh4c-6fx4-qh6g), preserving unrelated package pins during that security update.
  • Full-corpus LLM scheduling with request-bound checkpoints and explicit incomplete results.
  • Shared readiness/configuration contracts and typed distributed cancellation/results.
  • Experimental ordinary-wheel THRML categorical smoothing and cpomdp continuous control with explicit admission limits.
  • Regenerated manuscript and source-bound paired FEP/GEO interchange checks.

See the changelog and migration guide for migration details. The verification receipt identifies exact source/check/artifact epochs. Repository documentation records a prepublication snapshot; the post-publication receipt supplies the actual publication identities and date.

Scientific and security scope remains explicit: proposal-only autonomous mode; no universal backend, measured speedup, convergence or hardware-execution claim; no completed long-context LLM acceptance; no atomic confinement against hostile concurrent filesystem mutation. Issues #236/#241/#250 and separate GUI complexity alerts remain open. No PyPI upload or version-specific DOI is claimed.

Source-binding identifies the wheel/source contents; SHA256SUMS supplies artifact checksums. The post-publication receipt records final repository identities, publication date and direct download verification.