dispatch-1: record fleet goal, baseline, and first worker proposal

This commit is contained in:
thePR0M3TH3AN committed 2026-10-19 15:52:05 -04:00
1 parent d90591163f
commit 386cf14bbe
12 files changed
+126 -21

No files matched your search

+11 -16
View File
@@ -1,30 +1,25 @@
# Program — the owner's priorities and rulings
Kept by the session manager. Short on purpose: the backlog holds the tasks, RESUME-BRIEF.md
what is mid-flight. Every ruling is DATED and QUOTES the owner; session-manager calls are
marked vetoable.
Last updated: YYYY-MM-DD
Last updated: 2026-10-19
## Current milestone
TODO: one paragraph.
Work through the existing TODO backlog and fix reproducible bugs that make the client less robust or usable. Validate old reports at current HEAD before assigning them; deliver small, checked changes through local unstable.
## Priorities (owner's order)
## Priorities
1. TODO
2. TODO
1. Owner direction: TODO backlog progress, bug fixes, robustness, and usability.
2. Session-manager sequencing (vetoable): prioritize reproducible failures in core user flows and small changes with clear completion checks.
## Rulings log (newest first)
<!-- Format:
### YYYY-MM-DD HH:MM — <short title>
> "<the owner's exact words>" — owner
Applies to: <areas>. Recorded by: <session>.
### 2026-10-19 — Initial goal
> "lets try to work our way through some of the issues in the TODO backlog and find and bugs and generaly make the client more robust and usable. ." — owner
Applies to: all areas. Recorded by: dispatch.
### YYYY-MM-DD HH:MM — <short title> (session manager call, VETOABLE)
What was decided and why, in two lines. The owner overrides by saying so.
-->
### 2026-10-19 — Conservative startup limits (session manager call, VETOABLE)
No deploys, spending, production data, real-wallet operations, or scheduler activation. Present the first team for owner approval before starting workers.
## Standing rules