How I’m building You.one — with You.one

You.one keeps the work of building You.one organized, planned, tracked, discussed, and moving through Superboard, its Board view. I choose which Boards to keep and which work belongs in each. Within the development Boards, customer needs, product decisions, implementation, launch work, and support stay together so the tradeoffs involved in serving our first hundred customers remain visible instead of living only in my head.

This page includes a screenshot of my actual production Founder Board captured on August 21, 2026. The separate Card Room example remains a public-safe reconstruction of the kind of release decision I make.

The Board, Rooms, Stage, Chat, files, status, and the Ava help shown below are current. The later release-judgment story is Direction. I draw that line in public because I do not want this page to sell a workflow I do not have yet.

I currently keep a Personal Board and separate Boards for major areas of product work. Some screenshots still show older Board names from an earlier way I divided that work. Those are historical Board labels, not separate products: You.one is the product, and Superboard is its Board view. The useful rule is that each genuinely different mission gets its own Lists, Cards, Rooms, files, decisions, and pace.

I do not show my Personal Board publicly because it is personal. It uses the same pattern and stays separate because that mission is genuinely different from building the product.

That is the practical rule I recommend: keep a separate Board for every part of life or work that deserves its own clear operating picture.

Your missions will be different from mine. You might have one Board for school, one for a job search, one for caring for someone, one for a home project, and one for a hobby or side hustle. The point is not to become a project manager. It is to give each important mission one clear place where the work, notes, files, decisions, and conversation with Ava stay together.

If I leave the thinking in a temporary AI chat, a browser tab, or my head, I lose it. For each Card, I keep the ideas, debate, tradeoffs, and decisions with Ava in Chat. If an external article or reference bears on the Card, I copy the link and useful context into the same Chat.

That rule travels. If the thinking belongs to a course, renovation, volunteer campaign, book, or job search, it belongs in that Card’s Chat instead of a disposable thread.

In my engineering work, Ava also drafts large feature specs with me. Sometimes we begin in Chat; sometimes Codex—part of my programming setup, not a public You.one feature—produces a code-grounded draft first because it can inspect the repository, and Ava helps me question, revise, and improve it. The discussion stays in Chat; the resulting writing moves onto Stage.

I use native Stage Documents for drafting, working through ideas, and treating the page like a sketchpad. A proper visual Sketchpad is Direction; today the native Document is the flexible place where I think in writing.

I put the working specification on the Card’s Stage. After discussion and revision, I add the next named revision there too, so the Card holds the history of the spec beside the conversation that changed it. I name each revision myself; You.one does not yet version a Document automatically.

The same shelf can hold a syllabus, contractor plan, chapter draft, application packet, or event brief. Stage is simply where the work you are shaping stays with the reason it exists.

I keep Card status current and express priority in two ways: by ordering work within a List and with the Card’s priority picker. The Board tells me what is active, blocked, or done; the order and priority tell me what deserves attention first.

I attach relevant files—including PDFs—to the Card so the source material stays with the work and Search can find its filename later. You.one does not yet search inside every attached document.

In my programming setup today, governed internal tooling lets Codex post comments and updates directly to the Card. That is Founder infrastructure, not a public connector. A general public Codex connection is Direction.

Separately, on my Founder Board I explicitly ask Ava in Card Chat to review the Bugs List, rank the Cards from highest impact to lowest, and leave a one-line why so I can see the reasoning later. That is current, on-request help inside the Board. Ava does not continuously prepare or reprioritize across the mission by default; that broader default preparation is Direction.

Imagine a fictional homeowner planning a bathroom renovation. Her Board holds the renovation mission, and one Card holds the contractor decision. Chat keeps her questions, tradeoffs, and links to the estimates. Stage holds a bid comparison, the working scope, and a call checklist. The estimate PDFs stay attached to the Card. Status says Waiting on revised estimate; priority keeps the decision near the top. Pulse shows that the revised estimate is the next decision; Activity preserves when the bid terms changed and who changed them.

That is the same operating pattern I use, applied to a completely different mission. You.one today can keep that picture together. It does not contact the contractors or choose the bid for her.

My mission is to build You.one for the first hundred people who depend on it; You.one’s Superboard view holds and moves that work. The screenshot below is the live Board where You.one holds that product-building work. Its Lists cover engineering and infrastructure, the feature backlog, active work, blocked work, and completed work so I can scan the current front without rebuilding it from chats, notes, and memory.

My Cards hold customer interview synthesis, onboarding defects, release checklists, pricing decisions, support issues, and launch assets. You.one can hold these different forms of work in its Superboard view without forcing them into one task-only schema.

These Lists happen to be engineering, backlog, active, blocked, and done because that is this mission. A course, household project, book, volunteer year, or side hustle would use names that fit that work. The point is the same: I can see one mission without rebuilding it from chats, notes, and memory.

When I open a Card that actually matters, I do not want the draft in one place, the debate in another, and the files in a third. The Room keeps them with the Card: Stage for the working Document, checklist, and files; Chat for the discussion and explicit @Ava requests; Pulse for the current state I can scan without rereading Chat; Activity for who changed what.

Those Room surfaces and supported Undo are current. The public-safe Room below reconstructs the kind of release decision I make; it does not show Ava gathering broader evidence or preparing the later Direction workflow.

I have to choose whether to delay a release for a reliability fix that affects a small but important group. The Direction is for Ava to gather the relevant evidence, prepare viable options, identify uncertainty, and recommend a move. I make the consequential choice and provide any authority needed for an external action; Ava does not decide or authorize that boundary for me.

You.one today neither interviews customers nor deploys the product autonomously. Any future external action still requires the applicable connection and authority.

First-class connections for Codex and other external agents are Direction. They should work with Ava and update Board content only when I have clearly allowed it, and every change should be visible and reversible.

I remain the Owner of the calls that matter: what deserves attention, what quality the work must clear, which tradeoff I will live with, and what moves forward. Ava can help me prepare the decision; she cannot grant herself permission to deploy, publish, spend, or make a customer promise.

If this might fit your life, start with one Board for one mission you already carry. See whether keeping the work, thinking, files, priorities, and decisions together makes the next move clearer. Then read where human judgment belongs. The waitlist is appropriate only if today’s product fits a real mission you carry—work, study, a household, a craft, or a company.

The Board, Cards, Rooms, Stage artifacts, Chat, Pulse, Activity, search, saving, and supported recovery shown here are current product surfaces. The main Board image is a screenshot of my actual production Founder Board; the separate Room fixture is reconstructed and contains no private production or customer data.

The deeper cross-work reasoning, continuous monitoring, prepared external workflow, and sending or spending described in my story are illustrative Direction unless a current Help article says otherwise. I remain responsible for the mission, its constraints, every consequential judgment, and real authority throughout both the current workflow and that Direction.