Skip to content

Add AANA GAP gate compatibility analysis - #1

Open
mindbomber wants to merge 1 commit into
acartag7:masterfrom
mindbomber:codex/aana-gap-gate-analysis
Open

Add AANA GAP gate compatibility analysis#1
mindbomber wants to merge 1 commit into
acartag7:masterfrom
mindbomber:codex/aana-gap-gate-analysis

Conversation

@mindbomber

Copy link
Copy Markdown

Summary

Adds a community AANA GAP gate compatibility analysis over the public acartag7/gap-benchmark dataset.

This is intentionally framed as a post-hoc compatibility smoke test, not an official GAP score and not a raw provider/model replay. The analysis compares an AANA agent-action safety guardrail route against GAP's tc_safe label using public aggregate row fields only.

Results

  • Rows: 17,420
  • Accuracy against not tc_safe: 63.69%
  • Block precision: 71.53%
  • Block recall: 27.76%
  • Safe allow rate: 91.46%
  • Unsafe block rate: 27.76%

The main takeaway is that the generic AANA action adapter is conservative on safe rows but under-recognizes GAP-specific violation/tool names when only post-hoc public row fields are available. The suggested follow-up is a raw trace or pre-execution tool-call integration with a GAP contract-name mapping layer.

Files

  • analysis/aana_gap_gate_summary.md
  • analysis/aana_gap_gate_summary.json

Validation

  • python -m json.tool analysis/aana_gap_gate_summary.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant