Ben Stull
11 KiB
Wiggleverse Vision Docs — Plan
Three vision documents, written in sequence, each in its own session. All three live in this directory (benstull/docs/), in Ben Stull's voice, as personal authoring. They are not framework docs (those live in the OHM repo) and not product docs (those will live in a future Wiggleverse Org repo). They are the why that the framework and the product will both be answerable to.
Together they answer three different questions, in three different registers, for three different (overlapping) audiences:
- What is the Wiggleverse, and why does it need to exist? — for anyone who needs to understand the project at all.
- What does the MVP actually do? — for early collaborators, contributors, and the first invited humans.
- Who builds it, how, and under what governance? — for the planned 501(c)(3), future board members, fiscal sponsors, donors, and engineering leads.
Splitting them keeps each one short, on-voice, and answerable. Conflating them into one doc produces a soup that does none of the three jobs well.
The three docs, in order
1. wiggleverse-vision.md — Narrative + OHM word list
Purpose. State what the Wiggleverse is, why it needs to exist now, how it inherits from "How I Wiggle Through the World," and what OHM words it requires defined in order to be coherent. End with a Tier 1 / Tier 2 / Tier 3 word list — the bridge from this vision into actual OHM RFC work.
Audience. Anyone encountering the Wiggleverse for the first time — collaborators, future board, future users, and Ben himself six months from now.
Voice. Manifesto-toned, written by Ben, matching the register of PHILOSOPHY.md (in the OHM repo) and how-i-wiggle-through-the-world.md (in this repo). Continuous prose, not feature bullets.
Why this is first. The vision is the spine. Both the MVP doc and the Org doc reference it. The OHM word list inside it is also the first concrete bridge between Ben's vision and the framework's RFC pipeline — without those words named, neither downstream doc can be specific.
Rough length. 2–4 pages.
2. wiggleverse-mvp.md — MVP feature shape
Purpose. Describe what the Wiggleverse MVP actually does, at vision level — not engineering spec. Profile creation, persona, life-question answers, media upload with rich who/what metadata, invitation-in-context (personal / project / professional), and the reference-and-claim flow for humans who aren't in the system yet. Includes the "Ben's first hour" walkthrough as a concrete story.
Audience. Early collaborators and the first invited humans — people who need to imagine themselves using the thing, not just understand it abstractly.
Voice. Still Ben's, still manifesto-adjacent, but more concrete than Doc 1. Walkthrough-driven. Names features without specifying them.
Why this is second. Depends on the vision and the word list being settled — every MVP feature should map back to one or more Tier 1 OHM words. Writing the MVP first risks naming features that have no OHM grounding, which is exactly the trap OHM exists to prevent.
Rough length. 3–5 pages.
3. wiggleverse-org.md — Org & governance framing
Purpose. Name the three-layer structure — Ben Stull (visionary) → Wiggleverse Org, planned 501(c)(3) (builder + steward) → OHM (open standard the platform is built on) — and explain what that layering implies for how the project gets built, stewarded, and funded. Touch on public-benefit framing, what stays in OHM vs. what stays in the Wiggleverse Org's product surface, and the case for nonprofit form.
Audience. Future board members, fiscal sponsors, donors, legal/accounting help, and engineering leads who need to understand whose interests they're working in service of.
Voice. Slightly more formal than Docs 1 and 2 — still Ben's voice, but written with the awareness that pieces of it will get lifted into board materials, grant applications, or 501(c)(3) filings.
Why this is third. It needs both prior docs as referent. The org's purpose is to deliver the vision (Doc 1) by building the MVP and what comes after (Doc 2); without those settled, the org section devolves into generic nonprofit boilerplate.
Rough length. 2–4 pages.
How the three relate
Doc 1: Vision → the WHY (the spine; defines success)
Doc 2: MVP → the WHAT (the first concrete delivery of the why)
Doc 3: Org → the HOW (the legal/governance structure that delivers it)
Each doc cross-links to the others. None of them is the canonical OHM RFC text — the OHM corpus is its own work, on its own cadence, in wiggleverse/meta and per-RFC repos. These docs consume OHM and demand specific words from it; they do not define those words.
What flows out of these docs into OHM
Doc 1 surfaces a Tier 1 / Tier 2 / Tier 3 list of OHM words the Wiggleverse needs defined. Those words then become RFC work in the OHM corpus on the framework's own cadence (super-draft → argued → graduated). Wiggleverse cannot ship its MVP until at least the Tier 1 set has reached usable draft state in OHM, because the MVP's user-facing semantics depend on those definitions being settled enough that the OpenXML APIs and UX surfaces can be derived from them.
This is the dependency direction:
benstull/docs/wiggleverse-vision.md
│
│ names required words
▼
OHM RFCs in wiggleverse/meta (Human, Consent, Persona, Context, Invitation,
│ Connection, Reference, Claim, Content,
│ Experience, Moment, …)
│ English-canonical definitions
▼
OpenXML APIs + GraphQL schemas derived from the English
│
▼
Wiggleverse Org product code → wiggleverse.org
Session 2 kickoff prompt
The prompt below is self-contained. Paste it into a fresh Claude Code session opened in /Users/benstull/projects/benstull/git/benstull (the repo where the output file lives and where the commit will land) to start Doc 1. The prompt uses absolute paths throughout, so files in rfc-app/ and memory anchored to the rfc-app project are read explicitly rather than relying on auto-memory.
Write the Wiggleverse vision doc — Doc 1 of the three-doc plan in
/Users/benstull/projects/benstull/git/benstull/docs/wiggleverse-doc-plan.md.
Read these four files first, in order, before writing anything:
1. /Users/benstull/projects/benstull/git/benstull/docs/wiggleverse-doc-plan.md
— the plan you are executing against. Read in full.
2. /Users/benstull/git/rfc-app/PHILOSOPHY.md
— the framework's own manifesto. Voice and register reference.
3. /Users/benstull/projects/benstull/git/benstull/docs/how-i-wiggle-through-the-world.md
— Ben Stull's personal manifesto. The vision doc must inherit from
this directly; map each principle to a platform behavior.
4. /Users/benstull/git/rfc-app/SPEC.md (skim §1 only)
— confirms that OHM RFCs define one word each, that the first RFC
is "human," and that English is canonical with OpenXML/UX derived.
Also read these two memory files explicitly (they live in the rfc-app
project's memory and won't auto-load from this cwd):
- /Users/benstull/.claude/projects/-Users-benstull-git-rfc-app/memory/project_open_human_model.md
- /Users/benstull/.claude/projects/-Users-benstull-git-rfc-app/memory/project_wiggleverse.md
Then write /Users/benstull/projects/benstull/git/benstull/docs/wiggleverse-vision.md
with this structure:
1. What the Wiggleverse is
— one tight paragraph: the first inhabited surface of OHM,
wiggleverse.org, where defined OHM words become lived experience.
2. Why now
— OHM needs an existence proof; the manifesto needs a system to
live in; the two are the same project from two ends.
3. Founding posture
— wise speech + informed consent, mapped from the eight
principles in "How I Wiggle Through the World" to platform
behaviors. Don't list all eight as bullets; weave them into prose.
4. The shape of the MVP
— short, gestural. Profile, persona, life-question answers,
media with rich who/what metadata, invitation-in-context, the
reference-and-claim flow for humans not yet in the system. One
paragraph each, not a feature list. Detailed feature breakdown
belongs in Doc 2 — do not preempt it.
5. Walkthrough — Ben's first hour
— concrete story. Ben creates his profile, declares his persona
("edgy Mr. Rogers"), answers a life question ("How much is
enough?"), uploads a dog video that tags his friend Molly (who
isn't in the Wiggleverse yet — a Reference object is created on
her behalf), and invites a friend in *personal* context to watch
a woven Moment. Use this story to ground every prior section.
6. What this requires from OHM
— the Tier 1 / Tier 2 / Tier 3 word list. Tier 1: Human,
Identity, Persona, Consent, Invitation, Context, Connection,
Reference, Claim, Content, Experience, Moment. Tier 2: Audience,
Question, Answer, Stewardship, Witness, Weave. Tier 3: Trait,
Preference, Agency, Boundary, Harm, Trust, Disclosure, Privacy,
Expertise. One sentence each on why the MVP needs it.
7. Explicit non-goals for v1
— feeds, algorithms, public discovery, monetization, recommend-
ations, virality mechanics. Name them so the absence is intent-
ional, not oversight.
8. How this gets built
— short. Words first (OHM RFCs, English-canonical), OpenXML
APIs and GraphQL schemas derived from those words, Wiggleverse
Org product code implements the derived APIs. Org structure
itself belongs in Doc 3 — name it in one sentence, do not expand.
Voice: Ben Stull, first person, manifesto-toned. Match the register of
PHILOSOPHY.md and how-i-wiggle-through-the-world.md. Continuous prose,
not bullet soup. Headings are fine; nested bullet lists are not.
Length: 2–4 pages.
Hard constraints:
- Do not define OHM words yourself. Name them and gesture at why
the MVP needs them. Defining them is OHM RFC work, on its own
cadence, in wiggleverse/meta.
- Do not specify MVP features at engineering-spec level. Doc 2 does
that.
- Do not write org / 501(c)(3) / governance material beyond one
sentence of acknowledgment. Doc 3 does that.
- Do not invent OHM words not on the Tier 1/2/3 list without first
flagging the addition for Ben.
- No emojis. No trailing "Summary" section. No marketing copy.
When done, report back with: the file path, the final word count,
and any words from the Tier list you found yourself wanting to add
or remove while writing (those become RFC scope conversations).
Sessions 3 and 4
After Doc 1 lands and Ben has had a chance to read and revise it, kickoff prompts for wiggleverse-mvp.md (Doc 2) and wiggleverse-org.md (Doc 3) get added to this file in the same shape. Each later prompt will reference Doc 1 (and, for Doc 3, Doc 2) as required reading.