Founder intelligence and execution platform. Canonical build repository: proclean808/PlatFormula-One-v2.
This README is a recovery entry, not proof of a working release. Reopen the cited sources, inspect the current branch and commit, and verify target-runtime behavior before claiming completion. Do not infer execution from generated text, checkboxes, rendered screens, or deployment metadata.
Recorded: 2026-10-11, America/Los_Angeles (PDT).
Source baseline inspected: e0392f1ae443d7350933ffe50e2ade37fe1cc2a9.
Owner's spelling: PlatFormula.One. Preserve repository identifiers exactly; do not rename resources merely to match branding.
The intended front door is a conversation that causes work:
CONVERSE → UNDERSTAND → RESEARCH → QUALIFY → ASSEMBLE → BUILD → VERIFY → OPERATE
Joyce is the conversational surface. The intended workflow builds founder/company context, researches and qualifies resources, selects appropriate State of the Art (SOTA), Best in Class (BIC), and Best of Breed (BOB) components, assembles a stack, generates artifacts, obtains authorization for consequential actions, executes, verifies outcomes, and preserves evidence.
A resource directory, accelerator application form, or pitch generator describes only part of that intended workflow. A listing of tools does not prove that they are qualified or integrated.
Resource qualification direction:
DISCOVER → NORMALIZE → DEDUPLICATE → PRIMARY-SOURCE VERIFY → FRESHNESS → QUALIFY → RESOURCE REGISTRY → FOUNDER MATCHING
These are recovered design directions, not a newly approved definition of the business. The owner rejected the assistant's earlier reduction of the product to an accelerator/application SaaS. Current commercial scope and deliverables remain unresolved until supported by authoritative project evidence.
- ConvoLO / CouncilCLAW is the owner's personal two-phone AI operating environment. Its README explicitly excludes PlatFormula.One from that build. Do not conflate personal infrastructure with the customer product.
- Baseline is a local-first reference chassis for control-plane, protocol, governance, and evidence components. Its presence does not establish those components are integrated into this site.
- ChatGPT-ThreadLocker preserves response exports, sources, manifests, and work evidence. Its canonical-repo correction designates this repository as the build source.
- Related repositories and prototype components are evidence or donors until explicitly admitted; owning or forking them does not establish integration.
The live site positions delivery beyond accelerator applications:
- Venture Vision: in-house venture builds, a claimed library of 300+ proprietary concepts, co-build partnerships, and licensing/rebranding for launch. The page is explicitly marked Coming Soon; the concept count and delivery availability were not independently verified.
- Venture Vault: proposed confidential workspace, IP storage, investor collaboration, immersive Power Pitch Decks, founder avatars, data rooms, and an investor discovery feed. The page is explicitly marked Coming Soon. Encryption, access control, investor vetting, avatar generation, and data-room automation are marketing claims, not runtime-verified capabilities.
- Live pricing places Venture Vision portfolio access in Pro and Studio, with Venture Vault exclusive to Studio.
- The homepage says the stack assembled around a founder is replicated and handed over with a roadmap, and claims 80% pre-built. Treat this as advertised delivery intent; do not use the percentage as a proven result.
- Therefore a description confined to application forms, directories, or business-plan generation omits the venture-building, co-build, licensing, and investor-presentation offering visible on the current site.
React/TypeScript client with Vite, Tailwind, and an Express static server. Source modules include Dashboard, Resources, Builder, Pitch Studio, Tracking, Community, Pricing, authentication-related components, and a Supabase client.
| Item | Observed source behavior / verification limit |
|---|---|
| Homepage | Tab-based startup interface. Rendering alone does not verify each workflow. |
| Builder / pitch | TODO records interactive forms and simulated AI feedback; current end-to-end behavior has not been runtime-tested in this recovery. |
| Pricing | Source lists Foundry $0, Agent Forge $50/month, Crucible $100/month. Free/Pro buttons show a coming-soon alert; enterprise opens email. This is not verified checkout or entitlement enforcement. |
| Pricing claims | Mentoring, SLA, payments, refunds, and trial statements require operational and policy evidence before promotion. |
| Authentication | Files exist, but TODO records removal of protection/login routes. File presence does not establish active authentication. |
| Newsletter | Supabase-related implementation exists; no fresh live submission was performed in this recovery. |
| Build | Vite output is dist/public; Express bundle is dist/index.js. No local build was executed during this documentation change. |
| Vercel config | No root vercel.json existed at the inspected baseline. |
Browser inspection on 2026-10-11 established that https://platformula.one uses a frameset pointing to https://platformula-one.manus.space.
The Manus-hosted page displays different navigation and prices: Founder $0, Pro $29/month, Studio $99/month. Its racing/trophy imagery and homepage copy differ from this repository.
The separate repository proclean808/platformula1-v2 is not this repository. Its Dashboard source shares a blob with proclean808/platformula-one-live. Similar content is not proof of the exact active deployment commit.
Observed live-page issues:
- Owner explicitly requested removal of racing/trophy pictures and replacement with proper product content.
- Header/navigation overflow and overlap.
- Expired May 2026 accelerator deadline.
- Funding, acceptance, success-rate, and uplift claims lacked supporting evidence in the inspected page.
- Displayed pricing conflicts with this canonical repository.
Do not replace, reconnect, rename, or promote the wrong project. Trace domain → hosting target → project → repository → exact commit, then test a preview of the intended change before production.
Honor the package-manager version pinned in package.json and the committed lockfile.
pnpm install --frozen-lockfile
pnpm check
pnpm build
pnpm startThese are repository scripts, not a claim that they passed here. Inspect required environment variables before running integrated features. Never commit credentials or publish environment-variable values.
- No purchases, subscription upgrades, paid add-ons, or new metered API services.
- Do not replace existing paid-app access with an assumed BYOK integration.
- Preserve existing branches/worktrees and source provenance.
- Distinguish OBSERVED, PROPOSED, AUTHORIZED, EXECUTED, VERIFIED, and COMMITTED.
- No fabricated testimonials, outcome statistics, resource freshness, execution receipts, or success states.
- Recover the complete current customer offering from project documents; retain conflicting definitions rather than guessing.
- Identify the exact source behind the current Manus homepage.
- Reconcile homepage content, pricing, supported features, and operational limits with the owner’s actual offering.
- Remove requested decorative imagery and unsupported claims in the correct source.
- Build; verify navigation, workflows, mobile layout, pricing controls, persistence, and failure behavior.
- Test the intended Vercel deployment and confirm the exact source commit.
- Publish only with target-runtime evidence; record URL, commit, checks, failures, and unresolved work.
This README change only documents recovery. It does not deploy the homepage, fix runtime features, connect phones, or establish automatic cross-session hydration.
- Canonical repository correction
- Conversational agentic front door
- Functional audit and resource registry
- ConvoLO personal-product boundary
- Baseline recovery register
- Canonical source TODO
- Canonical pricing implementation
GitHub inventory returned 82 repositories. Root README retrieval was attempted for each. Recursive file trees were retrieved for 13 selected product/context repositories. Selected product documents and implementation files were read; not every file in all repositories. Missing root README files were recorded as missing, not as empty repositories. Upstream donor README claims do not establish PlatFormula.One runtime capabilities.