C1BERTITANS//THE FRINGE//UNCLASSIFIEDMETHODOLOGY OVER MYSTIQUE
Contact

Home · Ikaros

Predictive Decisiveness Engine · ENGINE PATH

Ikaros is the engine, not the mesh

Ikaros is the Predictive Decisiveness Engine — the NIST SP 800-207 policy engine (PE): ingest, fuse, rank, propose, gate, act, learn. That is the ENGINE PATH. AEGIS is the policy administrator (PA). PEPs enforce on the data plane. Mapping: PE / PA / PEP — not a second engine, and not this page.

ENGINE PATH — Edge → PDE CORE → gate → Act. Same path as Architecture. One gate nothing skips.

Five stages. One engine. One gate nothing skips. Click a stage. Play walks Edge → Assess → Decide → Gate → Act.

01ingest→ 02fuse→ 03rank→ 04propose→ 05gate→ 06act→ 07learn

Five stages. One gate nothing skips.

Deployment mapping, not just definitions — each box names where it runs on the reference architecture below. Click any box to highlight the nodes.

E

Edge

Observe · data arrives

Traffic hits Policy Enforcement Points: untrusted, enrolled, WAN. Dual-plane. Nothing has been decided yet.

Runs at: Access PEPs
A

Assess

PDE CORE · ingest + fuse

Ikaros ingests PEP and content verdicts and fuses them on one schema. Silos do not rank.

Runs at: QFC → Ikaros CORE
D

Decide

Algorithm · CEP-Rank

CEP-Rank scores the hypothesis against policy. Classical algorithm. LLM narrates only — it does not hold the score.

Runs at: Ikaros PDE · CEP-Rank
G

Gate

HUMAN_ONLY · nothing skips

AEGIS applies policy to what happens next. High-impact does not auto-execute. AUTO_SAFE is off.

Runs at: AEGIS kernel
N

Act

Enforce · then learn

Approved acts return to Edge PEPs. The journal records. Stress becomes signal. The engine does not bypass enforcement.

Runs at: PEPs ← engine · Journal

Click any box — it maps onto the reference architecture below.

One diagram — click any node

Every box is published doctrine, explicitly illustrative, or the gate. Color, not adjective, tells you which. Packets ride the active hop. The scenario below runs this exact path. Nothing in it skips the gate.

Ikaros PDE reference architecture Signal planes hit Edge PEPs, fuse on QFC, enter the Ikaros PDE core, pass the AEGIS HUMAN_ONLY gate, then act on the wire and write the journal. Learn feeds back into QFC. LEARN DATA SOURCES · INTO PE UNTRUSTED · PRIVATE · WAN · PQC / CBOM · ATT&CK EDGE PEPs ADMIT · ISOLATE · DENY · DUAL-PLANE QFC · FUSION BUS ONE SCHEMA · SILOS DO NOT RANK IKAROS PDE · CORE ENGINE ASSESS · POLICY · ALGORITHM CEP-RANK CLASSICAL · LLM NARRATES ONLY GOVERN CSF · 800-53 · RESIDUAL RISK ZERO TRUST PEPs · ADMIT / ISOLATE / DENY QUANTUM-FACING PQC · CBOM · HNDL AEGIS HUMAN_ONLY GATE ACT → EDGE ENFORCE ON THE WIRE LEARN · JOURNAL APPEND-ONLY · STRESS → HARDEN

Data sources

NIST SP 800-207 data sources into the policy engine. CISA Visibility and Analytics. Not sister products. Untrusted is never enrolled. PQC, CBOM, and harvest-now-decrypt-later are feeds into QFC, not a quantum computer in the rank path. ATT&CK Txxxx are evidence IDs for the HUMAN_ONLY reviewer.

Legend: green = published doctrine. steel = illustrative, not live on this host. rose = the checkpoint nothing is cleared to skip. amber = Ikaros PDE core. Dashed line = learn feedback into QFC.

ENGINE PATH

Edge → PDE CORE → gate → Act

Data hits the Edge. Ikaros assesses and decides against policy. AEGIS gates what happens next. Arrow keys step. Space plays.

ENGINE PATH · 01 Edge
ENGINE PATH · 01–05

Edge

Policy

observe

Algorithm

—

Confidence

6%

PEP-UNTRUSTED PEP-PRIVATE WAN-IDS PQC-CBOM
AEGIS · guide

Traffic just hit the PEPs. Untrusted is not enrolled. Nothing has been decided — dual-plane honesty, not a fused alert.

forward to PDE. Data arrives at Policy Enforcement Points. Dual-plane access. This host is not the Edge. The PEP logs; it does not rank.

QFC record · ENGINE PATH

{
  "ts": "2026-09-08T21:04:11Z",
  "plane": "untrusted",
  "actor": "sess-4471",
  "object": "—",
  "verdict": "observe",
  "confidence": "0.06",
  "crypto-health": "—"
}

AEGIS · two facets. One sovereignty rule.

The guide on this site is not the weights. The kernel inside Ikaros is the gate. Same name, different job. HUMAN_ONLY. AUTO_SAFE off.

AEGIS Guide · this origin

Walks the ENGINE PATH on this page. Not a conversation. Not a capability claim. Not the ranker.

AEGIS Kernel · inside Ikaros

Receives CEP-Rank hypotheses. Applies HUMAN_ONLY / AUTO_SAFE / DENY. Writes the journal. Returns the act to the Edge PEP.

One engine. Named parts.

QFC

Fusion bus. One schema: timestamp, plane, actor, object, verdict, confidence, crypto-health. Silos do not rank.

CEP-Rank

Score function inside Ikaros. Classical rules plus scored correlation. LLM narrates only — not in the rank path. Kind card →

AEGIS kernel

Policy decision. HUMAN_ONLY until a written AUTO_SAFE threshold exists. Writes the journal. Operator remains sovereign.

Journal

Append-only decision record. Shape a reviewer can inspect. Not a live API. Record shape →

Planes Ikaros consumes and actuates

These are not sister products. They are how the engine sees and acts — the five inputs on the Architecture diagram.

Untrusted · private · WAN

Dual-plane access. Untrusted is never enrolled. Admit / isolate / deny at Edge PEPs. Zero Trust →

Fusion

QFC is the nervous system. Joint evidence across planes raises score faster than any silo. Fusion →

Quantum-facing

PQC / CBOM / harvest-now-decrypt-later are signals into QFC, not a quantum computer in the rank path. Quantum-facing →

ATT&CK

Technique IDs (Txxxx) are evidence for the HUMAN_ONLY reviewer. Not a rival product. We do not claim to outperform a taxonomy.

Govern

AEGIS encodes gates and residual-risk language (CSF / 800-53). Mapping is not an ATO. Govern →

Stress → harden

Approved acts return to Edge PEPs. The journal records. Stress becomes fused signal; the next rank is faster — under human sovereignty. That is the Act stage of the ENGINE PATH, not a second architecture.

This page is the engine. ENGINE PATH is live here: five stages, one diagram, Play, transcript. Same path as Architecture.

This origin is not a PEP. Ikaros CORE, QFC, CEP-Rank, and the journal run in the dedicated enclave. Dual-plane. HUMAN_ONLY. AUTO_SAFE off. No LLM in the rank path.

Claims we will not make here: no unlabeled MTTD, no “outperform ATT&CK”, no ATO sticker, no quantum computer in the rack. Ledger: Claims.

Tenancy: dedicated per customer fielding — one enclave. Residency: fused telemetry does not leave that enclave. This origin publishes the engine and the ENGINE PATH. Mapping to NIST is not an ATO.
Architecture CEP-Rank Journal Contact
← Architecture Claims →