Record · logbook
News.
Releases, conformance-gate evolutions, and ecosystem alignments. Dated, sourced, on evidence.
-
Executable, inspectable, stateful, governed — and gated
The "Code as Agent Harness" survey closes on four properties: executable, inspectable, stateful, governed. runward embodies them on the delivery side — and stands alone in the box the corpus leaves empty: the deterministic human delivery gate.
-
The release is a gate too
runward's publishing chain applies the gate's principle to its own supply chain: the release is a human gesture, everything else is deterministic. OIDC with no long-lived token, SLSA provenance, an attested SBOM, actions pinned by SHA. Verifiable, not declared.
-
runward runs from your agent
An AI agent discovers, installs and operates runward with no human at the keyboard. New: runward wire recognises the tool running it or asks which one it is, a neutral init default that privileges no agent, and runward check --json, a deterministic machine verdict.
-
Install runward from where you already work
A family of distributable packagings, one line everywhere: runward check --strict. A GitHub Action (hard CI gate), a Claude Code plugin, siblings for Gemini, Codex, Copilot, Cursor, Kiro. Each honestly tiered by how hard its gate blocks. MCP = discovery, never a gate.
-
A second audit, closed in daylight
We ran our own method on ourselves again. Five fissures shipped the day before, fixed in daylight: traversal, ReDoS, OSCAL/spec drift, seal scope. The EU AI Act date corrected, and the deterministic gate wired into BMAD as a reviewer. Two releases in a day, the second repairing the first.
-
The hand-over is gated
"The hand-over is proven by a real task redone without you": the promise was written, no gate verified it. Phase six goes under the gate: redone-task proof, named succession, finalized charter. The OSCAL mapping becomes a citable spec, and Kiro joins the adapters.
-
Hollow evidence no longer passes
The gate proved a decision was traced; it now verifies the trace points at something real. Typed pointers, rule signatures, blocking drift, sealing a green. And runward now passes its own gate in CI, including with the network cut.
-
The gate can no longer lie
A multi-agent audit confirmed the chain runs green end to end and flagged gate-integrity defects: the paths by which a mission could look done when it wasn't. v0.14.0 closes them. A green gate is trustworthy ground truth again.
-
Both visions, one gated path
runward packages both visions of the doctrine: the application domain and the execution topology, where each port runs and under which sovereignty. The orphaned section 15 becomes a gated deliverable with its own conformance phase verified by the gate. Deterministic, never a runtime.
-
Evidence packs, not dead docs
runward complianceassembles your conformance work into a regime-framed evidence pack (ISO 42001, NIST, EU AI Act) and exports it as OSCAL. An upstream provenance layer, never a compliance claim. -
Retro-documentation & regional compliance
runward reconstructs the handover kit of an existing system (transmission pointed backward), and compliance becomes a regional profile, security-first. The gate stays deterministic, zero-LLM, read-only.
-
The spec is the easy part
Spec-driven development automated authoring intent. But ~95% of GenAI projects stall after — on the run, not the spec. Where runward begins.
-
Audit-ready alignment
The conformance manifest becomes audit-ready supporting evidence (OWASP ASI, 54 rules), an input to your ISO 42001 / EU AI Act technical file, and the deterministic gate wires into every harness — git, CI, Claude Code. Without ever becoming a runtime.
-
Conformance-gate hardening
The deterministic gate that verifies, rule by rule, that the delivered code carries a traced decision becomes hard to fool. Still zero-LLM, still owned by the operator.