NS Operator Dashboard
Front door for project state, demo health, AI staff, and control docs.
NowySystems Control Surface
Mobile-first command view for active project state, Codex handoffs, AI staff output, demo health, launch links, drift risks, and the next best actions.
Today
Start here before opening Codex, a project thread, or the next AI staff pass.
Launchpad
Front door for project state, demo health, AI staff, and control docs.
Funding intelligence and source-package validation. No public site yet; track state and demo-health from NS Brain.
Household planning platform. Public site is live; app/workflow state still tracked in NS Brain.
Existing gala check-in and auction site reference.
Request/case/timeline/review workflow. URL to be added when live.
Domain exists; landing page is pending. Keep this as the future public proof layer.
Highest Leverage
DR must stop at nothing short of the actual source package: source page, opportunity page, application path, NOFO/RFP/RFA/PDF, attachments, eligibility, deadline, and completeness status.
Open DR stateNext Repair
Restore safety first, then re-orient around product lanes. Do not let Bastion drift back into retirement-demo-centered architecture.
Open Bastion stateAI Staff Room
Strategy, product direction, memory interpretation, task framing, Codex handoff, and return review.
Current role: coordinate the system and keep projects aligned to NS Brain.Repo repair, implementation, validation, diff return, and code-level cleanup.
Current focus: Bastion repair/lane-lock and DonorRoute source-package repair.External references, source discovery, UI/UX pattern pressure, and source-package verification.
Rule: findings must become CONFIRM / CHANGE / ADD / IGNORE decisions.NOFOs, PDFs, source packages, uploaded docs, project docs, and structured extraction.
Next need: DonorRoute source-package parsing and missing-document flags.Future second-opinion role for long-form critique, product coherence, and written review.
Status: slot reserved, not wired yet.Future role for broad web/source sweeps, multimodal references, and external validation.
Status: slot reserved, not wired yet.Future server-backed private NS Brain search, local summaries, and daily operator briefs.
Status: server phase, after static dashboard proves useful.Source of truth for project state, decisions, design doctrine, lane maps, and do-not-regress rules.
Rule: all staff report back here.Demo Health
Source-package fixture check passes and blocks broad discovery pages from becoming complete opportunities.
Next: API-level fixture around /api/funding-search/candidates.Hourly income string normalization fix reported. Validation blocked by npm registry/dependency access.
Next: review PR diff and rerun validation where dependencies exist.Test planning mode, live command center, guest/check-in flow, and seating/table flow as separate demo paths.
Target: planning/live split health check.Static dashboard loads from phone/laptop. Next health check should verify mobile layout and key sections.
Target: no horizontal mobile scroll.Project Health
Source-package intelligence repair. Broad funding pages are clues, not answers.
StateRepair accidental simplification, then lock planning lanes and reduce beta clutter.
StateKeep planning mode and live-event mode separate. Do not mix check-in with planning clutter.
StateClean up request/case/timeline lanes. Avoid generic inbox/dashboard behavior.
StateControl layer is active. Keep master index, queue, ledger, and decision log updated.
StatePublic proof layer. Keep serious, operator-led, and product-studio oriented.
StateFast Access
Do Not Regress
Do not stop at broad state/source pages. Chase complete source packages.
Do not return to retirement-demo-centered architecture.
Do not mix planning mode and live-event mode.
Do not let project decisions disappear into chat threads.