Executioner is an open-source public source release for an execution planning system. The current focus is clarity, trust, and making the core product logic inspectable.
- Keep brain dump proposals review-before-commit.
- Keep scheduling rules deterministic and easy to test.
- Keep buckets, playbooks, constraints, and execution load explicit.
- Keep local setup and public repository boundaries clear.
- Keep private deployment details and customer data outside the public repo.
- More tests around brain dump proposal adaptation and scheduling previews.
- More coverage for daily deduplication, dependency ordering, and constraint-heavy schedules.
- Better local fixtures for onboarding, buckets, playbooks, constraints, and executed history.
- Clearer docs for account access, data deletion, and Supabase setup.
- More focused security checks for auth, access keys, Stripe, transcription, and model boundaries.
- Improve local demo data and fixtures.
- Add edge-case tests for scheduling rules.
- Improve accessibility in the schedule, brain dump, and review flows.
- Improve docs for local Supabase and Stripe test setup.
- Add examples that explain why AI proposals cannot bypass review.
- Motivation, streaks, points, or gamified productivity.
- Publishing customer data, private access links, production credentials, or hosted deployment wiring.
- Turning Executioner into a general-purpose task manager or configurable workflow builder.
- Replacing deterministic scheduling rules with model-only decisions.
Before any self-hosted deployment handles real user context, operators should review:
- Supabase RLS and service-role boundaries.
- Access-key exchange, rotation, and account-access rules.
- Stripe checkout, portal, webhook verification, and entitlement state.
- Brain dump processing, transcription, and prompt data minimization.
- Account deletion, export, and retention behavior.
- Dependency audit results.
- Incident response and private vulnerability reporting.