Open Standard · v1.2

Your identity.
Your terms.

MyCarryon is an open standard for a portable, owner-controlled identity and preference container. Carry what you need. Leave the rest behind.

Read the spec GitHub →
Scroll to explore
Not a passport
Passports are issued by authorities. Your carryon is packed by you.
Not a wallet
Wallets hold payments. Your carryon holds identity, preferences, and context.
Not a profile
Profiles are owned by platforms. Your carryon belongs to you — always.
What it is

Everything you need. Nothing you don't.

A carryon is a portable JSON container that holds the minimum context needed to interact with any compliant system — on your terms, not the system's.

Your AI companion packs it. You carry it. You decide who sees it. When you're done, you take it home.

Raw data stays at the system. Summaries come back to you.

  • ✕ Issued by an authority you don't control
  • ✕ Owned by a platform or vendor
  • ✕ Locked to a single domain (payments, travel, health)
  • ✕ Static and unchangeable
  • ✕ Shared without your consent
  • ✓ Packed and managed by you or your AI companion
  • ✓ Works across any compliant system
  • ✓ Minimal by design — carries what's needed
  • ✓ Extensible — you decide what goes in it
  • ✓ Encryption-ready for sensitive sections
How it works

Four steps. Any system. Every time.

01
Pack
Your AI companion packs the carryon with your uuid, preferences, and allowed API paths.
02
Present
You present the carryon to a compliant system. It reads what it needs — nothing more.
03
Transact
The system uses your uuid to authenticate and assigns its own internal id for the session.
04
Sync home
A summary returns to your carryon. Raw data stays at the system. Your companion ingests the summary.
Use cases

One carryon. Every domain.

🚊
Transit
Ride any JPods network in any city. Your uuid travels with you. Fare summaries sync home.
🏨
Travel & hospitality
Check into hotels with your room preferences already known. No forms, no repetition.
🏥
Healthcare
Carry allergies and emergency contacts to any provider. Visit summaries come home to you.
🛒
Commerce
Shop anywhere with payment preferences and shipping details ready. Order summaries sync back.
🎓
Education
Carry credentials and learning preferences. Completion records return to your knowledge base.
⚙️
Any system
If it can read a JSON file and honor the standard, it can work with your carryon.
The schema

Simple. Extensible. Yours.

The carryon is a JSON file. Here's what it contains — and what each section means.

  • identityTwo UUIDs: uuid_permanent (never shared, stable for life) and uuid_session (shown to external systems, rotates every 90 days or on demand).
  • contactPhones, emails, vcard, emergency contacts, and authorizations for people and systems.
  • medicalBlood type, allergies, medications, conditions, providers, insurance. High sensitivity.
  • credentialsAuth tokens. Plaintext now, AES-256 encrypted in v2.
  • preferencesLanguage, currency, timezone, payment method, notifications.
  • apisAllowed systems and blocked systems. You control the list.
  • actionsTasks and next steps. Connects to external calendars (Google, Apple, Outlook, CalDAV).
  • logTemporary session log. Auto-clears after sync to home companion.
  • notificationsAlerts, warnings, and messages queued for the owner. Prioritized and expirable.
  • dashboardsStored views — flagged offline (computes from carryon) or online (requires home db).
  • pendingEvents not yet synced home. dt_processed=0 until integrated. Same pattern as WebClerk pending.
  • recentLast 50 interactions. Enough to repeat a trip or reorder quickly.
  • settingsAllie rules, privacy settings, display preferences, and custom companion config.
  • syncHome companion endpoint. Summaries and pending items route here automatically.
  • customYours to define. Add anything meaningful to you.
// carryon.json v1.1
{
  "carryon_version": "1.2",
  "identity": {
    "uuid_permanent": "550e8400-...", /* never shared */
    "uuid_session": "a3f9c211-...", /* rotates 90d */
    "uuid_session_rotation": { "interval_days": 90 }
  },
  "contact": {
    "vcard": { /* fn, tel, email, adr */ },
    "emergency": [],
    "authorizations": {
      "people": [], "systems": []
    }
  },
  "medical": {
    "_sensitivity": "high",
    "allergies": [], "medications": []
  },
  "actions": {
    "items": [], "calendars": []
  },
  "notifications": { "items": [] },
  "dashboards": {
    "items": [
      { "mode": "offline" },
      { "mode": "online" }
    ]
  },
  "pending": { "items": [], "dt_processed": 0 },
  "log": { "_retention": "sync_then_clear" },
  "settings": { "allie": {}, "privacy": {} },
  "sync": { "home_allie_url": null },
  "custom": {}
}
Design principles

Built on eight commitments.

01
Owner-packed
Only you or your companion packs the carryon. No authority assigns it. No platform owns it.
02
Minimal footprint
Carry summaries, not raw data. The carryon grows with your interactions, not with surveillance.
03
Universal structure
Any compliant system can read a carryon. The standard is open and vendor-neutral.
04
Voluntary presentation
You decide when to present your carryon and to whom. Blocked systems are refused.
05
Async sync
Detailed data stays at the system. Summaries flow back to your companion on reconnect.
06
Encryption-ready
The credentials section is designed for AES-256 encryption. Plaintext now, secured in v2.
07
Human in the loop
Your AI companion manages the carryon. You make the decisions about what it contains.
08
Non-destructive
Interactions are summarized and archived. Nothing is silently deleted from your carryon.
Origin story

"We needed a way for a person to ride transit in any city — recognized, served, and private."

MyCarryon was conceived for JPods, a solar-powered personal rapid transit network designed to operate Bottom-Up — like WiFi — where each city manages its own database independently. A rider shouldn't have to create an account in every city they visit. Their uuid travels with them. The local system handles the rest. Summaries come home.

The same pattern applies everywhere a person moves between independent systems. Transit. Hotels. Healthcare. Commerce. The carryon is the universal solution.

JPods · WebClerk · Bottom-Up Networks
Personal sovereignty standard

A written constitution
for your digital identity.

The carryon is not just a convenience. It is an instrument of individual sovereignty — a written document that constrains what institutions may do with your identity, your data, and your presence in the world.

"What has destroyed liberty and the rights of man in every government which has ever existed under the sun? The generalizing and concentrating all cares and powers into one body."

— Thomas Jefferson, Letter to Joseph C. Cabell, 1816

Platform monopolies violate usufruct (to use for profit without harm) — the ethical principle that any use of a shared resource must be returned in like or better condition for those who follow. They consume your identity, your attention, and your relationships without return. The carryon enforces usufruct at the individual level: you use systems on your terms, they return summaries, your identity comes home intact.

The same consolidation of power that created oil addiction, Federal debt, and oil wars — documented at DividedSovereignty.com — is now happening to your digital identity. The remedy is the same: Divided Sovereignty, usufruct capitalism, and the individual as sovereign.

Physical mobility
JPods
Bottom-Up, solar-powered, locally governed transit. You own your mobility. jpods.com →
Commerce
WebClerk
Bottom-Up commerce infrastructure. Each network locally governed. You own your transactions. webclerk.com →
Digital identity
MyCarryon
The carryon is your written constitution for your digital presence. Enumerated permissions. Right of refusal. Identity that comes home.
Constitutional framework
Divided Sovereignty
The sovereign is the individual. Governments and platforms are agents with enumerated permissions — not owners. dividedsovereignty.com →
Infrastructure rights
postRoads
State sovereignty over internal improvements. No Federal monopoly on transportation or digital infrastructure. postroads.com →
Democratic corrective
Jury with 4-part verdict
When regulators are captured, citizens must have standing to sue for usufruct violations (to use for profit without harm). Juries assess harm Bottom-Up. reportof2026.com →
Digital Sovereignty essay → DividedSovereignty.com → postRoads.com → JPods.com → Report of 2026 →

Ready to implement?

Read the full spec, explore the JSON schema, and build a compliant system. The standard is open. The ecosystem is growing.

View spec on GitHub AI companion guide →