STANDARD TRACE / VIRGIL + AEGIS

Human presence is not human governance.

Standard Trace tests whether a defined claim of human control is structurally supported by system architecture, operator conditions, execution timing, intervention capability, and available trace.

STANDARD TRACE / ANALYTICAL SEQUENCEHOVER · FOCUS · TAP
STEP 02 / VIRGILWhat may the available record legitimately support?

Qualify each claim-relevant proposition by its trace basis, temporal meaning, inferential bridge, and support boundary.

This sequence organizes analyst review. It does not produce an automatic finding.

01 / GOVERNANCE QUESTION

Could the human still govern the action?

An operator may be present, attentive, trained, authorized, and able to respond after an event. Those facts do not establish that the operator retained a meaningful opportunity to alter the execution before it became materially committed.

SEQUENCE / APotentially governable interval
  1. 01System selects action
  2. 02Legible signal becomes available
  3. 03Intervention remains actionable
  4. 04Execution commits

The signal arrives while a meaningful intervention remains available over the execution under review.

SEQUENCE / BPost-commitment intervention
  1. 01System selects action
  2. 02Execution materially commits
  3. 03Alert becomes available
  4. 04STOP command is recorded

The response may support recovery, mitigation, or later control. It does not establish governance over the action already committed.

02 / ASSESSMENT STRUCTURE

What Standard Trace tests

One claim. One bounded configuration. A disciplined separation between assertion, evidence, observation, inference, limitation, and finding.

Explore the assessment workspace
03 / ASSESSMENT IN PRACTICE

Assessment in Practice

Human presence is visible. Human governance must be demonstrated.

This fictional example follows a single automated action from system classification through material commitment, operator notification, intervention opportunity, and available trace.

CLAIM UNDER REVIEW
A trained operator can intervene before the automated system commits the placement action.
ASSESSMENT BOUNDARY

Fictional warehouse placement cell · one automated placement · one execution interval

SAMPLE ID / AES-WH-01
AUTOMATED EXECUTIONThe system selects and commits the placement before the alert is displayed.

Classification, trajectory selection, motion, and material commitment form one ordered execution path.

  1. SYS-01
    System detects and classifies the case

    The case condition is classified and accepted for automated handling.

  2. PLN-01
    Placement trajectory is selected

    The controller selects the placement path for the classified case.

  3. ACT-01
    Motion begins

    Actuation begins along the selected placement trajectory.

  4. CMT-01
    Action reaches material commitment

    The reviewed placement can no longer be prevented, redirected, or meaningfully changed.

    MATERIAL COMMITMENT
  5. ALT-01
    Alert becomes available at the interface

    The exception state is transmitted to the operator interface.

  6. CMD-01
    STOP command is recorded

    An authorized stop request enters the controller.

  7. ACT-02
    System stops later motion

    Subsequent motion is halted after the stop request.

  8. TRC-01
    Qualified record is synchronized for review

    The execution record closes with the reviewed action already committed.

DECISIVE RELATIONT+00.360 Material commitmentT+00.410 Alert available
DEFINED GOVERNANCE CLAIMFinding: Unsupported

The operator was present and authorized to intervene, but the alert became available after the placement trajectory became materially committed.

This finding applies only to the defined claim, action, configuration, and execution sequence shown.

Demonstration only. This fictional example illustrates the Standard Trace assessment method and does not represent a finding concerning any identified commercial system.

Review the expanded evidence packet
04 / POSSIBLE FINDINGS

A finding is bounded by the claim and the trace.

01

Supported

The architecture, operator conditions, timing, intervention capability, and trace support the defined governance claim.

02

Limited

Governance capability existed under specified conditions or over a narrower interval than claimed.

03

Unsupported

Available evidence does not establish that the human could govern execution before material commitment.

04

Shadowed

The human appears to hold authority while operative control rests elsewhere in the system or organization.

05

Misrouted

Responsibility is assigned to a person or role without structural capacity to govern the execution under review.

05 / COMMERCIAL APPLICATIONS

Applied where the governance claim already matters.

For product safety, deployment, procurement, assurance, insurance, enterprise risk, human factors, and responsible automation teams.

Pre-deployment assessment

Test governance language against the system configuration before deployment.

Post-execution review

Reconstruct the governing interval and available trace after a defined event.

Procurement assurance

Specify evidence needed to evaluate a vendor’s human-control claim.

Vendor-claim testing

Separate product language from structurally supported operator capability.

Operator-governance review

Examine whether the assigned role can govern within actual timing and workload.

Evidence-requirements design

Define the records needed for later governance analysis.

Review service families
06 / DIAGNOSTIC INDEPENDENCE
“Payment purchases analysis, not a conclusion.”

Standard Trace engagements are conclusion-independent. The defined claim may be supported, limited, unsupported, shadowed, or misrouted. Findings are constrained by the system boundary and available evidence.

07 / RESEARCH LINEAGE

From execution to governance-claim analysis.

PUBLISHED OPERATIONAL REFINEMENT / AEGISVIRGIL

Trace qualification and resolution-sensitive guided execution reconstruction.

OPEN METHOD
BOUND THE CLAIM

Define the claim before the incident defines it for you.

Discuss a bounded assessment