Command Home

Plan authority content, video channels, shows, pilots, episodes, shorts, scripts, story worlds, production assets, distribution, sponsorships, SEO, and audience growth.

• Use this for Credit Intelligence Lab, CrownHouse / Blackridge, and future media/content businesses.
• Live publishing, sponsorship commitments, regulated claims, paid promotion, rights/licensing moves, and public channel launches require approval gates.

Create a repeatable onboarding path for new businesses, brands, media properties, product lines, service divisions, source systems, connectors, workflows, operating lanes, and approval boundaries.

• External accounts, spend, publishing, contracts, credential changes, and launches require owner approval.
• Every new business should enter here before it receives connectors, workflows, launch lanes, or source-system workers.

Turn full-business launch intent into rehearsed, approval-gated launch waves across every business and operating lane.

• The OS can plan, rehearse, score readiness, and queue launch actions.
• Public launch, publishing, spend, outreach, credential changes, contracts, and customer-facing action require owner approval.

Record proof that each launch lane, connector, workflow, and business operation has been tested before live launch.

• Evidence can mark a launch safety check as passed, failed, blocked, or needing review.
• Evidence does not approve live launch by itself; owner approval is still required for public, paid, customer-facing, credential, contract, or publishing actions.

Track market demand, search intent, competitor moves, pricing, positioning, offer gaps, audience pain, product opportunities, and launch timing for every current and future business.

• Use research items to feed SEO, content calendars, outreach angles, ad planning, product strategy, pricing, and future business decisions.
• Keep evidence links attached when available so recommendations can be checked before action.
• Recommendations stay internal until live spend, regulated claims, legal moves, and public commitments pass the relevant approval gates.

Generate weekly board-style packets covering launch readiness, business status, risk, research signals, strategic moves, owner decisions, and action assignments.

• Packets are internal strategy artifacts and should not publish, spend, sign, or change credentials.
• Use the packet to decide where the autonomous OS should continue and where owner approval is required.
• Keep legal, compliance, brand, platform, customer, and recovery risks visible before launch actions expand.

Use this as the draft-first communication bench for business messaging platforms such as WhatsApp, Slack, and Discord.

• Choose the business first so messages, contacts, and future sending rules stay isolated by brand.
• Choose the platform and write the message the way it should appear in that platform's native conversation flow.
• Saving creates an internal draft only. Live sending should happen only after platform credentials, consent rules, and approval gates are satisfied.

Prepare human-like support for chats and calls about orders, account access, downloads, refunds, product questions, service intake, and escalation across every business.

• Support drafts stay internal until the correct order system, privacy rule, refund rule, and approval boundary are satisfied.
• For ebook sites, the desk should verify order/access facts before giving download, login, or delivery instructions.
• Refunds, legal statements, regulated advice, credentials, payment changes, and hostile or high-risk cases route to owner approval or escalation.

Track organic and paid lead capture, outreach drafts, qualification, closer preparation, closing workflows, follow-up, and handoff across every business.

• Live outreach, sales calls, paid campaigns, regulated claims, contract terms, and payment collection stay gated by consent, credentials, and approval rules.
• Use closer notes to prepare the sales path before any human or autonomous closer contacts a lead.
• AI closer preparation includes Zoom-ready sales presentations, polished business presentation styles, objection handling, humor/personality calibration, and female or male closer presentation options within legal, platform, consent, and disclosure rules.
• Keep source, consent status, offer, lead need, next action, and risk visible before moving a lead toward closing.

Track legal, financial, customer, brand, platform, compliance, credential, publishing, paid-action, automation, and recovery risks before the OS acts.

• High and critical risks require owner review or a hard stop before public, paid, customer-facing, credential, publishing, legal, or financial actions proceed.
• Use stop rules to define exactly when the system must pause, ask, escalate, or avoid an action.
• Risk items should feed launch readiness, weekly board packets, approvals, customer support, sales, marketing, and source-system workers.

Track claims, disclaimers, refunds, customer disputes, regulated content, ads, outreach, contracts, privacy, platform rules, and business-specific review before sensitive action.

• The OS can prepare review notes and safer wording, but it cannot provide legal advice, sign contracts, approve regulated claims, issue refunds, change terms, or publish sensitive material without owner/legal approval.
• Reviews should feed approvals, risk-control stop rules, customer support, sales, ads, publishing, and business-specific compliance policies.
• Use this queue before live outreach, paid ads, public claims, refund decisions, customer disputes, and regulated credit-related content.

Coordinate organic traffic, SEO, paid traffic, lead magnets, content campaigns, ads, experiments, offers, tracking, and optimization across every business.

• Campaigns stay draft-first until spend, public claims, platform publishing, tracking changes, and customer-facing launch moves pass approval gates.
• Use market research to shape keywords, audience pain, creative angles, offer fit, lead capture, and launch timing.
• Paid traffic, ads, regulated claims, and high-risk public messaging should route through risk control and legal/compliance review.

This is the draft-first queue for platform-specific posts created by the social posting engine.

• Queue items stay internal until the business has credentials, platform rules, quality gates, and approvals satisfied.
• Each post keeps its own platform format, caption, tags, SEO image, title, description, timing window, and quality gate.
• Platforms such as Reddit, Quora, Medium, SlideShare, Slack, Discord, WhatsApp, and Zoom use their own channel rules instead of generic social posting assumptions.

This is a manual preview bench for a product sales page before the sales-page engine creates WordPress draft pages automatically.

• Choose the business/site first so the draft is tied to the correct WordPress property.
• Choose a real product draft or enter real product details manually before generating a review shortcode.
• Click Generate Draft Shortcode, paste the shortcode into a WordPress/WPBakery draft page, then paste the Additional CSS into WordPress > Appearance > Customize > Additional CSS if that site does not already have it.
• If the page needs work, come back here to adjust the TCW draft fields and recreate the shortcode. TCW should stay the source of truth.
• Approve the draft only when the structure is usable. Final automated sales pages should use the EDD purchase button/shortcode from the publishing workflow.

This is the review bench for ebook product structure before TCW creates a native ebook publishing job.

• Choose the business first so the package plan is tied to the correct ebook brand, storage source, disclaimers, and publishing path.
• Choose whether the product is a full funnel, a standalone ebook, or let the AI decide based on the files and content depth.
• Use AI pricing unless you need to override the prices manually. The engine should price the core ebook, cross-sells, upsells, or standalone product based on perceived content value.
• Use Discover From Storage when a real source folder is available. Otherwise, the file list can be manually reviewed or pasted as a package map.
• Generate Package Plan to preview what TCW thinks should become the EDD product structure, including core product, bonuses, cross-sells, upsells, sales page assets, pricing policy, and warnings.
• Create Native Ebook Job only after the plan looks right. That turns the reviewed plan into a staged publishing job for PDF generation, protection, EDD setup, sales page drafting, and approval gates.