Three connected accountability layers How KillChains, KillWebs, and Evulgare fit together KillWebs.com Evulgare.com
KillChains.com v1.24.0
Machine-speed decisions need machine-held evidence. Bounded education only: no real targets, operational control, executable payloads, or live-system actions. A human click is not a liability transfer. For production evidence and accountability software, visit Evulgare.com.

Institutional Authority Casebook

Operational delegation is not the same as legal authority.

Compare six source-reconciled cases across military decision support, bounded defensive automation, developmental mission autonomy, predictive enforcement, traveler screening, and watchlisting. Each case identifies what the machine performs, which institution sets the objective, who can interrupt or correct the process, and what remains publicly unknown.

Six reviewed casesSix institutional domainsMaximum three-case comparisonNo ratings or procurement advice

Answer-first summary

Direct answers

Release 1.24.0 · reviewed · evidence states

What is the Institutional Authority Casebook?

It is a source-reconciled comparison of real programs showing what software performs, which institution sets the objective, who can approve or interrupt action, and which decisive details remain public unknowns.

Read the supporting section

Does operational delegation give a machine legal authority?

No. A machine may collect, classify, prioritize, recommend, or execute a bounded function while human institutions retain formal office, authorization, correction duties, and liability.

Read the supporting section

Does the casebook rank systems or institutions?

No. It compares functions, lifecycle status, authority ownership, intervention paths, unknowns, and evidence boundaries without calculating capability, legality, effectiveness, procurement, or safety scores.

Read the supporting section

How to read the casebook

Separate technical capability from institutional permission.

A machine may collect, fuse, classify, rank, recommend, or automatically execute a bounded function. Those functions do not by themselves confer legal office, command authority, fiduciary status, moral agency, or independent liability.

01

Document the function

State exactly what the public evidence supports: retrieval, fusion, classification, prioritization, recommendation, screening allocation, mission autonomy, or automatic bounded action.

02

Locate the authority

Identify who sets objectives, owns data, approves consequential action, can interrupt the system, correct errors, and retire the program.

03

Preserve the unknown

Do not convert undisclosed thresholds, operating modes, error rates, or intervention windows into either “human-controlled” or “fully autonomous.”

Source-reconciled register

Six cases, one authority vocabulary

Filter the records or select up to three for a side-by-side comparison. Every source link resolves through the existing Source Review registry.

Reset

6 of 6 cases shown.

Military decision support · United States

Maven Smart System

Operational

The official program description presents Maven Smart System as a tactical AI platform for sensor-data fusion, object detection, tracking, and decision support. The public record used here does not establish autonomous weapon release.

Institution
U.S. Chief Digital and Artificial Intelligence Office and Department of Defense users
Domain
Military decision support
Public sources
1
Linked claims
2
Documented machine functions
Sensor or record collectionData fusion and associationDetection or classificationTrack maintenanceDecision support or recommendation
Authority and evidence details

Practical authority migrated

  • Large-scale sensor-data fusion
  • Object detection and track formation
  • Prioritization of information presented to operators

Human or institutional authority retained

  • Mission objective
  • Operational authorization
  • Rules and constraints
  • Legal accountability

Public unknowns

  • Exact data feeds and promotion thresholds
  • Field error and calibration rates
  • Operational configurations
  • The precise relationship between a recommendation and every downstream action

Source trail

Claim Lineage

Does not establish: This record does not establish that Maven Smart System independently authorizes weapon release or that every fused output is accurate, complete, or independently verified.

Bounded defensive automation · United States and disclosed operators

MK 15 Phalanx Close-In Weapon System

Operational

The U.S. Navy describes Phalanx as a self-contained close-in defense system that can automatically search, detect, evaluate, track, engage, and assess bounded incoming threats.

Institution
U.S. Navy program and shipboard command structure
Domain
Bounded defensive automation
Public sources
3
Linked claims
2
Documented machine functions
Sensor or record collectionDetection or classificationTrack maintenancePrioritization or queue orderingAutomatic bounded defensive engagement
Authority and evidence details

Practical authority migrated

  • Local threat evaluation
  • Track prioritization
  • Automatic defensive engagement inside a bounded envelope
  • Immediate assessment

Human or institutional authority retained

  • Mission and defensive policy
  • Mode selection and activation
  • Supervision and deactivation
  • Legal responsibility

Public unknowns

  • Exact threat-logic thresholds
  • Every customer configuration
  • False-positive and failed-engagement rates
  • All mode-specific intervention timelines

Source trail

Claim Lineage

Does not establish: Automatic defensive engagement does not prove unrestricted anti-personnel authority, contemporary machine-learning use, or one universal operating configuration.

Developmental mission autonomy · United States

Collaborative Combat Aircraft

Developmental or testing

The Air Force describes CCA as a developmental family of semi-autonomous aircraft and states that humans retain weapons-release authority throughout the described development and testing context.

Institution
U.S. Department of the Air Force
Domain
Developmental mission autonomy
Public sources
1
Linked claims
1
Documented machine functions
Autonomous flight or mission executionSensor or record collectionData fusion and associationTrack maintenanceDecision support or recommendation
Authority and evidence details

Practical authority migrated

  • Autonomous flight and mission functions
  • Machine-speed teaming and task execution
  • Sensor and mission coordination

Human or institutional authority retained

  • Weapons-release authority in the described testing context
  • Mission objectives
  • Program safety and legal responsibility

Public unknowns

  • Final operational doctrine
  • Future span of control
  • Communications-loss behavior
  • Mission-autonomy software configuration
  • Field performance outside testing

Source trail

Claim Lineage

Does not establish: Developmental flight or mission autonomy does not establish autonomous weapon release, final fielding, or one settled operating doctrine.

Predictive enforcement · Netherlands

Crime Anticipation System

Discontinued

The official Dutch algorithm register describes CAS as a place-based system that transformed recent police records into neighborhood crime-risk estimates and records it as out of use from December 2025.

Institution
National Police of the Netherlands
Domain
Predictive enforcement
Public sources
2
Linked claims
4
Documented machine functions
Place-based risk forecastingPrioritization or queue orderingDecision support or recommendation
Authority and evidence details

Practical authority migrated

  • Daily place-risk estimation
  • Ranking geographic cells for attention
  • Standardized analytical input into deployment discussions

Human or institutional authority retained

  • Patrol and deployment decision
  • Local contextual interpretation
  • Program discontinuation
  • Public-sector accountability

Public unknowns

  • Complete local use patterns
  • Incremental value over simpler mapping
  • Full effect on patrol distribution
  • Complete error and subgroup analysis

Source trail

Claim Lineage

Does not establish: A place-risk map did not identify a particular future offender, prove crime reduction, or automatically authorize police contact with any person.

Traveler screening · United States

Secure Flight

Operational

TSA describes Secure Flight as a risk-based passenger prescreening program that receives passenger information, compares records under controlled criteria, and returns screening or boarding instructions before checkpoint arrival.

Institution
Transportation Security Administration
Domain
Traveler screening
Public sources
2
Linked claims
0
Documented machine functions
Identity resolution and record linkagePrioritization or queue orderingScreening allocation or boarding instruction
Authority and evidence details

Practical authority migrated

  • High-volume identity comparison
  • Risk-based prescreening
  • Automated allocation of checkpoint or boarding instructions

Human or institutional authority retained

  • Program criteria and legal purpose
  • Identity-resolution and redress processes
  • Enforcement and boarding authority
  • Institutional accountability

Public unknowns

  • Complete matching and list rules
  • Aggregate false-positive and subgroup error rates
  • All data-sharing relationships
  • The practical timing of every correction pathway

Source trail

Does not establish: Secure Flight prescreening is not itself proof that a person committed or will commit terrorism, nor is every matching or allocation function necessarily machine learning.

Watchlisting and identity resolution · United States

U.S. terrorism-watchlisting lifecycle

Operational

The public record describes a federated lifecycle in which agencies originate and nominate information, NCTC and FBI perform different reviews, the Threat Screening Center manages acceptance and identity resolution, and downstream agencies decide what their own authorities permit.

Institution
Interagency watchlisting enterprise led by the FBI Threat Screening Center for acceptance and management functions
Domain
Watchlisting and identity resolution
Public sources
2
Linked claims
1
Documented machine functions
Identity resolution and record linkageData fusion and associationRecord dissemination and encounter supportPrioritization or queue ordering
Authority and evidence details

Practical authority migrated

  • Large-scale identity resolution
  • Cross-agency record consolidation
  • Automated dissemination and encounter support
  • Prioritization of records for review or screening

Human or institutional authority retained

  • Nomination and sufficiency review
  • Acceptance and removal decisions
  • Downstream agency action
  • Redress and institutional accountability

Public unknowns

  • Controlled nomination and matching thresholds
  • Complete subset criteria
  • Aggregate error denominators
  • All handling codes and data-sharing arrangements
  • The full basis for individual records

Source trail

Claim Lineage

Does not establish: A watchlist record is not itself an arrest warrant, criminal charge, probable-cause finding, inadmissibility decision, or proof of terrorism.

Maximum three. Extra selections are ignored server-side.

Maximum-three comparison

Where did practical authority move?

The matrix compares functions and institutional ownership. It does not calculate a capability, legality, effectiveness, or safety score.

Military decision support

Maven Smart System

Operational
Objective owner
Department of Defense mission and command authorities define the operational objective; the public program page does not identify every mission-level owner.
Transformation owner
CDAO program and platform teams own the released fusion, detection, tracking, and decision-support capability.
Approval owner
Human operational and command authorities retain consequential mission decisions in the bounded public description.
Interruption owner
Authorized operators, commanders, and system administrators are the plausible interruption owners; exact operating controls are publicly unspecified.
Correction owner
Program governance and the owning data organizations must correct source data, model behavior, and downstream records; the public correction workflow is unspecified.
Legal authority owner
The Department of Defense and its human chain of command retain legal and institutional authority.

Transformation chain

  1. Sensor and data inputsIngest and normalizeData-access and mission-purpose controls
  2. Fusion, detection, and trackingAssociate observations and create decision-support outputsAnalyst review and operational context
  3. Operational decisionPresent decision supportHuman authorization and responsibility

Intervention path: Authorized users can question, withhold, or escalate the machine-produced picture; exact live controls and override windows are not public.

Public boundary: This record does not establish that Maven Smart System independently authorizes weapon release or that every fused output is accurate, complete, or independently verified.

Bounded defensive automation

MK 15 Phalanx Close-In Weapon System

Operational
Objective owner
Naval command, doctrine, and mission planning define the protected asset, operating conditions, and permitted defensive purpose.
Transformation owner
The Navy program office, developer, and maintainers own the released threat logic and system configuration.
Approval owner
Commanders and operators choose the operating mode and activation conditions; the automatic mode can perform local engagements without a fresh target-specific click.
Interruption owner
Shipboard operators retain supervisory and deactivation responsibilities, although public sources do not disclose every timing and mode detail.
Correction owner
Program, maintenance, testing, and command authorities own configuration correction, software changes, and post-event review.
Legal authority owner
The human naval chain of command and deploying institution retain authority and accountability.

Transformation chain

  1. Local radar observationsSearch, detect, and trackConfigured operating mode
  2. Threat evaluationEvaluate and prioritize bounded incoming objectsDoctrine, configuration, and testing
  3. Defensive engagementEngage and assess in automatic modeSupervision, deactivation, and command accountability

Intervention path: Operators can supervise and deactivate the system, but public evidence does not establish every intervention window, target-class configuration, or mode used by every operator.

Public boundary: Automatic defensive engagement does not prove unrestricted anti-personnel authority, contemporary machine-learning use, or one universal operating configuration.

Developmental mission autonomy

Collaborative Combat Aircraft

Developmental or testing
Objective owner
Air Force operational and acquisition authorities define program objectives and command relationships.
Transformation owner
The CCA program, autonomy-software providers, test organizations, and integrators own the developmental transformations.
Approval owner
The Air Force states that a human retains weapons-release authority in the described development and testing context.
Interruption owner
Human command and test authorities retain abort, safety, and range-control functions; future operational details remain developmental.
Correction owner
Program offices, vendors, test organizations, and safety authorities own defect correction and revalidation.
Legal authority owner
The human military command structure retains legal authority over weapons release and operations.

Transformation chain

  1. Mission objectiveReceive bounded mission intentMission and test authorization
  2. Autonomous flight and mission behaviorExecute permitted flight and teaming functionsSupervision and safety constraints
  3. Weapons releaseSupport integration and execution after authorizationHuman release decision

Intervention path: Human command, test, and safety authorities remain the documented control point, but future operational timing and interface details remain under development.

Public boundary: Developmental flight or mission autonomy does not establish autonomous weapon release, final fielding, or one settled operating doctrine.

A machine can exercise substantial operational control while human institutions retain the formal office, authorization, correction duty, and liability. Conversely, nominal human presence does not prove meaningful control where time, information, or intervention authority is inadequate.

Evidence boundary

Every case remains bounded by its source class.

Government pages establish what an institution publicly says. Manufacturer pages establish product claims. Oversight reports document their own findings. A program record cannot fill in controlled thresholds, configurations, error rates, intervention timing, or real-world effectiveness that the public evidence does not disclose.

Correction and review

Each source has a stable review record, and every case has an explicit correction path. Corrections remain repository-authored and reviewed; this page does not accept public edits or automatically change factual status.

Open Source ReviewTrace Claim Lineage

Ecosystem boundary

Learn the failure here. Make the deployed machine answerable at Evulgare.

KillChains.com remains a synthetic simulation and public-research environment. KillWebs.com remains the sister learning environment for governed network paths. Stop using software that makes the nearest human explain a decision they could not see, verify, or control. Real-system evidence capture, software and model lineage, authority reconstruction, operator-view reconstruction, incident causality, and deployed-system answerability belong at Evulgare.com.

The Casebook compares public institutional authority. Evulgare is the production destination for proving which authorities, software, models, evidence, and human interfaces were actually present in a real system.

MAKE THE MACHINE ANSWERABLE.Open Evulgare.comOpen the Answerability LabReview the ecosystem split