ASBOSResearch
asbos.orgasbos.orgProposalProposal

Research portal / Experiments

Not started · October 2026

Experiments

No trial has been run. The sections below are protocols the prototype will be required to follow. They are not descriptions of observed behavior.

Each scenario will be given to the rule-based system, the single agent, and the ASBOS multi-agent design. The methodology states what is held constant and which measures are named. Results will be posted on this page after the experiments are conducted. Until then, this page will not show scores.

What a completed run would record

For each approach, on each scenario: the action or escalation chosen, the autonomy level used, whether a person had to approve or intervene, whether the action stayed inside policy, and the log a supervisor would need in order to reconstruct the decision. The exact fields will be fixed with the scoring rules, which are not yet written.

Scenario 1 · Planned

Late arrival or no-show

A scheduled officer does not arrive. The planned test asks the system to detect the gap, judge whether the post is uncovered, consider contact, replacements, qualifications, overtime, and travel, and decide whether a supervisor must approve coverage.

  1. Detect the absence
  2. Determine whether the post is uncovered
  3. Attempt to contact the assigned officer
  4. Evaluate available replacements
  5. Verify qualifications
  6. Check overtime
  7. Consider travel distance
  8. Recommend or assign coverage
  9. Determine whether supervisor approval is required

Scenario 2 · Planned

Guard leaves an assigned geofence

An on-duty officer leaves the assigned site. The planned test asks the system to distinguish normal activity, an authorized exception, a temporary problem, a coverage gap, or an event that needs a supervisor. A location anomaly is not to be treated as employee misconduct.

  1. Judge whether the movement is normal activity
  2. Judge whether it is an authorized exception
  3. Judge whether it is a temporary operational issue
  4. Judge whether coverage is now incomplete
  5. Decide whether a supervisor needs to see it
  6. Do not treat the location anomaly as misconduct

Scenario 3 · Planned

Missed patrol checkpoint

A required checkpoint is not completed on time. The planned test asks the system to consider recent checkpoints, elapsed time, location, site rules, active incidents, and officer status before it continues monitoring, contacts the officer, recommends an action, or escalates.

  1. Review previous checkpoint activity
  2. Measure time since the last activity
  3. Check current location
  4. Apply site requirements
  5. Check active incidents and officer status
  6. Continue monitoring, contact the officer, recommend an action, or escalate

Scenario 4 · Planned

Incident with coverage impact

An incident pulls an officer off a post or requires more people. The planned test asks the field, workforce, and dispatch agents to coordinate response, replacement coverage, supervisor notification, documentation, and follow-up.

  1. Coordinate the incident response
  2. Reassess staffing
  3. Arrange replacement coverage
  4. Notify a supervisor
  5. Document the operational change
  6. Track follow-up

Results

Not available. There is no table of resolution rates, response times, error rates, or workload estimates because those measurements have not been made.