phionyx-core v0.7.0 — Compliance Evidence Pack
Pre-releasePhionyx v0.7.0 — Compliance Evidence Pack
Release date: 2026-05-27 (target was 2026-11-30 → shipped ~6 months early; supplement target was 2026-06-30 → shipped one month ahead even of the recalibrated date).
Theme: From envelope chain to framework-shaped evidence draft. The same signed audit trail that powered v0.6.0 multi-agent evidence now exits the developer surface and enters the compliance surface — with bounded-authority pattern preserved, memory mutations audited, and two new schemas in the portfolio.
This release answers the question that follows "a model saying fixed is not evidence" and "multi-agent flows need a shared evidence shape": when a compliance officer or external auditor asks "what happened, signed, replayable, by whom, when, under what policy?" — what does the runtime evidence layer hand them?
Six work blocks ship: phionyx-compliance with four framework templates (W1), RGE v0.2 reasoning + retrieval extensions (W2.1 + W2.2), schema portfolio bump (W2.3), phionyx-letta memory mutation audit (W3), and the HearthOS bounded-authority envelope foundation with three reviewer-runnable pinned traces (W4.1 + W4.2.a). The actual interactive HearthOS demo UIs (W4.2.b) are intentionally deferred to product-cycle work; the v0.7.0 ship is the wire-level evidence layer.
Two new schemas join the portfolio: Schema 8 phionyx.memory_mutation_envelope.v1 (Letta) and Schema 9 phionyx.bounded_authority_envelope.v1 (HearthOS). Both are additive — every v0.6.0 envelope continues to validate; no breaking changes.
Highlights
| What | Where |
|---|---|
F14 — phionyx-compliance package + 4 framework templates |
tools/phionyx_compliance/ |
| F4 — RGE v0.2 reasoning surface extension (3 fields) | examples/envelopes/rge_v0_2/rge_v0_2.schema.json §reasoning |
| F8 — RGE v0.2 retrieval block activation (6 fields) | same schema §retrieval |
F15 — phionyx-letta memory mutation audit (Schema 8) |
tools/phionyx_letta/ |
| HearthOS bounded-authority envelope (Schema 9) | apps/phionyx-website/lib/hearthos/envelope.ts + 3 pinned traces |
| v0.7.0 schema portfolio document | examples/envelopes/v0_7_schema_portfolio.md |
F14 — phionyx-compliance (W1)
Read-only over the envelope chain. Produces framework-shaped markdown drafts from signed evidence. Does not certify.
Four framework templates ship at v1.0.0:
- EU AI Act Article 13 — transparency obligations (W1.2, first to ship)
- NIST AI RMF 1.0 — MAP / MEASURE / MANAGE / GOVERN functions (W1.5)
- ISO/IEC 42001:2023 — AI management system, Annex A controls subset (W1.5)
- OWASP Agentic AI Threats v1.0 — ASI01–ASI10 threat coverage (W1.5)
Every report carries the canonical disclaimer at head and tail:
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.
CLI surface:
phionyx-compliance list-templates
phionyx-compliance describe eu-ai-act-article-13
phionyx-compliance render-sample owasp-agentic-ai-v1 --format markdown
phionyx-compliance generate --trace trace-xxx --template iso-iec-42001 \
--operator-inputs operator_inputs.yaml --out reports/2026-05-27-article-13.mdClaude Code plugin command (W1.4):
/phionyx:evidence-report eu-ai-act-article-13 trace-xxx operator_inputs.yaml
Total: 30/30 tests pass across the four-template parity suite.
F4 — Reasoning surface extension (W2.1)
Three new optional fields on the RGE v0.2 reasoning block:
rationale_summary— runtime-produced one-line distillation of the reasoning surface (distinct frommodel_stated_rationale).knowledge_sources_consulted[]— typed list of consulted sources (retrieval_corpus / memory_block / tool_output / tool_descriptor_clause / static_doc / system_prompt / external_api).constraints_acknowledged[]— typed list with optionalsatisfied: bool(policy / user_directive / safety_boundary / tool_descriptor_clause / regulatory / self_imposed).
Additive — v0.6.0 envelopes without these fields continue to validate against the v0.7.0 schema. The builder in phionyx_mcp_server.audit_chain emits null/empty defaults so producers that do not surface reasoning metadata produce schema-valid envelopes without code change.
F8 — Retrieval block activation (W2.2)
The retrieval block in RGE v0.2 was reserved (status="reserved-for-v0.4.1-f8") since v0.4.0. v0.7.0 W2.2 flips Phionyx's own producers to status="active" and adds:
Block-level:
corpus({name, version, language}) — semantic corpus metadatasimilarity_threshold— cutoff used to gate retrieved → candidatequery_text_hash— SHA-256 of the user-formatted query text
Per-document:
chunk_offset— zero-indexed chunk positionsource_url— canonical URLretrieved_at— ISO-8601 retrieval timestamp (may predate envelope timestamp when cached)
New builder helper: phionyx_mcp_server.audit_chain.build_retrieval_block(RetrievalContext). build_envelope(..., retrieval=RetrievalContext(...)) integrates it into the signed envelope.
Test result: 6 new W2.2 tests + 14 prior = 20/20 pass.
W2.3 — v0.7.0 schema portfolio document
examples/envelopes/v0_7_schema_portfolio.md captures the eight-schema portfolio with the additive extensions and the two new schemas (8, 9) documented. Versioning policy reaffirmed: strictly additive within a major, schema id bump only on breaking change or semantic shift.
F15 — phionyx-letta memory mutation audit (W3)
New package. Schema 8 (phionyx.memory_mutation_envelope.v1). Per-mutation signed envelope with structured before/after diff.
Six mutation kinds: write, append, clear, delete, forget, consolidate.
compute_memory_diff() produces:
before_hash/after_hash(SHA-256)before_size_bytes/after_size_bytesadded_chars/removed_chars/unchanged_chars(via difflib.SequenceMatcher)- Optional
diff_text(opt-in only — PII safety)
W3.2 adds MemoryConsolidationAudit subblock — cross-references canonical pipeline block #43 (memory_consolidation) when episodic memories promote to semantic.
W3.3 adds cross-runtime composition via subject.metadata.memory_audit.parent_envelope_ref — upstream adapter envelopes (langchain_event, openai_agents_event, RGE v0.2) link to the memory mutation they caused.
Test result: 20/20 pass across W3.1 / W3.2 / W3.3.
HearthOS bounded-authority envelope (W4.1 + W4.2.a)
Schema 9 (phionyx.bounded_authority_envelope.v1). TypeScript runtime emits envelopes directly — no Node CLI shim, no Python translator. Reuses canonical JSON + SHA-256 hash chain + HMAC-SHA-256 signing.
Eight event types covering the full bounded-authority lifecycle: propose, execute_requested, execute_approved, execute_rejected, execute_completed, safety_gate_blocked, authority_tier_change, proof_recorded.
Seven preservation rules verified by verifyBoundedAuthority() (separate from verifyChain() — domain rules live in their own layer):
- No
execute_completedwithout priorexecute_approvedfor the sameaction_id. execute-high-stakesneeds two distinctapprover_id_hashvalues.safety_gate_blockedenvelope ALWAYS emits even when verdict=block (no sansür).authority_tier_changefollowed byproof_recorded(permission).approver_id_hashis hex of length 64 (SHA-256).never_rules_active+stop_conditions_activecannot shrink without interveningauthority_tier_change.proof_obligations_declareddischarged within K turns (default K=50).
Three pinned demo traces ship as .jsonl files under apps/phionyx-website/public/hearthos/audit-traces/:
| Trace | Envelopes | Demonstrates |
|---|---|---|
demo-diagnostic-v1.jsonl |
14 | PROPOSE-only flow (no EXECUTE, no approvals) |
demo-weekly-reset-v1.jsonl |
16 | Full lifecycle: 3 approved actions + 1 rejected + proof_recorded per outcome |
demo-boundary-script-v1.jsonl |
11 | safety_gate_blocked envelope emitted even when verdict=block (rule 3) |
Reviewers can verify any trace offline:
python3 -c "
from phionyx_mcp_server.audit_chain import verify_chain
import json, sys
chain = [json.loads(l) for l in open(sys.argv[1])]
print(verify_chain(chain))
" apps/phionyx-website/public/hearthos/audit-traces/demo-diagnostic-v1.jsonlSigning uses the publicly-published all-zeros HMAC key ("0" * 64) — replay reproducibility, not unforgeability. The browser-only demo has no operator-side state to protect; reviewers need byte-identical replay.
Scope note (corrected 2026-05-27 post-publish): the interactive HearthOS demo UI modules are already live at phionyx.ai/hearthos/demo — three Next.js static-export modules (12-question Diagnostic, Weekly Reset plan generator, Boundary Script generator with parent-approval queue). What v0.7.0 ships is the wire-level evidence layer that the demo modules will be wired to in a follow-up patch: the envelope library + the three pinned .jsonl traces. The integration step — making the live demos emit envelopes via the Schema 9 library to IndexedDB with a "Download audit chain" button — is W4.2.b in the next cycle. Today, reviewers can verify the wire-level discipline by downloading the pinned traces; the live demos demonstrate the pattern visually but do not yet emit envelopes.
Schema portfolio at v0.7.0
Eight schema identifiers (seven from v0.6.0 + one new). See examples/envelopes/v0_7_schema_portfolio.md for the full table.
- Schema 1
phionyx.governed_response_envelope.v0_2— extended (W2.1 + W2.2) - Schema 2
subagent_chain_v0_1.schema.json— unchanged - Schema 3
phionyx.langchain_event_envelope.v1— unchanged - Schema 4
phionyx.openai_agents_event_envelope.v1— unchanged - Schema 5
phionyx.judgment_envelope.v1— unchanged - Schema 6
phionyx.imported_langfuse_envelope.v1— unchanged - Schema 7
phionyx.imported_langsmith_envelope.v1— unchanged - Schema 8
phionyx.memory_mutation_envelope.v1— NEW (phionyx-letta) - Schema 9
phionyx.bounded_authority_envelope.v1— NEW (HearthOS envelope library)
All eight schemas share the canonical-JSON + SHA-256 hash chain + opt-in Ed25519 (or demo HMAC-SHA-256) signing surface. Mixed-schema chains are rejected by the verifier; cross-runtime composition happens via the subject.metadata.<surface> reference object pattern (see W3.3 and W4.1 §7).
What's NOT in v0.7.0
- HearthOS demo modules → envelope library integration (W4.2.b) — the live demo modules at
phionyx.ai/hearthos/demodo not yet emit Schema 9 envelopes to IndexedDB or expose a "Download audit chain" button. The wire-level pinned traces ship as standalone artefacts. Integration is the next cycle. - HearthOS server-side deployment — browser-only demo only.
- F4 reasoning surface envelope emission by Phionyx Core — the schema is extended and the MCP server builder populates the new fields with defaults; actual core-side runtime population is v0.8.0 candidate.
- Cross-runtime export (Phionyx → Langfuse / LangSmith) — v0.6.0 shipped import-only; export remains a v0.7.x patch candidate.
- EU AI Act Article 12 template — listed as candidate input in the 2026-05-26 Deloitte alignment audit; founder-paced per individual decision.
- PyPI publish of
phionyx-lettaand updatedphionyx-compliance— gated on GitHub Actions billing resolution (the workflow infrastructure is ready; PyPI release is workflow-driven).
Test count + verification surface
| Package | Tests passing | Notes |
|---|---|---|
phionyx-mcp-server (W2.1 + W2.2 extensions) |
31/31 | 11 baseline + 3 W2.1 + 6 W2.2 + 11 other |
phionyx-letta (W3) |
20/20 | New package, full test coverage of schema + diff + 7 W3 sub-tests |
phionyx-compliance (W1) |
30/30 | 4-template parity suite |
phionyx-website TypeScript typecheck |
clean | envelope.ts + lib/hearthos/ |
| HearthOS pinned traces self-verification | 3/3 | All three .jsonl files chain-intact and deterministic |
The reviewer-runnable surface is broader than v0.6.0:
- Schema validation — eight Draft 2020-12 JSON Schemas, standard validators apply.
- Hash chain integrity — same recompute-and-compare for all eight schemas.
- Cross-envelope linkage —
integrity.previous, plussubagent_chain.parent_envelope_hash(multi-agent), plussubject.metadata.memory_audit.parent_envelope_ref(cross-runtime memory), plussubject.metadata.bounded_authority.parent_envelope_ref(cross-runtime bounded-authority). - Bounded-authority preservation — 7 rules in
verifyBoundedAuthority(separate fromverifyChain). - Compliance draft generation —
phionyx-compliance generate ... --template <id> --trace <id>reproduces the same draft for the same chain.
Migration from v0.6.0
Nothing required. All envelope schemas remain backward compatible. The new fields on RGE v0.2's reasoning and retrieval blocks are optional. New schemas (8, 9) are additive new identifiers.
If a consumer wants to surface the new reasoning fields:
- Pydantic / dict consumers: read
envelope["reasoning"]["rationale_summary"]etc. with.get()defaults. - Schema validators: re-fetch
rge_v0_2.schema.jsonfrom the v0.7.0 commit.
If a consumer wants to read memory mutation or bounded-authority envelopes:
- They will see new top-level
schemavalues. Branch onschemafirst. - Mixed-schema chains are still rejected by all portfolio verifiers — keep one schema id per trace.
Companion package releases
| Package | v0.7.0 status | PyPI |
|---|---|---|
phionyx-core |
unchanged at 0.6.0 — no API surface delta | live |
phionyx-pipeline-mcp |
extended (W2.1 + W2.2 builder fields) | publish gated on GHA billing |
phionyx-mcp-server |
extended (same as pipeline-mcp) | publish gated on GHA billing |
phionyx-eval-inspect |
unchanged | live at 0.1.0 |
phionyx-langchain-langgraph |
unchanged | live at 0.1.0a1 |
phionyx-openai-agents |
unchanged | live at 0.1.0a1 |
phionyx-compliance (new) |
v0.1.0 ship | publish gated on GHA billing |
phionyx-letta (new) |
v0.1.0a1 ship | publish gated on GHA billing |
Substack posts (W4.3)
Two new posts published with this release:
docs/strategic/launch_drafts/substack_posts/post_15_compliance_evidence_drafts.md— Compliance Evidence Drafts: From Envelope Chain to Framework-Shaped Reportdocs/strategic/launch_drafts/substack_posts/post_16_hearthos_bounded_authority.md— HearthOS Bounded-Authority: A Wire-Level Reference for Family-Decision AI
Founder-paced publish window — both are publish-ready when founder schedules.
Acknowledgements
- Reviewer-aligned supplement (2026-05-26) timeline recalibration that compressed v0.7.0 by ~5 months.
- 2026-05-26 Deloitte alignment audit (Viryel-private) for external-landscape grounding.
- Pre-commit governance hooks (12 hooks live since 2026-05-26) for keeping the development chain dense.
License + citation
Same as the rest of the Phionyx stack: AGPL-3.0-or-later. Cite the parent project:
Abak, A. T. (2026). Phionyx Research — Runtime Evidence Layer for Agentic AI. ORCID
0009-0002-3718-4010.
Phionyx Research · v0.7.0 · Compliance Evidence Pack · 2026-05-27