Use case 1
Recover A Risky Repository
Problem
We inherited a repository that nobody wants to touch.
How FoldEngine approaches it
FoldEngine Offline Runtime preserves source, runs Objective Discovery into a confirmed Plan, executes through Workcells (and Nebula when coordination is needed), and reaches Governed Apply only under explicit authorization.
Runtime surfaces involved
Repository Takeover Wizard, Objective Discovery, Workcell, Formal Review, Governed Apply, Project Checkpoint.
Evidence produced
Governed workspace, evidence, receipts, review candidate.
Who owns the decision
FoldEngine prepares candidates. Humans decide whether changes leave the workcell.
Use case 2
Start A New AI-Assisted Project
Problem
We need to move from idea to implementation safely.
How FoldEngine approaches it
It captures intent through Objective Discovery, confirms a bounded objective, preserves unknowns, and prepares construction before Workcell execution. Research and Plan stay distinct.
Runtime surfaces involved
New Project Guided Intake, Objective Discovery, Construction Workspace, Workcell.
Evidence produced
Normalized requirements, blueprint, acceptance, construction package.
Who owns the decision
Construction is preparation, not approval.
Use case 3
Review AI-Generated Work
Problem
We need to understand what AI proposed before accepting it.
How FoldEngine approaches it
It turns a proposed change into governed evidence, preserved receipts, and an inspectable review surface so the team can evaluate the work before it crosses delivery boundaries.
Runtime surfaces involved
Workcell Run Detail, Formal Review Decision, optional Governed Apply after authorization.
Evidence produced
Evidence, receipts, provenance, review guidance.
Who owns the decision
Evidence informs review. Humans approve.
Use case 4
Preserve Evidence For High-Risk Changes
Problem
We need to understand what happened months later.
How FoldEngine approaches it
It preserves the receipt chain and continuity record so a team can reconstruct what happened, what was reviewed, and what evidence existed at the time of the decision.
Runtime surfaces involved
Receipt chain, Continuity, Transition records.
Evidence produced
Evidence, provenance, receipt chain.
Who owns the decision
Evidence supports reconstruction. It does not rewrite history.
Use case 5
Govern Human + AI Collaboration
Problem
Multiple people and AI systems contribute to one project.
How FoldEngine approaches it
It provides project-level visibility, role-aware views, and review-aware work tracking so teams can understand what is active, blocked, awaiting review, or ready for the next governed action.
Runtime surfaces involved
Project Workspace, Organization Operations Center, Role Projections (surfaces inside Offline Runtime, not separate products), Nebula Program when multi-Workcell coordination is needed.
Evidence produced
Project visibility, review queue, next governed action.
Who owns the decision
Human authority remains explicit.
Use case 6
Operate In Local Or Controlled Environments
Problem
Our repositories cannot leave our environment.
How FoldEngine approaches it
It runs as FoldEngine Offline Runtime under controlled delivery with readiness checks, protected source handling, and evidence-preserving Workcells.
Runtime surfaces involved
Environment Readiness, Local Runtime (FoldEngine Offline Runtime), Project Home, Workcells, Project Checkpoints.
Evidence produced
Readiness, governed workcell, protected source.
Who owns the decision
Local operation does not expand runtime authority.
