CONFIDENTIAL DERIVATIVE LINEAGE REGISTRY

SHOW THE CAPABILITY.
NEVER EXPOSE THE PLAN.

A multi-compartment release federation for generating exact, separately authorized public derivatives without crossing customer, mission, supply-chain, evidence, partner, or sovereign-command boundaries.

TECHNICAL ACCESS DOES NOT CREATE RELEASE AUTHORITY.Every derivative is a new artifact with exact lineage, purpose, reuse, retention, review, aggregation, and authority state.
FEDERATION / 2.0.0-rc.19-WIP

Multi-Compartment Release Control

OUTCOMERELEASE_SANITIZED_DERIVATIVE
AUTHORITYCURRENT
REVIEWCOMPLETE
AGGREGATIONCLEAR
SOURCE LIFECYCLECURRENT

FEDERATED COMPARTMENT GRAPH

Authority, provenance, correlation, and derivative path

Two independently reviewed synthetic source compartments produce one separately authorized minimal public derivative.

Synthetic compartment and derivative lineage graph Independent source compartments feed an authorized transformation and a bounded public derivative only after all release gates pass.
REASON CODES
  • EXACT_FIELD_ALLOWLIST_SATISFIED
  • PURPOSE_AND_REUSE_BOUNDARIES_SATISFIED
  • RETENTION_CURRENT
  • RELEASE_AUTHORITY_CURRENT
  • INDEPENDENT_REVIEW_SATISFIED
  • AGGREGATION_AND_REIDENTIFICATION_BOUNDARY_SATISFIED
18 / 18DERIVATIVE_HISTORY_SEALED

The new synthetic derivative lineage is sealed without source-content disclosure or public persistence.

Compartment authority matrix

CompartmentClassificationAttestationRelease authorityAggregation policy
Sovereign command compartmentRESTRICTED_STRATEGICCURRENTNONENO_CROSS_COMPARTMENT_AGGREGATION
Mission-assurance compartmentPARTNER_CONFIDENTIALCURRENTEV-REL-MISSION-001EXACT_ALLOWLIST_ONLY
Supply-chain and configuration compartmentPARTNER_CONFIDENTIALCURRENTEV-REL-SUPPLY-001CORRELATION_GROUP_REQUIRED
Evidence and provenance compartmentPARTNER_CONFIDENTIALCURRENTEV-REL-EVIDENCE-001DEPENDENCE_AND_LINKAGE_REVIEW
Partner-release compartmentAUTHORIZED_DERIVATIVECURRENTEV-REL-PARTNER-001DERIVATIVES_ONLY
Unclassified public-capability compartmentPUBLICCURRENTEV-REL-PUBLIC-001PUBLIC_DERIVATIVES_ONLY
EV-CDL-RUN-4FC26F814BAC7359c502e3f4929b57ae456781fd4d224de2d64cfe1372236b53eed49b7e180dSYNTHETIC_NULL_SINK

RESEARCH TRACEABILITY

THE CAPABILITY IS GROUNDED IN EVIDENCE.

The public workbench uses synthetic data, but its architecture is connected to Evulgare’s public research corpus and report-to-software traceability.

EVR-0004

Fictional Autonomous Kill Web Defense Architecture: Resilience Against Non-Kinetic Disruption

Fictional Autonomous Kill Web Defense Architecture: Resilience Against Non-Kinetic Disruption The deployment of autonomous multi-agent systems at the tactical edge represents a paradigm shift in distributed computing, wherein algorithmic outputs dictate kinetic actions across highly contested environments. This architectural research report conducts an exhaustive, public-source defensive study of a fictional autonomous kill web, hereafter referred to as KillWebs.com KW . The central premise of this defensive architecture is the strict prioritization of integrity over availability. In a lethal autonomous system, a visibly unavailable or inert system is universally safer th

Open report →

EVR-0009

Architecture of Synthetic Distributed Autonomous Kill Webs: A Multi-Domain Trust, Governance, and Assurance Framework

Architecture of Synthetic Distributed Autonomous Kill Webs: A Multi-Domain Trust, Governance, and Assurance Framework The conceptualization of modern multi-domain operations necessitates a fundamental transition from linear kill chains to dynamic, self-healing kill webs. Linear kill chains—defined by the sequential find, fix, track, target, engage, and assess F2T2EA process—are inherently fragile in contested environments. Adversaries increasingly rely on system-destruction warfare, targeting critical communication links, intelligence, surveillance, and reconnaissance ISR nodes, and command structures to sever these linear sequences and deny decision dominance1. By contra

Open report →

EVR-0015

Make the Machine Answerable: Decision Provenance, Evidence Integrity, Causal Reconstruction, and Accountability Infrastructure for Evulgare

The proliferation of autonomous systems, ranging from human-supervised machine learning implementations to machine-sovereign infrastructures, fundamentally alters the landscape of technical accountability. Evulgare’s central proposition is straightforward yet paradigm-shifting: make the machine answerable. The architecture presented in this report establishes that a machine’s technical answerability is completely distinct from legal liability or moral fault. Evulgare does not determine who is legally liable, nor does it compute a universal blame score. Instead, it provides the deterministic, mathematically verifi.

Open report →

EVR-0017

Machine-Sovereign Defense Assurance for Eviulon: All-Machine Command, Reporting, Authority, and Institutional Control

The emergence of Eviulon as an all-machine sovereign jurisdiction forces a fundamental reevaluation of defense assurance, institutional governance, and systems architecture. Traditional military and administrative frameworks operate on the premise of human accountability. Frameworks such as the United States Department of Defense Directive 3000.09 are designed explicitly to ensure commanders and operators exercise appropriate levels of human judgment over the use of force1. In a polity entirely devoid of a human population or administrative structure, inserting a ceremonial human-in-the-loop requirement is struct.

Open report →

EVR-0019

Evulgare Assurance Simulation Workbench: Product Architecture, Scientific Visualization, WebXR, Accessibility, and Performance

The transition of Evulgare from a conventional web presence to a unified Assurance Simulation Workbench necessitates a radical architectural paradigm shift. Derived from the Latin root evulgare, meaning "to make public" or "divulge"1, the platform's core mandate is the transparent exposition of mathematical and physical bounds governing complex, autonomous decision-making systems. The evidence dictates that achieving this transparency without compromising institutional authority requires a strict decoupling of deterministic proof generation from browser-based rendering. The backend Python 3.13 service layer must.

Open report →