Each page states whether it describes working software, a tested component, a design, or an idea. The build log is the dated project inventory. A separate technical page covers threats and engineering details.
KISOP is in development. This website and its browser-based tools work today. Early archive software is available for programmers to inspect and test, while other parts remain designs. The software has not received an independent security review and is not ready for personal records. Publishing work in progress lets people inspect it and report problems.
The rooms that are finished are real rooms. You can stand in them today. The scaffolding stays up, visibly, until the work it guards is done. Nobody here will tell you the house is finished while it's wearing scaffolding.
A project being built in the open. KISOP is Care Delivery Inc's project to give every person one place for their whole life's information, a place that lives with you, in your house, and belongs to you.
A website you can use today. Everything you can read here, and the four tools (the action plan, the health-records access guide with a fallback request letter, the starter kit, and the handoff brief) work right now, entirely in your browser. What you type never leaves your device. That part is done, and "What we built" walks you through it.
Early software with status labels. Behind the site, the first working pieces of the archive itself exist: programmers can read them and test them today. Each piece has its own dated page saying exactly what's been tested and what hasn't. Built things say "built"; designs say "designed"; ideas say "idea."
An invitation. To follow along (the "New in this place" board on the main site announces every change, dated), to tell us what worries you, and, if it's your craft, to help build.
Read this list as carefully as the one above. It's the same plain accounting, pointed the other way.
You cannot download KISOP today and put your medical records in it. The archive software exists in early, working pieces, built for builders and testers. It is not ready for your family's records. When that changes, the site will say so, dated. No page here will quietly start saying otherwise.
This is the most important line on this page. The people building KISOP test their own work carefully, and publish exactly what has been tested and what hasn't. No independent security expert has been brought in to try to break this software. No certification stands behind it. Until an outside expert has been through it, and this page announces that, dated, treat the early software as a workshop bench: don't put anything into it that you couldn't stand to lose, or to have someone else see.
No tool here diagnoses, treats, or replaces a clinician, and nobody here is your doctor. In an emergency, call 911. In a mental-health crisis in the US, call or text 988.
This is not a patient portal, and Care Delivery Inc is not a health-care provider or a health plan. Nothing here reaches into your medical chart, and no hospital's records flow here. The tools help you request and organize your own records: the records themselves go to you. They never pass through us.
The site has no accounts, and what you type into the tools never reaches us: the documents are made on your device. If you ask the site to remember your name, that memory lives in your browser. It never reaches us. The full accounting is in the Privacy Policy draft, and it's short because there's little to account for.
No ads, no analytics, no selling of anything about you: this site doesn't even talk to other companies' servers. A technical person can verify that in the page source in about a minute. We check it by machine before every release.
The Terms, Guidelines, Privacy Policy, and project pages are dated and versioned. When the project changes, the relevant page records the date. Please report any claim that exceeds what the software or organization can currently do.
Read everything, share anything. The pages are free, and made to be passed along.
Use the four tools. They leave behind only what you print or save yourself. Make the plan, choose a route for gathering records, use the fallback letter if needed, and build the kit: that's what they're for, today.
Tell us what's wrong, or what worries you. On the main site: Write to us → "feedback." If you found a security problem, Write to us → "security": good-faith research is welcomed, credited, and protected by a safe harbor written into our Terms, §15.
Follow along. The "New in this place" board is the project's public changelog: every visible change, dated. (The doors open our own intake service at apply.kisop.com, live since September 9, 2026; its host stays gated to the founder’s network until the site itself goes public.)
And the one thing not to do yet, said once more: don't put real personal records into the early software. It isn't ready to hold them, and it says so itself.
The site uses one status system: the build log as the central inventory; dated pages; the labels built, designed, and idea; the 📋 mark for pending verification; and the "New in this place" board for visible changes. Any independent security review will be announced with its date, scope, and findings.
Written July 13, 2026, as the whole project's status page, the project-wide version of the status box you'll find at the bottom of every page here. In review 📋: Carmen's review is pending.
August 8, 2026: the project's status inventory moved to the build log — one page, updated every time reality changes. This page keeps the plain-words meaning of those statuses.
This page will say so, dated, when any of it changes. Same as every page here.