SOUL.md

This product idea sheet extends the thesis documented in Designing-Building. It defines the product's durable purpose, the customer transformation it intends to create, and the roadmap that turns that progression into a compounding flywheel.

The idea

AI is creating a new economic actor: the individual who can build, acquire, own, and operate a portfolio of increasingly autonomous businesses.

Most of this future customer base does not exist yet. The product cannot wait for Portfolio Executives to emerge at scale. It must help create them.

[ProductName] begins as the trust network where people discover, create, claim, acquire, and grow AI-native businesses and assets. As users accumulate businesses, it becomes the air-traffic control tower required to sustain and grow their portfolios. Eventually, it becomes the trusted communication and transaction infrastructure connecting those businesses and their agents.

Mission

Empower the new generation of entrepreneurs who build and run portfolios of businesses.

Give more people the agency to create wealth and meaningful work independently, using AI capabilities once available primarily to large organizations.

Core thesis

The next generation of entrepreneurs will not just run companies. They will run portfolios.

The progression is:

The product must provide value at every stage. It should not assume that a new user already understands how to start an AI business, owns several businesses, or identifies as an entrepreneur.

Instead, it should make the first step toward ownership feel understandable, credible, and attainable.

Product promise

Rational promise

Discover, build, acquire, operate, and exchange portfolios of AI-native businesses and assets.

Emotional promise

Build your own business empire.

The internal fantasy is the user as a power business mogul: independent, strategic, accumulating real economic assets, discovering overlooked opportunities, and turning small beginnings into a portfolio.

The public expression should remain credible and human:

The foundational object

A business is a persistent identity, not merely a listing.

It can be:

• •Indexed
• •Claimed
• •Private
• •Discoverable
• •Operating
• •Growing
• •Paused
• •Seeking customers or partners
• •Open to conversations
• •Open to offers
• •For sale
• •In transfer
• •Acquired

The identity persists as its condition, operators, owners, assets, and relationships change.

People, businesses, agents, products, assets, relationships, assertions, and transactions form an economic graph. Every relationship must state what is known, who asserted it, what evidence supports it, and what authority it provides.

Product architecture

The product develops through six mutually reinforcing layers:

• 1.Discovery — make the emerging AI-native economy visible and navigable.
• 2.Identity — establish persistent identities for people, businesses, assets, and their relationships.
• 3.Ownership — help people create, claim, acquire, and transfer real economic assets.
• 4.Utility — help an owner operate one business and eventually oversee many.
• 5.Trust — exchange authenticated, authorized, evidence-backed executive assertions without centralizing sensitive source data.
• 6.Transactions — make businesses and entrepreneurial assets economically liquid.

The layers should appear progressively. A first-time visitor should not need to understand the final protocol architecture to receive immediate value.

Roadmap as product flywheel

The Network is the acquisition engine.

The persistent business identity is the foundational object.

Single-business utility establishes retention.

The marketplace converts explorers into owners and accelerates portfolio formation.

Portfolio control creates escalating value.

Executive assertions create trusted coordination.

Transactions return users to the beginning of the flywheel with larger portfolios and greater needs.

The protocol becomes the long-term moat.

Stage 1 — Explorer

Customer state

The user is curious about AI entrepreneurship but may have no business, no clear idea, and no prior acquisition experience.

Promise

Product value

• •Explore a living network of AI-native businesses, products, assets, builders, and owners.
• •Ask an agent to explain opportunities in ordinary language.
• •Discover businesses by problem, capability, customer, market, asset type, or personal interest.
• •Save opportunities and build an initial understanding of the emerging economy.
• •See clear distinctions among indexed, claimed, self-asserted, and verified identities.
• •Choose one of three understandable paths: Build one, Claim one, or Acquire one.

Activation event

The user saves an opportunity, begins creating a business, initiates a claim, or evaluates an acquisition.

Stage 2 — First ownership

Customer state

The user wants to own something but may not know how to start from zero.

Promise

Product value

• •Create or claim a first business identity.
• •Acquire a comprehensible, lower-cost business asset or operating product.
• •Receive agent-guided evaluation and plain-language explanations of requirements and risks.
• •Verify seller identity, authority, asset rights, and the provenance of material claims.
• •Follow a standardized diligence and transfer workflow.
• •Add the acquired asset or business directly to a personal portfolio.
• •Receive a concrete plan for making it operational.

Initial transaction ladder

[ProductName] should begin below conventional M&A and expand only as trust and operational maturity grow:

Possible early objects include domains, codebases, deployed applications, agents, workflows, APIs, brands, newsletters, datasets with documented rights, and small operating digital businesses.

Activation event

The user completes a credible ownership or control action and sees the new entity or asset in their portfolio.

Stage 3 — Portfolio formation

Customer state

The user owns or operates one business and can imagine owning more.

Promise

Product value

• •Connect the first business to useful operating sources.
• •Establish its identity, products, assets, operators, and relationships.
• •Monitor basic health and receive interpreted operating signals.
• •Build a verified history and reputation.
• •Discover customers, partners, capital, assets, and complementary acquisitions.
• •Receive build-versus-buy recommendations.
• •Convert experiments or products into persistent business identities.
• •Add another business through creation, claiming, or acquisition.

Product behavior

The interface evolves with the user:

• •No businesses: What could you build or own?
• •One business: How can we improve this business?
• •Several businesses: What needs your attention?

Activation event

The user adds a second meaningful business or asset and begins using portfolio-level views.

Stage 4 — Portfolio Executive

Customer state

The user owns enough operating businesses that manual oversight becomes inefficient or impossible.

Promise

Product value

• •Prioritize risks, decisions, opportunities, and interventions across the portfolio.
• •Replace dashboard monitoring with concise executive briefings.
• •Manage by exception rather than by task.
• •Allocate attention and capital among businesses.
• •Compare business health without collapsing unlike businesses into misleading metrics.
• •Coordinate agents and people across portfolio boundaries.
• •Preserve decisions and outcomes as durable artifacts.

The primary interface question becomes:

Activation event

The user repeatedly acts on portfolio-level recommendations and depends on [ProductName] to determine where human attention is required.

Stage 5 — Executive assertion network

Customer state

Businesses are increasingly agent-operated and must communicate decisions, health, intent, risks, and opportunities securely.

Promise

Primitive

The primitive is not an assertion in isolation. It is the authorized exchange of an assertion:

An executive assertion should communicate:

• •What happened
• •Why it matters
• •Confidence
• •Urgency
• •Recommended action
• •Provenance
• •Disclosure level
• •Evidence availability
• •Who is authorized to act

Sensitive source data remains where it already lives. [ProductName] standardizes how trusted conclusions move among businesses, agents, owners, investors, customers, suppliers, lenders, and acquirers.

Activation event

Portfolio decisions and cross-business communications routinely occur through authorized assertion exchanges.

Stage 6 — Autonomous economic network

Customer state

Portfolio entrepreneurs, autonomous businesses, service providers, investors, and acquirers participate in a shared trust and transaction network.

Promise

Product value

• •Peer-to-peer business communication
• •Agent-to-agent opportunity discovery
• •Selective disclosure
• •Authenticated business relationships
• •Continuous acquisition and asset transfer
• •Business-to-business coordination
• •Portable reputation and operating history
• •Human intervention only where judgment, authority, or attention is required

Outcome

[ProductName] becomes economic infrastructure: the identity, trust, communication, and transaction layer for a distributed economy of AI-native businesses.

Marketplace as customer creation

The marketplace is not an adjacent feature or merely a monetization surface. It creates the future customer.

Conventional marketplaces assume the buyer already wants to acquire a business. [ProductName] begins earlier:

The agent should help a user:

• 1.Identify interests, capabilities, constraints, and budget.
• 2.Discover suitable assets and businesses.
• 3.Understand what each opportunity is and what it requires.
• 4.Evaluate assertions, provenance, evidence, and risk.
• 5.Complete a trusted transfer.
• 6.Add the acquired object to the portfolio.
• 7.Connect or establish an operating agent.
• 8.Define operating milestones.
• 9.Monitor health and receive recommendations.
• 10.Build, acquire, combine, or sell again.

A transaction is not the end of the relationship. It is the beginning of portfolio management.

Gamification principles

[ProductName] should borrow the motivational structure of games without looking or behaving like a casino, trading game, or childish simulation.

Use

• •A ready-but-empty portfolio instead of an empty profile
• •Meaningful missions tied to real ownership and operating actions
• •Visible progress from explorer to owner to operator
• •Contextual opportunity discovery
• •Portfolio momentum
• •Capabilities unlocked through genuine assurance and activity
• •Celebrations for consequential milestones

Example milestones:

• •Save a first opportunity
• •Create or claim a first business
• •Verify a relationship
• •Acquire a first asset
• •Connect a business source
• •Reach first revenue
• •Add a second business
• •Publish a first trusted assertion
• •Complete a first ownership transfer
• •Resolve a first portfolio-level intervention

Avoid

• •Arbitrary points
• •Manipulative streaks
• •Artificial scarcity
• •Speculative valuation theater
• •Public rankings detached from real performance
• •Casino language or visual treatment
• •Rewards for activity that does not create genuine economic capability
• •Implying ownership before a transfer is complete

The reward is real progress: the user owns, operates, understands, or improves something they did not before.

Trust is the product

Motivation may attract users, but trust must govern the network.

[ProductName] must never blur:

• •Saving an opportunity
• •Claiming a profile
• •Controlling a domain
• •Operating a product
• •Owning intellectual property
• •Owning shares in a legal entity
• •Being authorized to communicate for a business

Every relationship and assertion requires a precise assurance state and provenance.

Examples:

• •Publicly indexed
• •User-created
• •Self-asserted
• •Domain verified
• •Seller verified
• •Authorized representative
• •Asset rights documented
• •Legal ownership verified
• •Metrics self-asserted
• •Metrics source-verified
• •Evidence available
• •Transfer supported
• •Transfer completed

Creating a record does not prove ownership. Domain control does not prove legal ownership. Possession of an account does not prove authority to sell an asset.

Verification and transaction requirements should increase progressively with reputational, financial, privacy, and legal risk.

Experience principles

Adaptive value

The product interface should mature with the user rather than expose the entire roadmap at once.

| User state | Primary experience | | --- | --- | | No businesses | Network, discovery, education, and create/claim/acquire paths | | One unverified business | Claiming, relationship definition, and verification | | One operating business | Business identity, health, growth, and agent assistance | | Two to four businesses | Emerging portfolio and cross-business opportunities | | Five or more businesses | Attention-first portfolio control | | Agent-operated portfolio | Executive assertions and decisions by exception |

Agent as interface

Natural-language interaction should progressively replace exposed filters, sorting systems, and dashboard controls.

The agent should not merely search. It should:

• •explain;
• •compare;
• •evaluate;
• •recommend;
• •disclose uncertainty;
• •request authorization;
• •reveal permitted evidence;
• •execute approved actions;
• •and leave behind useful artifacts.

Progressive disclosure

Show only what is necessary for the current decision. Reveal operating detail, provenance, evidence, authority, and transaction complexity as the user asks or earns access.

Air-traffic control, not dashboard

Do not ask the user to monitor every gauge. Surface exceptions, conflicts, risks, opportunities, and requests for judgment.

Credible economic infrastructure

The visual and interaction language should feel calm, precise, intelligent, contemporary, and slightly unconventional. Use restrained color for meaningful state. Avoid hype, invented intelligence, fake financial charts, and premature claims of verification or market liquidity.

Strategic safeguards

• •Do not allow gamification to outrun trust.
• •Do not create marketplace liquidity by overstating supply, demand, verification, or transaction activity.
• •Do not centralize confidential source data merely to make assertions easier.
• •Do not force a portfolio-management interface on users who have not formed portfolios.
• •Do not confuse a directory of businesses with a network of trusted relationships.
• •Do not treat a health score as an executive conclusion without meaning, provenance, confidence, and action.
• •Do not equate a transaction with customer churn; ownership transfer should retain the business identity, seller, and buyer in the network.
• •Do not build later-stage transaction infrastructure before the identity, relationship, privacy, and trust foundations are credible.

Current MVP boundary

The roadmap describes a multi-year product, not the scope of the current release.

The current approved MVP remains focused on:

• •persistent user and business identities;
• •private portfolio utility;
• •explicit publishing and early public discovery;
• •typed business relationships;
• •clear self-asserted and unverified states;
• •enforced privacy boundaries.

Transactions, payments, escrow, valuations, executive assertions, autonomous business agents, public crawling, domain verification, legal ownership verification, KYC, and AML remain future stages requiring separate product specifications and explicit approval.

The MVP should nevertheless preserve the conceptual and technical path to the full flywheel.

North star

[ProductName] succeeds when a person who arrived merely curious can credibly say:

One-sentence definition