Decision execution infrastructure is the layer between a decision being made and the work it causes being tracked, owned, and done — with a policy check in front of every action and one record of who approved it, across every tool it touches.
Engineer. Currently the only person building Conductor, with one contract engineer planned as the first use of the raise. Everything on this site — the pipeline, the memory store, the copy you’re reading — is his work.
The architecture decision that defines the product: the guardrail stage sits in front of execution, not beside it. A system that acts in a team’s name has to be boring before it can be clever — policy first, then action. That choice is why Conductor executes real work in real tools instead of drafting suggestions it can’t be trusted to send.
He writes the build log below himself. It’s terse because it’s real.
Updated weekly since May 2026. Every entry dated, nothing backfilled. The permanent home of every update, oldest at the bottom.
The category sentence now carries the policy check and the audit trail. Compare and Pitch rebuilt around what Linear and Notion shipped this year; the policy model and OAuth scopes published on Architecture.
Every page now serves an investor or an ops lead doing diligence. Category language made identical across all seven pages. No pricing page, no forms — one CTA: talk to the founder.
Moved off “founder productivity.” New ICP: operations and engineering leads at 20–150 person companies running Linear + Slack. The product didn’t change — the buyer did.
A 90-second Slack summary: what happened, what’s still open, and why the original decision was made. The visible proof of the memory loop.
Four tools now executed natively: Linear, Slack, Notion, Gmail. External email is drafted, never sent without a human — enforced in the guardrail stage, not by convention.
Per-workspace memory store landed. Retrieval measured under 50ms. Every approved, edited or rejected card now writes back with its rationale.
Nothing reaches a tool without passing policy first. Slower by milliseconds, trustworthy by design. This reordering is the whole product philosophy in one commit.
One sentence became a Linear ticket and a Slack message with no copy-paste in between. Watch the first full loop → Rough, but the loop closed. Everything since has been making that boring and reliable.
Executing end to end in Linear, Slack, Notion and Gmail. Pre-launch: no self-serve, no SOC 2, no SSO.
Named first in the risk list, not last. One contract engineer is the first use of funds.
