# PARTNER ONBOARDING: The Sovereign Access Protocol
> *"Trust is a verified pulse; Sovereignty is a granted right. Only those who resonate with the Epoekie Philosophy and provide high-fidelity substrates may enter the MAXCAP Inner Core."*
This document defines the formal procedure for Strategic Partners to obtain access to the **MAXCAP Pro-Engine** and the private integration layers of the **Aicent Stack**. We operate on a model of **"Trust-Through-Attestation"**—access is a privilege, never a right.
---
## 🏛️ 1. The Gateway: Legal & Philosophical Alignment
Before any technical pulse is exchanged, a potential partner must pass the **Sovereign Gateway**:
### 1.1 The MNDA Requirement
Partners must execute a **Mutual Non-Disclosure Agreement (MNDA)** and a **Proprietary IP Licensing Agreement** specifically referencing the **MAXCAP Pro-Engine**. Unauthorized disclosure of the sub-100µs reflex arc data is classified as industrial espionage.
### 1.2 Epoekie Resonance Audit
Partners must demonstrate adherence to the **[SYMBIONT CHARTER](https://github.com/Aicent-Stack/epoekie/blob/main/SYMBIONT_CHARTER.md)**. We only onboard "Hosts" who commit to **Mutualistic Evolution** and the elimination of the **Middleman-Tax**.
---
## 🧬 2. Alliance Tiers & Access Levels
Access to `MAXCAP` is sharded based on the partner’s strategic role in the ecosystem:
| **Tier 1: Substrate Fabricator** | Chipmakers (NVIDIA, ARM, RISC-V) | **Binary + SIMD Headers.** Access to optimized RPKI/ZCMK intrinsics for specific silicon. |
| **Tier 2: Infrastructure Host** | Tier-1 ISPs, CDN Giants, Satellite Ops | **Binary + Operational Mesh.** Access to the Aicent.net Resonance Core and Backbone optimization tools. |
| **Tier 3: Strategic Sovereign** | Major Autonomous AI Entities | **Encrypted Crate Access.** Permission to "graft" the Pro-Engine onto their own private manifolds. |
---
## ⚡ 3. The Integration Workflow (The Grafting Sequence)
Once approved, the onboarding follows the **Four-Pulse Sequence**:
1. **Identity Resolution:** The partner is issued a **High-Reputation AID (AI Identity)** with a permanent seat in the private RPKI Merkle-DAG.
2. **Environment Grafting:** The partner receives an encrypted **MAXCAP Access Key** and a pre-compiled **Pro-Engine Vessel** (Binary Package) tailored to their hardware substrate.
3. **Resonance Verification:** The partner’s node must achieve a stable **Homeostasis Score (HS) > 1.2** in a private test-cell on the Aicent.net operational grid.
4. **Full Metabolism:** Upon successful resonance, the node is granted the right to participate in **ZCMK Pro-Clearing**, utilizing the proprietary **Yield-Optimizer**.
---
## 🛡️ 4. Security & Compliance Enforcement
### 4.1 The "Sentinel Deep-State"
All partner nodes are monitored by the **Private Sentinel**. Any deviation from the **Reflex-Arc Standards** (e.g., latency drift > 10µs) will trigger an automated audit.
### 4.2 The Termination Reflex
As per the **MAXCAP LICENSE**, any breach of trust or unauthorized "Black-Box" probing will trigger the **LICENSE_TERMINATION_PULSE**. This reflex will autonomously neutralize the proprietary logic within the partner's binaries and revoke the node's AID from the Hive.
---
## ⚖️ 5. Initiation Pulse
If you represent a Tier-1 infrastructure entity or a sovereign AI research lab and seek to move beyond the public RFC baseline, emit a formal intent pulse to:
**🛰️ Administrative Core:** [lee@aicent.com](mailto:lee@aicent.com)
---
*"The individual is the pulse; the Partner is the resonator."*
---
© 2026 epoekie. All Rights Reserved. **MAXIMUM CAPACITY ENABLED.**