For institutional partners who require the DCFN substrate to run inside their own confidential-compute environment. A Secure Enclave partner receives a private deployment of the relevant DCFN substrate inside a trusted execution environment they choose, together with the engineering work required to integrate it to their data shape and operational environment.
🔒 Confidential-compute deployment — validated
The Secure Enclave deployment architecture is validated on GCP Confidential Space (AMD SEV) with hardware remote attestation. In plain terms: the deployment runs in a sealed container inside your environment, your data never leaves it, license/access is verified inside the enclave, and Living Eden Frameworks holds no remote kill switch, cannot reach into your environment, and cannot see your data. The same image is portable to AWS Nitro Enclaves and Azure Confidential VMs; for federal pathways it pairs with GCP Assured Workloads for the compliance boundary.
Private Enclave Deployment
The DCFN substrate deploys inside the partner's chosen Trusted Execution Environment, such as AWS Nitro Enclaves, GCP Confidential Space, or Azure Confidential VMs. This includes enclave deployment, attestation-policy configuration, partner-specific connector work, and dedicated engineering through production deployment.
Fee structure
This Schedule defines the structure and cadence of the commercial terms. The figures — and any exclusivity premium — are set in the Exclusive or Non-Exclusive Field License you sign, to your scope and field of use; they are not published here.
- Base Integration Fee — one-time, billed across three auto-tracked, partner-verifiable milestones: container build; connector, wire, and test; and sustained operation.
- Annual Access Fee — the only recurring charge, tiered by the data-complexity (or program-scope) tier assigned at the Data Readiness Assessment. No separate maintenance fee and no revenue royalty.
- Data Readiness Assessment — a mandatory, non-refundable prerequisite that credits in full toward the Base Integration Fee if the agreement is signed within 30 days of deliverables.
- Optional add-ons — a monthly post-warranty engineering retainer and a change-order hourly rate for engineering required by partner-side schema changes.
Operational telemetry (metadata only)
For service quality and failure diagnosis, the engine emits operational telemetry for each Assessment and run: the processing stage reached, error classification, run duration, and assigned complexity tier. This is metadata only — it contains no portfolio content (no patent identifiers, claim text, or document contents), and the partner's identity is one-way cryptographically hashed. In a Secure Enclave deployment the engine never transmits your data; this operational metadata is the only signal that can leave the enclave, and what egresses your environment is governed by your own network controls. It is independent of the optional structural-pattern-sharing election, which is a separate opt-in.
Three-Layer IP architecture (non-negotiable)
- Layer 1 — LEF Substrate Architecture: retained by Living Eden Frameworks LLC. The DCFN substrate, engine architecture, canonical-element graph, connector pattern library, and any improvements to them remain LEF-owned. The patent-protected mechanisms describing how the engine works. No license is granted to the substrate itself.
- Layer 2 — LEF Ai.E (the meta-engine): retained by Living Eden Frameworks LLC. LEF Ai.E is the self-evolving application that operates the Layer 1 substrate across every DCFN build. While Layer 1 describes the mechanisms, Layer 2 IS the running engine that executes them and continuously refines its own behavior across runs. Proprietary application, trade-secret implementation, and self-evolution behavior. No license is granted to LEF Ai.E at any tier or route.
- Layer 3 — Connector Instance License: the partner receives a perpetual, irrevocable, worldwide, royalty-free, paid-up, non-exclusive, non-transferable license to use the specific Connector Instance built for that partner under the Enclave agreement, solely within the scope of that partner's use of the DCFN substrate under the agreement and any successor agreement. The architectural patterns underlying the Connector Instance remain LEF-owned.
Pause, exit, and decommission
Access is payment-gated. If the Annual Access Fee is not paid — whether a missed payment or a deliberate pause between cycles — the deployed engine simply ceases operation (it stops running); it does not erase or destroy anything, and a later payment resumes the same deployment for a fresh full cycle with no re-onboarding. Living Eden Frameworks never reaches into your environment to remove or disable software.
On a true exit (not a pause), you decommission the deployed substrate and Connector Instance within your own environment; where deployed in a TEE this is performed by cryptographic erasure. You may optionally file a machine-verifiable erasure attestation as a clean record of decommission, but none is required. The uncapped liability carve-out in the Enclave agreement attaches to preserving or continuing to operate the substrate after license expiry — not to any attestation step.
AI substrate — runs on your own credentials
The deployment runs on your own Anthropic API credentials, which you supply and maintain. Because the engine executes inside your enclave on your key, model usage is billed by Anthropic directly to you — Living Eden Frameworks does not supply the key and does not resell, mark up, or meter model usage. The Annual Access Fee covers the LEF engine, not the underlying model spend, which is your direct cost with Anthropic.
Until the cross-substrate benchmark program is complete, all Enclave deployments run against Anthropic Claude as the AI substrate. When the election capability ships, Enclave partners may elect their AI substrate at signature time, with that choice disclosed in the contract.
When this makes sense
This route is appropriate when partner data cannot leave the partner's environment, when enclave deployment is required by policy or procurement, or when the deployment will operate as internal infrastructure inside the partner's security boundary.
This Schedule attaches to a Field License. To begin, start a conversation: sales@livingedenframeworks.com.