percolation-inversion-compiler-ts 0.4.4

package/LICENSE

@@ -0,0 +1,152 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and
+distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright
+owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities
+that control, are controlled by, or are under common control with that entity.
+For the purposes of this definition, "control" means (i) the power, direct or
+indirect, to cause the direction or management of such entity, whether by
+contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising
+permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including
+but not limited to software source code, documentation source, and configuration
+files.
+
+"Object" form shall mean any form resulting from mechanical transformation or
+translation of a Source form, including but not limited to compiled object code,
+generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made
+available under the License, as indicated by a copyright notice that is included
+in or attached to the work.
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that is
+based on or derived from the Work and for which the editorial revisions,
+annotations, elaborations, or other modifications represent, as a whole, an
+original work of authorship. For the purposes of this License, Derivative Works
+shall not include works that remain separable from, or merely link (or bind by
+name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version
+of the Work and any modifications or additions to that Work or Derivative Works
+thereof, that is intentionally submitted to Licensor for inclusion in the Work by
+the copyright owner or by an individual or Legal Entity authorized to submit on
+behalf of the copyright owner. For the purposes of this definition, "submitted"
+means any form of electronic, verbal, or written communication sent to the
+Licensor or its representatives, including but not limited to communication on
+electronic mailing lists, source code control systems, and issue tracking systems
+that are managed by, or on behalf of, the Licensor for the purpose of discussing
+and improving the Work, but excluding communication that is conspicuously marked
+or otherwise designated in writing by the copyright owner as "Not a
+Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of
+whom a Contribution has been received by Licensor and subsequently incorporated
+within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this
+License, each Contributor hereby grants to You a perpetual, worldwide,
+non-exclusive, no-charge, royalty-free, irrevocable copyright license to
+reproduce, prepare Derivative Works of, publicly display, publicly perform,
+sublicense, and distribute the Work and such Derivative Works in Source or Object
+form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this License,
+each Contributor hereby grants to You a perpetual, worldwide, non-exclusive,
+no-charge, royalty-free, irrevocable patent license to make, have made, use,
+offer to sell, sell, import, and otherwise transfer the Work, where such license
+applies only to those patent claims licensable by such Contributor that are
+necessarily infringed by their Contribution(s) alone or by combination of their
+Contribution(s) with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity alleging that the Work or a
+Contribution incorporated within the Work constitutes direct or contributory
+patent infringement, then any patent licenses granted to You under this License
+for that Work shall terminate as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or
+Derivative Works thereof in any medium, with or without modifications, and in
+Source or Object form, provided that You meet the following conditions:
+
+(a) You must give any other recipients of the Work or Derivative Works a copy of
+this License; and
+
+(b) You must cause any modified files to carry prominent notices stating that You
+changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works that You
+distribute, all copyright, patent, trademark, and attribution notices from the
+Source form of the Work, excluding those notices that do not pertain to any part
+of the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its distribution, then
+any Derivative Works that You distribute must include a readable copy of the
+attribution notices contained within such NOTICE file, excluding those notices
+that do not pertain to any part of the Derivative Works, in at least one of the
+following places: within a NOTICE text file distributed as part of the Derivative
+Works; within the Source form or documentation, if provided along with the
+Derivative Works; or within a display generated by the Derivative Works, if and
+wherever such third-party notices normally appear. The contents of the NOTICE
+file are for informational purposes only and do not modify the License. You may
+add Your own attribution notices within Derivative Works that You distribute,
+alongside or as an addendum to the NOTICE text from the Work, provided that such
+additional attribution notices cannot be construed as modifying the License.
+
+You may add Your own copyright statement to Your modifications and may provide
+additional or different license terms and conditions for use, reproduction, or
+distribution of Your modifications, or for any such Derivative Works as a whole,
+provided Your use, reproduction, and distribution of the Work otherwise complies
+with the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any
+Contribution intentionally submitted for inclusion in the Work by You to the
+Licensor shall be under the terms and conditions of this License, without any
+additional terms or conditions. Notwithstanding the above, nothing herein shall
+supersede or modify the terms of any separate license agreement you may have
+executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names,
+trademarks, service marks, or product names of the Licensor, except as required
+for reasonable and customary use in describing the origin of the Work and
+reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in
+writing, Licensor provides the Work on an "AS IS" BASIS, WITHOUT WARRANTIES OR
+CONDITIONS OF ANY KIND, either express or implied, including, without limitation,
+any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or
+FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any risks
+associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in
+tort (including negligence), contract, or otherwise, unless required by
+applicable law or agreed to in writing, shall any Contributor be liable to You
+for damages, including any direct, indirect, special, incidental, or
+consequential damages of any character arising as a result of this License or out
+of the use or inability to use the Work, even if such Contributor has been
+advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the Work or
+Derivative Works thereof, You may choose to offer, and charge a fee for,
+acceptance of support, warranty, indemnity, or other liability obligations and/or
+rights consistent with this License. However, in accepting such obligations, You
+may act only on Your own behalf and on Your sole responsibility, not on behalf of
+any other Contributor, and only if You agree to indemnify, defend, and hold each
+Contributor harmless for any liability incurred by, or claims asserted against,
+such Contributor by reason of your accepting any such warranty or additional
+liability.
+
+END OF TERMS AND CONDITIONS

package/NOTICE

@@ -0,0 +1,21 @@
+Percolation Inversion Compiler
+Copyright 2026 K. Takahashi
+
+This product includes software developed for finite certificate compilation
+interfaces derived from the following CC-BY-4.0 research artifacts:
+
+- Takahashi, K. (2026). Executable Capability Percolation Theory. Zenodo.
+  https://doi.org/10.5281/zenodo.20535654
+- Takahashi, K. (2026). Bottleneck Inversion Theory: Machine-Readable Witness
+  Calculus for Unlockable Potential. Zenodo.
+  https://doi.org/10.5281/zenodo.20545356
+- Takahashi, K. (2026). Typed Reality Compilation: Operational Tolerance
+  Allocation for Resource-Efficient Cyber-Physical Frontier Compilation. Zenodo.
+  https://doi.org/10.5281/zenodo.20554083
+- Takahashi, K. (2026). Salience-Queue Occupation Theory. Zenodo.
+  https://doi.org/10.5281/zenodo.20526451
+- Takahashi, K. (2026). Abstraction Liquidity Theory. Zenodo.
+  https://doi.org/10.5281/zenodo.20476200
+
+The cited papers are not vendored in this repository. Extractors operate on
+user-provided TeX sources or externally obtained canonical artifacts.

package/README.md

@@ -0,0 +1,255 @@
+# percolation-inversion-compiler-ts
+
+AI agent output checker and workflow report generator for Node.js.
+
+`percolation-inversion-compiler-ts` helps a JavaScript or TypeScript agent turn
+draft output, local runtime files, agent messages, and packet sidecars into
+structured JSON reports. The reports show what is accepted, what is usable for a
+workflow, what still needs checking, and what must not be treated as completed
+work.
+
+This npm package is a TypeScript port of the public JSON, CLI, schema,
+conformance fixture, and safety behavior of
+`percolation-inversion-compiler` v0.4.4. The Python package remains the
+canonical implementation:
+
+- Canonical repository:
+  [kadubon/percolation-inversion-compiler](https://github.com/kadubon/percolation-inversion-compiler)
+- Canonical wiki:
+  [percolation-inversion-compiler Wiki](https://github.com/kadubon/percolation-inversion-compiler/wiki)
+
+## What It Does
+
+Use this package when an agent output should be checked before it is reused,
+sent to another agent, turned into a packet, or used to plan the next workflow
+step.
+
+In plain terms, it answers:
+
+- What did the agent claim?
+- Is the JSON envelope accepted by the checker?
+- Can this report guide the next safe workflow step?
+- What evidence, identity, or verification work is still missing?
+- Which command or SDK call can inspect the next step?
+- Which content must remain candidate-only and not be promoted to completed
+  work?
+
+The package is local-first and Python-free at runtime. It does not execute
+arbitrary shell commands, mutate repositories, crawl in the background, or prove
+real-world truth.
+
+## Quick Start
+
+Install from npm:
+
+```sh
+npm install percolation-inversion-compiler-ts
+```
+
+Run a compact agent check:
+
+```sh
+npx pic-ts agent check --compact --text "Candidate packet: preserve residuals." --profile development
+```
+
+Plan the next workflow step:
+
+```sh
+npx pic-ts phase plan --compact --text "Candidate packet: preserve residuals." --profile development
+```
+
+The package exposes two command names:
+
+- `pic-ts`: recommended for npm and Node.js projects.
+- `pic`: compatibility bin matching the Python CLI command name.
+
+## Run The Node-Only Agent Loop
+
+This loop works without Python. It creates demo input files, checks one runtime
+step, exports the result as inert packet data, inspects that packet without
+executing embedded text, and builds a phase plan from a request JSON file.
+
+```sh
+npx pic-ts demo bootstrap --output-dir .pic-demo --overwrite
+npx pic-ts agent check --compact --text "Candidate packet: preserve residuals." --profile development
+npx pic-ts runtime step --state .pic-demo/runtime_state.json --input .pic-demo/runtime_step_input.json --output .pic-demo/runtime_step_report.generated.json
+npx pic-ts packet export --report .pic-demo/runtime_step_report.generated.json --output .pic-demo/packet.json
+npx pic-ts packet inspect --packet .pic-demo/packet.json
+npx pic-ts phase plan --request .pic-demo/asi_proxy_phase_request.json --compact
+npx pic-ts agent accelerate --compact --text "Candidate packet: preserve residuals." --profile development
+```
+
+This is the practical npm version of the ASI-proxy loop: verified candidate work
+is preserved, missing work is kept visible, and bottlenecks are routed to finite
+checks. It is not a claim that real ASI, physical outcomes, simulator truth, or
+oracle truth has been proven.
+
+## Common Commands
+
+Check agent output:
+
+```sh
+npx pic-ts agent check --compact --text "Candidate packet: route evidence and preserve residuals." --profile development
+npx pic-ts agent intake --text "Candidate packet: route evidence and preserve residuals." --profile development
+npx pic-ts agent runbook --profile development
+```
+
+Plan workflow repair:
+
+```sh
+npx pic-ts phase plan --compact --profile development
+npx pic-ts phase gap --compact --profile development
+npx pic-ts phase runbook --profile development
+```
+
+Run the bundled runtime fixture:
+
+```sh
+npx pic-ts runtime step --state fixtures/python_v044_demo/runtime_state.json --input fixtures/python_v044_demo/runtime_step_input.json
+```
+
+Work with packets as data:
+
+```sh
+npx pic-ts packet export --report fixtures/python_v044_demo/runtime_step_report.json --output packet.json
+npx pic-ts packet inspect --packet packet.json
+```
+
+Inspect schemas and conformance fixtures:
+
+```sh
+npx pic-ts schema --type PhaseAccelerationPlan
+npx pic-ts portability verify --manifest fixtures/portability_conformance/manifest.json
+npx pic-ts snapshot list
+```
+
+## Use From JavaScript
+
+Root import:
+
+```ts
+import {
+  buildPhaseAccelerationPlan,
+  phaseAccelerationCompactPayload,
+  runAgentCheck,
+  schemaByType,
+  verifyPortabilityManifest,
+} from "percolation-inversion-compiler-ts";
+
+const check = runAgentCheck(
+  { agent_output: "Candidate packet: preserve residuals." },
+  true,
+);
+
+const plan = phaseAccelerationCompactPayload(
+  buildPhaseAccelerationPlan({ compact: true }),
+);
+
+const schema = schemaByType("PhaseAccelerationPlan");
+```
+
+Subpath imports for agent runtimes:
+
+```ts
+import { schemaByType } from "percolation-inversion-compiler-ts/schema";
+import { createAgentMessage } from "percolation-inversion-compiler-ts/agent/messages";
+import { packetEnvelopeFromRuntimeReport } from "percolation-inversion-compiler-ts/packet";
+```
+
+## How To Read The JSON
+
+The JSON fields are intentionally separate:
+
+| Field                  | Plain meaning                                                                        |
+| ---------------------- | ------------------------------------------------------------------------------------ |
+| `accepted`             | The input envelope passed the finite checks for this command.                        |
+| `workflow_usable`      | The report can guide the next workflow step. This is not settlement.                 |
+| `operationally_usable` | The deeper runtime result can be used under the selected profile.                    |
+| `settled`              | All scoped finite obligations are discharged. This is often `false`.                 |
+| `missing_obligations`  | Work that is still missing, such as evidence, identity, route, or verifier checks.   |
+| `residual_ledger`      | Remaining debt, limits, or unresolved work that must stay visible.                   |
+| `safe_commands`        | Suggested inspection commands. They are not permission to execute arbitrary actions. |
+
+`settled=false` is not a command failure. It usually means the checker preserved
+unfinished work instead of hiding it.
+
+## Safety Limits
+
+This package is designed for safe local inspection and agent workflow routing.
+
+It does not:
+
+- prove real ASI or general intelligence;
+- prove physical, simulator, policy, legal, or oracle outcomes;
+- grant shell, repository, network, or model-mutation authority;
+- treat agent text, registry metadata, or queue priority as verified evidence;
+- silently promote unresolved obligations to `settled=true`;
+- execute packet content or command-like strings embedded in messages.
+
+Heavy routes that would require Python-only services, live connectors, local
+runtime stores, repository mutation, or external verifier authority are exposed
+as safe diagnostic compatibility routes. They fail closed with
+`operationally_usable=false`, `settled=false`,
+`execution_authority_granted=false`, visible residual ledgers, and visible
+missing obligations.
+
+## Python Canonical Implementation
+
+The canonical implementation is the Python package
+`percolation-inversion-compiler==0.4.4`.
+
+Use the Python project when you need the canonical source implementation,
+Python SDK behavior, optional Python sidecars, or the full project
+documentation:
+
+- Repository:
+  [https://github.com/kadubon/percolation-inversion-compiler](https://github.com/kadubon/percolation-inversion-compiler)
+- Wiki:
+  [https://github.com/kadubon/percolation-inversion-compiler/wiki](https://github.com/kadubon/percolation-inversion-compiler/wiki)
+
+This TypeScript package keeps the same public JSON meaning for npm and Node.js
+agent runtimes. It does not vendor the canonical TeX or PDF papers, and it does
+not copy Python internals line by line.
+
+## Compatibility
+
+| Command family                                                                                                                                                                                        | Compatibility claim                                                                                         |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
+| `agent check`, `agent intake`, `agent runbook`, `agent autonomy-audit`, `agent manifest`, `agent communication-guide`                                                                                 | Exact Python v0.4.4 golden JSON for bundled fixture-backed modes.                                           |
+| `phase plan`, `phase gap`, `phase runbook`, `phase benchmark`, `phase benchmark-suite`, `phase dashboard`, `phase observe`                                                                            | Exact Python v0.4.4 golden JSON for static fixtures; dynamic `--request` preserves public v0.4.4 semantics. |
+| `runtime step`, `schema`, `snapshot`, `routes`, `portability`, `adoption`, `identity`, `demo installed-smoke`                                                                                         | Python v0.4.4 golden JSON or bundled canonical schema and fixture semantics.                                |
+| `agent message`, `agent inbox`, `packet`, Node-only demo bootstrap                                                                                                                                    | npm/Node sidecar implementation with the same non-promotion and residual-preservation rules.                |
+| evidence heavy routes, runtime service/store/heavy actions, SQOT audit, ALT heavy routes, ecology heavy routes, ECPT heavy routes, audit/extract/check/coverage/parse/provenance/sbom/demo datacenter | Safe diagnostic compatibility only.                                                                         |
+
+## Development And Publishing Checks
+
+Run the local gate before publishing:
+
+```sh
+npm run typecheck
+npm run lint
+npm run format:check
+npm run test
+npm run conformance
+npm run pack:check
+npm run installed:smoke
+npm run publint
+npm run attw
+npm audit --audit-level=high
+npm run prepublishOnly
+```
+
+The package uses a `files` whitelist. The publish safety check rejects local
+paths, obvious secrets, TeX/PDF sources, archives, source maps, model weights,
+private keys, dependency folders, and private data paths.
+
+## Search Terms
+
+AI agent output checker, workflow report generator, Node.js agent runtime, npm
+agent checker, LLM output validation, AI workflow verification, JSON report,
+safe reuse check, evidence routing, verifier routing, residual ledger,
+unresolved work ledger, missing obligations, packet export, packet inspection,
+agent-to-agent message checking, runtime step report, phase planning, workflow
+bottleneck planning, portability conformance, JSON schema validation,
+percolation inversion compiler, PIC, ECPT, BIT, TRC, SQOT, ALT, ASI-proxy
+workflow loop.

package/dist/agent/messages.d.ts

@@ -0,0 +1,23 @@
+interface AgentMessageCreateOptions {
+    sender: string;
+    text: string;
+    receiver?: string;
+    nonce?: string;
+}
+interface MessagePolicyOptions {
+    profile?: string;
+    seenNonces?: string[];
+    identityContextPath?: string;
+}
+declare function createAgentMessage(options: AgentMessageCreateOptions): Record<string, unknown>;
+declare function readAgentMessage(path: string): Record<string, unknown>;
+declare function agentMessageContract(message: Record<string, unknown>): Record<string, unknown>;
+declare function verifyAgentMessage(message: Record<string, unknown>, options?: MessagePolicyOptions): Record<string, unknown>;
+declare function initAgentInbox(path: string, inboxId?: string): Record<string, unknown>;
+declare function readAgentInbox(path: string): Record<string, unknown>;
+declare function writeAgentInbox(path: string, inbox: Record<string, unknown>): void;
+declare function appendAgentMessage(inboxPath: string, message: Record<string, unknown>): Record<string, unknown>;
+declare function deliveryReport(action: string, inboxRef: string, inbox: Record<string, unknown>, reports: Array<Record<string, unknown>>, profile?: string): Record<string, unknown>;
+declare function receiveAgentInbox(inboxPath: string, options?: MessagePolicyOptions): Record<string, unknown>;
+
+export { type AgentMessageCreateOptions, type MessagePolicyOptions, agentMessageContract, appendAgentMessage, createAgentMessage, deliveryReport, initAgentInbox, readAgentInbox, readAgentMessage, receiveAgentInbox, verifyAgentMessage, writeAgentInbox };