Three phases.
One eligible solo-formation set.
The boundary is deliberately narrower than the full MZN story. Phase 1 demonstrates prior product and market execution. Phase 2 defines the solo formation record under review. Phase 3 tests, professionalizes and selectively advances what was formed.
Team-Built Product Foundation
Bounded Solo AI-Native Formation
Independent Review & Execution
The Phase 2 provenance set is historically closed.
The boundary is not a permanent isolation rule for the assets. It is a historical eligibility rule for OPU review. Any later staffing, partnership, validation, festival participation, investment, rebuild or integration belongs to Phase 3 and does not retroactively enter the Phase 2 solo claim.
What can count.
What cannot.
The boundary is applied to each artifact, not to the founder by reputation and not to the portfolio by association. A Phase 2 item is eligible only when its formation belongs to the bounded solo period and no material human co-builder contributed to that formation.
Included in the eligible Phase 2 formation set
| Category | Examples / scope | Status |
|---|---|---|
| AI / System Architecture | Mapped architectures and system designs such as ZOE and related architecture layers formed during Phase 2. | Eligible if provenance holds |
| Technical Assets | Tokenizer and GPU-related systems, including implementation or internal testing where the asset-specific record supports that state. | Eligible if Phase 2 formed |
| Research / Theory | Research programs and theory candidates such as BioCode/HUAI-related work, without converting research status into technical or legal validation. | Eligible formation output |
| Documentation / Specifications | Architecture notes, specifications, review packages, strategic documents and other externalized formation records. | Eligible if solo-formed |
| Review Architecture | Phase boundaries, review manuals, challenge frameworks, routing and evaluation structures created to make the case inspectable. | Eligible methodology output |
Excluded from the Phase 2 solo claim
| Category | Why excluded | Status |
|---|---|---|
| Phase 1 Mazzaneh product / market work | Team-built historical execution. Relevant context, but not solo-formed. | Excluded |
| Any artifact with material human co-building | If a human team member, cofounder, contractor, agency or advisor materially contributed to formation, that artifact leaves the eligible solo set. | Excluded |
| Phase 3 professional work | Legal/IP review, independent technical review, pilots, implementation support, partnerships and commercialization belong to professionalization. | Excluded from provenance |
| External recognition / platform signals | Rankings, invitations, correspondence or outside interest can be context or signals; they do not become solo-formed assets or proof of value. | Context only |
| Future teams, funding or execution | What happens after the bounded formation record cannot be retroactively added to it. | Excluded |
Bounded for reviewability,
not for permanent isolation.
The strongest part of the old Claim Boundary page is the distinction between formation and later execution. That logic is preserved, but the new page removes claims that belong in founder context, accounting reconciliation or evidence review.
Keep team-built and solo-formed work separable
Without a hard boundary, Phase 1 execution could be incorrectly absorbed into the Phase 2 one-person claim, making provenance impossible to evaluate cleanly.
Make the claim falsifiable
A boundary must allow exclusion. If a material human contributor is found on a claimed Phase 2 artifact, that artifact should be removed from the eligible set rather than explained away.
Separate the method from the verdict
AI-assisted solo formation is itself a methodology worth examining. Demonstrating that a method was used is different from proving that every output is novel, valuable, patentable or commercially ready.
Allow Phase 3 to add people without rewriting Phase 2
The bounded claim concerns origin and formation. Professional legal, technical and commercial work can be added later without being misrepresented as part of the historical solo record.
- The solo claim applies to eligible Phase 2 formation only.
- Artifacts can be included or excluded individually.
- Later teams can validate and execute without changing historical provenance.
- Negative or undecided review outcomes remain valid.
- Solo building is inherently superior to team building.
- The founder must remain solo forever.
- Phase 1 is less important or less valuable.
- AI outputs automatically count as validated inventions.
- Future reviewers or partners are unwelcome.
Formation can be solo.
Validation can be institutional.
The old page used an architect/construction analogy to explain this distinction. The useful principle is retained: later execution resources do not become original co-creators merely because they are required to test, professionalize or scale what already exists.
Origin and later execution are separate questions.
Phase 2 asks: what was formed, by whom, and under what operating boundary?
Phase 3 asks: which assets survive independent technical, legal/IP, commercial or research review, and what should be rebuilt, piloted, partnered or scaled?
One boundary.
Different maturity states.
Being eligible for the Phase 2 solo-formation set says who formed an asset and when. It does not say every asset reached the same technical or commercial maturity.
Four questions before
asset-level judgment.
Boundary first.
Then inspect the work.
The updated sequence matches the new MZN landing and Phase 2 overview. Evidence remains intentionally outside the active route until the final evidence experience is rebuilt.
A bounded claim is stronger because
it tells the reviewer what can defeat it.
Phase separation is not a request for a favorable verdict. It is the minimum structure required to test provenance without mixing team-built history, solo formation and later professional review.
Use the boundary,
then follow the relevant layer.
This page no longer routes to the legacy evidence stack. Use the current Evidence Hub for public evidence routing; source-backed controlled or sensitive material remains staged for the appropriate diligence process.