Who I am and how I work

I’m a product leader who builds the infrastructure that makes data trustworthy enough for AI systems and people to act on without re-checking it. Twenty years across data platforms, semantic layers and model measurement, most of it spent turning one-off data requests into reusable infrastructure that compounds. The current chapter is the semantic and data quality layer for a large finance organization, and a public thesis about trust infrastructure at thetruthlayer.dev.

Rather than run the independent work as a pile of prototypes, I run it as an operating repo. Daily sessions decide, every ruling goes into a ledger with a date, batches build from that ledger, and a Friday sync rewrites the state file so the next week starts from the record rather than from memory. Every launch is logged against the post that shipped, and the ones that failed are logged the same way. That’s what the year page is drawn from.

The idea I keep coming back to is that a number should carry its own warrant. A dashboard that looks right isn’t enough. The number needs a contract that says who signed, what it covers and when it stops being true. Verdict, Overlay and MeetingFlow are three attempts at that idea in three registers, and the work pages show what each one decided.