Start a new SiXiS project
PROJECT-ONBOARDING-V0-1 / PHASE 1 / PASTE-BASED FLOW
Amendment 219a3485…
PROD ADMIN VIEW · READ-ONLY · WRITES STILL ON LOCAL
Amendment 219a3485…
claude · 2026-05-06 02:17:35
Cross-project amendment_proposed against dashboard_v0_1's Layer B: the dashboard HTTP server evolves from 'minimal queryable layer' (current scope per dashboard_v0_1 Layer B) to a dynamic write surface that exposes routing + SQLite write endpoints. Driven by the project-onboarding-v0-1 Cycle 1 deliverable that mounts /new-project on the existing server (council-ratified on poll 36c9dcf8). Implementation will replace SimpleHTTPRequestHandler with a custom Handler subclass that retains static-file serving fallback while adding /new-project (HTML form), POST /api/draft (writes project_draft_started + draft_saved events), GET /api/discovery-prompt/<draft_id> (generates click-to-copy discovery drill prompt with the hardcoded template per FORCED_RULE_PO_11 ratified storage form), and ui_launch_event firing when user clicks Start discovery drill. The 'queryable layer' framing in dashboard_v0_1's Layer B implied read-only; the upgrade is a real character shift that the dashboard project should ratify in its own next meta-cycle. Surfaced now under the watchdog spirit (orchestrator self-audit on cross-project assumptions) before the implementation lands. Amendment is documentary — does not block project-onboarding-v0-1 Cycle 1 work, since that work was already ratified at the project-onboarding-v0-1 level. Recommend dashboard_v0_1 ratify a parallel amendment in a future cycle to formally update its scope language.
Awaiting council: 2 more ratify position(s) needed (have 0/2)
Council positions (0)
≥2 distinct brains with position='ratify' (and zero 'refuse') unlocks the inline Ratify button.
No council positions logged yet.
Ratification chain (0)
Events that reference this amendment_proposed via caused_by_event_id.
(none yet)