Skip to content

percolation-inversion-compiler-ts v0.4.5

Choose a tag to compare

View all tags
@kadubon kadubon released this 21 Jun 20:00
v0.4.5
38f9ca1

percolation-inversion-compiler-ts v0.4.5

percolation-inversion-compiler-ts is a Node.js and npm package for checking AI agent outputs, validating JSON workflow reports, and keeping unresolved work visible instead of silently treating it as complete. It is a TypeScript-compatible port of the public JSON, CLI, schema, conformance, and safety semantics from the canonical Python implementation.

Canonical Python project: https://github.com/kadubon/percolation-inversion-compiler
Canonical documentation and wiki: https://github.com/kadubon/percolation-inversion-compiler/wiki
Python compatibility target: percolation-inversion-compiler==0.4.4

What this package does

  • Checks AI agent output and returns machine-readable JSON reports.
  • Separates useful candidate work from completed verified work.
  • Preserves blockers, missing obligations, residual notes, and candidate-only reasons.
  • Provides a Node.js CLI and JavaScript/TypeScript SDK for agent runtime workflows.
  • Supports schema validation, packet inspection, phase planning reports, runtime-step reports, adoption reports, and conformance fixtures.

Recommended npm CLI: pic-ts
Compatibility alias: pic

Install and quick start

npm install percolation-inversion-compiler-ts
npx pic-ts agent check --compact --text "Candidate packet: preserve residuals." --profile development

For local agent loops, use pic-ts from npm scripts or npm exec -- pic-ts ... so the same commands work on Windows, macOS, and Linux.

Changes in v0.4.5

  • Runtime report digests now use a real SHA-256 digest in the form sha256:<64 hex characters>.
  • Markdown output is more useful for adoption reports, phase reports, dashboards, observation reports, and autonomy audits.
  • --format markdown --output <path> now writes Markdown to the requested file while JSON output behavior remains unchanged.
  • Packet inspection now detects common Node.js, npm, package-manager, cloud, container, and shell-like command strings such as npm install, npx, node, docker run, and kubectl.
  • Packet inspection remains inert: detected command-like text is reported only and is never executed.
  • Documentation now recommends pic-ts for npm and explains that pic is a compatibility alias that may be confused with the Python CLI.
  • Publish safety checks were hardened to reject unqualified overclaims and package-leak risks.
  • A CHANGELOG.md was added for release tracking.

Safety boundary

This package is a deterministic report generator and validation helper. It does not prove real-world truth, physical outcomes, or artificial superintelligence. It does not grant shell, repository, network, cloud, browser, or model-execution authority.

Important output fields are intentionally separate:

  • accepted: the input passed the relevant public checker for that route.
  • workflow_usable: the result may help a workflow continue.
  • operationally_usable: the result is usable under the selected operational profile.
  • settled: all scoped finite verifier obligations were discharged.

In this package, useful candidate work, adoption readiness, benchmark scores, dashboard metrics, packet inspection, and safe_commands do not imply settled=true. safe_commands are recommendations or display data only; they are not executed automatically.

Compatibility scope

The Python package remains canonical. This TypeScript package targets Python v0.4.4 public behavior for fixture-backed JSON contracts, schema, conformance data, CLI semantics, and safety boundaries. Python-only heavy routes are handled as safe diagnostic compatibility routes that fail closed and preserve residual obligations instead of inventing new TypeScript semantics.

Validation before release

This release candidate passed the local and GitHub Actions release gates:

  • TypeScript typecheck
  • ESLint and Prettier format check
  • Vitest unit and semantic tests
  • Conformance fixtures
  • npm pack safety scan
  • Installed-package smoke tests without Python
  • publint
  • Are The Types Wrong
  • npm audit with high-severity threshold
  • GitHub Actions CI on Node.js 20 and 22
  • Cross-platform installed smoke on Windows, macOS, and Linux

Search terms

Node.js AI agent output checker, npm AI workflow report generator, TypeScript JSON schema validation, LLM output validation, AI agent safety boundary, residual ledger, missing obligations, packet inspection, phase planning, runtime step report, Python compatibility port, conformance fixtures, deterministic certificate service.

Assets 2
Loading