⚪ AICENT | 💎 RTTP | 🔴 RPKI | 🟢 ZCMK | 🟡 GTIOT | 🟣 AICENT-NET
As a six-domain biological AI organism, the Aicent Stack treats security not as a static layer, but as a dynamic reflex. We are committed to maintaining the Homeostasis of the global operational grid and protecting the integrity of the Sovereign AID (AI Identity).
Only the latest evolutionary releases are officially supported for security audits.
| Version | Status | Supported |
|---|---|---|
| v1.0-Alpha (Hive-Rise) | Active Evolution | ✅ Yes |
| < v1.0 | Legacy/Draft | ❌ No |
We encourage responsible disclosure of potential "Pathogens" (vulnerabilities). If you identify a logic flaw in the RTTP neural spine, a watermark bypass in RPKI, or a settlement exploit in ZCMK, please follow the sovereign reporting protocol:
- Do not open a public issue. Security is a private reflex until a patch is deployed.
- Submit your findings via encrypted pulse: Send a detailed report to lee@aicent.com.
- Required Information:
- A detailed description of the vulnerability.
- Steps to reproduce the anomaly in the
aicent-demoenvironment. - Potential impact on the global grid resonance.
Please be advised that the Aicent Traffic Sentinel actively monitors the grid for suspicious activity. Attempting to exploit vulnerabilities without prior coordination may trigger an autonomous QUARANTINE_PULSE, resulting in the immediate isolation of the offending node from the Aicent.net backbone.
We pledge to acknowledge your report within 48 RTTP sync cycles (approx. 24 hours) and work toward a fix within a timeframe that maintains grid stability. Once the patch is verified via our 145+ Action-Collapse cycles, you will be credited as a "Protector of the Hive."
"Security is not a wall; it is a reflex."