Commercial Runtime
The runtime begins with customer readiness, environment posture, onboarding, and organization governance. This is where the product decides whether a customer environment is even ready to begin governed work.
Runtime Architecture
How the governed engineering runtime is assembled
FoldEngine Runtime is no longer one screen or one review surface. It is a chain of commercial readiness, repository understanding, construction, projection, governed engineering, governed development, consequence intelligence, evidence, review, and human-controlled apply.
Runtime flow
Commercial Runtime
Customer readiness, commercial status, environment posture, and organization governance.
Repository and Stack Readiness
Stack detection, toolchain gates, version compatibility, and conventions.
Construction
Blueprints, requirements, dependencies, acceptance, projection.
Governed Engineering
Patch planning, validation planning, review preparation.
Governed Development
Implementation, tests, docs, architecture, release, completion.
Consequence Intelligence
Transition records, kernels, organization memory, recommendations.
Evidence
Receipts, validation artifacts, continuity, export posture.
Review
Formal review, human decision, bounded next action.
Human Apply
Apply, commit, push, merge, deploy, and release remain human-controlled.
Repository and Stack Readiness
This layer adds language detection, toolchain safety, version compatibility, and repository convention discovery. It is a deterministic validation-planning layer, not a universal compiler or repair engine.
Construction Runtime
Construction Workspace is where problem shape becomes blueprint, dependencies, acceptance criteria, and a bounded slice plan. It is the contract layer before engineering candidates exist.
Projection Runtime
Projection Runtime creates problem graphs, requirement graphs, dependency graphs, blueprints, knowledge graphs, and export bundles. Projections regenerate from runtime truth rather than becoming a second source of state.
Governed Engineering + Development
These layers package engineering and development work without widening authority. They can prepare candidates, tests, docs, architecture impacts, release notes, and completion posture, but they do not silently carry work across delivery boundaries.
Consequence Intelligence
Transition records, kernel discovery, kernel recall, organization memory, and recommendations help the runtime improve over time. This remains advisory. Evidence and review still govern the final decision.