FoldEngine Runtime
FoldEngine Runtime understands repositories, shapes construction packages, generates governed candidates, validates bounded work, preserves evidence, and improves through consequence intelligence.
It remains the offline operating environment where teams shape work, trial bounded changes, preserve evidence, and decide whether proposed work should cross real delivery boundaries. Every major activity produces governed evidence while preserving human authority and local-first control.
Runtime preserves source, does not merge or release on its own, and keeps the final decision with the operator. Humans still authorize apply, commit, push, merge, deploy, release, and publication.
Runtime journeys
Each journey answers: what are you trying to accomplish, which surface supports it, what evidence is produced, and who owns the next decision.
Surface: New Project Guided Intake
Capture intent, discover requirements, identify unknowns, and prepare a construction candidate. No implementation begins automatically.
Evidence: intake record, requirements summary, construction handoff candidate.
Next decision: operator chooses whether to proceed to construction.
Surface: Repository Takeover Wizard
Preserve source, isolate the workspace, inspect the repository, and prepare a governed candidate. Remote repository cloning is not performed by Runtime.
Evidence: takeover observations, test results, classified next safe move.
Next decision: operator confirms the governed path forward.
Surface: Construction Workspace
Work through problem shape, blueprint, acceptance criteria, slice planning, and governed handoff to the workcell. Architecture is shaped for review — not generated and applied autonomously.
Evidence: construction package, acceptance framing, slice plan.
Next decision: operator authorizes bounded work to enter the workcell.
Surface: Workcell
Run isolated execution, validation, evidence capture, continuity, and receipts inside a governed workcell. Protected source remains protected.
Evidence: run detail, validation output, continuity record, receipt summary.
Next decision: operator reviews results before any export or apply boundary.
Surface: Formal Review Decision
Review evidence, inspect receipts, understand risk, and determine the next governed action. FoldEngine supports review. It does not approve work.
Evidence: review record, receipt inspection, risk posture summary.
Next decision: human reviewer — proceed, hold, or block.
Surfaces: evidence-backed workspaces + export boundary
Inspect provenance, receipts, continuity, export boundaries, and raw evidence availability. Evidence makes review possible — it is not a compliance guarantee.
Evidence: provenance chain, receipt summaries, continuity history.
Next decision: operator decides what may cross the export boundary.
Surfaces: Project Workspace · Organization Operations Center
See projects, work status, review queue, readiness, evidence activity, and current next action across governed work. This is portfolio visibility — not autonomous portfolio orchestration.
Evidence: project posture, review load, blocked work, activity trail.
Next decision: operator or lead selects the next governed action.
Surface: Environment Readiness
Check runtime, storage, models, source mounts, and delivery posture before work begins. Environment readiness reports current posture. It does not configure environments automatically.
Evidence: readiness report, storage and model posture, source mount status.
Next decision: operator resolves gaps before proceeding.
Operational flow
Why Runtime is different
| Traditional AI | FoldEngine Runtime |
|---|---|
| Produces output | Governs work |
| Optimizes completion | Governs consequence |
| Produces code | Preserves evidence |
| Assumes approval | Preserves human authority |
Runtime surfaces
Each surface has one customer purpose. Architecture stays underneath.
How deployment works
Runtime is delivered for local use with guided setup, clear boundaries, and the artifacts a team needs to operate it responsibly.
Each deployment includes the materials needed to install, verify, and operate Runtime locally with confidence.
Deployment depends on the environment. Target support is confirmed case by case so teams know what is proven for their operating setup.
Runtime demonstrations
Explore the Runtime Preview, then use the two explainers for physical consequence and evidence-backed continuity.
Product pillars
These pillars map directly to the runtime that now exists rather than to vague AI categories.
1. Commercial & Customer Readiness
Customer readiness, organization governance, stack detection, toolchain gates, version compatibility, and repository conventions.
Open commercial runtime →2. Governed Construction
Requirements, dependencies, acceptance mapping, slice planning, and construction handoff before engineering work begins.
See construction runtime →3. Governed Engineering
Governed engineering automation, patch candidates, apply boundaries, validation preparation, and review package assembly.
See governed engineering →4. Governed Development
Implementation planning, tests, docs, architecture, release planning, completion, and review-backed development lifecycle packaging.
See governed development →5. Consequence Intelligence
Transition records, kernel discovery, kernel recall, organization memory, and recommendations that remain advisory and evidence-backed.
See consequence intelligence →Runtime reference pages
These pages turn the public site into a guided product demonstration rather than a generic company narrative.
A complete first-month walkthrough from mounted repository to governed engineering and review-backed handoff.
Runtime ArchitectureCommercial readiness → repository and stack posture → construction → projection → governed engineering → governed development → consequence intelligence → review → human apply.
Capability MatrixAvailability, evidence, commercial posture, and examples for each major runtime capability.
Projection RuntimeProblem graphs, requirement graphs, dependency graphs, blueprints, and export bundles that regenerate from runtime truth.
Evidence & ReviewReceipts, evidence packages, review surfaces, export posture, and human-controlled apply boundaries.
Organization MemoryCross-project memory, recalled kernels, repeated patterns, and operational recommendations.
Commercial ProgramsDiagnostic-first commercial ladder, customer readiness, guided deployment, and proof-backed expansion paths.
Next step
If the guided journeys match your team’s work, the next commercial step is a governed repo diagnostic with one repo or one change problem, a construction blueprint, and a review-backed evidence pack.
