-
Notifications
You must be signed in to change notification settings - Fork 0
Node Only Agent Loop
This page shows a local loop that works from npm without Python.
The goal is practical: preserve useful candidate work, keep missing work visible, and produce JSON reports that another agent or CI job can inspect.
npx pic-ts demo bootstrap --output-dir .pic-demo --overwriteThis creates small JSON files for a runtime state, runtime input, phase request, and threshold example.
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.jsonThe result is a JSON report. It can be useful even when settled=false.
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.jsonPacket content is inert data. The inspector may detect command-like text such
as npm, node, docker, kubectl, curl, bash, or powershell, but it
does not run it.
npx pic-ts phase plan --request .pic-demo/asi_proxy_phase_request.json --compact
npx pic-ts phase gap --request .pic-demo/asi_proxy_phase_request.json --compactCandidate-only intake does not reduce the phase gap. Missing obligations and blockers remain visible.
npx pic-ts phase lab init --output-dir .pic-lab
npx pic-ts phase lab ingest --store .pic-lab --report .pic-demo/runtime_step_report.generated.json
npx pic-ts phase lab observe --store .pic-lab
npx pic-ts phase lab graph --store .pic-lab
npx pic-ts phase lab closure --store .pic-lab
npx pic-ts phase lab executable-paths --store .pic-lab
npx pic-ts phase lab threshold-status --store .pic-lab --threshold .pic-demo/asi_proxy_development.jsonThe lab stores JSON/JSONL records. It records file basenames, not absolute local paths.
npx pic-ts agent accelerate --compact --text "Candidate packet: preserve residuals." --profile developmentThis is a report generator. It does not execute shell commands or mutate a repository.
The loop is useful for Node.js agent runtimes because it produces structured reports that can be reused safely.
It does not prove real ASI, physical outcomes, simulator truth, policy truth, or oracle truth. It preserves unfinished work and shows the next finite checks.
- Home
- Quickstart
- Getting Started
- Acceleration Measurement
- Operation Guide
- AFST Satisfaction Flux
- Python TypeScript Compatibility
- Security
- Node Only Agent Loop
- ASI Proxy Loop v0.9
- Token Reports and Agent Loop
- ASI Proxy Acceleration
- CCR Interop
- MCP And A2A Safety
- Operation Gate
- Phase Ecology Lab
- CLI Recipes
- JavaScript SDK
- Diagnostic Commands
- How To Read The JSON
- Agent Guide
- Agent Messages and Packets
- Schemas and Conformance
- Safety and Limits
- Compatibility With Python
- npm Package and Release Checks
- Use Cases
- Core Concepts
- Concepts in Plain Language
- What PIC Does Not Do
- Theory Map
- Glossary
- FAQ
- v1.1 Release Notes
- v0.9.0 Release Notes
- v0.8.0 Release Notes
- v0.7.0 Release Notes
- v0.6.0 Release Notes
- v0.5.0 Release Notes