Most people separate "deep thinker" from "gets things done." I find that distinction mostly useful for avoiding accountability.

I'm a Fractional COO / Operations Architect. Consulting since 2002, building things that work inside organizations that sometimes don't.

My specific obsession: the gap between what an organization says it does and how it actually operates, and the human decisions, or their absence, that create that gap.

This shows up in my work as:

• Task governance and self-running administration: process where ownership is visible, drift gets caught early, and nobody is chasing paperwork.
• Asset and cost accountability: every tool, domain, and license accounted for and current, so an organization can execute a scale change in a week.
• Access and credential accountability: self-hosted secrets and credential management for organizations whose current security model is that the sysadmin knows all the passwords.
• AI in operations, humans accountable: automations and agents run through daily work. One rule is non-negotiable: no AI output acts without human review and approval.
• Grants Intelligence: an AI-assisted pipeline that ingests and scores funding programs against an organization's profile.

Currently: process and governance lead (COO function) across the Metis Foundation portfolio (Metis L2, ZKM, GOAT Network, LazAI, HoZK), and COO of CryptoChicks, a non-profit teaching AI and blockchain skills to women and youth worldwide.

In practice that means operations for a distributed, multinational, remote team with a deliberately non-enterprise mindset. Enterprise process does not survive that environment. Neither does no process. Working out what does is the most interesting problem I have had.

AI-assisted ingestion and scoring of funding programs and partnership candidates, Power BI reporting, and a ClickUp pipeline the team works from.

First working version shipped in one week. In production: 36 funding programs and 100+ scored leads tracked. Co-application discovery shipped as the first stage; improvements in progress.

Built for CryptoChicks. The model is portable to other resource-constrained non-profits running on grant funding.

I use philosophical frameworks the way architects use load calculations: not decoration, the thing that determines whether the structure holds.

A few lenses I apply constantly:

Dialectics: every system contains its own contradiction. An organization that says it values accountability but has no mechanism to enforce it is already failing; it just hasn't noticed yet.

Epistemic humility: most bad decisions aren't made by bad people. They're made by people who didn't know what they didn't know, at the moment it mattered most.

Test-driven governance: before implementing any policy or decision, write the falsifiable conditions it must satisfy. If it can't pass its own tests on paper, it shouldn't pass in a vote.

I write about this at the Operators Guild and publish governance frameworks and operating policy on the Unified Governance forum.

• Consulting since 2002, delivered almost entirely as an outsider working inside someone else's organization, accountable from the first week without institutional cover. Nuclear (Bruce Power), fintech (Servus Credit Union), Government of Alberta departments, Edmonton Police Service, City of Edmonton, Workers' Compensation Board.
• Master of Computer Science, evaluated and confirmed by World Education Services (WES), November 2025.
• Currently: Decentralization Coordinator, Process & Governance (COO function), Metis Foundation. COO, CryptoChicks (volunteer).
• Toronto-based, remote and async-first, working across NA and EU time zones.

Stack I work in: ClickUp, Power BI, Google Cloud, Google Workspace, Microsoft Azure and Microsoft 365, .NET, SQL Server, Discourse and the infrastructure under it, self-hosted secrets and credential management, Claude Code, and whatever the engagement requires.

A penetration tester. A compliance checkbox vendor. Someone who runs your payroll, manages your people, or firefights without a mandate to fix the process underneath.

If your systems work exactly as documented and your team does exactly what it's supposed to, you don't need me.

If there's a gap between the org chart and reality, between the policy document and actual behavior, that's the gap I've spent two decades building infrastructure to close.

Building something and hitting the operations wall? Read something here that made you argue with your screen?

→ LinkedIn → Operators Guild writing → andrei@etherni.io

Serious conversations preferred.

Opinions are my own. Frameworks are open source. Accountability is non-negotiable.