Executioner

Executioner is an open-source execution planning system that turns unstructured brain dumps into committed outcomes.

It is built around one practical question:

What should be executed today?

Executioner takes loose thoughts, constraints, playbooks, and existing commitments, then produces a schedule the user can review, commit, execute, or abandon. The AI layer helps extract candidate outcomes from messy input, but scheduling rules, capacity checks, daily deduplication, and execution closure stay in inspectable code.

This repository is the public source release for Executioner's core app and product logic. Hosted production configuration, customer data, private access links, and deployment operations are managed separately.

What Executioner Does

• Turns messy brain dumps into proposed outcomes, checklists, constraints, and schedule edits.
• Uses buckets and playbooks so planning context is explicit instead of remembered manually.
• Applies deterministic scheduling rules for execution load, daily outcomes, dependencies, and capacity.
• Requires every outcome to end as executed or abandoned.
• Keeps public development grounded in test data and documented local setup.

Trust Model

Executioner is built around a narrow public boundary:

• User-owned context: Brain dumps and playbooks may contain sensitive personal or operational context.
• Deterministic scheduling rules: Capacity, deduplication, dependencies, and outcome closure are handled in code.
• Server-side credentials: Supabase service-role keys, Stripe secrets, model keys, webhook secrets, and Resend keys must never be exposed to the browser.
• Review before commit: AI proposals become drafts first; the user reviews before changes are committed.
• Production separation: This repo excludes private deployment wiring, customer data, access keys, and internal runbooks.

For more detail, read the architecture guide and security policy.

Architecture

At a high level:

1. The React app handles onboarding, brain dumps, schedule review, execution, and account access.
2. Supabase Auth and Postgres provide identity, access state, outcomes, checklists, buckets, playbooks, and constraints.
3. Edge functions handle checkout, account access, transcription, and brain dump processing.
4. The brain dump engine preprocesses input, adapts model proposals, decomposes drafts, and packs them into a schedule.
5. Deterministic rules enforce execution load, daily deduplication, dependencies, and capacity.

Quick Start

Use Node 24 and Bun 1.1 or newer.

npm install
cp .env.example .env.local
npm run typecheck
npm test
npm run build

Run the app locally:

npm run dev

Open http://localhost:8080.

Verification

npm run typecheck
npm test
npm run lint
npm run build
npm run audit:prod

Security-sensitive changes should include targeted checks around auth, access keys, Supabase RLS assumptions, Stripe checkout, account deletion, transcription, and brain dump processing.

Repository Boundary

This public repo should include reusable Executioner product logic and public documentation only.

Included:

• Brain dump review, scheduling, execution, buckets, playbooks, constraints, and app workflow state.
• Deterministic scheduling rules, capacity logic, daily deduplication, dependency handling, and account-access logic.
• Tests, migrations, public docs, and generated repository assets needed to understand the product.

Excluded:

• Production secrets, customer data, private access links, provider settings, hosted deployment wiring, and internal runbooks.
• Local agent files, recovery plans, scratch files, logs, Supabase .temp metadata, generated attachments, and private workflow docs.
• Historical private repository state. Public releases are cut from a clean export.

Project Docs

• Architecture
• Contributing
• Security
• Roadmap
• Code of Conduct

Website

The public website is executionr.app.

License

Executioner is released under the MIT License.