Nakama Health
Discuss Your Cohort

Open protocol · Robinhood Chain

Public proof.Private health data.Human decisions.

Nakama is being built and tested for Robinhood Chain. Until the audit, source, and deployment receipts reconcile, this page stays visibly pre-deployment.

Review the evidenceInspect source
01

System boundary

What is public. What stays private. Who decides.

Public program facts, private health information, and human decisions belong in different layers.

01

Public program layer

Pre-deployment — no published Nakama Robinhood deployment

Approved program identifiers, terms commitments, aggregate funding, obligations, settlement, and release state may be published only from the canonical status artifact.

Program identifiers, permissioned display names, approved terms commitments, aggregate funding, obligations, settlement, role classes, ACP agent and offering identifiers, published offering terms, verified aggregate ACP activity or an explicit evidence blocker, and release state only.
02

Stays private

Required by design

Contact details, eligibility evidence, health records, reviewer notes, model inputs, and support conversations stay outside the public status layer.

Private evidence is access-controlled and disclosed only to the authorized people who need it for the support process.
03

People stay responsible

Named authority

The Nakama Operator can organize information and watch deadlines, but named people set program terms, decide requests, authorize support, and review appeals.

A token, model, or public status artifact cannot decide a support request or expose private member evidence.
02

Publication standards

No proof, no live claim.

Missing approval, audit, deployment, or source evidence keeps the public status pending.

01

Public evidence

No address, program, funding state, or live claim appears until the canonical artifact contains the required approval and deployment receipts.

02

Open source

Protocol source, release inputs, schema, generated status, and reproducible checks remain inspectable together.

03

Privacy

The public layer contains bounded program evidence. Member identity, health information, reviewer notes, and support conversations remain excluded.

04

Security

Publication fails closed when approval, audit, freshness, finality, reconciliation, or source-integrity evidence is absent or inconsistent.

Inspect the protocol source
03

Decision authority

Software prepares. People decide.

Every role has a clear job and a clear limit.

RoleMayNever

Member

May

Provides information privately, receives the written terms and decision, and may use the stated appeal path

Never

A member is not required to publish health information or use the unpublished token route.

Sponsor or program controller

May

Sets the approved program budget and written terms, and may control new intake within those terms

Never

The controller cannot rewrite a completed decision, expose member evidence, or represent an unpublished program as live.

Initial reviewer

May

Considers a prepared request against the written program terms and explains the decision

Never

The reviewer cannot change the terms, control the program budget, or decide an appeal of their own decision.

Appeal reviewer

May

Reviews a challenged decision independently under the published appeal process

Never

The appeal reviewer receives only the evidence authorized for that review and cannot alter public status evidence.

Nakama Operator

May

Organizes documents, checks what is missing, watches deadlines, and prepares the work for authorized people

Never

The Operator does not decide requests, authorize support, control program money, or enable the token route.

04

The walkaway test

Leaving should not erase the trail.

The status, release inputs, private records, and human escalation path must remain usable beyond Nakama’s interface.

  1. 01

    Read the canonical status directly

    Available

    The generated JSON artifact and schema expose the same publication state used by the website build.

  2. 02

    Verify the release inputs

    Release requirement

    Source revision, manifest digest, deployment evidence, and publication packet must reconcile before live status appears.

  3. 03

    Keep private records portable

    Product requirement

    Nakama must provide a usable private-record export before describing the evidence layer as portable.

  4. 04

    Keep human escalation available

    Program requirement

    A named person decides each request and a different authorized person reviews an appeal.

05

Source and build evidence

The release record, as it stands.

Available fields are shown. Missing evidence remains pending, and the token route remains disabled until its publication gate passes.

Pre-deployment

Nakama Health is independent. No infrastructure provider, launch platform, or public status artifact decides member support or certifies Nakama's health work.

pendingProtocol contract
Not published
pendingDeployment transaction
Not published
pendingDeployment receipt
Not published
availableSource revision
0cb347f1ac0d790b1fc7053a6c0fcb2e0a53dd75
pendingCompiler settings
Not published
pendingVerified bytecode
Not published
pendingReserve asset
Not approved or published
pendingIndependent audit
Independent audit not published
pendingEmergency authority
No deployment authority statement is published until the canonical release packet names its roles and limits.
pendingSigned release manifest
Not published
disabledProtocol token integration
Not published — the external $NAKAMA market token is not connected to this protocol
availablePublic sponsor-funded programs
No public program exists in the canonical status artifact.