About RocSite.
RocSite is the institutional memory of the company. You grant the mess. Originals stay on your machines. When you ask, the answer is already waiting, dated, sourced, and able to be signed. The bar underneath that memory is independent validation, receipts, published either direction.
Why we exist.
Companies forget themselves. The pile sits in PDFs, a CRM, the folder nobody opened. RocSite exists so the grant happens once, originals stay, and when you ask the answer is already waiting: dated, sourced, able to be signed.
The bar under that memory is the passport: a Definition-ID, a PROVABLE or ATTESTED record, and the binding. Offline. No self-grade. Receipts. Publish either direction.
How we work.
We pre-register. We lock the hypothesis before touching the data. We publish the result regardless of direction. Our methodology is designed to survive review, and our systems are designed to produce receipts: a passport that carries a grade. Not every output is PROVABLE. ATTESTED is disclosure. It is not proof. There is no third sentence. No self-grade.
What's running now.
RocSite, Inc. is a Delaware C-Corporation, established in 2022. A focused team that ships. One company. No third product.
Governor, Caliper, ICH, and Discovery are tanks under the passport, not the mission. ICH Triage produces the passport for a named imaging event, offline, no off-site PHI; FDA Pre-Sub Q253397 is pedigree, not the firm. AI Governor grades a model claim against a locked instrument and signs the receipt; it is not a medical device. Caliper and Discovery staple a definition to a graded safety record. The sepsis falsification study is the receipt: 286,510 ICU patients, MIMIC-IV and eICU-CRD, pre-registered, null published.
That last sentence is the discipline. We pre-register. We lock the hypothesis. We publish the result regardless of direction.
How we operate.
We read every email ourselves. Every public claim should carry a grade. If you find one that does not, write to us and we will correct it. Whatever you've heard about how startups operate, that isn't how this one operates.
We apply the same posture to our own development. How we build describes the internal infrastructure, the verification gates it has to pass, and where the line sits between it and regulated device software.
We're not trying to look like anything other than what we are, a small technical team building the institutional memory a board can staple, with the discipline of people who would rather be right than impressive.
Graded, not asserted.
The parts of our work that carry a public grade are below. Click through to confirm any of them yourself. Not every output is PROVABLE.