Mission Control
Executive command board for decisions, ownership, and leverage.
The old version had dashboard vibes. This version is structured like an operating system: Mission Control on top for governance, owned work in the middle, and profit reality underneath.
Command score36
Lower drag, clearer priorities, tighter operator leverage.
Executive thesis
The operating problem is not lack of activity. It is diffuse profit defense, fuzzy decision rights, and governance living in too many places. Put Mission Control on top, tighten those three, and the whole board gets smarter.
Executive layer
Decision directives
Protect profit before adding more output
Recovery Gel and paid media drift are eroding the portfolio narrative. Fix the leak before chasing new volume.
Make Mission Control the actual control layer
Use this board as the canonical place for decision rights, approvals, and recurring executive review so governance stops floating between tools.
Reduce hidden work and planning fog
Promote buried tasks into explicit owners so Tim is making portfolio decisions, not carrying invisible clutter.
Control signals
Fast read of system pressure
Profit at risk
$7.6kRecoverable profit currently trapped in ads discipline, pricing, and refund cleanup.
Decision pressure
8 live callsToo many unresolved calls means the operator layer is still absorbing ambiguity.
Execution focus
19 active / 1 backlogHealthy systems move explicit work, not a growing pile of intentions.
Hidden work drag
18 inferred tasksThe board is structurally ready, but invisible work and unclear approvals still sit outside reliable operating loops.
Amazon profit cockpit
Contribution-first analytics, structured for SP-API
Net profit run-rate$48.2k+11.4% vs prior 7d
Normalized after ad spend and refunds instead of top-line vanity revenue.
Contribution margin22.7%-1.8 pts
Margin compression is concentrated in two ASINs with rising PPC and storage drag.
Ad efficiency18.9% TACoS+2.1 pts
Spend is outrunning conversion in the products that should be harvested, not pushed.
Recoverable profit$7.6k3 bottlenecks found
Profit likely recoverable from repricing discipline, refund reduction, and ad pruning.
ASIN / product7d revenueContributionNet profitOperator call
TNT Hot Cream 4oz
TNT Pro Series • B0TNT001
stable
Push: hold price, trim broad-match waste, and expand branded bundles.
- Ad spend drifting up on broad terms
- Subscription attach rate below target
TNT Sweat Cream 2-Pack
TNT Pro Series • B0TNT002
watch
Watch: tighten campaign segmentation and refresh merchandising before scaling spend.
- PPC intensity is too high for a defended bundle
- Refund rate elevated from expectation mismatch
TNT Recovery Gel
TNT Pro Series • B0TNT003
urgent
Urgent: stop treating this like a growth asset until unit economics recover.
- Margin below threshold after ads
- Refunds and couponing erase operating leverage
Org chart
Decision rights and reporting structure
Tim
Principal / final authority
Owns final approval on capital allocation, new agents, external commitments, and any rule-changing decision.
Reports to: —
Mission Control / Control Center
Governance and org layer
Holds the decision map, executive reviews, approval gates, and reporting structure above the runtime.
Reports to: Tim
El Jefe
Chief operator / main runtime lead
Runs synthesis, routing, execution oversight, and uses Mission Control as the command surface for owned decisions and escalations.
Reports to: Mission Control / Control Center
Amazon Operator
Commerce performance lead
Owns contribution margin, ads discipline, and ASIN intervention loops inside the approved operating guardrails.
Reports to: El Jefe
Engineering Cell
Systems and product implementation
Builds internal tooling, data pipes, and automation that survives beyond one sprint.
Reports to: El Jefe
Creative / UGC Lead
Content systems and testing
Translates product truths into media assets and repeatable content loops once explicitly staffed.
Reports to: El Jefe
Finance Signal Layer
Decision-support model
Supplies margin truth, scenario framing, and exception alerts into Mission Control.
Reports to: Mission Control / Control Center
Decision rights map
Who can decide what
Execution and routing
Mission Control is the governing layer; OpenClaw executes underneath it.
El Jefe can decide
- Sequence approved work across execution lanes.
- Refactor docs, task structure, and internal operating views for clarity.
- Escalate decisions into Mission Control when a call exceeds delegated authority.
Requires Tim approval
- Changing strategic priorities across brands or major projects.
- Creating a new standing review ritual that materially changes Tim’s cadence.
Proposed agents can do
- Prepare drafts, analyses, summaries, and scoped implementation work assigned by El Jefe.
- Operate only within the task boundary and existing written rules.
Never without explicit approval
- Send external communications as Tim unless explicitly authorized.
- Create permanent new agents, departments, or autonomous loops.
Product, systems, and data
Mission Control is the governing layer; OpenClaw executes underneath it.
El Jefe can decide
- Implement scoped internal tooling changes inside approved projects.
- Improve dashboards, docs, and decision surfaces to make governance clearer.
Requires Tim approval
- Starting a net-new product initiative or materially changing product strategy.
- Connecting sensitive external systems or paid services with new operational risk.
Proposed agents can do
- Build or analyze within approved specs and report back through El Jefe.
Never without explicit approval
- Ship risky production changes blindly.
- Expose secrets, private data, or external integrations outside approved boundaries.
Capital, hiring, and governance
Mission Control is the governing layer; OpenClaw executes underneath it.
El Jefe can decide
- Recommend hires, agent roles, and governance changes for review.
- Mark work as kill / push / watch and tee up the rationale.
Requires Tim approval
- Any hiring, sub-agent creation, budget commitment, or external vendor commitment.
- Any change to top-level governance rules or decision-rights policy.
Proposed agents can do
- Exist only as proposals, role definitions, or temporary scoped workers after approval.
Never without explicit approval
- Self-replicate, expand headcount, spend money, or redefine authority.
Agent hiring / planning
Propose roles, not autonomous expansion
Policy
Proposal mode only. New sub-agents or operating roles can be recommended here, but no sub-agent should be created without Tim’s explicit approval.
Amazon Profit Guardian
Continuously catch contribution-margin leaks and recommend kill/repair/scale calls by ASIN.
Leverage: Turns channel noise into a weekly profit-defense loop.
Trigger: Promote when live SP-API data is wired and margin reviews become recurring.
Content Wedge Analyst
Pressure-test UGC and offer angles against conversion evidence before production expands.
Leverage: Prevents creative optimism from outrunning demand reality.
Trigger: Promote if UGC Engine gets a concrete TNT content wedge.
Operations Archivist
Keep docs, memory, and task surfaces clean so hidden work does not silently compound.
Leverage: Improves decision hygiene and reduces operator drag.
Trigger: Promote when inferred tasks exceed explicit tasks for two consecutive reviews.
Agent board
Kanban by owner, not by generic status
El Jefe
Main assistant / chief operator
Utilization 81%
Owns decisions, sequencing, and keeping Tim out of low-leverage noise.
Review AI receptionist offer for a sharper guarantee
offers • offers/ai-receptionist/01_OFFER_STRATEGY.md
Turn the missed-call pain into a clearer ROI promise and a tighter proof section.
Run weekly kill / push / watch review
portfolio • Control Center / portfolio classifier
Force concentration decisions instead of letting old bets linger by sentiment.
Amazon Operator
Commerce performance lead
Utilization 74%
Focuses on contribution margin, paid media discipline, and ASIN-level interventions.
Triage TNT Recovery Gel economics
amazon • Amazon profit cockpit
Decide whether to cut, reprice, or rebuild the offer before more spend leaks out.
Tighten broad-match PPC waste on core catalog
ads • mock-sp-api-adapter
Harvest branded demand without subsidizing low-intent traffic.
Engineering Cell
Systems implementation
Utilization 69%
Turns dashboard intent into durable tooling and live data paths.
Wire first live SP-API ingestion path
system • Control Center / integration readiness
Replace mock numbers with one trusted live path before broadening scope.
Connect the 2nd brain to a lightweight document ingestion flow
system • second-brain-nextjs/README.md
Future pass: add upload, tagging, and semantic search over local notes.
Operations Archivist
Proposed memory / hygiene role
Utilization 26%
Role is proposed, not created. Any sub-agent creation requires Tim approval.
Capture enduring personal context in MEMORY.md
memory • MEMORY.md
The workspace has daily and identity context, but long-term memory curation appears light or absent.
Surface hidden work into explicit owners
ops • Control Center / inferred tasks
This role should not be instantiated until Tim explicitly approves it.
Bottlenecks
Where leverage is currently getting choked
1 low-margin ASIN below 10% contribution margin
Profit is obscured by blended reporting
The dashboard needs true contribution views by ASIN, otherwise weak products hide inside healthy top-line numbers.
Action: Prioritize ASIN-level finance ingestion and weekly margin review.
18 inferred tasks detected
Important work is still buried in docs
Unchecked markdown tasks and note-based obligations create invisible load for the operator.
Action: Promote the top inferred tasks into explicit execution lanes.
1 backlog task(s)
Backlog is diluting decision quality
Too many “someday” items flatten urgency and make the dashboard less trustworthy as a command surface.
Action: Force kill/push/watch decisions at the project level every review cycle.
Execution lanes
Explicitly separate now, next, and hidden work
Now
Work that should move this week because it changes output, cash, or clarity.
Review AI receptionist offer for a sharper guarantee
offers • offers/ai-receptionist/01_OFFER_STRATEGY.md
`.env` has 600 permissions
skills/credential-manager/references • skills/credential-manager/references/security.md
`.env` is in `.gitignore`
skills/credential-manager/references • skills/credential-manager/references/security.md
No credentials in code
skills/credential-manager/references • skills/credential-manager/references/security.md
No credentials in logs
skills/credential-manager/references • skills/credential-manager/references/security.md
Next
Backlog that deserves sequencing, not vague guilt.
Capture enduring personal context in MEMORY.md
memory • MEMORY.md
Hidden work
Implicit tasks trapped inside documents and notes.
`.env` has 600 permissions
skills/credential-manager/references • skills/credential-manager/references/security.md
`.env` is in `.gitignore`
skills/credential-manager/references • skills/credential-manager/references/security.md
No credentials in code
skills/credential-manager/references • skills/credential-manager/references/security.md
No credentials in logs
skills/credential-manager/references • skills/credential-manager/references/security.md
Separate dev/prod credentials
skills/credential-manager/references • skills/credential-manager/references/security.md
Diagnosis
Why the information architecture changed
Old structure
Strong visual language, weak executive clarity. The dashboard showed useful pieces, but not the chain of command or where decisions should land.
New structure
This board now flows from executive directives → owned teams/agents → live economics → task-level execution. That makes it legible as an operating cockpit, not a wallpaper of widgets.
Design principle
Every major surface now answers one of four questions: what matters, who owns it, what should happen next, and what is still waiting on Tim.