closeboard.live

Build Slice

Real dashboard shell, not a placeholder.

This is the first live operator-facing structure for the system. It maps the architecture you gave me into concrete dashboard surfaces we can wire up next: accounts, scheduler rules, prompt editing, content handling, and analytics.

Execution Spine

Dashboard issues operator intent
Central API validates account state and settings
Master cron evaluates posting windows
Execution engine loads compressed account context
Browser automation and AI complete the run
Analytics and memory are compressed back into storage

Recent Master Runs

Cycle log

Manual and autonomous runs both land here as the scheduler audit trail.

Accounts Tracked 3

Each account keeps its own posting config, browser session, and compressed memory.

Cycles Completed 0

Every cycle should leave a clear audit trail and a compact run summary.

Forced Posts 0

Accounts crossing the hard threshold should get continuity protection.

Core Rules

What this system refuses to become

No agent swarm One centralized scheduler instead of a zoo of always-on workers.

No context bloat Do not drag full logs, full chats, or raw browser dumps into generation context.

No fake flexibility Deterministic tasks stay deterministic. AI is for language, judgment, and dynamic UI work.

No operator hostage situation Prompts, thresholds, media, and cooldowns should be editable without redeploying backend code.

Per-Account Isolation

Account command center

Browser session, schedule behavior, posting mode, and media stock stay isolated per account.

Dense Audit View

All accounts at a glance

Use cards for operations, use this grid for a compact read of the whole fleet.

Account	Platform	Theme / Objective	Window	Mode	Signals	Last Post	Next Slot	Engagement	Decision	Session	Actions

Memory Files

personality.json
performance.json
engagement_patterns.json
recent_context.json
compressed_history.json

Browser Strategy

Persistent cookies and local storage
Reusable authenticated sessions
OpenClaw browser primary
Model-guided page actions

Engagement Intake

Last 24h comments and replies
Mentions and audience interactions
Sample only the top-value signals
Questions and emotional reactions first

Timing Policy

Posting window controls

Soft threshold (minutes) 90 Hard threshold (minutes) 180 Max engagement sample 10 Manage posting windows Enable autonomous scheduler loop Auto-run interval (minutes) 30 Browser operator model Triage model Final writing model Max accounts escalated per cycle (0 = no cap) 0 Max final generations per cycle (0 = no cap) 0 Allow model escalation after deterministic approval Skip model calls for cooldown-protected accounts Skip model calls when there is no engagement signal

Decision Rules

Scheduler Runtime

Autonomous loop health

This should become the boring reliable heartbeat of the whole system.

Deterministic vs AI

Boundary line

Deterministic automation owns

Media download and folder movement
Queue bookkeeping and post-upload file moves
Retry loops and session restoration
Routine scheduling and cooldown enforcement

AI owns

Text generation and community voice adaptation
Reply drafting and emotional calibration
Trend-aware strategy adjustments
Dynamic page interaction where rigid selectors are not enough

Editable Prompt Surfaces

Prompt editor scaffold

System Prompt Platform Rules Viral Formula Community Style Engagement Rules

Prompt edits now persist to real markdown files under closeboard-site/prompts/.

Content Queue

Upload pipeline view

Execution Log

Worker run history

Worker Runtime

Actual task consumer state

This is now backed by a real worker process contract, not just queue rows.

Browser Handoff Queue

Tasks waiting for a browser worker

Upload transitions now emit concrete browser-task payloads instead of only changing labels.

Apollo Rescue Queue

Last-resort manual escalations

Only jobs that fail browser fallback and need final human-grade rescue should land here.

Media Library

Incoming vs uploaded inventory

Add Queue Job

Create a persisted content job

Queue records now live as their own entity set and survive reloads.

Top Hook Type Operator Pain

Posts framed around workflow leakage and admin chaos are winning.

Reply Jobs Queued 0

Every cycle should surface how much moderation work was queued back into the system.

Media Ready 0

Incoming media inventory should stay visible so video accounts do not go dry silently.

Recent Learnings

What should survive compression

Engagement Audit

System Overview