Reliability across teams
One standard that holds for many teams, instead of one solution per team.
Career
Senior SRE in payment infrastructure, open to Staff SRE roles.
What I do at staff scope
SLOs
Targets a team can measure and the business can read, with the error budget deciding what comes first.
Incidents
From the response to the postmortem that becomes a change in the system, not a report in a drawer.
Platform
The reliable path is the easiest one to follow: other teams ship without waiting for me.
AI-native systems
Reliability where a model sits in the middle: declared origin, a spend ceiling, and a person who approves before anything goes live.
The proof that is already public
Reliability Pipeline
The method in everything I ship: declared origin, automatic critique with veto, a spend cap, and a person approving before anything is published.
Aurora Concierge
AI-powered service for a homecare operation, on a CRM of my own: inbox, takeover, human release. The final word belongs to a person, in a place built for it.
Acolhera
The same platform, white-labeled for health operations. The design takes a second brand without becoming a second system: same pipeline, different owner. It is where the per-project-plus-maintenance model already runs.
Notes
The public archive: how I think through a problem before solving it.
Two problems I solved
Each with its own model page, running in the browser.
For a conversation about a Staff SRE role, the shortest way is the booking page.