Projects, tasks, proof, and gates should be data-backed, then rendered in multiple views.
v0.04 research-led MVP
Celestia work-management cockpit
One calm surface for projects, gated automation, deployment posture, memory health, proof, and platform decisions.
Show ownership, blockers, approvals, and next action before decorative analytics.
Public surfaces can show posture; Retool or equivalent should hold mutable admin machinery.
Research complete; local build active.
Every write requires a keycard boundary.
Runner readiness is visible; writes stay gated.
Local screenshots and scans recorded.
Custom cockpit plus Retool machinery.
Command
Today’s operating picture
Built for quick decisions: what is active, what is blocked, what needs Jeet, and what has proof.
Operator loop
From intake to proof
Needs Jeet
Approval queue
- Cloudflare deployApprove
- DNS or token permission changesStop
- Cortex production accessStop
- Private memory promotionReview
Next best move
Platform decision
Superblocks is the stronger Retool alternative when AI governance, Git workflow, and central auditability matter more than speed.
Priority lane
Work that moves Observatory forward
Portfolio
Project registry and boundaries
Inspired by portfolio, roadmap, and project-table systems: every item needs owner, status, surface, and next signal.
| Project | Role | Health | Surface | Boundary | Next signal |
|---|---|---|---|---|---|
| Observatory | Operator dashboard | Active | Public plus private later | Writable in project root | v0.04 review and deploy approval |
| Cortex | Owned memory layer | Protected | Private only | No production touch | Staging-only schema planning |
| Celestia Voice | Voice chain | Planned | Private operator | No private export | Query-pack interface |
| CouncilOS | Reviewer loop | Tracked | Private plus proof summaries | Council-safe state only | Reviewer flow mapping |
| Quest / Superagent | Agent product track | Tracked | Separate project cell | Explicit scope required | Keycard before writes |
| Smart YouTube Library | Product cleanup | Waiting | Separate product | Explicit scope required | Recovery inventory |
| Obscura | Fast ROI product | Queued | Product workspace | New scope brief first | Opportunity sizing |
| Retool machinery | Internal admin console | Later | Private only | Auth and schema required | Data model before build |
Queue
Work-management lanes
Use the same records as table, board, timeline, and proof views instead of duplicating work across tools.
Now
Next
Waiting
Later
Automation
Runner readiness without raw secrets
Borrow observability patterns: health, owner, last proof, next run, and escalation path before any writable control.
Runtime lanes
Capability map
Automation catalog
v1 fields
- OwnerRequired
- CadenceRequired
- Write scopeRequired
- Last proofRequired
- Kill switchRequired
Planned jobs
Next automations
- File intakeLater
- Task extractionLater
- Deploy smokeReady
- Proof writebackDesign
Themes / Codex Theme
Codex theme control room
Local skin library, chooser launcher, and visual direction for the Codex shell.
Local module
Theme library endpoint
Commands
Local command files
- Serverrun-theme-server.command
- Chooserchoose-codex-theme.command
- Apply liveapply-codex-live-theme.command
- Launch themed Codexlaunch-themed-codex.command
Night set
Visual directions worth keeping
Design fixes
What the page should improve
- Group by moodNight / Light / Material
- Show live stateServer / selected preset
- Protect controlsToken counter visible
- Make launch obviousOne primary action
- Keep preview denseReal Codex shell
Evidence
Proof trail and audit links
Every important state should point to a durable artifact, a verification result, or a next action.
| Proof | Kind | What it proves | Public-safe? | State |
|---|---|---|---|---|
| v0.04 local screenshots | Visual QA | Desktop and mobile layouts render without obvious collision. | Yes | Captured |
| Overflow sweep | Responsive QA | All views fit at desktop and mobile widths. | Yes | Passed |
| Public secret scan | Safety QA | Public app avoids secret-like strings and private identifiers. | Yes | Clean |
| Deploy note | Release proof | Existing URLs and current deployment posture. | Redacted | Recorded |
| Runtime note | Staging proof | Staging smoke path works without exposing raw token text. | Redacted | Recorded |
Stack
Recommended build approach
Retool is the admin layer, not the brand/product layer. Design stays in Figma; public/operator UX stays custom.
Decision matrix
Which tool owns which job
Top-company lessons
Patterns to steal carefully
- LinearTriage and relations
- GitHubTable, board, roadmap
- AsanaPortfolio dashboards
- AtlassianIdeas to dev work
- DatadogHealth and incident posture
- GrafanaVariables and filters
Retool later