agent-failure-registry 0.1.0__tar.gz

agent_failure_registry-0.1.0/LICENSE-CODE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

agent_failure_registry-0.1.0/LICENSE-DATA

@@ -0,0 +1,11 @@
+CC0 1.0 Universal — Public Domain Dedication
+
+The registry data in `registry/` and the compiled index `afr/_index.json` are
+dedicated to the public domain. The person who associated a work with this
+deed has waived all copyright and related or neighboring rights to this work,
+to the extent allowed by law. You may copy, modify, distribute and use the
+work, including for commercial purposes, all without asking permission.
+
+No warranty of any kind is given.
+
+Full legal text: https://creativecommons.org/publicdomain/zero/1.0/legalcode

agent_failure_registry-0.1.0/PKG-INFO

@@ -0,0 +1,172 @@
+Metadata-Version: 2.4
+Name: agent-failure-registry
+Version: 0.1.0
+Summary: Agent Failure Registry - a neutral namespace and crosswalk for AI agent failure modes
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/canja006/agent-failure-registry
+Project-URL: Repository, https://github.com/canja006/agent-failure-registry
+Project-URL: Issues, https://github.com/canja006/agent-failure-registry/issues
+Project-URL: Schema, https://github.com/canja006/agent-failure-registry/blob/main/registry/SCHEMA.md
+Keywords: ai-agents,failure-analysis,taxonomy,observability,crosswalk
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE-CODE
+License-File: LICENSE-DATA
+Provides-Extra: dev
+Requires-Dist: pyyaml>=6.0; extra == "dev"
+Dynamic: license-file
+
+# Agent Failure Registry
+
+**A neutral namespace for AI agent failure modes, and a crosswalk between the
+taxonomies that already exist.**
+
+Not another classifier. There are at least seven of those, each with its own
+private vocabulary: Agent-Xray's `tool_selection_bug`, AgentRx's
+`Invalid Invocation`, and five more describing overlapping reality under names
+that share nothing. This is the mapping layer between them.
+
+```python
+>>> import afr
+>>> afr.map("agentrx", "Invalid Invocation")
+[AF-0023 (exact)]
+>>> afr.map("agent-xray", "spin")
+[AF-0058 (exact)]
+>>> afr.mode("AF-0058").layer
+'harness'
+```
+
+The analogy is CVE, not CWE. Plenty of people have proposed taxonomies; nobody
+has done the boring institutional work of assigning stable ids, accepting
+mappings, and letting tools *reference* them. CVE's value was never
+intellectual — it was giving the whole industry a shared noun.
+
+## Why this and not a classifier
+
+- **It gets stronger as rivals ship.** Every new classifier with a private
+  taxonomy increases the need for the crosswalk. A classifier is threatened by
+  the next classifier; a namespace is fed by it.
+- **Incumbents structurally cannot build it.** A registry operated by one
+  vendor is one every competitor is right to ignore. Microsoft declined the
+  standards position for AgentRx explicitly.
+- **Distribution runs through other repos.** You do not need an audience — you
+  open a PR adding a mapping file to each classifier.
+
+## Install
+
+```bash
+pip install agent-failure-registry     # zero runtime dependencies; imports as `afr`
+```
+
+## Use
+
+```python
+import afr
+
+# One tool's report, tagged with shared ids
+labels = afr.normalize({"stuck_loop": 31, "context_overflow": 18}, "agent-xray")
+print(afr.profile(labels).render())
+```
+
+```
+failure profile  (source: agent-xray, n=49)
+--------------------------------------------------------------------
+AF-0058    63.3%  ######################              Unproductive repetition
+AF-0064    36.7%  ############                        Context overflow truncation
+--------------------------------------------------------------------
+by layer: harness=49
+```
+
+That is the pitch in one output. `67% pass` tells you nothing you can act on.
+
+```bash
+afr modes                              # every mode
+afr show AF-0142                       # full record, plus who maps to it
+afr map agentrx "System Failure"       # source category -> AF ids
+afr unmap AF-0064 agent-xray           # and back, with relations inverted
+afr coverage                           # how much of each taxonomy is mapped
+afr gaps                               # what nobody has named yet
+```
+
+## Two levels of identifier
+
+| | | |
+|---|---|---|
+| **`AF-0142`** | mode | Permanent, versionless, like CWE. What classifiers map onto and humans cite. |
+| **`AFI-2026-08-0417`** | instance | One observation, pinned to model + harness version, like CVE. |
+
+Conflating them breaks the query that justifies the whole project: *did Opus 5.2
+regress on AF-0142 relative to 5.1?* That needs modes stable across time and
+instances pinned to versions — so they cannot be the same identifier.
+
+Instances are **deliberately not implemented yet**. Open collection only once
+three independent tools emit AF ids.
+
+## Relation direction
+
+`relation` describes **the AF mode relative to the source category**: `exact`,
+`broader`, `narrower`, `overlaps`. `afr.unmap()` inverts it for you — swapping
+`broader` and `narrower` — because hand-authoring the reverse is how crosswalks
+silently corrupt.
+
+At most one `exact` per source category. One wrong `exact` discredits the table.
+
+## Status
+
+Pre-v0. 18 modes, all `provisional`; 3 source taxonomies; 90% of AgentRx and
+86% of Agent-Xray mapped — Agent-Xray from a full read of its classifier, not
+its README (see [`registry/crosswalk/notes/`](registry/crosswalk/notes/)). The
+remaining modes are week-one reading, not coding — see
+[`registry/crosswalk/academic.yaml`](registry/crosswalk/academic.yaml) for the
+queue.
+
+Findings are already falling out of the structure, which is the point.
+`afr gaps` surfaces four:
+
+- `agent-xray:tool_bug` — a **tool-layer defect** has no AF mode; the registry
+  has no `tool`-layer entry yet. (As detected, the category mostly catches
+  fabricated tools and schema errors, which *do* map.)
+- `agent-xray:routing_bug` — **tool never exposed by the harness**. No AF mode.
+- `agent-xray:tool_selection_bug` — **wrong tool selected**. No AF mode.
+- **`AF-0142`** (stale context re-read) has **no source mapping** — a failure
+  everyone has seen that no published taxonomy names.
+
+## Repo layout
+
+```
+registry/modes/AF-####.yaml     canonical mode records (CC0)
+registry/crosswalk/*.yaml       one file per third-party taxonomy (CC0)
+registry/SCHEMA.md              field semantics and relation direction
+afr/                            the library (Apache-2.0), no dependencies
+afr/_index.json                 compiled from YAML, committed, CI-enforced
+scripts/compile.py              YAML -> index (the only place PyYAML is needed)
+scripts/validate.py             integrity checks; a lying crosswalk is worse than none
+```
+
+## Development
+
+```bash
+make check      # build + validate + test
+make demo       # coverage, gaps, and a sample profile
+```
+
+## Licensing
+
+Registry data is **CC0**; the library is **Apache-2.0**. A namespace with an
+attribution clause invites legal review, and legal review is the friction that
+stops tools embedding it.
+
+Governance, including the commitment to move to a neutral foundation once three
+independent tools map to this namespace, is in [GOVERNANCE.md](GOVERNANCE.md).
+
+## Outreach
+
+Distribution runs through other projects' repos, not through this one. Drafted
+mapping-file PRs for AgentRx and Agent-Xray, and an issue for AgentDebugX, are
+in [`outreach/`](outreach/) — including the order to send them in, which
+matters more than the speed.

agent_failure_registry-0.1.0/README.md

@@ -0,0 +1,149 @@
+# Agent Failure Registry
+
+**A neutral namespace for AI agent failure modes, and a crosswalk between the
+taxonomies that already exist.**
+
+Not another classifier. There are at least seven of those, each with its own
+private vocabulary: Agent-Xray's `tool_selection_bug`, AgentRx's
+`Invalid Invocation`, and five more describing overlapping reality under names
+that share nothing. This is the mapping layer between them.
+
+```python
+>>> import afr
+>>> afr.map("agentrx", "Invalid Invocation")
+[AF-0023 (exact)]
+>>> afr.map("agent-xray", "spin")
+[AF-0058 (exact)]
+>>> afr.mode("AF-0058").layer
+'harness'
+```
+
+The analogy is CVE, not CWE. Plenty of people have proposed taxonomies; nobody
+has done the boring institutional work of assigning stable ids, accepting
+mappings, and letting tools *reference* them. CVE's value was never
+intellectual — it was giving the whole industry a shared noun.
+
+## Why this and not a classifier
+
+- **It gets stronger as rivals ship.** Every new classifier with a private
+  taxonomy increases the need for the crosswalk. A classifier is threatened by
+  the next classifier; a namespace is fed by it.
+- **Incumbents structurally cannot build it.** A registry operated by one
+  vendor is one every competitor is right to ignore. Microsoft declined the
+  standards position for AgentRx explicitly.
+- **Distribution runs through other repos.** You do not need an audience — you
+  open a PR adding a mapping file to each classifier.
+
+## Install
+
+```bash
+pip install agent-failure-registry     # zero runtime dependencies; imports as `afr`
+```
+
+## Use
+
+```python
+import afr
+
+# One tool's report, tagged with shared ids
+labels = afr.normalize({"stuck_loop": 31, "context_overflow": 18}, "agent-xray")
+print(afr.profile(labels).render())
+```
+
+```
+failure profile  (source: agent-xray, n=49)
+--------------------------------------------------------------------
+AF-0058    63.3%  ######################              Unproductive repetition
+AF-0064    36.7%  ############                        Context overflow truncation
+--------------------------------------------------------------------
+by layer: harness=49
+```
+
+That is the pitch in one output. `67% pass` tells you nothing you can act on.
+
+```bash
+afr modes                              # every mode
+afr show AF-0142                       # full record, plus who maps to it
+afr map agentrx "System Failure"       # source category -> AF ids
+afr unmap AF-0064 agent-xray           # and back, with relations inverted
+afr coverage                           # how much of each taxonomy is mapped
+afr gaps                               # what nobody has named yet
+```
+
+## Two levels of identifier
+
+| | | |
+|---|---|---|
+| **`AF-0142`** | mode | Permanent, versionless, like CWE. What classifiers map onto and humans cite. |
+| **`AFI-2026-08-0417`** | instance | One observation, pinned to model + harness version, like CVE. |
+
+Conflating them breaks the query that justifies the whole project: *did Opus 5.2
+regress on AF-0142 relative to 5.1?* That needs modes stable across time and
+instances pinned to versions — so they cannot be the same identifier.
+
+Instances are **deliberately not implemented yet**. Open collection only once
+three independent tools emit AF ids.
+
+## Relation direction
+
+`relation` describes **the AF mode relative to the source category**: `exact`,
+`broader`, `narrower`, `overlaps`. `afr.unmap()` inverts it for you — swapping
+`broader` and `narrower` — because hand-authoring the reverse is how crosswalks
+silently corrupt.
+
+At most one `exact` per source category. One wrong `exact` discredits the table.
+
+## Status
+
+Pre-v0. 18 modes, all `provisional`; 3 source taxonomies; 90% of AgentRx and
+86% of Agent-Xray mapped — Agent-Xray from a full read of its classifier, not
+its README (see [`registry/crosswalk/notes/`](registry/crosswalk/notes/)). The
+remaining modes are week-one reading, not coding — see
+[`registry/crosswalk/academic.yaml`](registry/crosswalk/academic.yaml) for the
+queue.
+
+Findings are already falling out of the structure, which is the point.
+`afr gaps` surfaces four:
+
+- `agent-xray:tool_bug` — a **tool-layer defect** has no AF mode; the registry
+  has no `tool`-layer entry yet. (As detected, the category mostly catches
+  fabricated tools and schema errors, which *do* map.)
+- `agent-xray:routing_bug` — **tool never exposed by the harness**. No AF mode.
+- `agent-xray:tool_selection_bug` — **wrong tool selected**. No AF mode.
+- **`AF-0142`** (stale context re-read) has **no source mapping** — a failure
+  everyone has seen that no published taxonomy names.
+
+## Repo layout
+
+```
+registry/modes/AF-####.yaml     canonical mode records (CC0)
+registry/crosswalk/*.yaml       one file per third-party taxonomy (CC0)
+registry/SCHEMA.md              field semantics and relation direction
+afr/                            the library (Apache-2.0), no dependencies
+afr/_index.json                 compiled from YAML, committed, CI-enforced
+scripts/compile.py              YAML -> index (the only place PyYAML is needed)
+scripts/validate.py             integrity checks; a lying crosswalk is worse than none
+```
+
+## Development
+
+```bash
+make check      # build + validate + test
+make demo       # coverage, gaps, and a sample profile
+```
+
+## Licensing
+
+Registry data is **CC0**; the library is **Apache-2.0**. A namespace with an
+attribution clause invites legal review, and legal review is the friction that
+stops tools embedding it.
+
+Governance, including the commitment to move to a neutral foundation once three
+independent tools map to this namespace, is in [GOVERNANCE.md](GOVERNANCE.md).
+
+## Outreach
+
+Distribution runs through other projects' repos, not through this one. Drafted
+mapping-file PRs for AgentRx and Agent-Xray, and an issue for AgentDebugX, are
+in [`outreach/`](outreach/) — including the order to send them in, which
+matters more than the speed.

agent_failure_registry-0.1.0/afr/__init__.py

@@ -0,0 +1,26 @@
+"""Agent Failure Registry - a neutral namespace for AI agent failure modes.
+
+    >>> import afr
+    >>> afr.map("agentrx", "Invalid Invocation")
+    [AF-0023 (exact)]
+    >>> afr.mode("AF-0023").layer
+    'model'
+
+Relations are recorded as *AF mode relative to source category*.
+Data is CC0; this library is Apache-2.0.
+"""
+
+from .crosswalk import coverage, map, normalize, unmap
+from .data import categories, mode, modes, reload, source, sources, version
+from .model import LAYERS, RELATIONS, Label, Mapping, Mode, Source, invert
+from .profile import Profile, profile
+
+__version__ = "0.1.0"
+
+__all__ = [
+    "map", "unmap", "normalize", "coverage",
+    "mode", "modes", "source", "sources", "categories", "version", "reload",
+    "profile", "Profile",
+    "Mode", "Mapping", "Source", "Label", "invert",
+    "RELATIONS", "LAYERS",
+]