FoldEngine Stabilized.

FoldEngine Offline Runtime · local operator console

Move AI-assisted engineering work forward without giving the machine release authority.

FoldEngine governs whether AI-assisted work is allowed to become real.

FoldEngine Offline Runtime is a working local operator console for clarifying objectives, running bounded engineering work, reviewing evidence, applying authorized changes, and preserving accepted project state.

Available through controlled deployment. Not self-service GA.

See the Runtime journey Request Evaluation Access
Project Home for synthetic project External Workspace Stabilization, showing lifecycle position and next lawful action
Project Home keeps lifecycle, authority, blockers, active work, and the next lawful action in one place. Illustrative Runtime view using synthetic project data.

After you start

Your first governed project

At every stage, FoldEngine shows what is happening, what is blocked, who holds authority, and what may lawfully happen next.

  1. 1Choose the project
  2. 2Confirm the objective
  3. 3Run bounded work
  4. 4Review evidence
  5. 5Apply or reject
  6. 6Accept a checkpoint

The first governed project journey works today through controlled deployment: create or select a project, bind an external workspace, confirm the first objective, admit governed work, review, apply under authority, and checkpoint.

Lifecycle remains Research → Plan → Execute → Review → Ship. Project Home is the cockpit across that lifecycle — not a stage before Research.

  • Research
  • Plan
  • Execute
  • Review
  • Ship

One project · one journey

External Workspace Stabilization

Demonstration objective: stabilize repository admission for external project workspaces without weakening source-boundary controls. Lifecycle remains Research → Plan → Execute → Review → Ship. The moments below are operator product moments — not a second lifecycle model.

Objective confirmation surface for External Workspace Stabilization

Clarify the objective

Confirm before work is admitted

The operator confirms the objective before it becomes admitted work. Model proposals remain distinct from operator intent.

FoldEngine calls this governed clarification step Objective Discovery.

Bounded Workcell execution surface for External Workspace Stabilization

Run bounded work

Execute inside declared scope

AI and tools operate inside bounded Workcells with declared scope, evidence, stop conditions, and receipts.

Multiple dependent Workcells can be coordinated through a Nebula Program.

Review decision surface with evidence and uncertainty

Review · then apply · then checkpoint

Decide, authorize, accept state

The operator reviews evidence and uncertainty, may authorize a governed apply ceremony, then accepts a checkpoint so the project can continue. Operator authority remains outside the model.

Full Governed Apply and Project Checkpoint frames live on Runtime Preview — Checkpoint is not a sixth lifecycle stage.

Walk the full six-frame Runtime journey →

Illustrative Runtime view using synthetic project data. Not a customer case study.

Authority Boundary

Consequential authority stays with the operator

FoldEngine governs engineering work without granting the Runtime autonomous authority to release.

FoldEngine does not mutate source autonomously. Source changes occur only through explicit admission, authorization, bounded application, validation, and a source-state receipt. Commit, push, merge, deploy, and release remain outside autonomous authority. It does not autonomously apply source changes, commit, push, merge, deploy, release, accept organizational delivery, or promote project-local knowledge globally.

  • commit
  • push
  • merge
  • deploy
  • release

FoldEngine does not autonomously perform the actions above.

Status

Working today through controlled deployment

  • local Offline Runtime
  • project creation and external workspace binding
  • governed objective confirmation
  • bounded Workcells
  • optional multi-Workcell coordination
  • evidence-backed operator review
  • authorized source application and validation
  • accepted project checkpoints
  • lifecycle-aware Project Home
  • deterministic browser-proven operator journeys

The first governed project journey works. Commercial installation and deployment remain controlled rather than self-service.

Boundaries

Not yet offered as

  • self-service SaaS
  • one-click public installation
  • autonomous performance of commit, push, merge, deploy, or release
  • generally available enterprise distribution

Product family

Three independent public lanes

FoldEngine Offline Runtime, Hosted Probes, and Client Portal share the same governance doctrine, but none requires the others as a default next step. They are not equally mature expressions of the same product.

  • Primary product

    Offline Runtime

    Move engineering work through a governed local lifecycle. Clarify objectives, execute bounded work, review evidence, apply deliberately, and preserve accepted state.

    Explore Offline Runtime
  • Online lane

    Hosted Probes

    Inspect a repository with a bounded diagnostic. Receive evidence and findings without installing the full Offline Runtime operator environment.

    Explore Hosted Probes
  • Client surface

    Client Portal

    Access delivery, evidence, commercial status, and customer-specific materials. Assigned-client summaries only.

    Client Sign In

None of these lanes requires the others as a default next step.

See the journey, then request access

Walk one synthetic project through the Offline Runtime, or request Evaluation Access for controlled deployment.

See the Runtime journey Request Evaluation Access View sample outputs

FAQ

What happens after I start with Offline Runtime?

You bring a project and an uncertain objective. FoldEngine helps structure bounded work, shows evidence and blockers, waits for your decisions at consequential boundaries, may apply an explicitly authorized change, and records the accepted state so the project can continue.

Is this generally available for download?

No. The first governed project journey works through controlled deployment. Commercial installation and deployment remain controlled rather than self-service. It is not self-service SaaS or one-click public installation.

What authority does FoldEngine have?

Operator authority remains outside the model. See the Authority Boundary above for the full formula. Commit, push, merge, deploy, and release remain outside autonomous authority.

How do Hosted Probes relate?

Hosted Probes are an independent online lane for bounded diagnostics. None of the public lanes requires the others as a default next step.