v0.2.8

The OWASP starter policy pack now maps to the OWASP Top 10 for Agentic Applications 2026 (ASI01-ASI10), with the LLM Top 10 and Threats & Mitigations lineage retained where it fits. Three new rules: agent-version pinning (ASI04), per-agent attribution (ASI07/ASI10), and a code-execution approval template (ASI05). ASI08 and ASI09 are runtime/organizational risks a record policy cannot assert; the pack's note says so.

Also in this release: the demo's email gate shows a demo-mode hint for cold visitors, and the demo agent carries a version field.

Architectural boundaries are now documented in LIMITS.md.

0.2.7 — report rendering and demo realism

Small quality release.

• Runtime Report rendering: activity-table timestamps stay on one line, and the "Captured via" provenance cards get proper spacing.
• Demo realism: halo demo now backdates its scaffolded records across a believable few days of pilot activity instead of a single instant — the demo report reads the way a real one does.

No format changes; records verify with any prior verifier.

0.2.6 — date-windowed Runtime Reports

Date-windowed Runtime Reports

halo report --from 2026-06-01 --to 2026-06-30 renders a report covering only the review window — the disclosure shape audit periods and security reviews ask for.

• Only in-window records are embedded in the page; records outside the window never enter the artifact.
• The browser re-verifies the window against its anchor — the chain head immediately before the window — so window integrity is checked client-side without the full chain.
• The full chain is verified at generation; a windowed report is refused on a chain that fails verification (same rule as halo export).
• Witness checkpoints that land inside the window are re-verified in the browser; checkpoints before and beyond it are disclosed, including that the chain continues past the window.
• The report banner states exactly what the artifact is: which records of how many, the window bounds, the anchor, and the chain head at generation.

Multi-agent attribution

Chains that carry more than one agent now say so: the report header counts and names the fleet, and the activity table attributes each action to the agent that performed it.

AIUC-1 control mapping

The README's compliance-stack section now names the specific AIUC-1 Accountability controls the records serve (E015.4 tamper-evident logging; E015.2 execution-chain and authorization records), and halo verify states the claim its result supports: tamper-evident relative to the verified head.

Records written by 0.2.6 verify with any prior verifier; no format changes.

0.2.5

Evidence now names the agent build that produced it.

• halo export gains agent_version, model, and model_version columns — an audit answer is only as strong as its binding to the version that was actually running during the window
• The Claude Code hook reads HALO_AGENT_VERSION / HALO_AGENT_MODEL to stamp every captured record with the build and model behind it
• New ATC.md: how halo-record maps onto the Agentic Trust Controls (trustcontrols.ai) — the records behind RBM-03 and AID-05, and the witness layer beyond the catalog

halo-record 0.2.4

Authority snapshots — records can now carry a privacy-safe snapshot of the rules, skills, and tool registry that governed a run (hashes and refs, never content), sealed into the chain, with automatic dedup across consecutive records. Contributed by @caioribeiroclw-pixel (#4, #5) — this project's first external contributions.

halo export — date-bounded, workpaper-ready evidence export: a CSV of one row per record plus a manifest tying the export to the chain head. Refuses to run on a chain that fails verification.

Also: CI on every pull request, and contribution guidelines in CONTRIBUTING.md.

halo-record 0.2.3

Generated reports and the schema link now point at the repository.

halo-record 0.2.2

The demo agent is now Globex, a fictional support agent, used consistently across the demo, docs, and sample reports.

halo-record 0.2.1

Documentation alignment: the quickstart writes to ./audit.jsonl; the anchor example matches the CLI's witness argument.

halo-record 0.2.0

Policy corroboration: deterministic rule evaluation over a chain, with AIUC-1 and OWASP starter packs. New report-viewers command lists who unlocked a gated report.

halo-record 0.1.3

Patch release. Aligns the version reported by halo --version with the package version. No functional changes since 0.1.2.