Use case · closed-loop platform
From assessment to review to evidence to continuity — a local-first governance architecture for AI-assisted work.
FoldEngine connects Trial Probe (hosted online entry) and FoldEngine Runtime (offline) into a local-first loop, so each runtime pass starts from what the last one learned. FoldEngine Runtime carries repo readiness, local system governance, adaptive strategy, and a bounded local workcell, while built-in review and evidence continuity keep recommendations, receipts, and lineage visible to an operator.
The closed loop
- 1Trial Probe or local intake captures the project need
- 2FoldEngine Runtime builds context and recommends the next bounded move
- 3Bounded roles run candidate work only through the local workcell
- 4Consequence is classified, receipted, and held for review with lineage
- 5Consequence memory preserves continuity for the next run
Online and offline, connected by evidence
Trial Probe (hosted) and FoldEngine Runtime (offline) are connected by evidence — probe reports and decision receipts can inform local governance runs. They are connected conceptually; there is no live ledger bridge between them today.
The FoldEngine Shell is the shared local operator environment for that runtime. It brings together evidence, review state, continuity, repo stabilization views, and runtime receipts in one place. The shell is a shared operator surface, not a standalone product or a source of truth by itself.
Why this matters
Most governance tools are cloud-only or local-only. FoldEngine is moving toward local-first governance with a clear public front door, a bounded offline runtime, and consequence memory that keeps continuity private by default and recoverable across runs.
Boundaries
- No Stability Ledger bridge.
- No hosted production platform.
- No action executor — FoldEngine does not execute actions.
Explore the use cases: Govern, SDLC, Research, Compliance.