[ OPERATIONS HOME // PRIVATE ]

Maha operator console

A read-only daily map of the existing systems. It joins no ledgers, sends no messages, publishes nothing, and keeps the separate authorization boundaries intact.

Epistemic Phase 2 Re-ingestion compiler Phase 3 releases Phase 4 pilot reviews Workflow orchestration

Growth, content & outbound

Opportunity queue, demand, experiments, content workflow, utility validation, and outbound CRM.

Market mapping token

Optional for this view

Inbound operations

Qualified contact submissions and manual review queue.

Inbound operations token

Optional for this view

Revenue metrics

PII-free revenue, reconciliation, and product funnel metrics.

Revenue control token

Optional for this view

Tokens are held only in React memory for this page. Closing or reloading the tab clears them. This console uses existing protected endpoints rather than a new shared credential.

Market signals to review

—

Review direct-demand evidence

Active inbound items

—

Qualify or request context

Experiments ready to measure

—

Retain, iterate, or retire

Publication handoffs ready

—

Review then explicitly release

Demand and offer validation

Unlock to load

Approved signals awaiting corroboration

—

Validated demand clusters

—

Micro-utility validations due

—

Demand gate SOM evaluator Experiments Utility validation

Advance only when the listed gate is genuinely met. A validated cluster permits a bounded experiment, not autonomous publishing, spend, outreach, or product deployment.

Editorial and distribution

Unlock to load

Private/editorial drafts to review

—

Human release handoffs

—

Outbound follow-ups to record

—

Content workflow Amend live sources Outbound CRM Sales pipeline

A score-qualified content handoff is not a truth guarantee or automatic release. Outbound drafts must be personally sent and then recorded accurately.

Inbound and revenue

Unlock to load

Qualified inbound

—

Net reconciled revenue

—

Paid opportunities

—

Inbound queue Revenue dashboard

Stripe remains payment authority. Log revenue status only from reconciled payment/delivery/reversal events; this console does not expose inbound PII.

Today’s safe operating sequence

Live snapshot

01 Review urgent qualified inbound and personally decide the response.
02 Review direct-demand evidence, not generic topical results.
03 Advance one best-supported demand/experiment step.
04 Check revenue/refunds and record only actual outcomes.
05 Publish or send only after the relevant explicit approval gate.

This is an operations guide, not an automation command. Empty queues are an honest signal to learn from—not a reason to invent work or loosen the gates.