Retro-documentation & regional compliance.

Retro-documentation: transmission pointed backward

runward can now reconstruct the handover kit of a system that skipped the transmission phase — phase 6, pointed backward, as an elicitation-and-validation pipeline: the tool proposes, the operator validates.

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

Regional compliance: the mapping is universal, the regulation is a lens

The OWASP ASI mapping is the universal core; the named regulation becomes a swappable regional lens, security-only by default. The manifest is the same artifact everywhere — only the cited regulation changes.

New framing references (not gate logic) under docs/compliance/: ISO/IEC 42001 (the global anchor), NIST AI RMF (US), EU AI Act (EU). Lead with the universal security posture, then map to the buyer's regime. The gate itself stays regulation-agnostic.

Every piece decided before the code, locked in an ADR (0013 through 0015), proven by the test suite. runward's own method applied to runward.

---

Install: npx runward init

Release v0.10.0 on GitHub · CHANGELOG

← All news