Emit canonical authorization records from deterministic action gates

[safal207]

Goal

Add an interoperability exporter that converts PythiaLabs deterministic gate decisions into canonical authorization_record artifacts for downstream lifecycle joins.

Canonical profile: safal207/Liminal#108

Why

PythiaLabs already evaluates proposed agent actions before tool execution using evidence, authorization, environment, credential, temporal, and recovery context. The decision trace should be exportable in a stable provider-neutral shape so another runtime can later attach the actual observation and response-integrity verdict.

Deliverables

• Add a canonical authorization export schema containing:
  • action identity and canonical arguments digest;
  • gate/profile identifier and version;
  • evidence references used at decision time;
  • decision and stable reason codes;
  • decision timestamp and evaluation clock;
  • validity/expiry interval;
  • approval and credential state;
  • environment/target-state digest;
  • continuation or revalidation requirements;
  • artifact digest and verification metadata.
• Add exporters for the current infrastructure, banking-risk, and Web3 treasury showcases.
• Add a portable adapter that does not expose Elixir-specific internal terms as normative fields.
• Add a downstream observation handoff example.
• Add a joined demo using an externally supplied response-integrity record.

Required fixtures

• accepted reversible action;
• blocked destructive action without approval;
• expired temporal authorization;
• target-state drift after decision;
• evidence updated after decision but before execution;
• accepted action followed by matching observation;
• accepted action followed by contradicted external response claim.

Boundary

• PythiaLabs produces deterministic pre-execution decisions.
• It does not certify the truthfulness of a later model response.
• Imported observation/integrity records remain independently attributed.

Acceptance criteria

• The same semantic decision produces stable canonical bytes and digest.
• A downstream verifier can determine what was authorized, when, and against which evidence snapshot.
• Temporal and target-state drift remain visible after export.
• Authority, observation, and response-integrity verdicts are not collapsed.
• Fixtures align with Liminal#108.

[safal207]

Implementation started in draft PR #205:

#205

The PR adds:

• a provider-neutral PythiaLabs authorization_record profile;
• JSON Schema;
• seven fixtures across infrastructure, banking-risk, and Web3 treasury showcases;
• deterministic canonicalization and SHA-256 record references;
• explicit evidence, environment, target-state, expiry, and revalidation bindings;
• downstream observation and external response-integrity handoff examples.

The implementation preserves PythiaLabs as the pre-execution authority layer. Observation and response-integrity verdicts remain independently issued and attributed.

The PR remains draft while automated review and CI status are pending.

[safal207]

Completed and merged via #205.

The v0.1 PythiaLabs authorization export now includes:

• provider-neutral authorization records across infrastructure, banking-risk, and Web3 treasury showcases;
• RFC 8785/JCS canonicalization with pinned SHA-256 references;
• Draft 2020-12 JSON Schema validation;
• independently derived temporal, drift, approval, credential, and verification authority state;
• independently derived observation and response-integrity join outcomes;
• explicit zero-side-effect expectations for blocked, expired, and revalidation-required authority;
• adversarial tests for forged authority, forged joins, malformed schema values, JCS number encoding, and post-export list mutation;
• a dedicated Authorization Export CI workflow.

CI, Security, Authorization Export, and CodeRabbit were green before merge, and all review threads were resolved.

Squash merge commit: 9231876592536cdea5f04a61f81e06f042e6de56.