Life-X Growth OS — Session 3 demo
Open the interactive demonstration · Plain text
This complete read-only explanation requires no JavaScript. The interactive buttons require a normal JavaScript-capable browser.
Life-X · Growth OS / Session 3
LIFE-X GROWTH OS SESSION 3 · INTERACTIVE DEMOReset demo ↺
WORKSPACE / 02 NOV 2026
Evidence before
action.
00 Start here01 Opportunity workflow02 Commercial truth03 Invest-ly1204 System & readiness
DEMO BOUNDARY
Synthetic records.
No live Grok call.
No external messages.
No production access.
Browser memory only. Reset clears this run.
WELCOME / A FIVE-MINUTE INTRODUCTION
A clearer path from
opportunity to action.
Read the complete demo overview (no JavaScript required) →
Life-X Growth OS is a proposed workspace that helps a founder organize business opportunities, check the evidence and decide what to do next.
WHY IT EXISTS
Keep promising conversations from getting lost.
A business can spot an interesting opportunity, then lose track of the source, the offer or the next step. Growth OS brings that information into one reviewable workflow. It helps people prepare decisions; the founder stays in control of consequential actions.
Here, “agents” are named responsibilities in that workflow. Some have small working components; others are role contracts. They are not twelve independent bots running a business automatically.
WHAT YOU WILL DO
Try one fictional cocoa case.
Import a source: a fictional cocoa producer might need help comparing roast profiles.
Review the CRM record: CRM means the organized record of opportunities and conversations.
Make a founder decision: approve preparation of a draft, or reject the opportunity.
See a proposed next action: a follow-up draft is prepared. Nothing is sent.
Start the guided demo →WHAT IS REAL HERE?
Working logic.
Fictional business data.
The buttons run real validation, review gates, an event log and draft preparation using code shared with the Growth OS repository.
The company, opportunity, approval and commercial history are synthetic. No live AI research, customer database, email or payment service is connected. Your run stays in this browser tab and resets on reload.
Purpose: show how the process works, not claim a customer has bought anything.
THE NAMES, IN PLAIN LANGUAGE
Grok Bot / Scout-ly
Prepares a sourced opportunity. This demo uses a manual fixture instead of a live AI call.
CRM-ly
Keeps the record. It is the only component allowed to change commercial state.
FollowUp-ly
Suggests the next step and prepares a draft for review.
Perm-ly
Defines which actions need the founder’s explicit permission.
Invest-ly
The proposed twelfth role: prepares investor research and evidence checklists. It cannot contact investors.
Use the menu to explore commercial evidence, Invest-ly and the system boundaries at any time. No account or customer information is needed.
A SMALL, COMPLETE WORKFLOW
From a signal
to a considered next step.
Walk one fictional opportunity through a sourced import, CRM record, founder review and follow-up draft.
Grok Bot Manual fixture→CRM-ly Sole writer→Founder Review gate→FollowUp-ly Draft only
SCOUT / GROK-2SYNTHETIC
Workshop Cocoa
A fictional cocoa team is considering a sensory comparison of two roast profiles using an existing dataset.
SOURCE CARD / FIXTURE-S3-001
Invented workshop brief, dated 2 November 2026. This is demonstration evidence, not a real buyer signal.
Inspect fixture source ↗
Unknown: demand, data rights, budget and decision authority. Confidence: low.
1. Import synthetic opportunity →
Uses the real manual-import schema. No live Grok API call.
FOUNDER REVIEWAWAITING IMPORT
Keep the decision human.
Approve this record version for draft preparation, or reject it. Neither choice authorizes contact.
No CRM record imported yet.
2. Approve draft preparationReject3. Prepare proposed action →
You are simulating the founder. This is not owner authorization.
FOLLOWUP-LY / PROPOSED COMMERCIAL ACTIONNOT SENT
A reviewable draft. Zero dispatch.
External sending unavailable
A scoped, exact-version approval would be required in a live system. This demo has no sending tool.
AUDIT TRAILDownload run JSON ↓
No events yet. Start with the synthetic import.
Actual timestamps for this browser run; synthetic business events. Reload starts a new run.
LIVE COMMERCIAL OUTCOMES
€0 collected
No buyer acknowledgment, accepted contract, signature or payment is generated by this demo.
Inspect the commercial distinctions →
THE COMMERCIAL EVIDENCE LADDER
Sent is one fact.
Accepted is another.
A redacted fictional cocoa case illustrates the process used to review private correspondence. No customer identity, email, attachment or Gmail link is public.
FICTIONAL REFERENCE CASEILLUSTRATIVE HISTORY
01 / Formal proposal recorded as sent
Illustrative order and NDA. Example schedule: €750 at launch, €1,375 in March, €1,375 in May; €3,500 excluding VAT in total.
02 / Follow-up recorded as sent
Asks whether the offer was received and proposes the initial €750 session. A question about receipt is not acknowledgment.
Proposal sent Illustrative
Recipient acknowledged Unverified
Contract accepted Unverified
NDA / order signed Unverified
Payment received Unverified
Gmail SENT alone does not prove recipient server acceptance, inbox delivery, opening or signing. The private correspondence dossier remains separate.
Proposed next action
Request acknowledgment and a decision on the initial session, subject to explicit founder approval. No correspondence is sent from this demonstration.
ROLE REGISTRY / 12 OF 12
Invest-ly.
Prepared to support a decision.
The proposed twelfth Growth OS role turns investor research into evidence-backed recommendations for the founder.
RESPONSIBILITIES
Research. Qualify. Prepare.
Research public investor mandates, stage and geography.
Separate published facts from inferred fit.
Identify diligence gaps, conflicts and next experiments.
Propose CRM tasks through CRM-ly.
Invest-ly proposes. CRM-ly writes. The founder decides. Perm-ly checks the action boundary.
SMALLEST SAFE COMPONENT
Readiness checklist
Generate a checklist for the current synthetic opportunity. No investors are searched or contacted.
Prepare internal checklist →
Evidence and permission boundaries
Every fit claim needs a source URL, observation date, mandate evidence and explicit uncertainty. Sensitive materials, investor contact, spending, commitments and contracts need separate founder authorization. This component has no external tools and no CRM write authority.
ARCHITECTURE / READINESS
One writer.
Clear boundaries.
Twelve registered responsibilities do not imply twelve autonomous agents. This increment makes one bounded manual workflow demonstrable.
PUBLIC DEMO
Grok / Scout fixture
Validated manual import↓
CRM-ly
Existing reducer · synthetic in-memory state↓
Founder review → FollowUp-ly
Version-scoped decision · draft only↓
Perm-ly boundary
No external executor
Invest-ly → evidence checklist / proposed tasks → CRM-ly + founder.
SEPARATE PROTECTED APPLICATION
Next.js on Vercel → authenticated API → dedicated Supabase → row-level security and scoped writes. The public demo has no connection to that database.
Demonstrated here
Schema validation and idempotent fixture import
CRM-ly single-writer event reducer
Approval and rejection paths
Version-specific draft preparation
Audit trail and synthetic export
Invest-ly checklist, role 12
Still outside this demo
Live Grok integration and research
Hosted commercial ledger persistence
Authenticated founder review of this workflow
Customer demand and delivery validation
Email, campaigns, payments and contracts
Advanced investor automation
TWELVE REGISTERED ROLES
PM-ly · Growth-ly · Scout-ly · Campaign-ly · Conversion-ly · Report-ly · Perm-ly · Dactylo-ly · CRM-ly · FollowUp-ly · Publish-ly · Invest-ly
Invest-ly is proposed role 12. Registration defines responsibilities; it does not activate autonomous execution.
Technical workflow demonstration ≠ commercial validation. Public demo state is local to this tab and is not proof of durable hosted CRM operation.
LIFE-X GROWTH OS SESSION 3 / SYNTHETIC DEMONSTRATION / NO LIVE ACTIONS