Skip to content

Decision Forge v0.3.2

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 03 Nov 10:11
· 6 commits to main since this release
v0.3.2
d9f2bd4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Version 0.3.2 keeps published families in their splits across dataset versions and sends rule
conflicts that appear only at generated dimension values to review. Both fixes change what builds and
reviews produce: commit the new project.splits.lock.json next to each specification, regenerate
plan-recipe plans, and record conflict reviews again.

Changed

  • Consolidate duplicated pipeline, CLI, ingestion, provider, and workflow code without changing any
    dataset, export, plan, review fingerprint, or ingestion output, and cover twelve CLI failure paths.
  • Update GitHub Actions, mypy, and pre-commit hooks.
  • Tell the project's story in the README and a new Why Decision Forge page: the missing
    trust layer for AI agents, the three kinds of organizational data it requires, and where Decision Forge
    fits in the data → model → organization stack.

Fixed

  • Keep every published family in its split across dataset versions (#35). Rebuilding with build after
    adding scenario families could move existing families between train, development, and test, leaking
    held-out examples into training. The first build now records each family's split in a split lock next
    to the specification (project.splits.lock.json); later builds keep locked families in place, give
    new families a stable per-family split, and remember removed families. build --locked-splits fails
    instead of creating or changing the lock. Plans from plan-recipe made with older versions must be
    regenerated.
  • Send allow/deny rule pairs to review when they overlap only at generated dimension values (#36). Conflict
    witnesses were searched in seed states alone, so an override that appeared only in a generated
    situation was labeled without review. The gate now searches every situation the build samples and
    also queues pairs whose conditions cannot be proven disjoint, since synthesis can reach new states.
    Conflict items report overlap, witness_count, and up to five witnesses with their dimension
    values; existing conflict reviews must be recorded again. Thanks to sunxiuguo for an independent fix in #44.
  • Attest only the wheel and sdist in the release workflow; uv build also writes dist/.gitignore.
Assets 4
Loading