Documentation hub
Start with the guide that matches your role. FoldEngine documentation is organized around buyer evaluation, runtime operation, review, governance, and architecture — not around internal implementation stages.
Documentation explains the runtime. It does not grant authority to apply, approve, publish, deploy, or release work.
Primary documentation paths
These paths are curated to help a buyer, operator, reviewer, or technical evaluator start with the smallest useful set of guides.
1. Buyer Evaluation
Understand what FoldEngine is, when to use it, and how evaluation works.
2. Operator Guide
Learn how to run repository takeover, inspect evidence, and decide the next governed action.
3. Product / Architecture Guide
Understand how FoldEngine shapes work before execution and preserves construction boundaries.
4. Reviewer / Security Guide
Understand what was proposed, what evidence exists, what remains human-controlled, and what FoldEngine does not claim.
5. Executive Brief
Understand the business value, risk posture, and evaluation path without implementation detail.
6. Technical Reference
Understand offline runtime posture, evidence model, source protection, and governed projection.
How to read documentation status
Governed documentation projection
FoldEngine can prepare audience-specific documentation candidates from governed source material. These candidates include manifests, provenance, review status, and authority boundaries. They are not published automatically.
That makes projection useful for buyers, operators, reviewers, and executives without turning documentation into an uncontrolled publishing channel.
Public runtime references
The website now doubles as a product demonstration. These public pages are the best starting point for technical evaluators who want concrete runtime structure before deeper delivery documentation.
End-to-end runtime chain from customer readiness to human apply.
Capability MatrixCurrent status, evidence, availability, and examples by capability.
Projection RuntimeGraphs, blueprints, export bundles, and runtime truth regeneration.
Consequence IntelligenceTransition records, kernel recall, organization memory, and recommendations.
Claims and non-claims
Use this matrix to see what FoldEngine can safely claim today, which wording is allowed, and which claims remain forbidden.
This is especially useful for legal, procurement, security, executive review, and commercial copy alignment.
Role bridge
FoldEngine documentation leads with familiar terms such as project, repository, review, evidence, and next step, then bridges into runtime labels like Project Workspace, Formal Review Decision, and Workcell Run Detail when needed.
Canonical runtime terms stay intact, but readers should not have to start from internal implementation vocabulary to understand the product.
