FRAME v1.0 · batch #1
FRAME / Batch #1 · May 28, 2026
PROBLEMATIC
5/24

YouBase White Paper

YouBase/white-paper

2014-era founding document in patient data sovereignty tradition — individual ownership, third-party subscription model, BIP32/IPFS architecture. Draft 1, appears dormant. Historical ancestor of current FOUNDATIONAL projects.

CreatorJosh Robinson / Leonard Kish / Nate DiNiro (unclenate)
LicenseUnknown — no LICENSE file in repo
Stars★ 6
FHIRNo
Write opsNo
Stack White paper only — BIP32, IPFS, distributed hash table described
historicalwhite-paperdata-sovereigntyBIP32IPFSBitcoindormantpre-FHIRindividual-control
§ 01 / FRAME dimension scores eight axes · zero to three
PAI
2/3
Patient Agency
AI
1/3
Architecture Integrity
TM
0/3
Technical Maturity
SDP
0/3
Safety & Disclaimer
IS
0/3
Interoperability Stack
CA
1/3
CLAIM Alignment
SM
0/3
Sustainability Model
SH
1/3
Scope Honesty
§ 02 / Recommendation analyst-facing
ARCHIVE + CREDIT

Historical context for patient data sovereignty intellectual genealogy. Not a current patient tool. The person (Nate DiNiro) may be worth engaging if active in patient AI space.

§ 03 / Installation no runnable artifact

Not a runnable repository (spec, white paper, or design artifact). A 2014 white paper, not software. The repository contains a draft document describing a BIP32-and-IPFS-based architecture for individual health data sovereignty. There is nothing to install — read it as an intellectual ancestor of today's patient-controlled AI substrate projects (OpenKP, OwnChart, Tula).

§ 04 / Full audit narrative + CLAIM

FRAME Audit: YouBase White Paper

URL: https://github.com/YouBase/white-paper
Entry point: https://github.com/unclenate (Nate DiNiro / BDITS LLC / YouBase)
Date: 2026-05-28
Analyst: FRAME v1.0 / Synambix
Note: The URL submitted was a GitHub profile (unclenate), not a specific repo. The most relevant health data project pinned on that profile is YouBase/white-paper. This audit covers that repo. See “Scope Note” at bottom.
Documents reviewed: README.md (white paper body), repo file listing


One-Line Verdict

PROBLEMATIC | Score: 5/24 | A historically significant pre-patient-AI concept paper from circa 2014-2016 — not an active project. Scores in the bottom tier due to no implementation, no safety posture, and apparent dormancy. The ideas were ahead of their time; the artifact is now a historical document.


Dimension Scores

DimensionScoreEvidence
Patient Agency Index2/3Strong concept: individual as primary controller, third parties subscribe to user-owned data rather than storing it. Individual-centric security structure. Correct direction. No implementation to verify.
Architecture Integrity1/3Technical design described: BIP32 HD wallets, IPFS distributed storage, hierarchical permission trees. Architecturally coherent for its era. “Draft 1” — white paper only.
Technical Maturity0/3White paper only. Repo contains CSS (document styling) and markdown. No application code. 6 stars, 3 forks, appears dormant. Last commit history not datestamped in visible metadata but the BIP32/IPFS framing is circa 2014-2016.
Safety & Disclaimer Posture0/3No safety disclaimers of any kind. No “not a medical device” framing. No HITL design. No emergency guidance. Health data is mentioned as a use case but no safety posture exists.
Interoperability Stack0/3No health interoperability standards mentioned. Architecture is Bitcoin/IPFS based. No FHIR, HL7, CCDA, or any EHR integration path.
CLAIM Alignment1/3Individual control and selective sharing are proto-patient-agency ideas that predate the CLAIM framing. “Individual as primary controller” and “third parties subscribe to data owned by individual” are structurally aligned. No AI literacy framing. No interrogative stance. No evidence contract.
Sustainability Model0/3No active development visible. No license file found in repo. No contributing guide. No community channel. CSS-only repo contents suggest documentation project, not implementation project.
Scope Honesty1/3”Draft 1” label is honest. Abstract framing does not make specific implementation claims. Does not state what it is NOT. The “whitepaper” framing sets expectations correctly.
TOTAL5/24

Important Tier Classification Note

The PROBLEMATIC tier in FRAME is defined as: “agency-washing, misleading claims, structural contradictions, or safety failures.” YouBase/white-paper does not meet this definition. It is not an active project making false claims — it is a historical concept paper that scores technically in the bottom tier because it has no implementation, no safety posture, and appears dormant.

The FRAME rubric scores what is present in a repo as it exists today, not what the authors intended in the year of writing. A white paper from the pre-FHIR, pre-patient-AI-literacy era that laid out individual data sovereignty principles deserves contextual interpretation alongside the technical score.

Better label for this case: HISTORICAL. This repo is evidence of the intellectual genealogy of patient data sovereignty, not a current implementation to evaluate for patient use.


Key Strengths

  • The individual data sovereignty argument (2014-era) prefigures everything that followed. The YouBase framing — “third parties subscribe to data owned by the individual” rather than storing copies — is the correct architecture that patient-AI tools like OwnChart and Tula are now building. YouBase described the destination before the infrastructure existed to build it.
  • Hierarchical permission structure is technically coherent. BIP32 key trees for access control is a real cryptographic design pattern. The architecture described in the whitepaper, if built today with modern tooling, would be a credible privacy-first approach.
  • The IPFS + distributed storage angle pre-dates decentralized health data conversations by years. The convergence of cryptographic identity, distributed storage, and health data that YouBase described in Draft 1 is now the leading edge of patient data sovereignty discussions.

Key Gaps

  • Draft 1, still Draft 1. A decade later, the white paper has not evolved into implementation. The core ideas remained at the concept stage. Whether this is a resource problem, a market timing problem, or a scope problem is not visible from the repo.
  • Bitcoin as the identity layer did not age well for healthcare. The BIP32/Bitcoin framing is technically coherent but the Bitcoin ecosystem moved toward speculation, not health data infrastructure. The underlying cryptographic principles remain valid; the specific implementation stack became stranded.
  • No health standards integration path. The whitepaper does not address HL7, FHIR, or any existing health data format. Without a standards integration path, the architecture would have required every healthcare institution to adopt a new data exchange protocol.
  • The YouBase/Cortex product appears to have continued development off GitHub — unclenate’s bio references @YouBase/Cortex as an active project. This analysis covers only the public white-paper repo; there may be active implementation work not visible here.

CLAIM Assessment

Historical framing only. The CLAIM framework did not exist when this white paper was written, and applying it in full would be anachronistic. The relevant observation is:

The YouBase whitepaper is part of the intellectual genealogy that CLAIM draws on — the movement from “institutions own your health data” to “individuals own their own data” to “individuals can reason with AI about their own data.” YouBase represents generation 2 (individual data ownership) in that progression. The repos in this batch scoring FOUNDATIONAL represent generation 3 (individual reasoning capacity with AI on owned data).


Patient Agency Verdict

YouBase/white-paper is a founding document in the patient data sovereignty tradition. Its core argument — that individuals should be the primary controllers of their own data and that third parties should subscribe to user-owned data rather than storing it — is the structural premise that every FOUNDATIONAL project in this batch is building on, whether or not they cite it.

As a current patient AI tool, it does not serve patients today. As a historical artifact, it is worth preserving and crediting.


Scope Note

The URL submitted was https://github.com/unclenate (a profile, not a repo). This audit covers YouBase/white-paper as the health-relevant repo pinned on that profile. If there are active health repos associated with Nate DiNiro / BDITS / YouBase/Cortex that are not public on GitHub, they are not included here. A search of unclenate’s 58 repos for active health projects would require a separate pass.


Evidence Flags

  • No license file visible in repo. The repo contains CSS and markdown but no LICENSE file is listed in the file tree. This creates ambiguity about reuse rights.
  • YouBase/Cortex referenced in profile bio as active project — implementation may exist beyond this white paper. Not visible for analysis.

Recommendation

ARCHIVE + CREDIT. Worth documenting as historical context in the PatientsUseAI Radar — the intellectual ancestry of patient data sovereignty. Not a tool to recommend to patients. If Nate DiNiro is active in the patient AI space, the person (not this repo) is worth engaging.