phionyx-eval-inspect 0.1.0

Interoperability bridge — export Phionyx Reasoned Governance Envelope (RGE) evidence into Inspect AI evaluation logs.

phionyx-eval-inspect

Interoperability bridge — export Phionyx Reasoned Governance Envelope (RGE) evidence into Inspect AI evaluation logs.

Inspect AI is the open-source frontier-model evaluation framework maintained by UK AISI and used (per inspect.aisi.org.uk as of 2026-05-19) as the standard frontier-eval framework across multiple government AI safety institutes — UK AISI, US CAISI, EU AI Office, Japan AISI, Korea AISI.

This package is not an endorsement by or partnership with any of those organisations. It is a read-only interoperability adapter that lets Phionyx-governed runs become natively inspectable in Inspect AI's tooling.

What this package does

Two complementary bridges:

1. Storage adapter: convert a Phionyx RGE envelope chain (the per-turn signed evidence records the phionyx-mcp-server writes under ~/.phionyx/mcp_audit/<trace_id>/) into a single Inspect AI .eval log file under ./logs/<task>/<run_id>.eval. The log is then viewable with inspect view, queryable with Inspect's standard tooling, and joinable with any other Inspect log in your eval workflow.

2. MCP tool wiring documentation: docs/wiring_phionyx_mcp_in_inspect_task.md walks through how to register the companion phionyx-mcp-server MCP server as a tool inside an Inspect AI eval task, so the agent under evaluation goes through Phionyx's runtime governance on every tool call.

Install

pip install phionyx-eval-inspect

# To also view the resulting .eval logs in Inspect's UI:
pip install "phionyx-eval-inspect[inspect]"

The adapter itself has zero runtime dependencies on inspect-ai — it emits the .eval JSON shape directly. The [inspect] extra exists only for when you want inspect view or a live Inspect task.

Use — CLI

# Convert a Phionyx envelope chain into an Inspect log file:
phionyx-eval-inspect convert \
    --trace trace-abc-001 \
    --task phionyx_governed_replay \
    --audit-root ~/.phionyx/mcp_audit \
    --logs-dir ./logs

# Show the converted log without writing to disk:
phionyx-eval-inspect show \
    --trace trace-abc-001 \
    --audit-root ~/.phionyx/mcp_audit

Then view it with Inspect AI:

inspect view ./logs/phionyx_governed_replay/trace-abc-001.eval

Use — Python

from phionyx_eval_inspect import (
    envelope_chain_from_directory,
    envelope_chain_to_inspect_log,
    write_log,
)

envelopes = envelope_chain_from_directory(
    "~/.phionyx/mcp_audit", "trace-abc-001"
)
log = envelope_chain_to_inspect_log(
    envelopes,
    task_name="phionyx_governed_replay",
    run_id="trace-abc-001",
)
write_log(log, logs_dir="./logs")

The function is read-only over the envelope chain. It never modifies the input, and it never scores the run — scoring stays in Inspect's own solver/scorer chain.

What the log carries

Each envelope becomes one Inspect sample. The sample carries:

• id: Phionyx turn index.
• input: the user text (envelope input.user_text).
• output.completion: the released text (envelope output.text).
• events: one per pipeline block step (phionyx.pipeline.block) plus an event per MCP tool call (phionyx.mcp.tool_call) when present.
• metadata.phionyx: the governance evidence — trace id, decision, decision reason, policy basis, pipeline path, integrity chain (previous + current + signature), and the full mcp_tool_audit block when populated.

Phionyx-specific fields live under metadata.phionyx so native Inspect tooling sees them without colliding with Inspect's native data model.

Companion packages — the wider stack

Package	Role
phionyx-core	Deterministic AI runtime governance — 46-block pipeline, kill switch, ethics + safety gates, signed audit envelopes
phionyx-mcp-server	MCP trust boundary: descriptor hash, signed RGE envelope, audit chain (outward layer)
phionyx-pipeline-mcp	Self-governance MCP for Claude Code: three-layer verification over the agent's own "fixed / tested / changed" claims (inward layer)
phionyx-eval-inspect	(this) Interoperability bridge into Inspect AI eval logs

When all three MCP-related packages are installed, a single Claude Code session: emits Phionyx envelopes (outward + inward) → shares one trace_id across both MCPs → this adapter converts the chain into an Inspect .eval log → inspect view shows the full run.

Schema pinning

The adapter is pinned to Inspect AI log format v0.3.x (as of 2026-05-19). Override with:

PHIONYX_INSPECT_LOG_SCHEMA_VERSION=v0.3.x phionyx-eval-inspect convert ...

To support a new Inspect schema, drop log_schema_v0_<minor>.py next to adapter.py and extend _resolve_schema_module. Bump-policy doc forthcoming in the umbrella repo under docs/conventions/inspect_log_schema_bump_policy.md.

Framing — what this package does NOT claim

• It is not an endorsement, accreditation, or partnership with UK AISI, US CAISI, EU AI Office, Japan AISI, or Korea AISI.
• It does not validate or score the Phionyx-governed run — it surfaces evidence so Inspect's own scorers can be applied.
• It does not require Inspect AI to be installed at runtime — only at view time.
• It does not modify Inspect AI; the adapter writes a standard .eval file the framework's native tools read.

The framing is interoperability, not endorsement.

Tests

pip install -e ".[test]"
pytest -q

License

AGPL-3.0-or-later. See LICENSE.

See also

• Project hub: github.com/halvrenofviryel/phionyx-research
• Phionyx Core SDK: pypi.org/project/phionyx-core
• Inspect AI: github.com/UKGovernmentBEIS/inspect_ai
• Inspect AI documentation: inspect.aisi.org.uk
• Reasoned Governance Envelope (RGE) v0.2 RFC: phionyx-mcp-server/specs/rge_v0_2