phionyx-compliance
Evidence-grade compliance report drafts from Phionyx RGE v0.2 audit chains. AGPL-3.0 · Python 3.10+ · alpha (v0.7.0 cycle)
phionyx-compliance turns a signed envelope chain produced by phionyx-core,
phionyx-mcp-server, or any other Phionyx component into a framework-shaped
markdown draft report — suitable as input to a compliance officer or auditor's
review.
It does not certify. Reports are evidence-oriented mappings; a lawyer or auditor must review before any use that implies legal posture.
Sixty-second usage (target spec; lands at v0.7.0)
pip install phionyx-compliance
phionyx-compliance generate \
--trace trace-e2dd588aaf4d4c97 \
--template eu-ai-act-article-13 \
--out reports/<DATE>-article-13-draft.md
What it does:
- Reads the envelope chain at
~/.phionyx/mcp_audit/<trace_id>/(or the path the operator passes via--chain-root). - Walks the chain and extracts the per-envelope evidence the chosen template requires.
- Renders a markdown draft against the template's prompts and the chain's actual evidence.
- Includes the canonical disclaimer at the head and tail of the document.
Supported templates (v0.7.0 ship list)
| Template | Framework | Status |
|---|---|---|
eu-ai-act-article-13 |
EU AI Act, Article 13 (transparency) | first to ship |
nist-ai-rmf-1 |
NIST AI RMF 1.0 — MAP/MEASURE/MANAGE | second |
iso-iec-42001 |
ISO/IEC 42001:2023 — Annex A controls subset | third |
owasp-agentic-ai-v1 |
OWASP Agentic AI Threats v1.0 coverage | fourth |
Each template is a self-contained directory under templates/<framework>/:
templates/
└── eu-ai-act-article-13/
├── template.md (markdown with {{placeholders}})
├── schema.json (Pydantic JSON Schema for the data inputs)
├── mapping.yaml (how envelope fields → template placeholders)
└── README.md (framework-specific notes + disclaimer text)
Composition with the Phionyx stack
phionyx-compliance is read-only over the envelope chain. It does not
modify chain state, does not re-sign anything, and does not produce envelopes
of its own. The output is a markdown file plus an optional JSON-formatted
summary (--format=json).
This composes cleanly with:
phionyx-pipeline-mcp— self-claim gate envelopes feed the "agent's own attestations" section of every framework template.phionyx-mcp-server— third-party tool-call envelopes feed the "tool-call audit" section.phionyx-eval-inspect— Inspect AI.evalexports include the same envelope chain; the compliance draft can cite the.evallog id as the reviewer-runnable evidence pointer.
Plugin command (lands at v0.7.0 with F12++)
The phionyx-claude-code-plugin will gain /phionyx:evidence-report that
shells out to this package and renders the draft inline in the Claude Code
chat. Pattern preserves the v0.5.1 plugin extraction discipline (no Anthropic
plugin content copied verbatim).
Status (2026-05-26)
- W1.1 — scaffold landed. Package skeleton, version pin to phionyx-core>=0.6.0, CLI entry-point declared.
- W1.2 — template substrate landed. First template:
eu-ai-act-article-13v1.0.0. Renderer + CLI subcommands (list-templates / describe / render-sample / generate --sample). 15/15 tests. - W1.3 — chain → inputs walker landed.
ChainView.from_disk()+resolve_inputs()(4-category mapping resolver). Realgenerate --trace <id>works. 25/25 tests. - W1.4 — plugin integration landed.
/phionyx:evidence-reportslash command in the Claude Code plugin wraps the CLI. - W1.5 — additional templates landed (this commit). Three new framework templates at v1.0.0 each:
nist-ai-rmf-1(NIST AI RMF 1.0 — MAP/MEASURE/MANAGE/GOVERN)iso-iec-42001(ISO/IEC 42001:2023 — AI Management System)owasp-agentic-ai-v1(OWASP Agentic AI Threats v1.0 — threat coverage) Cross-template parity test suite (test_all_templates.py, 5 tests). 30/30 total tests pass.
v0.7.0 W1 complete. W2 (F4 reasoning audit + F8 RAG audit) is the next milestone.
See docs/DESIGN.md for design notes.
Disclaimer (canonical)
Reports produced by this package are evidence-oriented mappings, not legal compliance guarantees. A lawyer or auditor must review before any use that implies legal posture. Phionyx does not certify AI systems; it produces the evidence chains that certifications rely on.
License
AGPL-3.0-or-later. See LICENSE.
Citing
If you use phionyx-compliance in academic or policy work, cite the parent
project: Abak, A. T. (2026). Phionyx Research — Runtime Evidence Layer for
Agentic AI. ORCID 0009-0002-3718-4010.
Release files for phionyx-compliance 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| phionyx_compliance-0.1.1.tar.gz | 53.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| phionyx_compliance-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 115.9 kB
Release files / phionyx_compliance-0.1.1.tar.gz
| Download URL | phionyx_compliance-0.1.1.tar.gz |
|---|---|
| Size | 53.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
569650fea9bea9597705d2ae2026973f63398b1b22bc34aa130b83ed09967f45
|
|
BLAKE2b-256 checksum How to use checksums |
6b36df5b8315c41c8d26f0e8656228730fe4415372f39d49f9c57db8b3c1e660
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 27, 2026.
Transparency logRelease files / phionyx_compliance-0.1.1-py3-none-any.whl
| Download URL | phionyx_compliance-0.1.1-py3-none-any.whl |
|---|---|
| Size | 62.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
81584f13cad80bffef5583ed7ebecc832a4dd625b095a50fd93b9128bcee82af
|
|
BLAKE2b-256 checksum How to use checksums |
d7b6007aaf2c7f27f3b7421c4f6e6fe75935a90cc79b6fa3109dc679edd49c58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 27, 2026.
Transparency log