Reference

MOTHA System Dictionary™

Plain-language definitions of the systems, modes and status words you meet in Prep School. Each entry says what it is, what it does, what it does not do and whether it is live today. This is an explanation layer — the Spell Book remains the canonical source, and your live records always win over a definition.

54 entries

MOTHA PREP SCHOOL™Runtime: LIVEKnowledge: COMPLETECORE SYSTEMS

What it is: The founder and business-builder course you are using right now — the first sellable part of the wider MOTHA ecosystem.
What it does: Teaches a phase of business building, has you apply it to your own company in My Business, collects proof of the work, and lets people review it before you move to the next phase.
Why it matters to me: You finish with a real, reviewed business record instead of a pile of notes — every lesson ends in something you actually built.
What it does not do: It is not the whole MOTHA universe (no banking, ERP, factory or city systems) and it does not grant progression just because you watched lessons.
What I should do: Start at Prep Home, follow the next mission, and do the work inside My Business.
Current owner: Prep School app (curriculum, tasks, business, proof, review and V-Gate records)
Related: My Business, V-Gate™, SMART MOTHA™
Also known as: Prep, Prep School
Where used: /how-it-works

MOTHA COSS™Runtime: REFERENCEKnowledge: COMPLETECORE SYSTEMS

What it is: The operating-system layer MOTHA uses to describe how inputs are taken in, checked, routed and turned into output.
What it does: In Prep School it appears as the operating sequence map (Ingest → Indolence → Digest → … → Root Return) that explains how guidance and review are organised.
Why it matters to me: It shows you the order the system thinks in, so a recommendation or review is never a mystery.
What it does not do: In this build it is not a separate running engine; the stages are carried out by existing Prep features and people.
What I should do: Use it to understand why a step comes before another — not as a tool to run.
Current owner: Operating sequence map in the Prep connection registry
Source state: Canonical lineage and Root DNA live in the Spell Book; not reproduced here.
Related: SMART MOTHA™, MOTHA AI SYSTEM™
Also known as: COSS
Where used: Explanation/reference only

SMART MOTHA™Runtime: LIVEKnowledge: COMPLETECORE SYSTEMS

What it is: Your in-course guide. It reads the records your own account is allowed to see and explains where you are and what to do next.
What it does: Answers questions about lessons, your business and returned proof, suggests the next step with a link that takes you there, and can hand your question to a human.
Why it matters to me: You are never stuck guessing what a page wants — the explanation is grounded in your real records.
What it does not do: It cannot approve proof, change a review, activate payment or pass a V-Gate. Its answers are guidance, not decisions.
What I should do: Ask it “What should I do next?” or “Why was this returned?” on any page.
Current owner: Smart Motha chat (server-checked role, account-scoped reads)
Boundary: GUIDANCE ≠ AUTHORITY
Related: MOTHA THINK™, MOTHA AI SYSTEM™
Also known as: Smart Mother, Motha guide
Where used: /smart-motha

MOTHA THINK™Runtime: LIVEKnowledge: COMPLETECORE SYSTEMS

What it is: The small floating bubble in the corner of signed-in pages — Smart Motha's quick-access surface.
What it does: Shows where you are, the next suggested action and why it is being suggested, with a Take me there button.
Why it matters to me: Help is always one tap away without leaving the page you are working on.
What it does not do: Dismissing it only hides a suggestion; it never changes your records. It is separate from the Guidance box at the top of pages.
What I should do: Tap it when you are unsure what a page needs from you.
Current owner: Smart Motha floating bubble
Related: SMART MOTHA™
Also known as: Think bubble
Where used: Explanation/reference only

MOTHA AI SYSTEM™Runtime: PARTIALKnowledge: COMPLETECORE SYSTEMS

What it is: The core system that groups guided execution and governed validation: Lesson Mode, Review Mode and the Decision Engine.
What it does: Presents what a task needs from you (Lesson Mode), how your work is checked (Review Mode) and a recommended outcome (Decision Engine) — all built from your existing task, proof, quiz and review records.
Why it matters to me: One consistent view of “what to do” and “how it will be judged”, on every task and review.
What it does not do: It is not a second review or progression engine and never makes the final call.
What I should do: Read the Lesson Mode panel before starting a task; read the Review Mode panel when work comes back.
Current owner: Shared MOTHA AI SYSTEM panels over existing task, proof and review records
Boundary: Final progression remains with human review, Qualification and V-Gate.
Related: Lesson Mode™, Review Mode™, Decision Engine
Also known as: AI System
Where used: Explanation/reference only

Lesson Mode™Runtime: LIVEKnowledge: COMPLETELEARNING / PROGRESSION

What it is: The guided-execution view inside MOTHA AI SYSTEM that spells out exactly what a task requires.
What it does: Shows your position, the objective, the required action, what proof is needed, the CEO Diary entry required, the expected output and what unlocks next.
Why it matters to me: You know the finish line before you start, so you do not submit incomplete work.
What it does not do: It does not grade you. Missing information shows as DATA_REQUIRED instead of being guessed.
What I should do: Check each line off before submitting proof.
Current owner: Task page (curriculum, task, business, proof and diary records)
Related: MOTHA AI SYSTEM™, CEO Diary
Where used: Explanation/reference only

My BusinessRuntime: LIVEKnowledge: COMPLETELEARNING / PROGRESSION

What it is: The single living record of the company you are building during the course.
What it does: Holds every business section with prompts and examples, each moving through seven states: Missing → Building → Built → Executing → Evidenced → Reviewed → Authorized, with a full change history.
Why it matters to me: It is the actual output of the course — your business plan grows as you learn.
What it does not do: It is not a worksheet dump; filling a box does not mark it Reviewed or Authorized — people do.
What I should do: Update the section each lesson points to, then attach proof.
Current owner: Business sections and history records
Where used: /what-you-build

CEO DiaryRuntime: LIVEKnowledge: COMPLETELEARNING / PROGRESSION

What it is: Your private written log of decisions, challenges and lessons learned as you build.
What it does: Captures a reflection tied to a task, which reviewers and Feedback Review can reference.
Why it matters to me: It shows how you think, not just what you produced — reviewers look for that.
What it does not do: It does not replace proof and is never used to guess your personal traits or mental state.
What I should do: Write a short entry each time a task asks for one: what you did, what happened, what you learned.
Current owner: Diary records
Related: MOTHA FEEDBACK REVIEW™
Where used: Explanation/reference only

A1 Observe / A2 Recommend / A3 Prepare / A4 Execute Within Approved EnvelopeRuntime: PARTIALKnowledge: COMPLETELEARNING / PROGRESSION

What it is: Four levels describing how much a person or system is allowed to do on its own.
What it does: A1 only watches, A2 may suggest, A3 may prepare work for approval, A4 may act — but only inside limits someone already approved.
Why it matters to me: It makes clear who is allowed to act, so nothing happens without the right permission.
What it does not do: Reaching a level does not remove human approval for decisions outside the approved envelope.
What I should do: Read it as the permission ladder behind every action and recommendation.
Current owner: Learner authority level (learner_state), assigned by the governed V-Gate decision
Source state: A1–A4 is recorded on approval; an authority level never bypasses human review or grants unrestricted execution.
Also known as: A1, A2, A3, A4, Authority levels
Where used: Explanation/reference only

MOTHA INGEST™Runtime: REFERENCEKnowledge: COMPLETEINTELLIGENCE / REASONING

What it is: The first stage: taking in an input, event or command.
What it does: Collects what was asked and the records around it before anything is decided.
Why it matters to me: Good answers start with complete input.
What it does not do: It does not judge or act on the input.
What I should do: Give clear questions and complete submissions — that is what gets ingested.
Current owner: Smart Motha context reads (partial)
Source state: Canonical lineage and Root DNA live in the Spell Book; not reproduced here.
Related: MOTHA INDOLENCE™
Where used: Explanation/reference only

MOTHA INDOLENCE™Runtime: PARTIALKnowledge: COMPLETEINTELLIGENCE / REASONING

What it is: MOTHA's anti-easy-answer safeguard.
What it does: Checks whether available context, files, Root ownership and continuity were actually reviewed before an answer is accepted or something new is created. If not: stop, search, cross-reference, correct, verify, then continue.
Why it matters to me: Prevents shortcut errors, duplicate systems and confident assumptions from spreading.
What it does not do: It does not make final decisions and is not another AI engine or learner-facing authority.
What I should do: Expect the system to say DATA_REQUIRED rather than guess — that is Indolence working.
Current owner: Build rules plus the operating sequence map; no separate runtime
Boundary: AVAILABLE CONTEXT NOT CHECKED = SYSTEM FAILURE. ONE UNVERIFIED FAILURE SHALL NOT BE MULTIPLIED.
Related: MOTHA INGEST™, MOTHA CROSS-REFERENCE™, MOTHA TRUE SERUM™, SMART MOTHA™
Also known as: Indolence, anti-easy-answer
Where used: Explanation/reference only

MOTHA DIGEST™Runtime: REFERENCEKnowledge: PARTIAL SOURCEINTELLIGENCE / REASONING

What it is: The stage where ingested input is broken down into what it actually means.
What it does: Separates facts, requests and gaps so later stages work on understood material.
Why it matters to me: Stops the system from reacting to surface wording.
What it does not do: It does not execute or approve anything.
What I should do: No action needed — it explains how guidance is formed.
Current owner: DATA_REQUIRED
Source state: Canonical lineage and Root DNA live in the Spell Book; not reproduced here.
Where used: Explanation/reference only

MOTHA CONSCIOUS RECALL™Runtime: PARTIALKnowledge: COMPLETEINTELLIGENCE / REASONING

What it is: The stage that brings back relevant earlier records and history.
What it does: Pulls prior submissions, returns and diary entries into view so advice reflects your past work.
Why it matters to me: You are not treated as starting from zero each time.
What it does not do: It does not rewrite or alter history.
What I should do: Keep your records complete so recall has something to use.
Current owner: Smart Motha account-scoped record reads
Source state: Canonical lineage and Root DNA live in the Spell Book; not reproduced here.
Where used: Explanation/reference only

MOTHA CROSS-REFERENCE™Runtime: PARTIALKnowledge: COMPLETEINTELLIGENCE / REASONING

What it is: Comparing one record against others to confirm they agree.
What it does: Checks a claim against proof, quiz results, business sections and history, flagging contradictions or gaps.
Why it matters to me: Catches work that looks complete but does not line up.
What it does not do: It does not decide the outcome; it surfaces issues for review.
What I should do: Resolve any flagged contradiction before resubmitting.
Current owner: Review Mode contradiction/gap checks
Source state: Canonical lineage and Root DNA live in the Spell Book; not reproduced here.
Where used: Explanation/reference only

MOTHA TRUE SERUM™Runtime: PARTIALKnowledge: COMPLETEINTELLIGENCE / REASONING

What it is: The truth check — does what is claimed match what is actually on record?
What it does: Keeps statuses honest: submitted is not approved, waiting is not stalled, reference is not live, failed reads show DATA_REQUIRED.
Why it matters to me: You can trust every badge and state you see.
What it does not do: It is not a lie detector about you personally.
What I should do: Rely on status labels; report any that look wrong.
Current owner: Shared status-truth rules and labels
Source state: Canonical lineage and Root DNA live in the Spell Book; not reproduced here.
Where used: Explanation/reference only

MOTHA CONSCIENCE™Runtime: REFERENCEKnowledge: RECOVERY REQUIREDINTELLIGENCE / REASONING

What it is: DATA_REQUIRED
What it does: DATA_REQUIRED
Why it matters to me: DATA_REQUIRED
What it does not do: It is not connected in this build and makes no decisions.
What I should do: Treat as a named concept only.
Current owner: DATA_REQUIRED
Source state: DATA_REQUIRED — definition not verified in current project sources.
Where used: Explanation/reference only

MOTHA DEEP SEEKER™Runtime: NOT CONNECTEDKnowledge: COMPLETEINTELLIGENCE / REASONING

What it is: Dig for the root cause behind a surface problem.
What it does: Names a way to look beyond the first symptom before choosing a response.
Why it matters to me: A surface fix can leave the real problem untouched.
What it does not do: No independent search or sourcing runtime is connected in this build.
What I should do: Describe the problem and check its underlying causes before acting.
Current owner: Fundamental Toolbox reference library
Source state: Source: approved Toolbox seed (Deep Seeker); reference definition only, not a running service.
Where used: Explanation/reference only

MOTHA TROJAN HORSE™Runtime: NOT CONNECTEDKnowledge: COMPLETEINTELLIGENCE / REASONING

What it is: Enter a market through a small trusted offer first.
What it does: Describes a smaller initial offer before wider market entry.
Why it matters to me: A first offer can be tested before expanding it.
What it does not do: It does not prove demand or run a market-entry system here.
What I should do: Test the initial offer and document what actually happens in My Business.
Current owner: Fundamental Toolbox reference library
Source state: Source: approved Toolbox seed (Trojan Horse); reference definition only, not a running service.
Where used: Explanation/reference only

MOTHA INTERCONNECTIVE™Runtime: PARTIALKnowledge: COMPLETEINTELLIGENCE / REASONING

What it is: The idea that every MOTHA record connects to the others instead of living in isolation.
What it does: In Prep, lessons, tasks, business sections, proof, diary and review all point at the same records.
Why it matters to me: One change shows up everywhere it should — no duplicate copies to fall out of sync.
What it does not do: It is not a separate integration service.
What I should do: Use Take me there links to move between connected records.
Current owner: Prep connection registry and shared records
Source state: Canonical lineage and Root DNA live in the Spell Book; not reproduced here.
Where used: Explanation/reference only

MOTHA INTERLINK™Runtime: REFERENCEKnowledge: COMPLETEINTELLIGENCE / REASONING

What it is: The operating stage that links a result to the other systems it affects.
What it does: Explains how an approved output feeds the next lesson, business section or cycle.
Why it matters to me: Your work carries forward instead of being filed away.
What it does not do: It does not connect external providers in this build.
What I should do: No action needed.
Current owner: Operating sequence map
Source state: Canonical lineage and Root DNA live in the Spell Book; not reproduced here.
Where used: Explanation/reference only

V-Gate™Runtime: LIVEKnowledge: COMPLETEGOVERNANCE / AUTHORITY

What it is: The checkpoint that decides whether you may move on to the next phase.
What it does: After your proof is approved and you score at least 70% on the phase quiz, a person reviews your request and returns APPROVE, HOLD, RETURN, REDIRECT or DATA REQUIRED.
Why it matters to me: Advancing means your business really reached the standard — not that time passed.
What it does not do: It is never decided by AI and is not triggered by progress alone (PROGRESS ≠ PERMISSION).
What I should do: Finish approved proof and pass the phase quiz, then request your V-Gate.
Current owner: Qualification and V-Gate records, human reviewer
Boundary: Consequential progression authority — human-governed.
Also known as: VGate, Gate
Where used: /proof-and-review

ValidationRuntime: LIVEKnowledge: COMPLETEGOVERNANCE / AUTHORITY

What it is: Checking whether a single piece of work meets its requirement.
What it does: Reviewers approve or return individual proof items against the task's standard.
Why it matters to me: Only APPROVED evidence counts as done.
What it does not do: Validating one item does not qualify you for a phase or pass a V-Gate.
What I should do: Fix and resubmit anything returned.
Current owner: Proof review records
Related: Qualification, V-Gate™
Where used: Explanation/reference only

QualificationRuntime: LIVEKnowledge: COMPLETEGOVERNANCE / AUTHORITY

What it is: Whether you have met every condition to request a V-Gate for a phase.
What it does: Combines approved proof and a phase quiz score of 70% or more into eligibility.
Why it matters to me: Shows exactly what still stands between you and the gate.
What it does not do: Being qualified is not being approved — the V-Gate still decides.
What I should do: Check the Gate page for what is missing.
Current owner: Qualification records and phase quiz results
Where used: /proof-and-review

MOTHA PERMISSION SUBMISSION™Runtime: LIVEKnowledge: COMPLETEGOVERNANCE / AUTHORITY

What it is: Your formal request to progress, built from the proof, qualification and V-Gate state you already have.
What it does: Shows required proof state, whether it is submitted, qualification state, review state, V-Gate request state and the exact next action.
Why it matters to me: One place to see if you can ask to advance and what is blocking you.
What it does not do: Submitting is not approval (SUBMITTED ≠ APPROVED). It stores no separate copy of your records.
What I should do: Follow its next action line.
Current owner: Existing proof, qualification and V-Gate records
Also known as: Permission Submission
Where used: Explanation/reference only

MOTHA SYSTEM ORDINANCE™Runtime: PARTIALKnowledge: COMPLETEGOVERNANCE / AUTHORITY

What it is: The standing rules the system must obey.
What it does: Includes laws like: lesson reviews are ungraded, the phase quiz needs 70%, V-Gate is human-governed, waiting on review is never stalling.
Why it matters to me: Rules are applied the same way for everyone.
What it does not do: It cannot be overridden by AI guidance.
What I should do: Read the FAQ and policies for the rules that affect you.
Current owner: Build rules and server-side checks
Source state: Canonical lineage and Root DNA live in the Spell Book; not reproduced here.
Also known as: Ordinance
Where used: Explanation/reference only

Ghost ModeRuntime: LIVEKnowledge: COMPLETEGOVERNANCE / AUTHORITY

What it is: A staff-only way to observe a learner's path.
What it does: Lets authorised staff inspect a learner's state to help them.
Why it matters to me: Support can see the problem without asking you to screenshot everything.
What it does not do: It cannot modify, approve or impersonate — observation only, checked on the server.
What I should do: Nothing — learners never see or use it.
Current owner: Server-checked admin session
Where used: Explanation/reference only

MASTER MOTHERBOARD™Runtime: FUTUREKnowledge: PARTIAL SOURCEGOVERNANCE / AUTHORITY

What it is: The full top-level MOTHA control board.
What it does: Not built in Prep School; the Admin area is the only control surface here.
Why it matters to me: Explains why some controls you may hear about are not in this app.
What it does not do: It is not active in this build.
What I should do: No action.
Current owner: DATA_REQUIRED
Source state: Canonical lineage and Root DNA live in the Spell Book; not reproduced here.
Also known as: THA MASTER MOTHA BORAD™, Master Motha Board
Where used: Explanation/reference only

Review Mode™Runtime: LIVEKnowledge: COMPLETEPROOF / REVIEW / RETENTION

What it is: The validation view inside MOTHA AI SYSTEM showing how submitted work is checked.
What it does: Lays out structure, proof, behaviour signals, quiz/application alignment and contradictions or gaps from your real review records.
Why it matters to me: You see what reviewers see, so a return is never a surprise.
What it does not do: It is not the reviewer; missing data shows DATA_REQUIRED.
What I should do: Read it before resubmitting returned work.
Current owner: Review queue and proof review records
Related: Decision Engine
Where used: Explanation/reference only

Decision EngineRuntime: PARTIALKnowledge: RECOVERY REQUIREDPROOF / REVIEW / RETENTION

What it is: The review-output layer that suggests an outcome: PASS, HOLD, RETURN FOR CORRECTION, REDIRECT or DATA_REQUIRED.
What it does: Reads existing review data and proposes a recommendation with reasons for the human reviewer.
Why it matters to me: Every submission is checked the same way: REQUIREMENT → ANSWER KEY / RULE → EVIDENCE → CONTRADICTION → GOVERNANCE → CONFIDENCE → AUTHORITY → DECISION. It asks: does the answer match the task, are required fields present, does proof exist and support the claim, does anything contradict another record, is the learner eligible, are prerequisites complete.
What it does not do: It is a recommendation only — never the final authority. AI output is not verified truth; a recommendation is not an authorization.
What I should do: Treat its result as a preview of possible feedback, then fix what it flags before a human reviews.
Current owner: Review recommendation helper
Boundary: Final progression remains with human review / Qualification / V-Gate.
Where used: Explanation/reference only

MOTHA FEEDBACK REVIEW™Runtime: PARTIALKnowledge: COMPLETEPROOF / REVIEW / RETENTION

What it is: A structured look back after a result.
What it does: Shows what you did, what changed, what worked, what needs correction, what you learned and what you will do next, from your history and diary.
Why it matters to me: Turns every result — good or returned — into progress you keep.
What it does not do: It does not invent answers; unsupported fields show DATA_REQUIRED. Answer version history is not yet enabled.
What I should do: Read it after each review result and plan your next step.
Current owner: Review, history and diary records
Also known as: Feedback Review
Where used: Explanation/reference only

Proof / Master FileRuntime: LIVEKnowledge: COMPLETEPROOF / REVIEW / RETENTION

What it is: Your collection of evidence showing the work was really done.
What it does: Links each submission to its task and business section with timestamps and reviewer notes.
Why it matters to me: It is what reviewers approve and what the V-Gate relies on.
What it does not do: It references your records rather than copying them; submitted proof is not done until APPROVED.
What I should do: Upload clear evidence for each task that asks for it.
Current owner: Proof submission records
Also known as: My Proof, Master File, Evidence
Where used: /proof-and-review

WATCHFAX™Runtime: PARTIALKnowledge: COMPLETEPROOF / REVIEW / RETENTION

What it is: A watch-and-report summary of account and system activity.
What it does: Surfaces recent events and issues on the profile/health area.
Why it matters to me: Keeps problems visible instead of silent.
What it does not do: It is not malware scanning and takes no action by itself.
What I should do: Check it if something seems off.
Current owner: Profile and System Health summaries
Where used: Explanation/reference only

System HealthRuntime: LIVEKnowledge: COMPLETEPROOF / REVIEW / RETENTION

What it is: A page showing whether the parts of Prep School you depend on are working.
What it does: Reports failed reads, permission problems, broken links and which services are live, reference or not connected.
Why it matters to me: If something fails, you see a system problem — not a false “missing work” message.
What it does not do: It does not scan for viruses and does not fix issues automatically.
What I should do: Open Support if it reports a problem.
Current owner: System Health page and audit checks
Where used: Explanation/reference only

MOTHA 360 PROOF LOOP™Runtime: REFERENCEKnowledge: COMPLETEMETHODS / LOOPS

What it is: A method cycle: Progression → Proof → Pressure → Permission → Power → Repeat.
What it does: Explains how proven work builds the right to take on more.
Why it matters to me: A mental model for why proof comes before permission.
What it does not do: It is separate from the seven-stage Prep cycle and runs nothing.
What I should do: Use it as a thinking frame.
Current owner: Loop Library reference
Also known as: 360 Proof Loop
Where used: /curriculum-preview

Prep CycleRuntime: LIVEKnowledge: COMPLETEMETHODS / LOOPS

What it is: The seven-stage circle: Understand → Structure → Execute → Prove → Review → Permission → Advance.
What it does: Highlights where you are right now, based on your real records.
Why it matters to me: A one-glance answer to “where am I?”.
What it does not do: It stores no separate progress.
What I should do: Tap a segment to see its steps.
Current owner: Prep connection registry (derived from your snapshot)
Also known as: Understand Structure Execute Prove Review Permission Advance
Where used: Explanation/reference only

MOTHA OLYMPIA™Runtime: PARTIALKnowledge: COMPLETEMETHODS / LOOPS

What it is: A twelve-part capability and failure vocabulary for diagnosing business problems.
What it does: Matches a reported problem to a named capability, failure signs and linked My Business areas; a learner may save a diagnosis and planned method.
Why it matters to me: It helps locate the failing capability before adding another tool.
What it does not do: The twelve names are not separate engines; a diagnosis never approves proof or grants progression.
What I should do: Compare a real problem with the recorded failure signs in Learning Mode, then document the selected capability and method in Operating Mode.
Current owner: Olympia powers and account-scoped diagnosis records
Source state: Source: approved Olympia power/failure registry and existing diagnostic route; root systems perform the work.
Also known as: Olympia capability
Where used: /methods

MOTHA SCENARIO™Runtime: NOT CONNECTEDKnowledge: PARTIAL SOURCEMETHODS / LOOPS

What it is: Planned what-if simulation for business decisions.
What it does: Not built in this version.
Why it matters to me: SIMULATION ≠ REALITY — any future results would be labelled as simulations.
What it does not do: Nothing runs today.
What I should do: No action.
Current owner: DATA_REQUIRED
Where used: Explanation/reference only

MOTHA LAB™Runtime: NOT CONNECTEDKnowledge: COMPLETEMETHODS / LOOPS

What it is: A safe testing space for trying a business idea before it goes live.
What it does: Follows the Labs chain: Propose → Configure → Scenario → Stress Test → Compare → Risk Review → Measure → Recommend → Authority/V-Gate → Deploy. It connects to the 360 Proof Loop through Pressure.
Why it matters to me: You can see risks and weak points before spending real money or time.
What it does not do: A simulation is always labelled as a simulation. It is never real-world evidence and never authorizes progression. No Lab runtime is connected in this build.
What I should do: For now, test ideas in My Business and record real results as proof.
Current owner: Reference only — future Labs owner (with Risk Analysis, Scenario and V-Gate)
Source state: Source: owner source cluster (Labs chain, Stress Test attachment). Knowledge recorded; runtime not connected.
Also known as: MOTHA Labs
Where used: Explanation/reference only

Business TemplatesRuntime: REFERENCEKnowledge: COMPLETEBUSINESS / COMMERCIAL

What it is: Seven root-family structural shells with starter prompts for different kinds of business.
What it does: Configure your one My Business record by reference so its sections fit your model.
Why it matters to me: You start with a relevant structure instead of a blank page.
What it does not do: They are not complete Business-in-a-Box products and never auto-activate a purchase.
What I should do: Pick the family closest to your business.
Current owner: Template catalog bound to My Business
Also known as: Root families, Templates
Where used: Explanation/reference only

ERP SummaryRuntime: PARTIALKnowledge: COMPLETEBUSINESS / COMMERCIAL

What it is: A read-only summary of your business operations data.
What it does: Summarises what your records already say.
Why it matters to me: A quick operations snapshot.
What it does not do: It is not a full ERP — no accounting, inventory or banking.
What I should do: Use as an overview.
Current owner: Profile hub summary
Where used: Explanation/reference only

MOTHA FACTORY SOURCE™Runtime: NOT CONNECTEDKnowledge: COMPLETEBUSINESS / COMMERCIAL

What it is: The sourcing system for finding and comparing suppliers, vendors and manufacturers.
What it does: Uses the Cross-Reference method with a Vendor Record, Cost Structure and Pricing Tool. It feeds the Vendors / Costs / Fulfillment part of My Business.
Why it matters to me: Comparing MOQ, landed cost, lead time, branding options and return terms stops you picking a supplier on price alone.
What it does not do: No live supplier or vendor connection runs in this build. It does not verify a supplier for you.
What I should do: Compare suppliers on those five points in My Business, then submit supplier documents and your cost comparison as proof.
Current owner: Reference only — sourcing work recorded in My Business (Vendors / Costs / Fulfillment)
Source state: Source: owner canon notes (MOTHA FACTORY SOURCING™ root, method, tools, proof required). Knowledge recorded; runtime not connected.
Also known as: MOTHA FACTORY SOURCING™
Where used: Explanation/reference only

Listing readinessRuntime: NOT CONNECTEDKnowledge: COMPLETEBUSINESS / COMMERCIAL

What it is: Whether a business or offer is ready to be listed publicly.
What it does: Marks the step before a beta listing: Listing readiness → publish beta listing → market response → leads / inquiries / transactions → evidence → return to Prep.
Why it matters to me: Real market response becomes evidence that feeds back into your Prep path.
What it does not do: No listing is published from Prep School, and readiness is not a guarantee of sales.
What I should do: Build your offer, pricing and proof in My Business first.
Current owner: Reference only — future MOTHA LISTING™ owner
Source state: Source: owner MOTHA LISTING™ notes (readiness → beta listing → evidence → return to Prep). Runtime not connected.
Where used: Explanation/reference only

MOTHA BUCKET TRACKER™Runtime: FUTUREKnowledge: PARTIAL SOURCEFUTURE / NOT CONNECTED

What it is: A future money-allocation guide.
What it does: Will calculate suggested allocations only.
Why it matters to me: PROJECTED ALLOCATION ≠ ACTUAL TRANSFER.
What it does not do: No transfers, scheduler, notifications or ledger — ever implied.
What I should do: No action.
Current owner: DATA_REQUIRED
Where used: Explanation/reference only

Personal Savings FoundationRuntime: LIVEKnowledge: COMPLETEFUTURE / NOT CONNECTED

What it is: A private beginner record of one personal savings goal and the contributions you log yourself.
What it does: Stores your goal, optional monthly target, dated manual entries, corrections and review state; shows recorded total vs. projection.
Why it matters to me: Builds the saving habit before business money decisions. RECORDED = SELF-REPORTED; PROJECTED ≠ RECORDED.
What it does not do: No transfers, payments, bank links, account numbers, investments or advice; not the business Bucket Tracker. Savings Engine, Goal Engine, Daily Tracker, Habit Matrix and Fund Flow are historical concepts, not built engines.
What I should do: Set a goal, record each contribution, and note it in your CEO Diary.
Current owner: savings_goals + savings_entries (owner-only)
Also known as: Savings Engine, Goal Engine, Daily Tracker, Habit Matrix, Fund Flow
Where used: /savings

MOTHA REAL ESTATE ACADEMY™Runtime: FUTUREKnowledge: PARTIAL SOURCEFUTURE / NOT CONNECTED

What it is: A future specialty academy.
What it does: Not built.
Why it matters to me: Planned post-V1.
What it does not do: Not available for purchase or enrollment.
What I should do: No action.
Current owner: DATA_REQUIRED
Where used: Explanation/reference only

MOTHA FINANCIAL UMBRELLA ACADEMY™Runtime: FUTUREKnowledge: PARTIAL SOURCEFUTURE / NOT CONNECTED

What it is: A future specialty academy.
What it does: Not built.
Why it matters to me: Planned post-V1.
What it does not do: Not available for purchase or enrollment.
What I should do: No action.
Current owner: DATA_REQUIRED
Where used: Explanation/reference only

DATA_REQUIREDRuntime: LIVEKnowledge: COMPLETESTATUS LANGUAGE

What it is: The system does not have enough verified information to say.
What it does: Replaces guesses when a record is missing or a read failed.
Why it matters to me: A failed read never looks like missing work on your part.
What it does not do: It is not a failure mark against you.
What I should do: Add the missing information, or contact Support if it persists.
Current owner: Shared status rules
Where used: Explanation/reference only

WAITING ON REVIEWERRuntime: LIVEKnowledge: COMPLETESTATUS LANGUAGE

What it is: You submitted; a person has not reviewed it yet.
What it does: Holds the item in a neutral waiting state.
Why it matters to me: Waiting is never counted as stalling.
What it does not do: It is not approved yet.
What I should do: Continue other work while you wait.
Current owner: Shared status rules
Where used: Explanation/reference only

PASS / HOLD / RETURN / REDIRECTRuntime: LIVEKnowledge: COMPLETESTATUS LANGUAGE

What it is: The possible review outcomes.
What it does: PASS/APPROVE: accepted. HOLD: paused pending something. RETURN: fix and resubmit. REDIRECT: go to a different step first.
Why it matters to me: Every outcome tells you the next move.
What it does not do: AI-suggested outcomes are not final.
What I should do: Follow the note attached to the outcome.
Current owner: Review and V-Gate records
Also known as: APPROVE
Where used: Explanation/reference only

REFERENCE / LIVE / PARTIAL / NOT CONNECTED / FUTURERuntime: LIVEKnowledge: COMPLETESTATUS LANGUAGE

What it is: Truth labels describing how real a feature is today.
What it does: LIVE works now. PARTIAL works in part. REFERENCE is taught, not run. NOT CONNECTED exists by name only. FUTURE is planned.
Why it matters to me: You never mistake a concept for a working tool.
What it does not do: A label is not a promise of delivery dates.
What I should do: Check the label before relying on a feature.
Current owner: Shared capability labels
Where used: Explanation/reference only

BABE SCOUT™Runtime: REFERENCEKnowledge: COMPLETEBUSINESS / COMMERCIAL

What it is: MOTHA's flagship live execution and proof environment: Public → Private House → MOTHA Command.
What it does: Gives Prep School learning a real place to be executed, proven and reviewed.
Why it matters to me: Learning becomes evidence in a controlled environment before scaling.
What it does not do: It is not a competing school, grants no entitlement, and never transfers equity or IP automatically.
What I should do: Read the structure; enrollment is not open in this build.
Current owner: BABE SCOUT display config
Where used: /babe-scout

BABE BUS™Runtime: FUTUREKnowledge: PARTIAL SOURCEFUTURE / NOT CONNECTED

What it is: A mobile real-world market prototype lab and mobile asset, operated through BABE SCOUTS TOUR & EXPERIENCES™.
What it does: Planned field proof across cities with its own P&L and market intelligence.
Why it matters to me: Tests whether results travel beyond the House.
What it does not do: No live ledger; five-sided glass is not engineering-verified; no full commercial kitchen is assumed.
What I should do: Treat as a future reference.
Current owner: DATA_REQUIRED
Where used: /babe-scout

MOTHA ONION METHOD™Runtime: REFERENCEKnowledge: COMPLETEMETHODS / LOOPS

What it is: Layered Ecosystem Compression Architecture: one governed core supporting compatible value layers.
What it does: Uses the Onion Test to decide KEEP / COMPRESS / SEPARATE / REDESIGN / HOLD / REMOVE / SCALE.
Why it matters to me: Adds value density without bloat. Share infrastructure; separate obligations.
What it does not do: PROJECT X is a proving ground, not the method; no Onion Test records are stored yet.
What I should do: Use the laws to check whether a new layer earns its place.
Current owner: BABE SCOUT display config
Also known as: Onion Method
Where used: /onion-method

MOTHA 10™Runtime: FUTUREKnowledge: PARTIAL SOURCEFUTURE / NOT CONNECTED

What it is: 10 Babes operating 10 MOTHA starter businesses; each leads one Command Seat and operates across the other nine.
What it does: Planned operational business proof, kept separate from each Babe's independently owned business.
Why it matters to me: Tests CEO and operator skill on real businesses.
What it does not do: No seats, sales or customers are recorded in this build.
What I should do: Keep your own company in My Business.
Current owner: DATA_REQUIRED
Also known as: 10-Babe Operating Model
Where used: Explanation/reference only

Two separate badges: Runtime says whether it runs in this app today; Knowledge says whether its definition is fully sourced. “Not connected” never means “undefined”.

System Registry & ownership map

Directory (identify/register). Runtime, knowledge and product state are shown separately. DATA_REQUIRED means not yet sourced — nothing is assumed.

PRODUCT / ENVIRONMENT

Object	Owner	Records	Runtime	Knowledge	Product	Roles	Next mutation
MOTHA PREP SCHOOL™	This application	enrollments, modules, lessons, tasks	LIVE	COMPLETE	INCLUDED	public, learner, reviewer, admin, master_admin	Phase 2 visual assembly
VIP PREP SCHOOL™	DATA_REQUIRED	—	NOT CONNECTED	RECOVERY REQUIRED	FUTURE	—	Not represented in current build; source recovery before any work
Public Prep experience	PublicShell + public routes	—	LIVE	COMPLETE	INCLUDED	public, learner, reviewer, admin, master_admin	Phase 2 visual assembly
Signed-in Academic environment	AppShell + _authenticated gate	profiles, enrollments	LIVE	COMPLETE	INCLUDED	learner, reviewer, admin, master_admin	—
Founder / Master administration layer	user_roles(master_admin) + Admin panel	user_roles, system_settings, audit_log	LIVE	COMPLETE	—	master_admin	—
Learner environment	Snapshot (src/lib/prep.ts)	—	LIVE	COMPLETE	—	learner (+ staff via Learner View)	—
Reviewer environment	Review Queue	submissions, evidence_files	LIVE	COMPLETE	—	reviewer, admin, master_admin	—
Ghost environment	Ghost observer + in-memory Test Flow	audit_log (malfunctions only)	PARTIAL	COMPLETE	—	admin, master_admin	Simulated Diary/business/template flows need in-memory models

CORE SYSTEM

Object	Owner	Records	Runtime	Knowledge	Product	Roles	Next mutation
SMART MOTHA™	Chat route + page guidance + hourly audit	smart_motha_conversations, smart_motha_audits, smart_motha_intakes	LIVE	COMPLETE	—	learner, reviewer, admin, master_admin	Answer revision lineage (needs minimal history storage)
MOTHA THINK™	SmartMothaFab bubble	—	LIVE	COMPLETE	—	learner, reviewer, admin, master_admin	—
MOTHA AI SYSTEM™	MothaAISystem.tsx (presentation over records)	—	PARTIAL	COMPLETE	—	learner, reviewer, admin, master_admin	Phase 2 single-system interface
Lesson Mode	LessonModePanel	lessons, tasks, curriculum_registry, ceo_diary_entries	LIVE	COMPLETE	—	learner, staff	26 new lessons need source teaching content
Review Mode	ReviewModePanel	submissions, phase_quiz_attempts, ceo_diary_entries	LIVE	COMPLETE	—	reviewer, admin, master_admin	—
Decision Engine	review-recommend.ts (recommendation only)	submissions	PARTIAL	COMPLETE	—	reviewer, admin, master_admin	—
MOTHA FEEDBACK REVIEW™	FeedbackReview over lesson_reviews	lesson_reviews	PARTIAL	COMPLETE	—	learner	Version history (deferred schema)
MOTHA PERMISSION SUBMISSION™	PermissionSubmission over proof/qualification/V-Gate	submissions, module_qualifications, vgate_requests	LIVE	COMPLETE	—	learner	—
MOTHA 360 PROOF LOOP™	Reference visual	—	REFERENCE	COMPLETE	—	public, learner, reviewer, admin, master_admin	—
Prep Execution Cycle	CycleWheel (derived from snapshot)	—	LIVE	COMPLETE	—	learner, staff	—
V-GATE™	request_vgate / decide_vgate RPCs	vgate_requests, module_qualifications	LIVE	COMPLETE	—	learner (request), admin (decide)	—
MOTHA TRUE SERUM™	Status-truth rules (src/lib/status.ts)	—	PARTIAL	PARTIAL SOURCE	—	—	Source recovery for full definition
MOTHA CONSCIENCE™	DATA_REQUIRED	—	NOT CONNECTED	RECOVERY REQUIRED	—	—	Source recovery
WATCHFAX™	System Health history table	audit_log, business_section_activity	PARTIAL	COMPLETE	—	learner (own), admin	—
MOTHA INDOLENCE™	Build rule (AGENTS.md) + operating-sequence stage	—	REFERENCE	COMPLETE	—	—	—
MOTHA SYSTEM CONFIGURATION™	system_settings + Admin → Settings	system_settings	PARTIAL	PARTIAL SOURCE	—	master_admin (change), admin (view)	Configuration UI beyond settings is Phase 2+
MOTHA ESCROW BAR™	Escrow trust configuration (product-catalog.ts)	—	NOT CONNECTED	PARTIAL SOURCE	PREVIEW	public, learner, reviewer, admin, master_admin	Governed transaction storage and verified provider + human authority required before operation
MOTHA VERIFIED IDENTITY™	Escrow verification checkpoint (product-catalog.ts)	—	NOT CONNECTED	PARTIAL SOURCE	NOT FOR SALE	public, learner, reviewer, admin, master_admin	Provider or reviewed manual evidence and audit before verification
MOTHA FACTORY SOURCE™	Resource-intelligence reference flow (product-catalog.ts)	—	NOT CONNECTED	PARTIAL SOURCE	PREVIEW	public, learner, reviewer, admin, master_admin	Source-backed vendor records and verification required

KNOWLEDGE STRUCTURE

Object	Owner	Records	Runtime	Knowledge	Product	Roles	Next mutation
SourceCode	Outside this build (Spell Book)	—	NOT CONNECTED	PARTIAL SOURCE	—	—	Reference only in V1
NODA	Outside this build	—	NOT CONNECTED	RECOVERY REQUIRED	—	—	Source recovery
Index (locate)	KNOWN_ROUTES in connections.ts + dictionary search	—	PARTIAL	COMPLETE	—	public, learner, reviewer, admin, master_admin	—
Directory (identify/register)	This System Registry	—	LIVE	COMPLETE	—	public, learner, reviewer, admin, master_admin	—
Library (governed knowledge)	key_methods, toolbox_items, loop_library, olympia_powers	key_methods, toolbox_items, loop_library, olympia_powers	LIVE	PARTIAL SOURCE	—	learner, staff	—
Table of Contents (navigate programs)	My Curriculum (curriculum_registry)	curriculum_registry	LIVE	COMPLETE	—	learner, staff	—
System Map (relationships)	connections.ts + this registry's connections	—	PARTIAL	COMPLETE	—	public, learner, reviewer, admin, master_admin	Visual map is Phase 2
Archive	Proof Portfolio + audit_log (immutable)	submissions, audit_log	PARTIAL	COMPLETE	—	learner (own), staff	—
Chronology	Timestamps + business_section_activity + WATCHFAX	—	PARTIAL	COMPLETE	—	learner (own), admin	—

OPERATING STAGE

Object	Owner	Records	Runtime	Knowledge	Product	Roles	Next mutation
Mapping	Operating-sequence stage (connections.ts)	—	REFERENCE	PARTIAL SOURCE	—	admin view	Reference only; no runtime owner in V1
Grid	Operating-sequence stage (connections.ts)	—	REFERENCE	PARTIAL SOURCE	—	admin view	Reference only; no runtime owner in V1
Leverage Linkage	Operating-sequence stage (connections.ts)	—	REFERENCE	PARTIAL SOURCE	—	admin view	Reference only; no runtime owner in V1
Grand Central	Operating-sequence stage (connections.ts)	—	REFERENCE	PARTIAL SOURCE	—	admin view	Reference only; no runtime owner in V1
Interlink	Operating-sequence stage (connections.ts)	—	REFERENCE	PARTIAL SOURCE	—	admin view	Reference only; no runtime owner in V1
Root Capability	Operating-sequence stage (connections.ts)	—	REFERENCE	PARTIAL SOURCE	—	admin view	Reference only; no runtime owner in V1

MOTHA AI SYSTEM™ operating sequence · Ingest → Indolence → Digest → … → Root Return

Each stage shows the existing part of Prep School that owns it. LIVE = running now · PARTIAL = existing records support part of it · REFERENCE = process stage only, not executable. Guidance never grants progression; V-Gate decides.

Input / Event / Command:: Learner actions: tasks, diary, proof, V-Gate requests
Ingest:: Smart Motha reads RLS-scoped learner context
MOTHA Indolence™:: Anti-easy-answer safeguard: check context/root/owner/continuity → if insufficient STOP → search → cross-reference → correct → verify. Assists Ingest, Cross-Reference, True Serum, Smart Motha. Partly enforced today by DATA_REQUIRED on failed reads and Review Mode gap checks; not an engine, not an authority
Digest:: Smart Motha guidance summary
Conscious Recall:: Lesson reviews + CEO Diary history
Cross-Reference:: Review Mode rules (R0/R1) + quiz alignment
Chronology:: Submission, V-Gate and section change history
Root:: My Business record (seven states)
Loop:: Prep Cycle derived from snapshot
Ordinance:: Canon rules / policies
True Serum:: Truth labels + DATA_REQUIRED on failed reads
Mapping:: Connection registry (known routes)
Grid:: Prep Transit Grid
Leverage Linkage:: Templates bound by reference
Grand Central:: Prep Home
Active:: Enrollment access state
Allocate:: Not built in V1
Automate:: Not built in V1
Hyper-Autonomy:: Not built in V1
Interlink:: Not built in V1 (no MCP/provider runtime)
Root Capability:: Authority levels granted by V-Gate
Execution:: Tasks + My Business
Output:: Evidence submissions
Endput:: Master File / My Proof
A+ Check:: Human review queue (Review Mode)
V-Gate (where required):: decide_vgate — human authority
Archive:: Proof + qualification records
Grid Update:: Snapshot refresh after each decision
Root Return:: Prep Home next phase