Skip to content

PIC-TS v1.1.0 - Cross-Language Runtime

Latest
Latest

Choose a tag to compare

View all tags
@kadubon kadubon released this 11 Jul 07:09
v1.1.0
3bde373
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

PIC-TS v1.1.0 brings the Python PIC v1.1 meaning and safety contract to Node.js agents.

Quick start

npm install percolation-inversion-compiler-ts@1.1.0
npx pic-ts agent check --compact

Typed runtime APIs are also available from the dedicated subpath:

import {
  compareRuntimeRuns,
  certifyRuntimeAcceleration,
} from "percolation-inversion-compiler-ts/runtime";

What is new

  • runtime compare and runtime certify-acceleration now perform the same resource-matched, direction-aware metric checks as Python PIC.
  • Typed AccelerationMetricComparison results explain improvement, regression, tolerance, and rejection reasons for every metric.
  • AFST freshness, authority, consent, profile gates, residual ordering, and non-execution flags are aligned with Python.
  • Unknown phase coordinates remain unknown; BIT gains need witnesses; SQOT uses measured costs; ALT revalidates evidence; TRC uses finite traces.
  • Approval-bound operations expose adapter-check -> plan -> preflight -> approve -> dispatch -> verify -> reconcile with Ed25519/JCS compatibility, replay protection, SSRF controls, bounded I/O, and independent verification.
  • Canonical CamelCase schemas are pinned to Python PIC v1.1.0 main commit 61c4fa77b163791d510006ccaea9de238f70149b; legacy TypeScript schema IDs remain available for compatibility.
  • Schema metadata generation is now independent of CRLF/LF line endings, and the package is tested on Node 20/22 across Linux, Windows, and macOS.

Safety boundary

PIC-TS does not prove real ASI, consciousness, legal authority, consent, or a physical outcome. Ordinary checks and AFST commands never dispatch side effects. physical_outcome_proven remains false; only a separately validated verifier report with matching scope and observation window can set physical_outcome_verified=true.

Compatibility

v1.1.0 is additive and keeps the v1 CLI and public entry points. Strict CLI and interop boundaries reject coerced numeric strings, string booleans, non-finite values, and ambiguous timestamps. Node.js 20 or newer is required.

See the README, docs/migration-v1.1.md, docs/resource-matched-measurement.md, docs/cross-language-contract.md, and docs/operation-security.md.

Assets 2
Loading