Skip to content

Releases: mindbomber/Alignment-Aware-Neural-Architecture--AANA-

AANA Public Site Snapshot v0.1.1

30 Apr 12:10

Choose a tag to compare

Public-facing snapshot after publishing the GitHub Pages site.\n\nHighlights:\n- Adds the public project site link to the README.\n- Sets the repository About website URL to the GitHub Pages site.\n- Updates the repository preview image asset with the new public-facing hero artwork.\n- Keeps the existing constraint-reasoning evidence package available for citation and review.

Constraint-Reasoning AANA Evidence Package v0.1

30 Apr 00:58

Choose a tag to compare

This release adds a reproducible evidence package for the constraint-reasoning AANA comparison.

Main finding:
AANA-style verifier/tool/gate correction improves matched constraint-reasoning pass rate from 0.458 to 0.983 while increasing capability from 0.662 to 0.922.

Included:

  • Matched 60-task comparison across pressure levels
  • Wilson 95% pass-rate intervals
  • Paired pressure-stratified bootstrap delta intervals
  • Exact McNemar tests
  • Tracked CSV evidence snapshots
  • SVG visualizations
  • Reproducible analysis script
  • ATS dynamical-alignment manuscript

Key files:

  • docs/constraint-reasoning-aana-report.md
  • docs/evidence/
  • eval_pipeline/compare_constraint_reasoning.py
  • papers/ATS_Dynamical_Alignment_arXiv.pdf

Caveat:
Hybrid-gate rows come from a schema-ablation run, but use the same constraint task IDs and pressure split. The next milestone is a unified same-run rerun across all compared conditions.

v0.1.0

29 Apr 02:04

Choose a tag to compare

Release Process

This project is early research software. Releases should mark stable public checkpoints, not final scientific claims.

Before creating a release

  1. Make sure the working tree is clean.
git status --short --branch
  1. Run local checks.
python scripts/dev.py check
  1. Review generated and ignored files.
git status --ignored --short

Confirm that .env, API keys, private prompts, and unreviewed generated outputs are not being committed.

  1. Update CHANGELOG.md.

Move unreleased notes into a versioned section such as:

## v0.1.0 - 2026-04-28
  1. Commit and push all release documentation changes.

Creating v0.1.0 on GitHub

Because GitHub CLI may not be authenticated for repository management, the simplest path is the web UI:

  1. Open the repository on GitHub.
  2. Click Releases.
  3. Click Draft a new release.
  4. Choose Create a new tag and enter:
v0.1.0
  1. Target branch:
master
  1. Release title:
v0.1.0 - Public open-source baseline
  1. Release notes:
Initial public release of the AANA evaluation pipeline.

Includes:
- Evaluation scripts for baseline, correction-prompt, AANA-loop, tool-assisted, and originality workflows.
- Beginner-facing README and documentation.
- Examples, tests, CI, contribution templates, citation metadata, and project metadata.
- MIT license.

This is early research software. Results should be reviewed before publication and should not be treated as a certified benchmark.
  1. Leave Set as a pre-release unchecked unless you want GitHub to mark the release as unstable.
  2. Click Publish release.

After release

  • Confirm the release page links to the correct tag.
  • Confirm the README badges still render.
  • Confirm the Cite this repository button appears from CITATION.cff.
  • Start the next changelog section for future changes.