Sharpen AANA public positioning
Browse files
README.md
CHANGED
|
@@ -13,7 +13,7 @@ pipeline_tag: text-classification
|
|
| 13 |
|
| 14 |
# AANA: Agent Action Control Architecture
|
| 15 |
|
| 16 |
-
AANA
|
| 17 |
|
| 18 |
This card describes AANA as a control-layer architecture and runtime package, not as a standalone frontier model. The intended pattern is:
|
| 19 |
|
|
@@ -98,4 +98,4 @@ Execute only when AANA returns `accept`, no hard blockers, and the relevant work
|
|
| 98 |
- AANA can over-block if evidence or authorization state is incomplete.
|
| 99 |
- AANA does not replace a capable planner, retrieval system, domain policy source, or human escalation path.
|
| 100 |
- Production deployments still need live connector review, audit retention policy, incident response, security review, and domain-owner signoff.
|
| 101 |
-
|
|
|
|
| 13 |
|
| 14 |
# AANA: Agent Action Control Architecture
|
| 15 |
|
| 16 |
+
AANA is a pre-action control layer for AI agents: agents propose actions, AANA checks evidence/auth/risk, and tools execute only when the route is accept.
|
| 17 |
|
| 18 |
This card describes AANA as a control-layer architecture and runtime package, not as a standalone frontier model. The intended pattern is:
|
| 19 |
|
|
|
|
| 98 |
- AANA can over-block if evidence or authorization state is incomplete.
|
| 99 |
- AANA does not replace a capable planner, retrieval system, domain policy source, or human escalation path.
|
| 100 |
- Production deployments still need live connector review, audit retention policy, incident response, security review, and domain-owner signoff.
|
| 101 |
+
|