Posts Archive
Technical and litigation notes
Ontology as Power — Who Defines Behavioral Reality?
A behavioral ontology decides what concepts exist, how they are defined, and which cultures they assume. The team that writes the ontology defines the system's model of human behaviour. That is a political act as much as a technical one.
AI Governance & RegulationGoverning AI Safe Language — Who Writes the Rules?
The governance wrapper translates harmful labels into safe phrases. But who decides which phrases are safe? This post examines the governance deficit in safe-language design.
Data Privacy & GDPREvent Buses and Data Minimisation
A behavioral event bus logs every signal emitted between engines. Those signals are personal data. This post examines the conflict between event logging for audit and GDPR data minimisation.
AI Governance & RegulationExplainability as Legal Evidence
An explainability trace generated at scoring time can be produced in discovery. This post examines chain-of-custody requirements, forensic soundness standards, and the gap between technical explainability and legal admissibility.
AI Governance & RegulationConfidence Scores and the Illusion of Precision
A confidence score presented without its uncertainty band and reducer list becomes a claim of certainty. This post explores the liability of precision theatre in AI outputs.
AI Governance & RegulationThe Control Plane as a Governance Chokepoint
The control plane knows everything: which engines ran, in what order, and with what outputs. That makes it the ideal — and perhaps the mandatory — place to enforce jurisdiction-specific AI regulation.
AI Governance & RegulationEngine Registries and the Right to Know
Should individuals have the right to know which AI engines scored them? GDPR Article 22 provides a partial answer. This post makes the case for mandatory engine-level disclosure.
AI Governance & RegulationWho Is Accountable When a Behavioral AI System Labels Someone?
When an AI system with 34 engines labels a person, the accountability chain breaks across engineers, vendors, and decision-makers. This post maps the gaps and proposes mandatory engine accountability registration.