FoldEngine Stabilized.

FoldEngine · proof / evaluator surface · runtime component

PASR Local

A local evaluator/runtime package and pre-intervention stability gate for AI-assisted actions, operator workflows, simulators, and adapter proposals — offline on your machine or in Docker.

PASR Local remains the intervention-governance runtime and evaluator / proof surface behind FoldEngine product assemblies. It is not the whole product hierarchy. See the FoldEngine product line →

PASR Local is a local white-box governance runtime for proposed interventions: it gates the action, records bounded decision events, reconstructs the intervention geometry, and exports safe human/JSON/JSONL artifacts without exposing the private FoldEngine memory engine.

  • Evaluator/runtime package — not the whole offline product line
  • Not autonomous action execution
  • Not safety-certified
  • Offline products are not public GA
  • Public sale is not opened

What PASR does

PASR Local is a pre-intervention stability gate. Before a proposed intervention becomes an action, PASR dry-runs it, checks readiness, blocks unready or out-of-policy paths, explains why, and exports evidence.

  1. 1Proposal
  2. 2Dry-run
  3. 3Gate
  4. 4Block / allow
  5. 5Evidence
  6. 6Readout
What the evaluation package includes

PASR Local helps evaluate proposed interventions before they become effects. It produces bounded decisions, evidence / readouts, intervention memory, and local continuity material. It is a component and runtime inside FoldEngine's containerized products — the main product line — and a proof / evaluator surface. It is not the whole product story by itself.

The current PASR package supports bounded intervention classes only:

  • HOST_UI_EVENT — host / UI events
  • SIMULATED_EFFECT — simulated effects
  • ADAPTER_PROPOSAL — adapter proposals
  • Evidence packs
  • Human-readable readouts
  • Local / container run path
  • Mac, Linux, and Pi / Edge no-hardware profiles

PASR's deployment-profile language is now being generalized across the FoldEngine product family through the Product Container Shell standard. Pi / edge is a deployment target, not a product, and is claimed only where validated.

PASR also fits human-facing systems such as prompts, journey transitions, and operator cues where an intervention should be checked before it reaches the person.

What it is not

PASR does not control actuators. PASR governs whether a proposed actuator-related intervention is allowed to proceed toward the manufacturer's control plane.

PASR Local is deliberately bounded — not autonomous action execution, not safety-certified, not a robot controller, and not a replacement for the offline product line.

Full boundary detail

PASR Local is deliberately bounded. To avoid overclaiming, here is what it is not:

  • It is not a physical actuator controller — physical actuator execution remains outside the current package and requires a separate future safety profile.
  • It is not safety-certified.
  • It is not a robot controller, and it does not control hardware.
  • It is not a cloud service, and there is no cloud dependency for local evaluation.
  • It is not a native app or installer yet, and not a C/C++ ABI release yet.
  • There is no hardware execution in the current package; the evaluation uses no privileged Docker, no /dev mount, and no host network mode.
  • It is not the private FoldEngine Memory engine, and it does not expose FoldEngine Memory internals.
  • It is not a raw memory dump, and not resonance / Core3 / Codex exposure.
  • It is not a ROS/ROS2 runtime today, and it does not replace ROS/ROS2.
  • It does not do ledger writes today.
How PASR relates to Stabilized Loop, Riverbed, Import Spine, and SEAM

Stabilized Loop is a shared runtime primitive inside the product line — not a standalone product. PASR substrate, Riverbed, Import Spine, and the SEAM / packet chain are shared components underneath containerized products. PASR Local is the evaluator/runtime package that gates proposed interventions; it does not replace those products or claim to be the whole hierarchy.

PASR vs Trial Probe

Trial Probe finds the unstable seam. PASR gates the intervention.

Trial Probe

  • Strategic diagnostic
  • Asks: what does the evidence allow us to conclude?
  • Output: reviewed report
  • Ledger role: a report can become a continuity entry later
View Trial Probe →

PASR Local

  • Tactical intervention gate
  • Asks: should this proposed intervention proceed right now?
  • Output: evidence pack, readout, evaluator return packet
  • Ledger role: an evidence pack / return packet can become continuity evidence later

PASR Local Evaluation Pack

Proof / evaluator pack

The Evaluation Pack is a proof and evaluation aid, not the main product line. It is for teams evaluating whether proposed AI, operator, simulator, or workflow interventions should be gated before they proceed. For finished products, see the FoldEngine product line.

PASR Evaluation Pack is currently available for bounded technical evaluation and guided pilot discussions. Delivery is manual while the product is in early evaluation.

Evaluation pack contents and expected demo

You receive a local evaluation artifact and a guided return path:

  • PASR release tarball
  • SHA256 checksum and manifest
  • external evaluator quickstart
  • archive verifier
  • Docker config / smoke / readout path
  • expected BLOCKED demo result
  • evaluator return packet workflow
  • optional guided review call

Expected demo result

  • Decision: BLOCKED
  • Reason: Actuation plane not ready
  • Mapped operator action: WAIT_FOR_PLANE_READY
  • Hardware touched: No
  • Simulated effect emitted: No

BLOCKED is expected in the default demo. It shows PASR refusing to proceed when the intervention plane is not ready — the gate working as designed, not a failure.

Two evaluations

Gate-only evaluation

Shows that BLOCKED is expected: PASR can stop an unready intervention and export evidence.

Memory-loop evaluation

Shows repeated blocked interventions forming a crease and producing a bounded memory readout / export.

The gate-only demo proves PASR can stop an unready intervention. The memory-loop evaluation proves PASR can remember bounded intervention decisions, reconstruct the shape of repeated decisions, and show the operator what pattern is forming.

An opt-in Docker memory-loop evaluation is available for technical review:

docker compose -f docker-compose.pasr.yml run --rm pasr-memory-loop-eval

Intentionally not included: no hardware execution, not a physical actuator controller, and no cloud dependency for local evaluation.

From gate to intervention memory

PASR Local is no longer only a one-off gate. Each gated decision can feed a bounded local memory loop, so PASR can show the operator what pattern is forming across repeated interventions:

  1. proposed intervention
  2. → PASR gate / evidence
  3. → bounded decision event
  4. → append-only local memory
  5. → geometry snapshot
  6. → intervention_memory readout
  7. → human / JSON / JSONL export

What the pattern means

  • repeated BLOCK events form a crease
  • NOT_READY forms a readiness seam
  • WAIT_FOR_PLANE_READY becomes the suggested stitch / operator action

See a memory-loop sample output →

How PASR is packaged

Layer 1 — PASR Local Runtime

Gate proposed interventions and create evidence.

Layer 2 — FoldEngine Memory

Private geometric memory / projection / resonance system. Not exposed in evaluation exports.

Layer 3 — Export Adapters

Human-readable Markdown, bounded JSON, and event-only JSONL now; ROS/ROS2, SIEM, ledger, and customer storage are future adapter directions.

The export is not the memory engine; it is a safe projection of what the memory engine knows.

How PASR works: the architecture →

Who it is for
  • AI agent / tool builders
  • Operator-console teams
  • Simulator / lab workflow teams
  • Robotics preflight teams
  • Local / offline governance evaluators
  • Research teams exploring evidence-gated interventions

PASR pricing and pilots

PASR is priced around the problem it solves: governed AI action evidence, local intervention memory, and reduced risk around proposed AI-agent actions.

Pricing tiers and pilot options

Evaluation Pack

Starting at $500 CAD

For technical evaluators who want a locally runnable PASR package with Docker/local evaluation, smoke test, BLOCKED demo, evidence pack, quickstart, and sample readout.

Request Evaluation Pack

Guided Pilot

Starting at $2,500 CAD

For teams that want a 30-day guided pilot, intervention schema setup, and return packet review around their own proposed intervention patterns.

Request Guided Pilot

Intervention Memory Pilot

Starting at $7,500 CAD

For teams ready to test the differentiated memory loop: repeated intervention decisions, geometry snapshot, intervention_memory readout, and human/JSON/JSONL memory export review.

Ask about Memory Pilot

Enterprise / regulated scope

Quoted

For enterprise, compliance, regulated, or board-facing use cases requiring custom governance framing, longitudinal evidence records, customer storage/export planning, and future ledger-compatible summaries.

Discuss enterprise scope

Governed AI Action Stack

For teams that want the full loop, FoldEngine can pair Trial Probe discovery with PASR Guided Pilot and Stability Ledger continuity framing. This is not a scanner plus a gate; it is a governed AI action loop.

Typical range: $4,500–$6,000 CAD

Ask about the Governed AI Action Stack

Prices are starting points for early pilots and may change as case studies, schemas, and deployment patterns mature.

PASR does not control actuators. PASR governs proposed interventions before they proceed toward a downstream control plane.

Layer 2 FoldEngine Memory remains private. Exports are safe projections, not the memory engine.

Public/evaluator PASR has no live Core3 routing.

Not included in public/evaluator PASR

  • No live Core3 routing
  • No safety certification
  • No actuator control
  • No ROS/ROS2 runtime
  • No implemented ledger bridge — future ledger bridge planning only
  • No private FoldEngine Memory internals
  • No raw memory dumps

Request a PASR Evaluation Pack

PASR is currently available for bounded technical evaluation and pilot discussions. Reach out and we will follow up about an Evaluation Pack or a pilot.