The problem
Your life gets split across apps, organizations, files, accounts, workers, providers, and devices. When one changes, you can lose context, repeat yourself, miss a handoff, or struggle to prove what happened.
A PLAIN-ENGLISH GUIDE
What is
The Human Code?
The Human Code is a way to help people carry the important parts of their story, permissions, progress, proof, and relationships with them when technology, organizations, professionals, or AI systems change.
The simplest idea is this: technology should remember the human, not just the data.
THE 60-SECOND VERSION
Most systems remember their records. Human Code is designed to remember the human thread.
A person can move through courts, healthcare, housing, work, family services, schools, benefits, and AI systems. Each system sees only a piece. The person is usually forced to connect the pieces by memory.
The Human Code idea
Keep a continuous, permission-aware record around the person so different systems can remain different without forcing the person to start from zero again.
The system can change.
The human story should not have to reset.
WHAT SITS AT THE CENTER
A human life, not an app account.
The architecture has become clearer over time: apps and AI are services around continuity. They are not supposed to own the person’s identity, history, permissions, or meaning.
HumanThe person remains the principal.
Identity + relationshipsWho this is, who is connected, and what role each relationship actually has.
Memory + eventsWhat happened, when it happened, what changed, and what should remain retrievable.
Authority + consentWho is allowed to see, use, share, or act on what information and for what purpose.
Evidence + provenanceWhere important information came from, what is verified, what is only asserted, and what remains unknown.
ContinuityThe ability to leave one system, return later, or move somewhere else without erasing the useful thread.
Understanding + legacyTurning preserved history into something a person, family, professional, or future system can actually understand and use.
WHAT HAS ACTUALLY BEEN BUILT
One architecture, several ways to experience it.
The recent audits made one thing clearer: this is not 100 separate products. It is a growing continuity architecture expressed through products, domain tools, reference components, previews, and specifications.
Droski
The human-facing companion and interpretation layer. Droski is meant to help explain what matters, what changed, what is missing, and what the person may want to review next.
See the platform →Continuity Wallet
A human-controlled continuity surface for portable records, permissions, receipts, evidence, exports, and recovery across changing systems.
Explore the Wallet →CourtChain
The legal continuity engine: one matter over time, source-grounded records, evidence, legal dates, preparation, and a safer separation between what someone said, what a document shows, and what a court actually found.
See CourtChain →Housing, work, care, and family support
Human Code has been explored through housing continuity, workforce continuity, recovery/care coordination, family-service routing, and other handoff-heavy environments.
Explore solution patterns →Provider-neutral intelligence
AI is treated as a capability that can be selected under policy. The long-term goal is to change models or providers without losing identity, authority state, provenance, or human-owned continuity.
See how AI is governed →Receipts, projections, and sovereign exports
The architecture is moving toward traceable events, minimum-necessary projections, verifiable action receipts, and portable continuity packages so Human Code itself does not become another lock-in trap.
See export concepts →Important status boundarySome Human Code surfaces are working software, some are tested previews, some are specifications, and some are future architecture. This page does not treat those stages as interchangeable.
HOW IT WORKS
Preserve first. Decide authority. Use the smallest necessary context. Then let AI help.
The recent architecture work made this much more concrete. The AI is not supposed to decide what information is true, who owns it, or what actions it is allowed to take.
Something happens→Preserve source + event→Resolve authority + consent→Compile minimum context→Select capability→Execute→Verify→Receipt
The source stays separate from the interpretation.
An AI summary can change. The original evidence, document, event, or authoritative source should remain traceable.
Availability is not authority.
A tool, model, connector, family relationship, or agent being available does not mean it is automatically allowed to access or act on information.
Execution is not automatic memory.
Doing something does not mean the result should be permanently retained. Retention remains a separate governed decision.
HOW IT WAS BUILT
Real problems first. Reusable architecture second.
The project did not begin as a giant software blueprint. It grew by repeatedly finding the same failure pattern in different parts of life: context gets lost, people repeat themselves, handoffs break, and systems cannot explain what happened.
1. Start with human friction
Look at the actual journey: court confusion, care transitions, housing paperwork, work continuity, family-service handoffs, AI memory loss, or another place where a person is paying a “restart tax.”
2. Separate the reusable pattern
Ask what should persist across that change: identity, relationships, permissions, evidence, progress, source truth, next actions, or recovery state.
3. Turn it into governed machinery
Build shared contracts for authority, events, context, AI routing, evidence, receipts, revocation, portability, and safe external actions instead of hard-coding a one-off solution.
4. Prove it in domains
Use CourtChain, Continuity Wallet, housing, care, work, family services, and other bounded experiences to test whether the same continuity principles remain useful under different rules.
WHAT THE RECENT AUDITS CHANGED
The mission stayed the same. The explanation became more precise.
The early explanation was basically right. The recent work did not replace it; it clarified what Human Code actually is and what it must never pretend to be.
From “memory” to continuity infrastructure
The system is not just about remembering things. It now explicitly joins identity, relationships, authority, consent, evidence, events, provenance, recovery, and portability.
From “an AI” to governed intelligence
Droski is the companion surface. Underneath it, the architecture is designed so intelligence providers can change while the human-controlled continuity layer remains stable.
From big context to minimum necessary context
The Context Compiler direction makes the system retrieve and assemble only what a task needs rather than throwing an entire life history into every model call.
From hidden automation to visible receipts
Consequential actions are supposed to cross an authority boundary, execute under policy, and leave evidence that can be checked later.
From generic legal AI to legal continuity
CourtChain is being shaped around one continuous legal matter, distinct legal timestamps, “Since Last Time,” source-grounded context, and explicit uncertainty instead of generic document generation.
From “everything is built” to proof over hype
The current operating discipline separates implemented, tested, proposed, protected, deployed, and verified states. That makes the project more credible, not less ambitious.
WHY THIS MATTERS
If it works, people could change systems without losing themselves between them.
The long-term implication is bigger than one app. Human Code could become a continuity layer that many applications and institutions can use without forcing all of them into one database or one AI company.
Less repetition
People spend less time re-entering facts and rebuilding context that another authorized part of the journey already knows.
Fewer broken handoffs
Important next steps, ownership, missing items, and progress can survive staff turnover, software changes, and organizational boundaries.
More trustworthy AI
AI answers can be bounded by source, authority, purpose, time, and explicit uncertainty instead of treating fluent language as truth.
Real portability
The human should eventually be able to export continuity and move it elsewhere instead of becoming trapped by the system designed to help them.
WHAT IT IS NOT
Big ambition does not require pretending.
The recent audits have made these boundaries increasingly important.
VERIFY THE WORK
Go from the explanation to the evidence.
The public site separates the story from the implementation record. You can inspect product surfaces, case studies, maturity labels, architecture, and the broader Atlas.
SimpleHuman-first explanation
AppliedProducts and workflows
TechnicalArchitecture and safeguards
HonestStatus and maturity boundaries
THE SHORTEST VERSION
Teach technology not to forget the human.
The Human Code is continuity infrastructure designed so identity, relationships, permissions, context, evidence, progress, and important history can survive changes in software, institutions, professionals, devices, and AI.
This public explainer describes the current project direction. It does not claim that every described capability is production-deployed.