Skip to content

runward v0.10.0 — retro-documentation & regional compliance

Choose a tag to compare

View all tags
@stranxik stranxik released this 10 Jul 07:50
v0.10.0
c0dc3ce

Two feature lines, both holding the invariants — the gate stays deterministic, zero-LLM, read-only.

Retro-documentation (ADR-0013/0014)

Reconstruct the transmission kit for an existing, undocumented system — the transmission phase pointed backward.

  • runward characterize — a read-only, deterministic inventory of a brownfield codebase (dependencies + lockfiles, entrypoints, CI, tests, git-log shape) → runward/characterization.md (facts, not decisions). Writes only into runward/, never runs or touches your code.
  • characterize --mine — deterministic git archaeology, no model call: proposes candidate structural decisions (stack, containerization, CI, notable dependency families) as DRAFT-*.md hypotheses (Status: hypothesis, why: UNKNOWN). The operating agent refines; the operator ratifies.
  • ADR hypothesis → accepted lifecycle — check --strict stays red until each reconstructed decision is ratified (real why + trigger). A hypothesis cannot pass as a decision.
  • check --coverage — advisory report of deliverable + decision-ratification ratios. New gap-analysis.md mission template.

Regional compliance (ADR-0015)

The OWASP ASI security mapping is the universal core; the named regulation is a swappable regional lens, security-only by default. New framing references under docs/compliance/ — ISO/IEC 42001 (global), NIST AI RMF (US), EU AI Act (EU). Copy de-EU-first'd. The gate stays regulation-agnostic.

Fixes

-p <absolute-path> now resolves on init/check/update/status; --mine help corrected.

Install: npx runward init · Full changelog: https://github.com/stranxik/runward/blob/main/CHANGELOG.md

Assets 2
Loading