Blog.

Subscribe via RSS

Research, perspective, and ideas in progress.

Missing evidence is not negative evidence.

An empty provenance field can mean not observed, not collected, unavailable, withheld or not applicable. Accountable AI systems should preserve that difference before making a decision.

Read article

A timestamp is not a causal chain.

When agents act across services, matching timestamps do not prove which event informed another. Accountable systems need causal links, provenance relations and independently observed effects.

Read article

An AI incident needs a decision trace.

An alert can show that something went wrong. A decision trace should show which model, context, policy, authority, tool action, override and observed effect produced the incident response.

Read article

Similarity is a lead, not a lineage.

A technical match can identify something worth reviewing. It cannot, by itself, establish derivation, access, permission, authorship or ownership.

Read article

A governance metric needs a denominator.

A count is not yet a governance signal. To support a decision, a metric should name the eligible population, time window, version, exclusions, steward and action threshold.

Read article

A claim should carry its conditions.

An AI claim becomes more governable when its scope travels with it: the evidence and version, intended context, responsible authority, uncertainty, challenge path and review trigger.

Read article

Representation changes what a study can resolve.

A more representative dataset can do more than widen participation. In the right study design, it can sharpen inference, reveal population-specific signals and show where a model may not travel unchanged.

Read article

Local data is not the same as local control.

Federated learning can keep original records inside each participant’s environment. Privacy and authority still depend on what updates reveal, who governs aggregation and how the global model is released.

Read article

A governance control needs a steward.

Shipping a control is a beginning, not a finish line. Someone must own its review, evidence and response when the system or its context changes.

Read article

Interoperability is not organization.

A common protocol can help agents exchange tasks and artifacts. It cannot decide who is responsible, who may act or how a disputed result should be corrected.

Read article

Governance needs a work surface.

If governance exists only in a policy document, the people doing the work still have to reconstruct it at the moment of decision.

Read article

Agreement needs independence.

A multi-agent answer is strongest when disagreement has a trace: independent first judgments, cited evidence, and a recorded path to the final decision.

Read article

Containment is not recovery.

Stopping an AI incident limits the damage. Recovery begins when trusted, authorized work can resume—and the organization can show why it should not recur.

Read article

The dashboard is not the control.

Visibility helps people understand an AI system. Governance becomes operational only when an authorized decision can shape the action before it crosses the boundary.

Read article

Attribution should survive subtraction.

A provenance record can show who and what was present. A controlled counterfactual can test which contribution materially changed the result—without pretending that technical influence settles a legal question.

Read article

Human review should leave an inheritance.

A review that ends at approve or reject wastes its most valuable signal. The harder governance question is how a correction should change future work without becoming unlimited permission.

Read article