Research / Public proof
The research surface joins authored research, published software and the evidence discipline behind public technical claims.
Authorship remains attached to the person who wrote the work. Publication authority remains attached to the company that publishes it.
Research publication / 001
Exploratory research on limits, conditioning, perception, pattern recognition and the failure mode where a pattern outruns its evidence.
Published software / 002
Published continuous-integration work centred on source-to-artifact provenance, durable deployment evidence and the idea that a receipt should carry more weight than a green check.
Published software / 003
A tenant-scoped agent registry with policy-aware, residency-enforced, grounded memory recall — tenant isolation, route authorization and subject erasure proven by automated test, not just documented. Built on Google Cloud (Cloud Run, Firestore, Vertex AI / Gemini 3.5-flash).
Benchmark status
No performance benchmark is asserted on this page today. A future baseline appears only when the metric, operating conditions, versions and methodology are publishable together.
Evidence discipline
01
A claim is published with the method, conditions and limitations needed to interpret it.
02
A metric is published with its unit, version, measurement date and provenance.
03
A benchmark is never promoted from planned or internal status merely because code exists.
04
A translated or regional paper keeps the underlying evidence envelope intact; geography does not change the measured claim.