Here the person using the tool defines the challenges they want to solve, the community funds and builds the features, and every feature lands in a public table anyone can read, argue with, and add to. This page lays out that whole machine — the zones the work lives in, the front end that shows you your life, the back end you choose the home for, and how features ride releases until a capability lights up.
By Carmen Wiedenhoeft · Palo Alto · July 2026 · draft v1.0. Drawn from her Product Features notebook (pages dated April 2024 – April 2025, exported July 7, 2026). The diagrams below are her pages, redrawn — margin notes, open questions and all.
A different way to think about products
This is a loop the community turns. The features on this page are requests, in the requester's own words.
"This is a different way to think about products. The person using the tool defines the challenges they want to solve."Product Features notebook
Every feature described below entered the world the same way: somebody living a situation (a mother packing school lunches, a daughter managing a parent's fifteen nurses, a member trying to understand a lab result) wrote down what they needed. In this system, that request becomes a job to be done, named, priced, funded in fractions by the people who want it, built and tested by the community, and released to everyone. The mechanics live on the jobs board and Ways to Work Together. Jobs fund the features, and the features make the jobs worth funding.
The loop, in her own blue ink: "As a user, you say what you want, the community builds + tests it. You adopt it + tell them what you think. The community improves it." Her parenthesis matters: the model gives traceability, and every feature can be traced back to who asked for it, who funded it, who built it, who tested it, and what release carried it.
Your voice in this loop is worth money: the system says so out loud. Members are paid to provide input: requirements that flow to the builders, to researchers, to use cases, to disease-specific work. And the data you choose to contribute (patient-generated health data, shared under a consent you can read) is what supports accountable research.
Redrawn from the notebook. The member is a paid contributor. Requirements and consented, patient-generated data flow out under class C4 consent (defined below), logged, and compensated.
The commitments · from the notebook's "Personal Health System" page
What the whole system promises, before any feature
Understand user needs, and build products that meet those needs.
Connect the information together. The user should not have to keep many different silos.
Separate the front end from the back end: the window you look through and the box your life is stored in are two different things.
Protect against exfiltration and ransomware.
Personal foundation models — a model that knows you, working for you.
The Personal Health Record, including medical records across every institution you've touched.
Health-plan benefits, coverage, payments, access to care — in the same place as the care itself.
Daily habits, and your own understanding (the American Heart Association pamphlet, kept next to your labs).
An economic engine that works, and a way for people to select the data they want to receive.
An extensible system — built to be added to by people we haven't met yet.
Zones of work
Her enumeration scheme, "used throughout the site": six zones, A through F, from what you do alone to how the money moves. Every feature carries a zone letter.
Health happens in a handful of real places: alone with a notebook, at the store, among your people, in the exam room, in the hospital, and inside the machinery that pays for all of it. Carmen drew those places as a strip of six zones. That strip is the spine of the whole feature catalog. A feature that helps you log your water lives in Zone A. A feature that gets your records out of a hospital lives in Zone E. A feature that helps a donor fund the next release lives in Zone F.
Zones of work, redrawn from the notebook's first drawing, with the four highlighter-marked areas from the page beside it. Together they form the address system: every feature in the public table below carries a zone letter. Enumeration by zone is what keeps the catalog from becoming a junk drawer.
Two axes give every feature an address. "Log my water" is A-zone work in individual hands. "Request my records" is D/E-zone work that service providers must answer. "A researcher asks for consented data" is third-party work that reaches the archive through the gate alone. And "publish the feature table" is core-business work: Zone F pays for it. The grid below is the whole catalog seen from above.
The catalog seen from above: zones across, areas down, features as squares. An empty cell is information too: it means nobody has asked yet, or nobody has funded it yet.
The front end — windows onto your life
Everything in this section is a way of seeing: views, logs, plans, invitations, events. Your life is stored downstairs, in the home. Windows are chosen, swapped, and discarded.
front end — a window you look through back end — the home your archive lives in
The commitment from the notebook is architectural: the front end is separated from the back end. Your data has one home: the archive you control. Every screen, summary, chart, and reminder is a window onto that home, opened through a consent gate that logs what was asked and what you allowed. This is what makes agency real: you can change the window without moving house, and you can move house without losing a single window.
The seam. Windows above, home below, one logged door between them. Anything derived (indexes, summaries, dashboards) can be rebuilt from the archive at any time. Nothing else can rebuild the archive. Rebuilding in only one direction is the operational meaning of ownership.
The viewing features, enumerated
These are the windows the notebooks ask for. Each one is a fundable job, listed with its address in the public table:
The health summary view — your whole picture, aggregated, and a view per folder: images (mammogram, x-ray), medical records from encounters, labs and tests, bills, medicines.
Logs you keep in seconds (weight, food, medicines, exercise, water) and daily-routine views that make healthy habits visible.
Trends over time — "you eat a lot of this, but you're missing this macronutrient against the daily recommended amounts."
The plan-of-care view (meds in the morning, meds in the evening, supplements, water), readable by the person, the family, and whoever walks in for the Tuesday shift.
The family view — updates that are simple and understandable, and a medication-and-allergy list the family can produce in one motion, in the hallway, when it matters.
Your story — a place to tell it. The notebook's page for this has three words on it: tell your story.
Invitations — "Invite Me": walks, exercise, eating well together, sharing a purchase, sent person to person, accepted in email or on your dashboard, landing on your calendar, visible in your member area.
The events catalog — community events by type and by zip code, some free; selecting one sends you an email with a calendar file; forwarding it invites your people, and the email encourages them to join you.
Two postures, one systemSome people want to use the app. Some people want to collect their data: an edge device quietly filling their archive. The notebook draws both without ranking them: the consumer posture and the edge posture are the same system worn two ways.
Access is a featureVoice is first-class and the system is natively multimodal: the notebook's example is a person with Down syndrome using voice where a keyboard excludes them. Language support is a feature line of its own. And accessibility + choice sit in the Design column of every release, where they can't be skipped.
Privacy shows up in small placesGroup events can run on a public line — a thousand people doing it with you is encouragement), but participant lists stay hidden to respect privacy, and a person and their loved ones can always elect a private line instead. Some events are just calendar placeholders with good health information attached.
The back end — where your archive lives
The Personal Neutral Archive (PNA) is the home. What's in it is yours; where it lives is your election; and the more secure ways of keeping it are choices you can make.
Underneath every window sits one thing: your Personal Neutral Archive (PNA), your canonical store, raw and processed, with each source's schema and provenance preserved, held as plain files in open formats on storage you control. Neutral in five senses: vendor-neutral, format-neutral, model-neutral, environment-neutral, purpose-neutral. The full specification is open knowledge (links below); what matters here is what it contains and where it can live.
The April 15, 2025 notebook page, redrawn. Her three pens kept: the summary layer that makes it readable, the institutional records you extract copies of, the data you gather yourself (with her margin note: watch and phone data is incomplete), and the coverage that pays for care. One archive, partitioned, holding health, finances, receipts, a parent's care file, andyour own writings too.
Where it lives is an election
Here is the part that is easy to say and rare to mean: the person chooses the home, and can change their mind: easy to say, rare to mean. The ways we have written about so far are the reference build: a home node holding the canonical copy, a replica on your own machine, two encrypted backups. Some people will start with a binder and a folder of PDFs. Some will elect much more secure arrangements than the reference. Every rung is legitimate; every rung keeps the same files, the same gate, the same rights.
The ladder of homes. The reference build is what the specification describes today; the rungs to its right are elections the specification must never foreclose. The rung on the far left is a person with a legitimate home. Every rung above the binder includes backup by design, so you cannot lose the archive.
Agency and transparency, made mechanical
Agency is the consent classes: you set, per partition of your archive, how far anything may travel. Transparency is the access log: nothing about you is shared by default, and the log records what was asked and what you allowed. Both are properties of the archive itself. Neither depends on trusting an interface.
Consent classes — the default set; the owner can extend it
Class
What it means
C0
Never leaves the archive. Local only, local models only.
C1
A local AI may read; results stay in the archive.
C2
A named remote model or agent may read under a specific grant, logged.
C3
A named person — Community Helper, physician, caregiver — may read specified partitions, logged.
C4
A consented research contribution — de-identified per the grant's terms.
C5
Public — the owner has published it.
Back-end features, enumerated
Back-end features are the ones that touch the home itself. They include the sources feeding it. The notebook's "Back end features" page names the pattern: you get your data into your repository, and vendors offer features against the standard. A lab company can offer delivery of results straight into your archive; a device maker can offer its readings the same way. They offer features. They never take custody. That inversion (vendors compete to serve your archive, and no vendor owns a copy of you) is the market this system creates.
Request, receive, send records — the right of access, exercised as a button: from every doctor, facility, lab, and imaging center on your list, into your archive, originals preserved.
Upload what you hold (vaccines, labs, imaging, the shoebox layer), hashed, dated, provenance written.
Manage where your data is stored — the election above, as a feature with a screen.
Data portability — close your account and move everything out, whole, any day. The system is built so that leaving it loses nothing; that promise is a conformance test.
Delete — tools may never remove or degrade your data. The owner's hand is the only one that erases.
Grant and revoke access (to your doctor, your family, your caregiver, a Community Helper, a researcher running a clinical trial), each grant scoped, classed, logged, reversible.
Protection as a feature line — encryption at rest, replication, versioned backups: the ransomware answer is that the canonical copy is yours, plural, and offline-capable.
The capabilities, A through H
A capability is what a person can actually do once enough features exist. The notebook enumerates eight, lettered in Carmen's own hand, and each card below keeps her numbering.
Features are small on purpose: fundable, buildable, testable one at a time. What people want is to manage their own health record. That ability arrives only when a family of features has landed. These eight capabilities are the system's promises; the numbered items are the features that keep them.
front end — a window back end — touches the home
A
User administration
everyone — the front door
Create an account, manage your password
Create a profile per person
Add people to your household
Add a role to a person — client · Community Helper (lead, associate) · provider · third-party administrator
Invite others to join the platform
Set up groups
A household is the real unit of care: one account can hold a mother, her kids, and her parents, each a full person.
B
Manage your Personal Health Record
client + community helper · full CRUD in the owner's hands
List your doctors + facilities
Request records
Receive records
Send records
Data portability — close your account, move records out
Manage your data storage location
Set disease conditions
Upload records — vaccines, labs, imaging
Delete records
Her margin note says it in four letters: CRUD — create, read, update, delete. All four verbs belong to the owner, and a tool gets none of them without her consent.
C
Grant access to your data
client · consent, as a verb
Grant access to your doctor
… to your family
… to your caregiver
… to a Community Helper
… to a researcher (clinical trial)
Grant permission for people to invite you
Join groups
Every grant is scoped to partitions, carries a consent class, is logged, and can be revoked. Even being invited requires your permission first.
D
Work as a Community Helper
the community's trained neighbor
List your services
Manage your credentials
Manage your profile
Send secure communications
Manage payments
Learn — find a class, sign up, complete it, receive a certificate of completion
Certification is visible: a certified host wears a flag, and a background check is required to earn it. Verified professional credentials get a flag of their own.
E
Send invitations
how the community moves together
Person to person — a walk, exercise, eating well together, sharing a purchase
Host to client — requires a relationship already added, so a host can never cold-call
Four steps, from the notebook: one sends the invite (email or dashboard) · the other accepts · it lands on both calendars · it can be edited. Invites live in your member area.
F
Manage your health
the daily fabric
Healthy habits — daily routines
Log — weight, food, medicines, exercise, water
Set goals
Review your plan of care — meds in the AM, meds in the PM, supplements, water
Everything logged lands in the archive, which is why a log kept for you in seconds becomes a trend your doctor can trust in a year.
G
Find help for your goals
from a walking partner to a hospice
Find a walk
Find a caregiver — by the hour · live-in · hospice
Research your options (i.e., insurance)
The same verb, "find help," spans a Saturday walk and end-of-life care. That span is deliberate: one system that already knows you, at every weight of need.
H
Track completion of services
did the help actually happen?
Track completion of services
One line in the notebook, drawn with an arrow from capability G, because finding help means little if nobody confirms it arrived. This is also the fraud, waste, and abuse defense: services that must be marked complete are services that can be audited by the family.
How a feature ships — define, design, build, test, deploy
Features ride releases. A release is a named, numbered bundle (features + libraries + tech stack), tested as a unit, priced in the open, deployed in ways that do not cause harm.
The pipeline page, redrawn. Her shorthand elsewhere in the notebook compresses it to D³ (define, design, deploy), wrapped around a build-and-test loop. The definitions stay human; the acceleration is AI; the deploy column carries the two lines that govern everything: fewer products meeting more needs of more people, deployed in ways that do not cause harm.
The proposed release trains cut the catalog into deliverable seasons: each one a fundable bundle with a published feature list and a test release number before it ships. The trains are a plan; the table is the truth. When the community funds jobs in a different order, the trains get re-cut and the table says so.
Release 0 — "the archive." The back end: the Personal Neutral Archive itself, ingest, provenance, the consent gate, storage-location choice, portability. Everything else stands on this.
Release 1 — "see your life." First windows: accounts, households, the summary view, logs, plan of care, the medication-and-allergy list, your story.
Release 2 — "together." The community layer: invitations, groups, the events catalog, Community Helper tools, accountability partners.
Release 3 — "help shows up." Finding caregivers, researching options, tracking completion, family updates, food answers at the shelf and the stove.
The rollup, in one line: features ride releases; capabilities fill. When capability B reaches nine of nine, you will actually manage your own health record.
The public feature table
Eventually this lives as a published, sortable register: every feature, its address, its layer, its release, its status, its funding. This is the seed, drawn entirely from the notebooks. The numbering inside each capability is Carmen's own; rows beyond her lists continue it.
A public table is the traceability her loop demands. Anyone can see what was asked for, what it costs, what it rides on, and what state it's in. Every shipped feature appears in the table, and every row shows its status. Current statuses: most rows are proposals awaiting funding; a few are specified in the open documents; a handful have already been lived in the v0 archive or prototyped in earlier tools. As the community funds jobs, rows move through funded → building → testing → released, and each release stamps its rows.
proposedfrom the notebooks, awaiting fundingspecifiedwritten into the PNA spec / PRDprototypedtried in an earlier toollived in v0already practiced in the founder's own archive
Seed of the public feature table · v1.0 · July 2026 — zones A–F per the strip above; layer: front = window, back = home
ID
Feature
Zone
Layer
Release
Status
A · User administration
A-1
Create an account, manage your password
A
front
R1
proposed
A-2
Create a profile per person
A
front
R1
proposed
A-3
Add people to your household
A
front
R1
proposed
A-4
Add a role to a person — client · Community Helper (lead / associate) · provider · third-party admin
A·C
front
R1
proposed
A-5
Invite others to join the platform
C
front
R2
proposed
A-6
Set up groups
C
front
R2
proposed
A-7
Manage contacts — "a wrong phone number can cause delays"
A·E
front
R1
proposed
B · Manage your Personal Health Record
B-1
List your doctors + facilities
D
front
R1
lived in v0
B-2
Request records from any institution
D·E
back
R0
specified
B-3
Receive records into your archive
D·E
back
R0
lived in v0
B-4
Send records where you choose
D
back
R0
specified
B-5
Data portability — close your account, move everything out
A
back
R0
specified
B-6
Manage your data storage location — the election of homes
A
back
R0
specified
B-7
Set disease conditions
A
front
R1
proposed
B-8
Upload records — vaccines, labs, imaging
A
back
R0
lived in v0
B-9
Delete records — the owner's hand only
A
back
R0
specified
C · Grant access to your data (consent)
C-1
Grant + revoke access — doctor · family · caregiver · Community Helper · researcher (clinical trial); classes C0–C5, logged
A–F
back
R0
specified
C-2
Grant permission for people to invite you
C
front
R2
proposed
C-3
Join groups
C
front
R2
proposed
D · Work as a Community Helper
D-1
List your services
C
front
R2
proposed
D-2
Manage your credentials — background check, certification flag, verified-credential flag
C
front
R2
proposed
D-3
Manage your profile
C
front
R2
proposed
D-4
Send secure communications
C
front
R2
proposed
D-5
Manage payments
F
front
R2
proposed
D-6
Learn — find a class, sign up, complete, receive a certificate
C
front
R2
proposed
E · Send invitations & gather
E-1
Person-to-person invitations — a walk · exercise · eat well together · share a purchase
C
front
R2
proposed
E-2
Host-to-client invitations — requires an added relationship
C
front
R2
proposed
E-3
Events catalog — by type + zip, some free, email with calendar file, forwardable to family
C
front
R2
prototyped
E-4
Private lines for you + loved ones · hidden participant lists on public events
Review your plan of care — meds AM · meds PM · supplements · water
A·E
front
R1
lived in v0
F-5
Tell your story
A
front
R1
proposed
F-6
Food answers — what to eat now · what to buy · special occasions · your diet over time vs. recommended
B
front
R3
proposed
F-7
Scan a grocery receipt → your food data (and, with the grocer, theirs)
B
back
R3
proposed
G · Find help for your goals
G-1
Find a walk — with a loved one, with a colleague
C
front
R2
proposed
G-2
Find a caregiver — by the hour · live-in · hospice
C·F
front
R3
proposed
G-3
Research your options (i.e., insurance)
F
front
R3
proposed
G-4
Find an accountability buddy — journal the plan the night before, text each night: we did it
C
front
R2
proposed
H · Track completion of services
H-1
Track completion of services — the audit trail the family can read
E·F
front
R3
proposed
H-2
Family updates — simple and understandable, on a regular basis
E
front
R3
proposed
H-3
Produce the medication + allergy list, in one motion
E
front
R1
lived in v0
The row that keeps the table alive"We want users to be able to recommend features." — the notebook, in the middle of the seniors pages. Recommending a feature is itself a feature, and it is how every other row got here. When the register goes live, the recommend button sits at the top of the table.
Who runs it with you
Features are software; the system is people. Community Helpers carry it into the world, often through local Solution Centers, and a membership ladder funds the ground they stand on.
Community Helpers — a broad role with clearly labeled qualifications
Community Helper is KISOP's umbrella term for people who help one another take practical steps for health. It includes neighbors, family caregivers, volunteers, community health workers, home health aides, nurses, and other professionals. A helper might host a walk or lecture, bring people together to review prevention schedules, organize questions, find services, or help someone understand their own information.
The umbrella does not erase important differences. A community health worker is a recognized occupation and may need state certification. A certified home health aide is a separate role with different training and permitted tasks. Clinicians have their own licenses. Informal caregivers and neighbors bring lived experience but no implied professional authority. The system must show these distinctions:
Every qualification is named. Profiles distinguish lived experience, KISOP training, background checks, state certification, and professional licensure. None substitutes for another.
Verified credentials get their own label. Community health workers, home health aides, doctors, nurses, and other professionals are marked with the exact credential verified and the jurisdiction that issued it.
Scope follows the person, task, and place. Calling someone a Community Helper never authorizes clinical, personal-care, or home-health work. Each person performs only tasks allowed by their training and local law.
Ethical lines are drawn in advance. Health insurance agents are prohibited from certain advising, for ethical reasons: the person selling you coverage does not get to be the person interpreting your options.
Health plans can fund appropriate training. Funding a training program does not create a state certification or professional license.
Solution Centers — the assisted-AI access point
A Solution Center is a physical place where a community gets its hands on all of this, because agency that requires an iPhone and a comfortable income only reaches a demographic. The notebook's design, dated April 2025:
What a center does: get help accessing AI · learn about AI · contribute to AI · have your voice heard with AI · protect your privacy and security. Community Helpers can train here. Language support is core. So is access to food — a center that helps with your labs must help with your groceries too.
How centers are organized: like the US Census, by state, county, city, zip. 3 → 33 → 330 → 33023. Four per state to start (north, south, east, west), with counties designated under each.
Who leads: private individuals lead the centers. Mayors are invited as advisors and speakers, governors as speakers, and legal counsel in each state defines the laws and their application.
When things go wrong: her margin question, kept: after a major fire, how do we support prevention and recovery? Can we predict disasters? A center that serves a community in ordinary years can coordinate during an emergency.
Membership — who pays for the ground
Six plans, drawn April 13, 2025: two for individuals, two for communities, and two for builders, all under a single membership spanning medical devices + AI. Each tier includes its member sites and the tiers below it. The numbers remain notebook drafts:
Payment plans + member sites — as drawn, April 13, 2025 · draft numbers
Plan
For
Draft price
Member sites unlocked
1 · Basic
individuals
free
Basic
2 · Premium
individuals
$5
Basic · Premium
3 · Community Helpers
communities
$10
Basic · Premium · Community Helpers
4 · Solution Center Leaders
communities
$20
Basic · Premium · Community Helpers · SCL
5 · Developers
builders
$35
Basic · Premium · Community Helpers · SCL · Developers
6 · AI Builders
builders
$100
All of the above, plus clinical, legal, medical device + AI: access to everything
Her note on the $100 tier: "the cost of a conference — but you get value year round." A core team maintains the private intranet behind it all; as a member, you can express interest in using the tools, or in becoming a Community Helper yourself. Membership money is one stream; the funded jobs and ventures are the others.
Worked examples — the features in a life
Three threads from the notebooks, kept concrete: a senior after the hospital, food from receipt to doctor's visit, and children learning health at the kitchen counter.
A senior who needs advanced care
"When a senior declines after a hospitalization, the care at home needs to be different. The senior needs help transferring from the bed to a commode. The senior needs care with feeding, support brushing their teeth, help eating, help with laundry. They are more prone to be subjected to fraud, waste and abuse. They need protection. Adult children need to get updates on a regular basis. The family needs extra support."Product Features notebook — the seniors pages
The notebook then names the operational reality. Nursing staff change every shift (fifteen or sixteen different nurses in a week), so the medical providers and the family both end up with partial information, and the family becomes the advocate carrying updates across shifts. The services must be frictionless, combinations of products, and they must not exist independent of the tools the family, caregivers, and social workers already use. Each sentence maps to rows in the table:
The phases of daily living change → the plan-of-care view (F-4) is rewritten for the new phase, and the household roles (A-3, A-4) let a Community Helper and caregivers in.
Hands-on help → find a caregiver by the hour, live-in, or hospice (G-2), and track completion of every service (H-1).
Protection from fraud, waste and abuse → consent grants that are scoped and logged (C-1), services that must be marked complete (H-1), and an access record the family can audit.
Fifteen nurses, one story → the family view (H-2), updates that are simple and understandable, and the medication + allergy list produced in one motion (H-3).
A wrong phone number can cause delays → manage contacts (A-7). The humblest feature in the table, and in a bad week, the one that matters.
Food, from the receipt to the doctor's visit
The food thread runs through the whole notebook because food is where health decisions actually happen: at the shelf, at the stove, on Sunday afternoon. The challenges, in her words: What food should I eat right now — for breakfast, for lunch, for dinner? When I'm grocery shopping, what should I buy? What about special occasions? How can I see what is happening over time with my diet? Then the features: scan your grocery receipt and the calories in the food become your data model (F-7), and work with the grocer so the same receipt improves their picture too. The trends view answers the over-time question (F-6). And the plan drawing ties it to the architecture:
The Food Plan page, redrawn. Notice what the drawing shows: the recommendation engine reads your structure and your sheet, wherever you keep it, and the last arrow in the flow points to your doctor.
Kids, moms, and the ways people actually move
The gentlest pages in the notebook are checklists: invite your child to do healthy meal prep for the week, on Sundays, for the lunches. Invite your child to learn about food. As a Community Helper, invite other moms to do meal prep together. Help your person exercise on a regular basis. Then the invitation kinds spill out: walk with a loved one, walk with a colleague, move with a loved one, listen to a live lecture, listen to a recorded one, sustain a professional network the way the women's groups at a big company do. And a page titled Intersections (culture, gender, LGBTQ, how we grew up, age) with two clouds in the corners: walk + listen, move + listen. Features are small so they can combine along the lines people actually live on: a recorded lecture in Spanish, walked to, with your mother.
Provenance
Where every piece of this page comes from, so the traceability we promise starts with the page itself.
The Product Features notebook (GoodNotes, pages dated April 2024 – April 2025, exported July 7, 2026) — the source of everything here: the zones-of-work strip and four areas · the community loop, in her blue ink · the member-input engine · the Personal Health System commitments · the seniors pages · the kids-health and meal-prep checklists · the invitation kinds and Intersections page · the HealthMoti events prototype notes · the "Invite Me" mechanics · the capabilities A–H, in her lettering and numbering · Solution Centers (April 12, 2025) · payment plans + member sites (April 13, 2025) · the notes originally titled "Health Host" certification and ethics, now developed as the broader Community Helper role · the repository contents page (April 15, 2025) · the food plan, food logging, and "what challenges am I trying to solve?" pages · the back-end features page (vendor integrations: lab and device companies offering features) · the Define–Design–Build–Test–Deploy drawing with the product-table margin.
Redrawing liberties, declared: the diagrams are faithful to her structures and words; hands differ. The pipeline drawing omits her funding-rail margin (venture money entering at Build); that thread lives on the economy pages. The accountability-buddy feature (G-4) generalizes a personal note naming friends. "The reference build" in the ladder summarizes the PNA back-end architecture document. Release trains R0–R3 are this page's proposal for cutting her catalog into seasons: the first thing the community should argue with.
The Personal Neutral Archive spec v0.1 (July 4, 2026) — the back end's definition: the five senses of neutral, the archive-is-canonical rule, consent classes C0–C5, KISOP-compatibility clauses.
The product layer — PRD v1.0 and the 18-use-case catalog (July 5, 2026): the features here trace into those use cases (the seniors thread is UC-02/UC-03; the Community Helper, originally called Health Host, is UC-09; the Solution Center director is UC-10).