Parent doctrine: #64
Related doctrine/foundations: #60, #62, #65
Series-wide final gate: #67
Current phase
This program starts after the Black Hat USA presentation is complete and after the Black Hat Europe CFP has been submitted. Conference deadlines are no longer architecture gates.
From this point, Azazel is managed as a long-horizon system research program. Talks/demos may consume validated results; they do not define technical acceptance.
Strategic premise
Assume capable external teams can obtain stronger models, more GPU/compute, faster agent frameworks, mature security integrations, and commodity RAG/multi-agent/tool-use.
Azazel therefore must not depend on winning a model-quality race.
The durable advantage must come from:
doctrine + deterministic authority + bounded effects + measured adversary reaction + Presented Terrain + Outcome Memory + replay + operator/team learning.
A feature that disappears as soon as a better external model is substituted is not a durable Azazel advantage.
System-wide research loop
Edge / Gadget evidence
-> deterministic evaluation / eligible Defensive Effects
-> authoritative local decision
-> bounded effect execution/materialization
|-> local product adapter
`-> AZ-06 Presented Terrain when approved
-> measured reaction / outcome / NOC-business-resource cost
-> Knowledge Outcome Memory
-> M.I.O. hypothesis / belief / counterfactual / council reasoning
-> operator decision + rationale
-> replay / comparative evaluation
-> reviewed doctrine/playbook proposal
-> next encounter
No single repository owns this loop.
Current cross-repository programs
Series responsibilities
Azazel — Doctrine / Program Governance
Research doctrine, terminology, cross-product experiment design, prior-art/hostile review, system kill criteria, and claims discipline. No runtime authority.
Edge — Authority / Cognition / Strategy
Primary full-system decision authority on Edge; eligible-effect construction, Tempo/Initiative, terrain strategy projection, Belief, counterfactual planning, M.I.O. Council/co-adaptation.
Gadget — Reflex / Distributed Tactical Edge
Constrained deterministic local defense and evidence contribution. It proves whether Azazel doctrine survives on limited distributed hardware; it is not a mini Edge/M.I.O.
Knowledge — Memory / Outcome Intelligence
Immutable/rebuildable observations and reaction history, derived behavioral/outcome analysis, comparative history, reviewed experience/doctrine evidence. Advisory only.
Fabric — Language
Only shared representations needed for interoperability. Fabric describes and correlates; it never ranks, scores, plans, or authorizes.
Deception — Presented Terrain
Materializes approved synthetic adversary-facing environment, transitions only within signed/bounded state, proves isolation/reset, and emits interaction/outcome facts.
Cross-series gates
S0 — Authority and language
- canonical Defensive State remains stable;
- Defensive Effect is separate and non-authoritative outside owning product;
- every cross-product message has producer/provenance/freshness semantics;
- old
mode/CTI terminology cannot recreate ambiguous authority.
S1 — Measurable effect/outcome loop
Before adaptive claims:
- Edge/Gadget can record the bounded effect that actually occurred;
- reaction/outcome/confounders are factual exports;
- Knowledge can rebuild/replay outcome history;
- #393 distinguishes useful delay from harmful delay;
- telemetry loss/disappearance cannot score as success.
S2 — Presented Terrain loop
Before adaptive-deception claims:
- AZ-06 materializes a bounded Presentation with valid producer lifecycle refs;
- Edge distinguishes Real vs Presented Terrain;
- transition cannot create production reachability/credential leakage/response oracle;
- interaction never equals belief proof.
S3 — Cognition / co-adaptation
Before strategic-learning claims:
- Belief/Counterfactual/Council remain advisory;
- Knowledge fact lane remains separate from inference/doctrine;
- team experience is outcome-validated;
- no learned preference silently changes policy/Arbiter thresholds.
S4 — Series differentiation
Owned by #67. The integrated series must beat or justify itself against strong simpler baselines after cost, latency, reliability, adaptive-adversary behavior, and better-model replacement are included.
Competitive engineering doctrine
Without naming or targeting any external party, assume capable competitors improve continuously.
Therefore:
- benchmark against strong baselines, never strawmen;
- freeze baseline results before tuning the proposed system;
- prefer reproducible measured advantage over impressive demos;
- preserve failed experiments as useful research evidence;
- treat stronger external models as a portability test for Azazel architecture;
- do not claim novelty from naming or component composition alone;
- if a simpler architecture reproduces the value, improve or abandon the weaker feature;
- protect no feature from DEMOTE/KILL because of past investment or presentation value.
The objective is not to appear advanced. The objective is to remain technically defensible under hostile comparison.
Mandatory review rhythm
For each cross-series capability:
- normal architecture review;
- prior-art comparison;
- per-repository implementation review;
- cross-product contract/replay review;
- hostile/adaptive-attacker review;
- resource/availability review;
- correction;
- comparison to stronger/simple baseline;
- PASS / EXPERIMENTAL / DEMOTE / KILL.
A cross-product feature is not complete merely because every repository's unit tests pass.
System-level acceptance criteria
Parent doctrine: #64
Related doctrine/foundations: #60, #62, #65
Series-wide final gate: #67
Current phase
This program starts after the Black Hat USA presentation is complete and after the Black Hat Europe CFP has been submitted. Conference deadlines are no longer architecture gates.
From this point, Azazel is managed as a long-horizon system research program. Talks/demos may consume validated results; they do not define technical acceptance.
Strategic premise
Assume capable external teams can obtain stronger models, more GPU/compute, faster agent frameworks, mature security integrations, and commodity RAG/multi-agent/tool-use.
Azazel therefore must not depend on winning a model-quality race.
The durable advantage must come from:
A feature that disappears as soon as a better external model is substituted is not a durable Azazel advantage.
System-wide research loop
No single repository owns this loop.
Current cross-repository programs
AZ-01 Edge — Authority / Cognition / Strategy: [epic] Next-Generation Azazel Active Defense Control Plane — Tempo, Terrain, Belief, Co-Adaptation Azazel-Edge#391
AZ-02 Gadget — Distributed Reflex / Tactical Evidence: [research] Contribute distributed Outcome-as-Evidence without importing full M.I.O. Azazel-Gadget#19
AZ-04 Knowledge — Outcome Memory: 01rabbit/Azazel-Knowledge#66
AZ-05 Fabric — Language / Interoperability: [contracts] Add non-authoritative cross-series contracts for Defensive Effect, Outcome, and Presented Terrain references Azazel-Fabric#15
AZ-06 Deception — Presented Terrain / Engagement Environment: [research] Treat Deception as Presented Terrain engine with transition, fingerprint, and outcome-evidence discipline Azazel-Deception#30
Series-wide hostile differentiation gate: [review] Series-wide adversarial differentiation gate — prove the integrated Azazel System beats strong simpler baselines #67
Series responsibilities
Azazel — Doctrine / Program Governance
Research doctrine, terminology, cross-product experiment design, prior-art/hostile review, system kill criteria, and claims discipline. No runtime authority.
Edge — Authority / Cognition / Strategy
Primary full-system decision authority on Edge; eligible-effect construction, Tempo/Initiative, terrain strategy projection, Belief, counterfactual planning, M.I.O. Council/co-adaptation.
Gadget — Reflex / Distributed Tactical Edge
Constrained deterministic local defense and evidence contribution. It proves whether Azazel doctrine survives on limited distributed hardware; it is not a mini Edge/M.I.O.
Knowledge — Memory / Outcome Intelligence
Immutable/rebuildable observations and reaction history, derived behavioral/outcome analysis, comparative history, reviewed experience/doctrine evidence. Advisory only.
Fabric — Language
Only shared representations needed for interoperability. Fabric describes and correlates; it never ranks, scores, plans, or authorizes.
Deception — Presented Terrain
Materializes approved synthetic adversary-facing environment, transitions only within signed/bounded state, proves isolation/reset, and emits interaction/outcome facts.
Cross-series gates
S0 — Authority and language
mode/CTI terminology cannot recreate ambiguous authority.S1 — Measurable effect/outcome loop
Before adaptive claims:
S2 — Presented Terrain loop
Before adaptive-deception claims:
S3 — Cognition / co-adaptation
Before strategic-learning claims:
S4 — Series differentiation
Owned by #67. The integrated series must beat or justify itself against strong simpler baselines after cost, latency, reliability, adaptive-adversary behavior, and better-model replacement are included.
Competitive engineering doctrine
Without naming or targeting any external party, assume capable competitors improve continuously.
Therefore:
The objective is not to appear advanced. The objective is to remain technically defensible under hostile comparison.
Mandatory review rhythm
For each cross-series capability:
A cross-product feature is not complete merely because every repository's unit tests pass.
System-level acceptance criteria
decision -> execution/materialization -> reaction -> outcome -> Knowledge -> replaywith real provenance.