Skip to content

V0.2_PYLON_RELEASE_AUDIT.md

Latest commit

 

History

History
160 lines (125 loc) · 7.14 KB

V0.2_PYLON_RELEASE_AUDIT.md

File metadata and controls

160 lines (125 loc) · 7.14 KB
Raw

Qwen Legal Pylon Boundary v0.2 Readiness Audit

Date: 2026-05-22 Repo: psionic Scope: Qwen legal Pylon training, user-distributed Pylon workers, payment decision/settlement proof boundary, telemetry, public-network contracts, and Psionic boundary identity.

Verdict

Psionic has a v0.2.0 source boundary for the Qwen legal Pylon worker and scheduler path, with the boundary stated in RELEASE_V0.2.0.md.

This is not the OpenAgents public Pylon v0.2 release record. Psionic owns a worker/scheduler/payment-proof boundary that OpenAgents Pylon releases can consume; it does not publish the public Pylon package, public Pylon release tag, or Nexus/Omega release gate.

This is not a claim that Psionic itself custodies or spends funds. The release is useful because Psionic now owns the parts that belong in this repo: signed remote job dispatch, worker receipt verification, payment decision receipts, Treasury handoff batches, live-small-value-compatible settlement proof validation, mandatory Pylon telemetry, stable public-network contracts, and an executable release gate.

Treasury or Nexus still owns the actual wallet operation that returns a live payment hash, transaction proof, or operator-approved deferral.

Boundary Identity

  • Workspace boundary version: 0.2.0
  • Boundary manifest: RELEASE_V0.2.0.md
  • Boundary gate: scripts/check-v0.2-pylon-release.sh
  • Retained gate report: reports/qwen-legal-v02-pylon-release-readiness-20260522.md
  • Worker server: cargo run -p psionic-train --bin qwen_legal_pylon_worker_server -- <bind-addr> <worker-id>
  • Supported dispatch modes: LocalOnly, Loopback, Tailnet, Production

Readiness Matrix

Area Status Evidence
Local/loopback Pylon execution Ready Qwen legal Pylon dispatch tests pass; Pylon network SFT checker remains in the release gate.
Remote Pylon dispatch Ready Tailnet and production modes now use signed TCP envelopes; tests cover a remote TCP worker.
Worker entrypoint Ready qwen_legal_pylon_worker_server serves one signed worker job over TCP and exits.
Scheduler/worker integrity Ready Scheduler verifies envelopes before dispatch; worker verifies scheduler signature before execution; scheduler verifies returned worker receipt signature before marking work payable.
Payment decisioning Ready Payable, withheld, duplicate-shard, failed-payment, deferred, and live-small-value operator-approved settlement paths are tested.
Wallet execution External Psionic validates settlement proofs but does not custody secrets or execute wallet sends.
Telemetry Ready Transport events and worker receipts now include the mandatory Pylon fields for operation and reconciliation.
Public-network contracts Ready Contract generator/checker graph is stable after removing the upstream/downstream digest cycle.
Boundary gate Ready scripts/check-v0.2-pylon-release.sh captures the v0.2 validation suite.

Remote Dispatch

The prior blocker was that Tailnet and Production were named modes but explicitly returned BlockedModeNotImplemented. That is closed.

The current protocol is:

  1. Scheduler builds a QwenLegalSignedJobEnvelope.
  2. Scheduler verifies the envelope digest and Ed25519 scheduler signature before writing or dispatching it.
  3. Tailnet/production mode connects to tcp://host:port, tailnet://host:port, or raw host:port.
  4. The worker server verifies the scheduler signature before running the job.
  5. The worker writes expected outputs, signs the receipt, sends the receipt on the same TCP connection, and exits.
  6. The scheduler verifies receipt digest, signable payload digest, and worker Ed25519 signature before recording payment as payable.

The release intentionally leaves transport encryption and network admission to the operator's Tailnet/private-network/gateway policy. The repo-level integrity checks are signed envelopes and signed receipts.

Payments

The v0.2 claim is "payments are wired through the Psionic boundary," not "Psionic is a wallet." The repo now proves:

  • accepted worker receipts become payable payment decisions
  • duplicate successful shard submissions are withheld
  • invalid or missing receipts are withheld
  • Treasury handoff batches are generated from payable decisions
  • settled, failed, deferred, duplicate, unknown-authorization, amount-mismatch, bad-digest, and secret-bearing proof paths are enforced
  • live-small-value operator-approved proofs require a settlement time and a payment hash or transaction proof
  • the promotion gate becomes PaymentSettled only when accepted payable work is settled; it becomes DeferredByOperator only with an explicit valid deferred policy

External wallet execution remains a Treasury/Nexus dependency. A production operator must attach the returned proof; Psionic rejects proofs that contain wallet secret material.

Telemetry

Transport events now retain:

  • request digest and request byte count
  • response digest and response byte count
  • endpoint and transport family
  • scheduler signature verification flag
  • worker signature presence flag
  • worker receipt digest
  • worker receipt verification flag

Worker receipts now retain:

  • input and output artifact counts
  • required output artifact count
  • output byte total
  • runtime milliseconds
  • shard index, shard count, and shard start/end indexes
  • agreed price and max cost
  • success state
  • existing hardware, version, git, logs hash, artifact hashes, signature, and payment fields

This is enough to debug the common v0.2 operator failures: unreachable worker, bad envelope signature, missing output, empty response, invalid receipt, duplicate shard, budget mismatch, and payment-proof mismatch.

Contract Stability

The public-network/payment checker failures were caused by an upstream digest cycle. The provider-neutral training evidence bundle hashed downstream public network contracts; those downstream contracts depended back on the run graph; the run graph depended on the evidence bundle.

The fix keeps downstream explorer/public contracts as declared path references inside the upstream evidence bundle. Each downstream contract still carries and checks its own authoritative contract_digest.

The v0.2 boundary gate now includes the evidence bundle, run graph, decentralized network, registry, assignment, dataset, miner, validator, consensus, fraud, reward, settlement, bootstrap, explorer, readiness, curated, open, and incentivized public-run checkers.

Remaining Non-Blockers

  • Production key custody still needs a real operator key-rotation story beyond deterministic local test keys. This is acceptable for v0.2.0 only because the release is a source/operator release with explicit identity boundaries.
  • The current worker server is one-job-per-process. Operators should run it under a supervisor or wrapper until a long-lived daemon lands.
  • Issue #985 remains open for MedPsy CUDA parity. It does not block the Qwen legal Pylon boundary.

Boundary Gate

Before tagging:

scripts/check-v0.2-pylon-release.sh

The script compiles the worker server, runs dispatch/payment tests, runs the Pylon network SFT checker, and checks the public-network/payment contract set.