Codetry: Carry the context. Keep the person.

A founding paper on freedom, meaning and person-centred cooperation

Bobbie

17. Oktober 2026October 17, 2026 · 75 Min. Lesezeit75 min read

Codetry: Carry the context. Keep the person.

A founding paper on freedom, meaning and person-centred cooperation.#

By Bobbie Parr

This paper begins with a human practice developed through years of working alongside people and communities. It explains the ideas built from that work, the tools that may help carry them between people, and what remains to be tested. Scope and review notes (see “Edition, implementation and enforcement scope” below).

It is written for cypherpunks, homeschooling families, community care organisations and others asking how people can cooperate without surrendering their own account of a life. Care provides the lived roots and a concrete worked example; it does not set the limit of the architecture.

The wider questions belong here too: how families pass on knowledge, how communities sustain useful work, how records and representations may travel, and how tools remain replaceable. Short application guides can explain a particular task without asking everyone to read the whole founding paper.

Carry the context. Keep the person.

Start here: five foundations#

Before the app, the ledger or the business, there is something worth protecting.

Headwaters begins with five foundations. They describe what the tools should serve, not a vocabulary that a family or worker must learn before taking part.

Sound Money Without an Issuer#

People need ways to hold and exchange value without depending on one issuer's continuing permission. For a household, that means chosen payment routes, reserves and voluntary exchange, with alternatives when a provider fails.

The Keepers#

Every household depends on people who keep returning: feeding, noticing, remembering, advocating and holding things together. Recognising that work means sharing its burden and helping necessary context travel between supporters, rather than assuming one dependable person can carry it all.

Rock Bottom as Threshold#

Begin with the real situation, resources and capacity available now. A difficult starting point can be a place to turn. The next step might be an accessible tool, a workable budget or a small piece of practical help. Nobody should have to perform success before receiving support.

Mother Nature as Holder#

Work takes place within living cycles: limits, rest, renewal, seasons and interdependence. Land use, enterprises and everyday rhythms should replenish what sustains them, leaving room for recovery and further life.

The Land#

Food, shelter, water and place remain when the software stops. A home, local production, practical skills and durable gathering places give care and memory physical anchors. The tools should serve that life, not replace it with a record.

A record helps us act on something real without becoming the thing itself. A land record is not the land. A care summary is not the person. A receipt for an exchange is not the value of everything exchanged.

The land is not the token. The person is not the profile. The relationship is not the score.

This gives the rest of the architecture its order:

Protect the foundations → name what matters → choose the crossing → do useful work → return value and learning → replenish the capacity to continue.

Context: foundations and practical limits (see “The primitives: interpretation and practical limits” below).

In one minute#

A person should not have to become a different person every time a different system starts supporting them.

Yet context can be lost at each handoff. A family account becomes an intake category. A preference becomes a compliance target. An interpretation, separated from its source, becomes the next worker's working fact. A platform's profile begins to stand in for the individual.

Person-centred care planning already names a different aim: support organised around the person's life, choices and goals. This work builds on that commitment. It is not an argument that care workers need to be persuaded to care. Staff can be as frustrated as families when forms, staffing pressures, reporting requirements and top-down procedures make a good plan difficult to put into practice.

The question is how to carry that commitment into the next ordinary decision: what matters to this person today, what does the next supporter need to know, and what would help them act on it? Codetry proposes a practical way to carry person-centred planning through daily work, rather than another standard for people to endorse.

For fifteen years, I have used human transmission protocols in person: trying to hear what someone was communicating, understand the situation around it and help carry that meaning into the next interaction. My background in recreation management and community development shaped how I work with people in groups and support systems.

I have worked along lines where people's crossings were refused or carried under someone else's account. Writing and research helped me ask how the next moment could be brighter than the last. I learned to listen for a signal that might otherwise go unheard—to hear what it sounds like when nobody else is in the room.

I built this work through writing, poetry, ideas and research. Over time, a practical method became a broader framework: how can people share enough context to help one another, without giving a worker, institution or machine the right to redefine the person?

Codetry is my name for that craft of naming what matters, agreeing what may cross a boundary, and preserving the ability to question, correct or refuse what happens next. The source account remains distinguishable from a summary or a machine's suggestion.

Codetry standardises the responsibilities of a handoff, not the meaning of a person. People can agree on a task, exchange useful knowledge and act together without agreeing on a complete account of one another. The purpose is not only to prevent misuse. It is to make chosen cooperation easier: learning together, sharing care, earning a living and carrying knowledge forward without making one person, institution or platform indispensable.

I bring advanced mathematical ideas and systems thinking into conversation with lived experience. They help me ask about uncertainty, connectedness, change and the limits of one viewpoint. The source material linked with each idea shows how those questions appear in the research and doctrine.

This matters in care because a useful handoff should reduce the burden of repeating and correcting an account, not turn a fragment of someone's life into a permanent definition of them. It matters elsewhere for the same reason: shared information should help people coordinate without becoming authority over the people it describes.

The approach can begin with a person, a chosen supporter and a piece of paper. Software, artificial intelligence and spatial or holographic displays are possible carriers, not extra authorities. Methodology first design will name it in place, before the cascade. The tool should remain replaceable; the person's choices and meaning should not depend on the tool's owner.

For the cypherpunk souls concerned with privacy, open systems and individual freedom—the practical proposition is:

Verify the crossing without claiming ownership of the person who crosses.

For a family#

You should not have to tell your whole story to every new worker. Nor should an old note decide who you are forever. Share what helps, say who may use it and why, keep the right to correct it, and take a usable account with you when support changes.

For a homeschooling family#

A learning record should help a child find the next useful step, not become a verdict on who they are. Interests change; someone may teach one skill while needing help with another. Share what a tutor or learning group needs, keep the child's own expressions visible beside adult observations, and let the account develop as the child grows. Parents and other responsible adults retain their actual responsibilities; those responsibilities should help make the child's participation possible, not make their perspective disappear.

For a care team#

You may already know what good support should look like and find the existing process gets in the way. Start with a real task, the person's current wishes and the knowledge your team already holds. Make the next action clear, keep room for professional observation and questions, and return corrections to the plan without making staff or families maintain a second system.

For a builder#

Preserve the source separately from its interpretations. Bind each disclosure and action to a specific authority and current purpose. Make refusal, correction, expiry and recovery inspectable. Do not confuse a valid signature with a valid instruction.

Why this matters beyond care#

Care makes the stakes visible, but the problem travels: a child becomes a school category; a worker becomes a performance score; a customer becomes a risk profile; a family's history becomes training material. Useful records become dangerous when the holder's model gains authority over the person it describes. When there is no longer another human on the other end, we will be type casted into reality from a central database without recourse. That is not the future I am leaving for my children.

The alternative is not to abandon shared facts, expertise or coordination. It is to agree on what a particular task requires without giving one organisation, model or ledger final authority over a life.

Freedom includes the ability to be understood without being reduced, to cooperate without being absorbed, and to change without asking a database for permission.

Choose a reading path#

1. The commitments come before the technology#

The person directs their own account and participation. Other people retain authority over their own accounts; being in the same setting does not merge everyone's choices into one permission.

The following commitments guide the design:

  1. Receiving information does not confer authority over its subject. A funder, institution, keeper, model or device receives only the role actually established for it.
  2. Source meaning survives translation. The person's words, expression or honest source reference remains beside the receiver's interpretation. Omissions and uncertainty are visible.
  3. Participation is bounded. Purpose, recipient, scope, duration and permitted actions are named rather than inherited by implication.
  4. Refusal is not a defect. People can decline optional disclosure, contest an interpretation, choose a quieter format and seek support without being assigned an adverse character label.
  5. Exit must be usable. Changing a provider, device or network must not require surrendering identity, buying back one's own record or losing essential support merely for declining optional technology.
  6. Privacy includes relationships and metadata. Protecting content while exposing a person's care network, movements or recurring needs is not a complete privacy design.
  7. The method must become transferable beyond its founder. The author's experience can guide its development without becoming a permanent condition of use. A new worker should be able to use the agreed record; a community should be able to practise without a central interpreter.
  8. No shared worldview is required. Mathematical, spiritual, cultural and scientific frames may inform local practice. None becomes the universal judge of what another person's experience means.

A lawful exception requires its own narrow authority, rationale and record. It must not be disguised as the person's consent. Context (see “Professional authority, heirs and legal instruments” below).

2. Naming is the beginning, not the limit#

The first practical question is simple: who chose the words that describe this situation, and what do those words allow other people to do? The words “engagement,” “compliance” and “independence” can lead to very different actions. Codetry calls naming “load-bearing” because decisions often follow the label.

A person may want companionship rather than attendance, assistance rather than supervision, or a reliable supporter rather than the withdrawal of all help.

Codetry asks who named the objective, what the name permits and whether the people using it mean the same thing.

The practice uses several tests:

The working method is simple: agree what matters, set the limits, keep important differences visible, arrange useful help, check what happened and leave someone else able to continue.

3. Support that helps without taking over#

A physical exoskeleton can help someone move without becoming that person. The doctrine uses this image for support that helps carry context—such as a preference, request or agreed instruction—without replacing the person.

Some burdens are physical: effort, movement and practical assistance. Others come from holding an arrangement together: repeatedly explaining preferences, correcting instructions and making sure the next supporter knows what matters. Good support should reduce both, rather than give the person a second job managing the support itself.

Carrying an account between people creates five responsibilities:

Preserve the source. Keep original wording, gesture, drawing or an honest reference beside the summary.

Carry the context. Name why the account exists, where it applies and where it does not.

Keep authority clear. Distinguish the person, chosen keeper, worker, institution, model and hardware event.

Keep uncertainty visible. Separate observation, interpretation, prediction and unknown.

Make room for a return. Let the recipient accept, question, correct, decline or request a different scope.

Meaning is in the moment. Inner experience is dynamic; a record holds a fragment from a particular situation, not a whole person waiting to be captured. The radiology analogy in my work is useful: an image shows a particular view at a particular time, not the whole living subject. How the image was made and how someone interprets it are not the same thing.

For a meaning-bearing moment, preserve when and in what situation it was expressed, how it was recorded, what was selected or omitted, and who interprets it. A later fragment can differ without making the earlier one fraudulent or the person inconsistent. Neither fragment becomes a timeless definition of the person.

Preserving meaning therefore does not mean freezing a person's experience. It means keeping authorship and context attached to each fragment, showing where accounts differ, and letting the person correct how others use what was shared. Combining fragments may help someone understand a situation; it does not make a complete or final account of the person.

The support must be replaceable. Its success is not measured by how indispensable the provider becomes. Read the supporting strategy and paper handoff rehearsal.

A companion can refuse without defecting#

A person-facing AI companion may decline an unsafe or unauthorised action while remaining available for explanation, safer alternatives and contact with a person-chosen human. Refusal must not become punishment, emotional leverage, an invented reporting mandate or a reason to trap the person in the service.

The companion may prepare a proposal; it does not independently gain authority to diagnose, spend money, change custody or decide eligibility. Genuine legal obligations remain separately identified. This is a relationship boundary as well as a data boundary.

4. Hold multiple interpretations without manufacturing a universal profile#

The same person may be described differently by themselves, a group, a particular handoff and the person or model receiving it. Those views need not be collapsed into one master profile:

These can differ without the source being wrong. A service category can be useful for one decision without becoming an adequate description of a life. Read the meaning-sovereignty principles.

A handoff produces an account for a particular task, not a definitive profile of the person.

An institution may say, “For this task, this is the category we use.” It must not silently turn that into, “This is who you really are.”

Mappings remain beside source expressions. Unmatched material stays unchanged. Unresolved, embodied, private or contradictory material need not advance toward classification. Approved vocabulary substitutions must not cascade into a sequence of unapproved reinterpretations.

Preserve the full private source in its proper custody; disclose only the authorised excerpt or reference needed for that crossing. Security context (see “Cryptography, networks and recovery” below).

This is the practical value of holding more than one state: the system can choose a usable view for a task without erasing the other views or demanding final agreement about the person.

5. The Gate: a relationship with bounded authority#

The Gate is the check before information or authority crosses from one person, group or system to another. The shared protocol is deliberately small. It records where information came from, who holds it, why it is crossing, what is allowed, who decided, how the decision can be challenged and how to stop or leave.

It does not require a universal vocabulary, central biography store, global person identifier or compulsory Codetry account.

That does not mean starting every agreement from nothing. People can share a reliable format for origin, purpose, permission and response while keeping their own language and interpretations. An established agreement can cover repeated uses within its stated limits. Software can check those limits in the background; a new recipient, changed purpose, withdrawal or other material change needs the appropriate new decision. Agreement on how to cooperate is not agreement on who someone ultimately is.

For a consequential crossing, ask:

  1. Who originated the material, and what is actually known about that origin?
  2. Who is requesting which use, for which recipient and duration?
  3. Who has standing to authorise that use?
  4. Which source and policy versions apply now?
  5. What does the receiver receive, retain and have permission to do?
  6. How can the person and receiver question or correct the handoff?
  7. What happens after expiry, withdrawal, compromise or departure?

A digital signature can help show that particular data was signed by a particular key. It does not, by itself, prove who controlled the key, whether the person agreed, or what the data means. Those questions need separate answers. Security context (see “Cryptography, networks and recovery” below).

Possession, authentication, disclosure, interpretation, action authority and historical witnessing are separate decisions.

Tools may enforce established scope and flag missing conditions. They may suggest a translation. They do not gain the right to approve a new use or make a person's decision to refuse.

What a permission can actually do#

The boundary needs more than well-written terms:

Inside a connected service, software can check the recipient and current permission before releasing a view, and reject an expired or unauthorised request. These checks must be implemented and tested in the actual service.

In a receiving organisation, a named worker and an accountable organisation agree how the information will be used, corrected, retained and challenged. Their workflow must honour the limits; a document alone cannot make it happen.

After someone has read or copied it, a system cannot reliably make them forget or recall every copy. Share less, identify misuse, stop further access where possible and provide a practical route to correction and remedy.

For a trial, the receiving team needs to identify who handles a disputed note, how a correction reaches the next shift, and what happens if someone uses information outside the agreement. This is a workflow to agree with the team, not a demand that one family force an institution to change. Staff need the time, access, backup and managerial authority to follow it. If a local process blocks a correction, identify who can resolve that obstacle rather than leave the worker to work around it alone.

Sharing a smaller task-specific account does not automatically erase the underlying care record or override a legitimate retention duty. Keep the historical record where required, show corrections and dates, and distinguish what must be retained from what the next worker needs to see for this task. Where an agreed route cannot be honoured, use an appropriate alternative for necessary support and record what needs to change.

The professional layer belongs to the crossing#

Codetry preserves the person's instructions and makes applicable authority, consent and professional requirements explicit at each crossing.

A person's care decision, a worker's acceptance of a task, a clinical intervention and an institution's disclosure are different decisions. Each requires the authority appropriate to that person, action and setting. Approval at one boundary does not automatically travel through the next.

Responsibility belongs where the consequential decision is actually made. Professional-layer context (see “Professional authority, heirs and legal instruments” below).

6. A handoff is not finished when a packet arrives#

Something happens, someone expresses it, another person receives a message, they explain what they understood, and trust may grow from what each person can verify. None of those steps can be silently skipped.

An event is not its entire record. A record is not its summary. A received summary is not proof of understanding. Understanding one instruction is not general authority over the person.

A useful handoff therefore needs distinguishable evidence for:

A delivery acknowledgement is only evidence that something arrived. It is not consent, proof of understanding or proof that care went well. Completing one task does not justify attaching a general trust score to the person.

The recipient has responsibilities and boundaries too. They may lack the competence, capacity or lawful authority to accept the task. A clear refusal can be a better handoff result than false acceptance. A worker declining a task is not the supported person withdrawing consent; those decisions must have different authors and records.

Reliance remains purpose-specific and current. A historical receipt can establish what was acknowledged then without granting permission now. If a service cannot verify the permission needed to show or share a record, it pauses that operation. That pause must not become an excuse to abandon the person: a separately authorised, accessible human or paper route may remain available.

7. A care handoff, without a total biography#

The lived practice behind the example#

My one-to-one care work, recreation management and community development put these questions in front of me long before I tried to express them as software requirements. My work included supporting people who did not communicate through speech. Receiving their signals as best I could, in the moment, mattered before any record could be made.

In recreation and community participation, the practical question was how to make a next moment more accessible and meaningful for the person—not simply how to fit them into the activity already on offer. Hearing what someone was trying to express and carrying that understanding into the next interaction became the foundation of the method.

Dated care-planning material from 2014 and later recreation-programme evaluation records support that history of practice and reported participation and barrier-reduction benefits. Practice and outcome evidence (see “Practice evidence, outcome claims and demonstration limits” below).

Those are the roots in my work. The outing below is a fictional walkthrough that lets readers inspect the method without publishing a person's private care history.

Fictional example: an adult wants support attending a community activity.#

Their source account says:

“Tell me before plans change. Offer the quiet space. Ask before touching me. I can choose not to join.”

For the named visit, a receiving worker gets those instructions and the relevant contact and return arrangements—not unrelated family discussions, finances or a lifetime history.

The worker acknowledges the current instructions. During the visit the person chooses the quiet space. The return receipt records what happened and any question requiring clarification. It does not turn “chose not to join today” into a permanent label of non-compliance.

If the person changes the instruction, the next view must reflect the current authorised version. The earlier instruction remains historical evidence, not an entitlement to disregard the change.

This can begin on paper. A phone may make it easier. A spatial display may later make the same source and scope easier to see together. None of those changes grants new authority.

Fit it into the work people already do#

The starting point is the person-centred plan and the people trying to make it work. Ask the supported person, family and staff where the daily process loses something important: a preference buried in a long file, an effective approach known to only one worker, or a change that never reaches the next shift. Choose one of those problems together.

Start with one existing handoff—not a second biography or another daily platform. With permission, use the relevant part of an existing care plan or shift note. Keep its origin visible and let the person add, amend or question it in a form they can use.

For the outing above, the working record needs only:

The worker can explain back what they intend to do in ordinary conversation. Their existing handoff note can carry the response where the organisation's rules allow it. The supported person should not have to produce a polished document, master a new glossary or repeat a painful history to complete the process.

Worker observations are valuable, including when they differ from a previous account. Keep them attributed, with the situation and date, and make room for the person's response. Separating an observation from an interpretation helps the next worker use professional knowledge accurately; it does not ask them to ignore it.

Record the preparation, receiving and review time alongside any time saved. Ask both people whether the account helped. If it duplicates work without improving understanding or choice, simplify it, change the task or stop adding the extra process. More completed fields are not evidence of better care.

Let AI carry routine administration#

Making the limits explicit creates room to automate work within them. Instead of repeatedly searching a long file and rewriting a summary, an AI assistant can be configured to prepare the relevant view, point to its source, highlight a change, draft a form and organise the permitted response. Those are proposed uses of the architecture, not permission for the assistant to invent an instruction or silently send a private account to an outside model.

People should review the important instruction, change or uncertainty—not approve every formatting and filing operation. Consequential choices remain with the people who hold the relevant authority. An agreed routine need not become a fresh consent questionnaire at every step.

The intended result is less reconstruction between supporters and less dependence on the one worker who remembers everything. Staff gain usable time and attention for care, rather than another system to maintain. The integrated trial should count checking and correction time as well as time saved. Automation has helped only if the whole task becomes easier without making the person harder to hear.

Can another supporter use it without me?#

Before relying on the method in a new setting, a second supporter should try the same fictional task using only the operating guide and current handoff record. The author should not interpret it for them.

Ask them to explain the instruction, identify what they may not do, deal with a changed preference, and return an account the person can question. Record where they needed help and revise the guide accordingly. In an agreed live case, use familiar, appropriately authorised supporters and preserve the ordinary backup arrangements.

The test is not whether someone repeats my language. It is whether they can provide the agreed help, recognise their limits and let the person change direction. The fictional walkthrough and steward operating playbook provide starting material, not a completed independent replication.

My involvement while the method is being articulated is not the failure this test looks for. The question is whether another supporter can carry it forward without needing my continuing interpretation or permission.

8. Understanding another person's situation without claiming it#

Stories can help us imagine another person's situation without claiming to be them or to know everything they experience. The family stories behind this approach explore that distinction.

Its dramatic situations illuminate ordinary questions. What travels when a grandmother cannot be present? Who carries the invisible work of keeping a household oriented? What does a supporter need to understand before intervening? What remains unresolved even after a powerful encounter?

Its practical contribution is preserving context, relationships, familiar cues, authored records and the right to answer back.

The return matters as much as entry. A meaningful encounter should leave people able to resume their own lives, contest the account and decline another session.

The family's care and knowledge are not an inexhaustible resource for institutions to extract. Reducing repeated explanation while adding unpaid preparation, monitoring and receipt work would not be a successful intervention. Supporting a caregiver also does not make that caregiver the sole author of the supported person's life.

Interdependent units, not ranks of people#

Support can be organised around a person, a couple, a household or chosen team, and the friends and family they can call on beyond it.

These are possible relationships, not a compulsory sequence or a hierarchy of human worth. Someone need not belong to a couple or conventional family to participate. Every unit has limits. A functioning network lets another meet a particular gap without acquiring general authority over the people involved.

A skilled supporter may need respite. Someone who needs help communicating may teach another person a practical skill. A household may manage daily care well but need transport or technical assistance. Helping and receiving help are changing roles, not permanent categories.

The Gate applies between these units as well as between software systems. Agree who will help with what; preserve the person's expressions beside others' interpretations; let people question, refuse and revise. A wider support circle adds capacity, not ownership of the source.

Watching, learning, practising, teaching#

Contribution and learning need a practical structure: name a need, agree an offer, do the work, obtain appropriate witnessing and record the agreed compensation or recognition. Work, payment, skill recognition and governing authority are distinct. Read the Helping Hands model and schema.

The learning progression is Watching → Learning → Practising → Teaching. A person may teach one skill while learning another. Watching provides a doorway before commitment; teaching passes capability onward rather than giving the teacher general authority over someone else. Source and implementation context (see “Community sources, learning stages and implementation differences” below).

The existing story The Button She Almost Didn't Press shows interest becoming supported practice. “I'm watching this” precedes an invitation to learn; “My grandmother showed me … Hers showed her” places the encounter in a longer chain of transmission. The Fish Who Stopped Trying to Climb offers a complementary image: “The fish led in the water. The child followed on land.” Different settings reveal different capacities.

These stories make a practical invitation: you can belong before you are proficient, try with help, and eventually bring someone else along. Participation in a marketplace, wallet, badge system or research study is not a condition of essential support.

In a home-learning group, for example, a child might watch a gardener, try planting with help, practise over a season and later show someone else. The useful record is what they tried, what helped and what they want to do next. A quiet first visit need not become a label of disengagement. Their drawing or explanation can sit beside an adult's observation without the two being mistaken for the same account. This is an illustrative application of the learning method, not a reported pilot result.

Expertise creates a particular responsibility. It does not create general authority over another person's meaning.

Context: narrative and research (see “Physics, two-pass return, holography and consciousness” below).

9. What remains useful after the event?#

After an exciting event, new tool or successful meeting, what actually remains? In care, that means asking:

A slow reference is not sacred merely because it is old. Harmful inherited patterns, outdated preferences and institutional convenience must not become compulsory restoration targets.

The person may revise their aims. The arrangement serves that changing account; it does not decide what a healthy life must be. The underlying systems model explores how conditions, events, loss and renewal interact.

The second pass: return is more than a receipt#

An interaction can appear complete before anyone knows whether it helped. Return after ordinary life has had a chance to test the arrangement:

  1. Encounter: offer a minimal, authorised account. Let the person recognise, question, amend or refuse it.
  2. Interval: allow ordinary living. Do not coach the person toward reproducing the first response. Withdrawal takes effect without waiting for a second meeting.
  3. Return: ask again, with renewed agreement and enough variation to allow a fresh response. Notice what persists, what changes, what is rejected and what needs another account.

A familiar response is one observation. The ability to disagree, redirect or stop matters too. The second pass is not a loyalty test or a demand to remain the same.

In a care handoff, the practical question is: “After the new helper has used this plan, does it still fit—and can the person change it?” In a family archive: “Does the way we are using this story still honour its source and the people affected?”

Context: two-pass research and geometry (see “Physics, two-pass return, holography and consciousness” below).

10. Study the support conditions, not a person's worth#

Who gets useful help? Where does it repeatedly stop? Who is carrying too much? Studying relationships, bottlenecks and available capacity can make those questions easier to examine.

The ethical question precedes any coordination metric: what is propagating, who benefits, who bears the cost, and can those people decline?

Community analysis uses its own permission and privacy controls. Measurement and privacy context (see “Mathematics, measurement, visualisation and privacy” below).

For example, a map of agreed support relationships might reveal that every transport request depends on one exhausted household. The useful response is to arrange backup with the people affected—not lower their score or demand that they become more cooperative.

For any proposed measure, say what was observed, what the calculation assumes, what it leaves out and what decisions it may inform. A connection on a diagram does not establish that help was wanted or beneficial.

The mathematical research notes (see “Research: Mathematics, measurement, complexity and visualisation” below) set out the models and their separate purposes. They are tools for particular questions, not a prerequisite for a useful care handoff.

Living complexity: enough stability to adapt#

Families and communities adapt through many local decisions, varied relationships and feedback. A routine can provide stability while leaving people room to improvise. A uniform score can conceal the difference between genuine agreement and exhausted compliance.

Codetry seeks to preserve the local variation, feedback, memory and revisability that centralised representations can suppress.

The practical aim is enough shared structure to cooperate, with enough independence to learn, differ and change course. Complexity and chaos context (see “Mathematics, measurement, visualisation and privacy” below).

11. Keep uncertainty separate from permission#

“They usually enjoy this activity” is an observation. “They will probably enjoy it today” is a prediction. “They chose to go today” records a particular choice. None is a substitute for the other.

A useful system can keep several possibilities open, show what remains uncertain and record the decision needed for this task. It need not turn that decision into a permanent identity. Repeated checking can also become a burden; review should help someone act, not occupy the life it is meant to support.

Some of my research explores these questions through comparisons with physics and probability. The linked research (see “Research: Quantum-type language, return and holographic research” below) explains those comparisons. The operating rules stand in ordinary language and can be implemented in ordinary software.

Long-lived records raise a separate security question: will their encryption, signatures and recovery arrangements remain adequate as computing changes? That needs tested engineering and migration plans, not an analogy. Cryptographic context (see “Cryptography, networks and recovery” below).

12. Shared encounters and generational handoff#

The practical direction is a shared encounter in which participants can see what is being offered, by whom, under which current permission, and what remains private. Read the holographic events and care protocol.

That might include a familiar recording, a person-authored instruction, an attributed care plan or a spatial arrangement of approved objects. Each source remains distinguishable from interpretation. Live, recorded and generated material must be clearly distinguished.

A past contributor's recorded permission and the present recipient's agreement are separate. Each person whose material appears needs an applicable authority basis. One family member's or group's enthusiasm is not consent for everyone.

A present capable refusal takes precedence over prior permission in the doctrine's authority order. For people using supported or lawful substitute decision-making, participation, assent and distress remain consequential; technical possession does not establish substitute authority. After death or incapacity, no one receives unlimited representation rights merely by being family or holding files.

A hardware provider does not issue consent, settle interpretation or own the underlying record. The same encounter must be justifiable without the spectacle. If it is not useful and properly bounded on an ordinary surface, a hologram does not repair it.

Presentation and consciousness-research context (see “Physics, two-pass return, holography and consciousness” below).

Copies, cloning and the right not to be rewritten#

Other people carry accounts of you that may no longer fit. A care note, photograph, family memory or generated replica can preserve something valuable while remaining partial and dated.

You may authorise, limit or prohibit particular uses of your entrusted records and generated representations, including cloning. Permission for one use does not authorise another. The boundary is against unauthorised impersonation, substitution and exploitation—not every voluntarily authorised representation.

This does not freeze your account. You can correct it, change your mind and author something new, with the authorship and date visible. Authorised help with writing remains help when your approval is clear; it must not quietly replace your account with someone else's.

These boundaries govern entrusted material and authorised operations. They do not confer ownership of other people's memories, observations or criticism. A worker's necessary observation or another person's independently authored recollection is a separate, attributed account—not permission to impersonate you or overwrite your source.

“Cloning” identifies the proposed act: copying a record, generating an interactive representation, biological reproduction, or an attempt at consciousness continuity. Each has its own permissions and questions. Capability and identity context (see “Physics, two-pass return, holography and consciousness” below).

For each proposed use, name the material, recipient, purpose, duration, permitted transformations, commercial terms and onward-use limits. Permission to play a recording does not imply permission to train a model, manufacture new speech, create a persistent replica or place it in another context. A replica's generated “yes” cannot manufacture the original person's missing permission.

If a future process produced a being with independent experience or agency, permission to use source material would not make that being property. Its interests and choices would require separate protection.

Family-heir handoff: stewardship, not ownership of a person#

The keeper and heir protocols carry bounded responsibilities across absence, incapacity and death. A person can specify what may be preserved, for whom, for which uses, under which keeper arrangements, and what must not be created or disclosed.

A memorial process may refer to instructions made in advance. It still needs to check the relevant evidence, authority and applicable version before releasing or using material.

The Heir Clause separates the deceased person's choices from other family members' rights. Someone's permission to represent their own life does not automatically release their children's records, a partner's private material or the family's associated accounts. Likewise, a relative does not acquire unlimited use of the deceased person's material merely through kinship.

A named keeper may have restriction or revocation responsibilities within a specific grant. Holding a file, controlling a key, inheriting an asset and having authority for a particular use are separate facts. An heir or keeper must not silently merge them.

The Heir Clause's application belongs at the particular succession, custody, disclosure or representation crossing. Inheriting an archive does not by itself grant permission to manufacture new speech or a replica.

For each use, distinguish the person's instructions, the authority and agreement applying to that use, what software actually prevents, and the route to a human or legal remedy. Each implementation must identify how it honours the instructions, who can challenge a disputed use, and what happens where enforcement is limited. Legal effect and technical enforcement must each be assessed for that operation, rather than presumed or dismissed across the whole architecture. Instrument and implementation context (see “Professional authority, heirs and legal instruments” below).

What may travel is a permissioned record and a responsibility to care for it. The person is not an inheritable asset.

13. Freedom requires replaceable infrastructure#

The architecture separates:

Nostr can provide signed-event and relay primitives.

XRPL and Bitcoin can support different historical-witnessing and payment arrangements. A proposed Monero payment adapter would address a different problem from secure care-record handling.

No rail should acquire interpretive authority because it carries a proof or payment. Changing a network should not silently join identities, migrate old permissions or convert a pending payment into a second payment.

Device-first custody, readable exports, bounded recovery assistance and restoration without the original provider turn sovereignty into practical engineering requirements. Threat model and network context (see “Cryptography, networks and recovery” below).

Local custody before wider disclosure#

The Salt Box direction begins with the person's locally held account, not a central database of everyone's life. A backup and a care disclosure are different operations: keeping an encrypted recovery copy does not give its holder permission to use the contents for support, research or model training.

The portable Salt Box recovery component already encrypts on the client, keeps the timestamp and selected private fields inside the encryption, and pads the payload to a fixed size. It exports an encrypted archive and separate recovery material by explicit action. Restoring the account does not restore old helper permissions. The source notes (see “Research: Cryptography, replaceable networks and recovery” below) distinguish this implemented component from the complete receiving installation.

The remaining privacy question is what leaves local custody during an authorised exchange, and what that exchange reveals about relationships or timing. Collect less, keep unnecessary identifiers out of shared views, and minimise logs and links between services. AI should operate within the chosen custody boundary; any outside processing needs its own specific arrangement. Local encryption reduces exposure at its source without making every later exchange invisible.

14. Independent communities without a universal biography#

Home, learning, work, exchange and public life ask different things of us. Connecting those settings should not require one institution to hold the definitive account of everyone. Headwaters organises tools around these different activities; the shared protocol connects them without taking over their local decisions.

Families, practitioners and communities can cooperate while retaining their own records, vocabulary and governance. Communities must not have to surrender their own authority or adopt a founder's ontology to participate.

Interoperability should establish that two implementations can perform the agreed crossing correctly.

An independent, separately governed protocol steward is the proposed governance direction. Standards and governance context (see “Edition, implementation and enforcement scope” below).

Regenerative economics: replenish the conditions that create value#

The economic question is larger than “Can this generate revenue?”

After the work is paid for, are the people, relationships, skills, land and tools better able to support the next round of life?

The model joins several functions:

The enterprise earns by selling useful facilitation, installation, training, tools, art and clearly bounded support or licences.

It sustains the work by paying for real labour, maintenance, accessibility, recovery and the reserves needed to keep promises.

It returns value through agreed compensation and reciprocity for the people and community whose authorised contributions made the work possible.

It replenishes capacity by setting aside agreed resources for rest, renewed local capacity and future work.

It hands forward usable skills, records and tools so another household, steward or community can continue.

This is a business model that can include profit, paid work and agreed intellectual-property licences. Regeneration asks what those revenues sustain. It does not require the founder, artists, carers or technical maintainers to work for free or accept incentives that undermine the people they serve.

For care, an organisation can pay for a person-centred installation and steward training while the supported person retains their account and choices. For artwork, a collector can buy a work whose agreed proceeds support creative and community capacity. For another community, a licence can buy bounded tools and support without purchasing authority over its members.

Selling more is not the only measure. If revenue depends on making families repeat their story, withholding their records or keeping them unable to leave, the commercial incentive contradicts the method. A healthy offer earns by reducing a burden, building capability or creating something people freely value.

There is an operating proposal behind this principle. The current business plan sets out paid delivery, backup, maintenance and illustrative financial assumptions. The service playbook assigns preparation, receiving, correction and closure responsibilities. These are specific arrangements to cost, agree and test—not evidence of an already validated commercial model.

Self-sufficiency, self-reliance and community sustainability#

These answer different questions:

Self-sufficiency asks what a person or household can supply directly from their own systems.

Self-reliance asks whether they can retain initiative and direction while coordinating with others.

Community sustainability asks whether the network can keep meeting needs and renewing people, knowledge, tools, relationships and land as circumstances change.

A person can need substantial assistance and still direct their life. A productive household can remain fragile if everything depends on one exhausted person. The aim is not universal self-sufficiency; it is capable, chosen interdependence with usable alternatives.

For example, a local food enterprise can pay for growing, preparation, transport and teaching; cover maintenance and reserves; and help another operator learn the method. The experienced grower need not also be the bookkeeper, technical administrator or permanent final authority. Local language, knowledge-holder permissions and community governance determine the actual arrangement.

The same principles, not identical machinery#

From one person to one billion, the intended rules remain recognisable: name the need honestly, choose participation, agree compensation, limit authority, preserve correction and refusal, fund upkeep and pass on usable knowledge.

At one person, reflection and practice are possible, but self-recording is not independent witnessing. At larger scales, local teams need coordination, backup cover, suitable witnesses, protected budgets and fair dispute routes. A rule requiring a five-person table cannot literally be applied to one person.

An economy without a permanent hierarchy of people still needs accountable responsibilities. A teaching role is specific to a skill; a coordination role has a defined scope. Neither should become a general licence to govern someone's life. Existing administrative powers must be judged against that intention, not renamed into compliance with it. Governance and implementation context (see “Community sources, learning stages and implementation differences” below).

Several benefits do not mean one blanket permission#

One supported activity may yield several benefits: an accessible outing, a worker's learning, a better handoff, an agreed community observation and an authorised creative work. Sharing infrastructure can reduce duplicate effort.

But a care event is not automatically an art commission, a research contribution or a public data source. Each use crosses its own Gate. Likewise, a commercial transaction does not automatically enrol someone in a donation scheme or grant perpetual access to their story.

A reading can become an expression, not an instruction#

A reading need not end in a command or a ranking of people. Selected, authorised observations can become an artwork: something to encounter, discuss, disagree with or freely support. A reproducible artistic mapping can preserve its connection to a reading without making the reading the final account of a community.

That is part of the purpose of the collection and generative-art instruments within this work. They give measurement an expressive and economic use without requiring people to live toward the number. Buying the expression does not buy the people, their private records or authority over their next decision.

The same separation belongs in storytelling. A fictional family can explore several interpretations of an event without becoming a diagnosis of a real family. An instrument may offer scene possibilities; the author chooses what belongs. Audience interest can guide a creative decision without being treated as evidence that the method improves care.

The boundary applies to the business too. If a community is pressured to produce a more attractive score or a more saleable story, expression has become another imposed target. The instrument offers a reading. The work offers an expression. Neither acquires authority over the person. Art, provenance and permissions (see “Regenerative enterprise, artwork and commercial arrangements” below).

The resulting cycle is:

Useful work → agreed income → maintenance and fair return → renewed human and ecological capacity → more independent useful work.

Business, financial and artwork context (see “Regenerative enterprise, artwork and commercial arrangements” below).

Connected records without tracking a whole life#

The practical requirement is not an uninterrupted public trace. Privacy, gaps, selective disclosure and deliberate endings remain valid. Continuity means preserving the necessary relationship between authorised accounts, not tracking the person everywhere.

Without that relationship, each institution can begin again from its own form. Context disappears and the person repeatedly pays the cost of reconstruction. If the remedy is instead one permanent master profile, context accumulates but power concentrates. Codetry proposes a third path: purpose-specific views, connected through attributed and contestable crossings.

Digital computation may use binary representations. That does not require binary social categories. Relevant alternatives and unresolved differences can remain visible until a particular decision needs to be made.

The design constraint is: keep the connection without erasing the differences. Physics context (see “Physics, two-pass return, holography and consciousness” below).

Pass on the method, not dependence on its author#

A second community is not a satellite obliged to orbit its founder. It should be able to adapt the process to its own place, vocabulary and responsibilities.

The seeding doctrine sets a demanding test: can an unrelated community use the method without the originator continually translating or rescuing it? Exporting terminology is not enough. Explain the decisions, preserve the limits and let the receiving community become a second original.

The person teaching the method must not quietly replace the supported person's account with their own interpretation. Record what the receiving household can now do without that teacher, and what remains theirs to change or refuse. One concrete test asks whether the household can make its next three decisions without calling the person who introduced it.

Local adaptation is compatible with faithful transfer when the shared limits remain explicit and local choices remain local. A freely carried practice and a separately purchased commercial tool or service must not be silently bundled together. The teaching and transfer guide and seeding principles develop this test. Commercial context (see “Regenerative enterprise, artwork and commercial arrangements” below).

What happens without a Gate?#

There is no inevitable technological destiny. But several failure paths are practical and recognisable:

A shared transaction history or checked measurement can be useful. The danger is not agreement about a bounded fact; it is extending that agreement into final authority over meaning and permission.

The Gate requires a consequential translation to identify its author, purpose, authority and limits; makes capture easier to contest; and preserves an alternative route. The same demands apply to Codetry itself. Enforcement scope (see “Edition, implementation and enforcement scope” below).

15. Next steps#

Encryption, signatures, consent records and federated software each have their own histories. The question is what happens when we bring these tools together around a person's ability to direct a handoff, question what was understood and leave with a usable record.

The idea this paper contributes is meaning sovereignty: keep the source account distinct from interpretations, keep permission within its agreed bounds, and make the return, correction and exit part of the handoff itself.

There are computational methods within that architecture, not only a statement of values. Existing components calculate direct and reinforcing benefits, apply bounded influence to community signals, enforce consent states in a routing session, and render readings as generative artwork. These are different instruments with different responsibilities.

The proposed reversal of an engagement-driven platform is to begin with a person's declared purpose and let computation serve it, rather than make the person serve an externally chosen target. The authored model, existing algorithms and a complete implementation of that reversal are not the same thing. The instrument and algorithm guide identifies the existing pieces and the combinations worth investigating. Using established mathematics does not make their arrangement trivial; having a distinctive arrangement does not by itself establish research novelty.

Prior work and verification context (see “Practice evidence, outcome claims and demonstration limits” below).

The first convincing demonstration can be small enough to inspect:

  1. One fictional source is presented in two receiving contexts.
  2. Each view preserves source attribution and declares its approved mapping, omissions and uncertainty.
  3. A prohibited mapping does not become an equivalent.
  4. A source or permission change makes a dependent stale view unusable.
  5. A receiver can question, refuse or correct the task and return a receipt.
  6. A recipient cannot use the same proof for a different purpose or onward recipient.
  7. The holder can export and restore a usable record without the original service, under an explicit tested key-recovery arrangement.
  8. A person can choose an accessible non-smartphone route without being silently penalised.
  9. A cloning prohibition blocks the specific replica operation; access to an archive does not bypass it.
  10. A keeper handoff preserves purpose limits, independent family rights and a usable restriction path rather than silently expanding authority.

Demonstration limits (see “Practice evidence, outcome claims and demonstration limits” below).

The compelling next step is not a claim to have built a digital person. It is evidence that a useful handoff can happen without building one.

For a builder, the same questions become a concrete contract: identify the source version, current permission, recipient, purpose, allowed action and expiry; record the authority for each decision and the receiver's separate response. Show what happens when permission changes, the status service is unavailable, a key is lost or someone tries to reuse a proof for another purpose. Keep private content out of public proofs. Then publish a versioned format and positive and negative test cases so a second team can try the same crossings.

Meaning remains human and contestable. A verifier can check a defined operation and its evidence; it cannot calculate the person's true self.

16. Practical value and questions worth testing#

The practical questions are whether the person has more usable choice, needs to repeat themselves less, encounters fewer misunderstandings and can correct a handoff. We also need to learn what the process asks of families and workers, including preparation, review and any extra burden.

Outcome-evaluation context (see “Practice evidence, outcome claims and demonstration limits” below).

Organisations can purchase facilitation, installation, accessible tools, training and bounded support. Payment buys that service—not ownership of a person's meaning, unlimited surveillance rights or permanent dependency. Affordability and the availability of alternatives remain practical constraints to resolve, not assumptions made true by a statement of values.

Before the work expands, builders and participating communities need to decide how independent challenge, accessible receiving, metadata privacy, current permissions, record recovery, retention and future maintenance will work. These are practical design and implementation questions; they do not erase the human method that came first.

Ten practical changes: self, relationships and shared life#

The examples below show where the approach might be useful and what people could look for. They draw on different kinds of work: some can begin with paper and human practice; others need their software or hardware tested.

1. An old account of me no longer fits.

Keep the earlier account as history, add my current words and correct the view used for today's decision. A past difficulty need not become a permanent identity. The next supporter should see the current account and be able to distinguish it from an attributed old interpretation.

2. A new worker supports my community outing.

Share my communication preferences, choices and return arrangements for that visit—not a total biography. Record the worker's acceptance separately from my consent. The worker should be able to follow the instructions, ask a question and return a useful account without adding avoidable burden.

3. The dependable family member needs a break.

A chosen supporter accepts one bounded task using the relevant instructions. Help can rotate without sharing unrelated household information. The task is covered, the usual supporter can actually step away, and neither gains nor loses authority by implication.

4. A child changes teachers.

Carry the child's expressions and the outgoing teacher's attributed observations into a scoped handoff. Let the child respond in an accessible way rather than treating last year's label as final. The incoming teacher should understand what helped and what remains uncertain without making the child repeatedly re-establish everything.

5. I want to learn but am not ready to commit.

Watch first, accept an invitation, practise with support and later teach a particular skill if ready and willing. Being a beginner in one area does not erase expertise elsewhere. Entry should be possible without premature qualification; recognition should reflect the particular skill and remain open to question.

6. A local enterprise depends on one expert.

Pay for a written operating method, cross-training, maintenance and backup—not just today's production. Practise an absence and correct the handoff. Another authorised person should be able to carry out the agreed work safely without the founder continually rescuing it.

7. A community needs outside funding or software.

Keep its own language and knowledge in local custody; prepare a separately attributed, approved translation for the funder's or provider's task. The report should serve its purpose without the funder's or software provider's categories replacing the community's own account.

8. My AI assistant can help, but I do not want it in charge.

Let it prepare a message, explanation or plan within scope. Require separate authority before a consequential send, spend or disclosure; offer a human or paper route. The assistant should reject an unauthorised operation, explain the boundary and remain helpful without punishing refusal.

9. A shared experience could become a gathering or artwork.

Separately choose participation, the permitted recording or representation, publication and sale. Someone can join an encounter without becoming its reusable data source. Only approved material should cross; another participant's permission cannot stand in for mine, and withdrawal needs a clearly stated effect.

10. A family inherits an archive or changes providers.

Hand forward an accessible record under specific keeper permissions. Preserve the source person's choice to permit, limit or prohibit replicas; identify a generated representation as such. Custody must not silently become authorship or cloning permission, and the record should remain usable without the original service.

The broader human significance is not a universal agreement about everyone's meaning. It is a way to cooperate while keeping differences, dependencies and changing lives visible. A person can receive help without becoming someone else's project; a community can share a method without surrendering its own account of the world.

Four demanding intellectual lenses#

These editorial lenses draw on the documented work listed below. Attribution context (see “Finney, Schwartz, Spirko and Rothbard: attribution and disagreement” below).

Hal Finney: inspectable security and working prototypes. Can someone inspect the mechanism, identify its trust assumptions and try its failure cases? Finney's RPOW announcement offered source, a specific hardware-attestation model and explicit beta limitations—not merely a promise of trustlessness.

David Schwartz / XRPL protocol design: agreement on a bounded state. Exactly what do participants agree on, under which rules and trust assumptions? Agreement about transactions must not become agreement about someone's identity or inner meaning.

Jack Spirko: practical independence and redundancy. Does this improve ordinary life, and does it remain useful when the internet, provider or original facilitator is absent? A paper route, practical skill and recoverable local record matter more than technological allegiance.

Murray Rothbard: self-ownership and explicit transfers. What authority or right was actually transferred, and what was retained? Providing support cannot amount to purchasing a person's future will. A promise, a service contract and a present permission are not the same thing.

Context: differences between these traditions (see “Finney, Schwartz, Spirko and Rothbard: attribution and disagreement” below).

The common challenge is useful: show the mechanism, name the dependency, leave the person an exit, and do not claim a right that was never granted.

Ready For Testing#

The paper is ready for discussion and inspection of its specific mechanisms. The next task is to connect and test the complete protocol, including the places where it must refuse an operation or recover from failure.

The strongest proposition is deliberately narrower than ownership of meaning: authenticate a bounded crossing without making the carrier the authority over the person. People remain free to author their own observations and criticism.

The strongest objection is also concrete: a beautifully worded permission that a recipient can ignore is not an enforcement mechanism. The technical companion must say what software prevents, what depends on a cooperating recipient, what remains visible only through audit, and what requires a human remedy. Open formats, independent implementations, adversarial tests and recovery without the original operator are the route from this argument to credible infrastructure. Security (see “Cryptography, networks and recovery” below) · Rights and attribution (see “Finney, Schwartz, Spirko and Rothbard: attribution and disagreement” below).

17. From specification to shared human evidence#

For me, Codetry began as a craft: notice what matters, name it honestly, hold a boundary, build something useful and prepare to hand it on.

Codetry builds on established cryptography to address a different problem: how people carry context between relationships and systems without surrendering authorship or granting unintended authority. Its contribution is the architecture connecting those responsibilities—supported by specifications, implemented components and a human method developed through practice.

The next step is to bring those parts together in a complete, independently inspectable handoff. That demonstration will examine what survives the crossing, what the receiver understands, how refusal and correction work, and whether the process makes support more useful without adding avoidable work. Implementation and evidence context (see “Edition, implementation and enforcement scope” below).

The proposition is ready to be examined:

Help people carry their meaning into new relationships without making them surrender authorship to the system that helps them.

Meaning arises in a moment and is recorded in situated fragments. Carrying a fragment without loss means seeking to preserve its expressed source, time and relevant context through a particular crossing—not freezing its meaning for all future situations. Keep interpretation attributed; make selection, omissions, uncertainty and disagreement visible; prevent unapproved changes of purpose or authority; and let the person correct what the receiver understood. The next moment can bring a new account. A signature can protect a record's integrity without proving its interpretation or the receiver's understanding.

Builders can examine those obligations using their own agents, models and software. No particular model, blockchain or metaphysical vocabulary should be required. The accompanying implementation and evidence map identifies the existing specifications, their observable requirements and the evidence still needed. Inspect the source, challenge the translation, attempt the forbidden operation and show precisely what is preserved or lost.

The next evidence layer: person-centred care#

A bounded starting interaction is two people cooperating: a person directing their own support and a receiving supporter working within the agreed structure. Other roles, such as a chosen keeper or human reviewer, are added explicitly where needed, not assumed. The aim is to examine a complete cycle: authored need, scoped offer, receiver response, agreed action, return, correction and closure.

The pilot will seek evidence that the person's intended meaning remains usable across that cycle, that misunderstandings can be detected and repaired, and that support returns capacity rather than adding avoidable work. It will examine burdens on both people, including repeated explanation, preparation, correction and review. A faithful packet, an understood instruction and a beneficial experience are separate things to establish.

This is the next evidence layer for the integrated technical approach, not the beginning of the underlying human care method. Its first results may support, narrow or challenge the design. They will not be presumed positive or treated as proof of every application, hardware proposal or research hypothesis. Practice, technical and outcome evidence (see “Practice evidence, outcome claims and demonstration limits” below).

The standard is whether someone can understand what happened, see what crossed, correct the account, choose what happens next and leave with something they can still use.

The theory and specifications establish what should hold. A front-to-end implementation makes those commitments executable. The first shared human pilot will begin to show whether they hold in practice.

A better handoff carries support forward without carrying control forward.

Intellectual and practical lineage#

The research and source companion (see “Research and source notes” below) links the authored care method, family stories, community-learning model, mathematical research, economic arrangements and technical specifications. Its source-name guide (see “Research: Finding the original sources” below) connects the plain-language ideas here to the original document names. Those names help locate the work; adopting them is not a condition of using the method.

External references for the critical lenses#

Linked research and source material#

The research and source companion (see “Research and source notes” below) opens the fuller material behind the paper. Follow a topic below for the relevant doctrine, models, evidence and research questions.

Edition, implementation and enforcement scope#

Read the implementation, evidence and enforcement notes (see “Research: Edition, implementation and enforcement” below).

The primitives: interpretation and practical limits#

Read the five-primitives source and its practical interpretation (see “Research: The five primitives” below).

Read the authority, keeper and heir source notes (see “Research: Professional decisions, keepers and heirs” below).

Mathematics, measurement, visualisation and privacy#

Read the mathematical models, complexity and visualisation sources (see “Research: Mathematics, measurement, complexity and visualisation” below).

Physics, two-pass return, holography and consciousness#

Read the quantum-type, two-pass and holographic research material (see “Research: Quantum-type language, return and holographic research” below).

Cryptography, networks and recovery#

Read the cryptographic threat model, network and recovery notes (see “Research: Cryptography, replaceable networks and recovery” below).

Regenerative enterprise, artwork and commercial arrangements#

Read the economic, artwork and propagation source material (see “Research: Regenerative enterprise, art and commercial arrangements” below).

Practice evidence, outcome claims and demonstration limits#

Read the practice, technical demonstration and outcome-evidence notes (see “Research: Human practice, technical demonstrations and outcomes” below).

Community sources, learning stages and implementation differences#

Read the community sources, learning stages and implementation comparison (see “Research: Learning, community sources and differences between implementations” below).

Finney, Schwartz, Spirko and Rothbard: attribution and disagreement#

Read the four intellectual lenses and their sources (see “Research: The four intellectual lenses and their sources” below).

Research and source notes#

Companion to the public white paper. The paper carries the argument; this companion links the underlying doctrine, models, research questions and evidence distinctions for readers who want to inspect them more closely.

The linked authored material explains the design and its intellectual development. Independent research and protocol documentation have their own authors and purposes. Neither kind of source is an endorsement of Codetry or a substitute for testing the proposed applications.

Research: Finding the original sources#

The public paper uses everyday descriptions. These original names locate the underlying work; a family, worker or independent community does not need to adopt them to use a scoped handoff.

Five foundations the tools should serve. The Primitives; “irreducible primitives.”

A record assists without becoming the thing it describes. “Forever pair,” in The Primitives.

Agree the aim, limits, alternatives, review and transfer. Codetry Kit Frame, including Both-States, Both-Sides, Rename Test and Refused shelf.

Reduce physical effort and repeated explanation without taking over. Continuity Suit and the paper handoff rehearsal.

Preserve several attributed accounts instead of one master profile. Ledger Superposition in Meaning Sovereignty.

Distinguish arrival, understanding and purpose-specific reliance. Event-to-Trust Chain.

A person, pair, household team and wider support circle. Source node, dual oscillator pair, Salt Box and Eave in the family and community material.

Learn another person's context without claiming their experience. Family Leap.

Track what remains useful after an event. RealityCore.

Examine support patterns and bottlenecks. Bubbler, historically called Sandman; the sociophysics research.

Make an authorised artistic expression from selected readings. Mermaid Engine; the resulting works are Symphonies.

Connect accounts without collapsing their differences. The Cursive String.

Offer a visual way to navigate learning and relationships. Raw Moon Codex.

Carry chosen memory and art into a physical heirloom. The Regenerator.

Pay for useful work and replenish capacity. Revenue Watershed; Well, Reservoir and related arrangements.

Teach a method that no longer depends on its introducer. Propagator Kit, Regenerative Receipt and Seeding and Replication.

Review another person's account of you, including replicas. Copies and Crossings.

Research and evidence by topic#

Research: Edition, implementation and enforcement#

The public paper is an author-review discussion draft, preserving the founding paper as a historical edition. It brings together established human practice, authored specifications, component implementations, a fictional paper exercise and synthetic checks. The whole technical approach has not yet been connected and tested end to end with people in a shared support structure. This editorial pass is not a production audit, clinical protocol or security certification.

Different questions need different evidence. Dated practice records support the history of the human method and reported participation and barrier-reduction benefits. Independent replication asks whether another practitioner can carry it faithfully. Technical integration asks whether the software preserves its limits through the complete interaction. Claims about incidents, quality of life, staff retention or net time saved need the evidence appropriate to that outcome and setting. The new tests extend and challenge what came before; they do not erase it.

The inspected encryption and commitment components use established cryptography. This edition presents an architectural contribution, not a claim to a newly invented cipher, network-consensus algorithm or zero-knowledge proof scheme. The originality of particular combinations requires comparison with prior work; neither a claims draft nor the absence of a new cryptographic primitive settles that question.

The implementation and evidence map identifies what each kind of evidence can establish. An independent protocol steward is proposed, not established by the paper. Compatibility concerns an agreed operation, not a community's worldview or care competence.

Enforcement has to identify what software prevents, what requires a cooperating recipient, what can be audited and what needs a human remedy. A Gate cannot abolish coercion or control every downstream actor. Public reading, reuse licensing and permission to publish source material remain separate decisions.

Research: The five primitives#

The Primitives gives the architectural starting points. They orient the tools; they are not experimentally established axioms about every society or conditions for receiving support.

Sound money without an issuer expresses an aim of independence. Networks and custody arrangements still face surveillance, coercion, fees, compromise and loss of access. The Keepers names care work across genders and does not itself establish custody or substitute authority. Rock Bottom means beginning with the real situation, not requiring distress, lost sleep or crisis. Natural cycles inform design; they do not establish universal regeneration laws. The land's place in the doctrine does not confer title through a token.

Research: Professional decisions, keepers and heirs#

Meaning Sovereignty and the Privacy Acceptance Contract explain separate decisions about authorship, access, interpretation and action.

Professional requirements attach to the particular action, person and setting. Codetry does not itself confer clinical, legal or substitute-decision authority. That is different from placing the whole human method on hold for universal clearance.

The Heir Clause is a draft instrument. Its effect depends on the succession, custody, disclosure, representation and jurisdiction. A memorial flag alone is neither proof of death nor consent; the Kin bridge is a specification, not a freshly verified integration. Exceptions need their own authority and record, rather than being described as consent. Historical legal explorations and attributions do not establish a jurisdiction-independent legal shield.

For a particular archive, training operation or generated representation, record the distinct questions:

Person's instructions. The material, allowed or prohibited uses, recipients, duration, changes and applicable version.

Authority and agreement. Who can authorise this specific use, what the agreement establishes, and how succession or lawful substitute authority applies in the relevant setting.

Technical control. Which actual access, training, generation or onward-disclosure operation is checked or blocked, with evidence from that implementation.

Challenge and remedy. Who receives an objection, what can be corrected or stopped, which copies or duties remain, and what human or legal remedy is available.

Permission to create a representation and a representation's technical feasibility are separate. A generated response supplies neither missing original permission nor substitute authority. Likewise, a valid restriction in one service is not evidence that every outside service enforces it. Assess the particular instrument and control rather than labelling all legal and technical force either established or future work.

Authorship protections do not require a frozen record or ownership of others' independent accounts. Corrections, new expression, attributed professional observations and criticism remain distinguishable from impersonation or unauthorised use of entrusted material.

Research: Mathematics, measurement, complexity and visualisation#

The mathematical material asks distinct questions rather than supplying a single equation for a person:

Directed graphs and percolation. Where are routes, disconnected groups, dependencies and fragile bridges?

Cascade distributions, likelihood comparisons and bootstrap checks. Does an observed spread fit one candidate statistical account better than another?

Ising-style interaction models. What changes when alignment and conflict are projected into a particular model?

RealityCore's discrete-time model. How do events, loss and restoration interact around a stated reference?

Information theory. What can a bounded channel carry, what is lost and how might errors be detected?

Combinatorics and multidirectional-load mappings. Which allocations, roles and pressures disappear when reduced to one total?

Double-spinor / 720-degree teaching geometry. How can revisiting and incomplete first closure be made memorable?

The Gate-residue research additionally explores Green's functions, integration by parts, Laurent series, fold catastrophes and condensed mathematics as prompts about reuse, restructuring burdens, concentrated difficulty, sudden change and representations that erase a needed distinction. Each proposed formal application needs its own variables, assumptions and derivation; the name of a mathematical technique does not establish the application.

Read RealityCore, the RealityCore–sociophysics research map, Bubbler, and the Mermaid Engine. They address different questions and do not supply one measure of a person.

An observed interaction is partial evidence. Financial circulation, witnessed support and human interpretation are separate streams. Neither an edge nor a composite score proves that help was wanted, delivered or beneficial. Heavy tails, generated cascades and model fit do not establish community health or causal benefit; synthetic observations stay distinguishable from field data. Ising alignment does not measure consent, consciousness or moral worth. Disagreement is not illness, and maximum alignment is not maximum freedom.

Information quantity is not understanding. Counting allocations or expressing load as a tensor does not decide what is humane. A mapping to a mathematical structure inherits its theorems only when the assumptions and derivation hold. In formal settings, chaos can mean sensitive dependence on initial conditions in a deterministic system; it is not synonymous with freedom or proof of a social dynamic.

Moon Codex geometry is an orientation and teaching device, not proof of maturity, identity or truth. Repeatable art reproduces a chosen mapping; it does not validate the input model. Aggregation and removing names do not guarantee anonymity, particularly in small communities. Scores and artwork need their own disclosure review; renderability is not publication permission.

Research: Quantum-type language, return and holographic research#

The Quantum-Type Architecture and Quantum Glossary set out the structural comparisons. The two-pass research protocol and Consciousness Continuity Compiler describe research proposals. Family Leap offers the narrative lens; holographic events describes encounters.

Quantum-type, spinor and string language here provides structural or teaching vocabulary rather than an established physical care mechanism. A useful analogy does not establish a formal mathematical isomorphism or borrow experimental validation from physics.

The underlying design comparisons can be stated separately:

Superposition / Both-States. Can different contextual accounts remain available without one becoming universal?

Contextual resolution. Can the view needed for this task be produced without overwriting its source?

Decoherence. Where does a translation erase a distinction the person needed preserved?

Zeno effect. Is repeated checking displacing the life or capacity the support should enable?

Propagation. Can another person use the method without its originator?

Paced transition. Can change proceed at a rate the affected people can meaningfully navigate?

Error correction. Can attributed records and witnesses reveal an error without unrestricted duplicate biographies?

Bit, Pbit and Qbit distinguish definite recorded values, probabilistic model states and the doctrine's comparison with unresolved possibilities. A weighted prediction is not permission. Qbit / qubit language does not establish a physical-qubit implementation of meaning or a format signature. Ordinary classical software can retain competing accounts and uncertainty. Long-lived cryptographic protection is a separate engineering question.

The research protocol identifies comparisons, confounds and defeat conditions. Two encounters do not by themselves validate recognition, subjective identity or a return interval. No literal non-local communication, mind-reading, travel into the past or consciousness transfer is established by this work. Group synchrony does not establish a mechanism for rendering an unrecorded memory. Repetition and agreement can preserve errors; a signature cannot make a recollection true.

Copying records, interactive simulation, biological reproduction and proposed consciousness continuity are different operations. Permission does not establish feasibility. Biological cloning alone does not transfer memories or consciousness.

Research: Cryptography, replaceable networks and recovery#

Salt Box: inspected component and receiving installation#

The portable source in recovery.ts implements manual client-side recovery using Web Crypto AES-256-GCM, random recovery material and a fresh IV. The payload is padded to a fixed size; the timestamp, selected goal/source/private note and historical accessibility settings are encrypted rather than exposed as header fields. Separate downloads do not, by themselves, establish independent physical key custody.

The rehearsal holds its live state in memory. Explicit export creates the encrypted file; it is not an automatically persisted device ledger. Restore recovers historical information, clears helper and aid permissions, and requires renewed accessibility confirmation. The earlier bounded browser-test report records no application API/provider traffic or browser storage writes during that workflow. Source inspection for this editorial clarification is not a rerun of those tests.

This evidence concerns the portable component available in this workspace. It does not inspect a newer receiving Salt Box repository, durable local storage installation, actual on-site backup medium or deployed AI inference configuration. Those are distinct from hosted Aquifer API paths. Do not infer their properties from either the local-first intention or the older hosted paths.

Fixed-size encrypted payloads reduce size disclosure for this format; they do not conceal the time, frequency or destination of every future transfer. Metadata review must follow the actual sharing, backup, AI and update paths. Local processing can avoid sending a record to a model provider; cloud processing, if chosen, has a different disclosure boundary.

The Privacy Acceptance Contract describes separate boundaries. NIST's post-quantum cryptography work provides the standards context for migration, distinct from the doctrine's quantum-type vocabulary.

A signature verifies data under a key and scheme, not legal identity, truth, capacity, care competence or disclosure permission. A commitment to a guessable secret may still be guessed. A signed behavioural pattern does not prove unique humanity.

Nostr does not guarantee universal delivery, current consent or metadata privacy. Public ledgers are not private care stores. Monero is a proposed payment option here, not a delivered adapter or automatic cross-asset failover.

The threat model includes operators, compromised devices, coercion, lost keys, stale policy, timing metadata, unavailable status services and abandoned maintainers. Encryption cannot protect plaintext on a compromised display. Revocation cannot recall every retained plaintext copy.

NIST has standardised post-quantum key encapsulation and signatures; this does not make the ecosystem migrated. Long-lived encryption, signatures, commitments and recovery each need analysis and tested migration. Recognition, a 720-degree image, a network name or a hash-family change is not a post-quantum guarantee. Local custody, readable exports and provider-independent recovery need an actual demonstration.

Research: Different repositories, different instruments#

Returned source reviews describe useful mechanisms in separate checkouts. Gatehouse reports in-process source-owner capabilities, scoped releases, separate interpretation and draft decisions, and source-bound crossings. Those fictional instruments are not yet a demonstrated real-person identity, guardianship or complete receiving-system enforcement layer.

The separate Mermaid checkout reports event-derived scores, a Canvas waveform renderer and verified testnet transaction-evidence handling. It does not establish an author/participant approval chain joining a particular source, representation, publication and later use.

That Canvas renderer is not the Aquifer SVG implementation discussed above. Shared names do not establish identical metrics, input meanings or outputs. Cross-repository reproduction needs the scoring instrument/version, complete source history and ordering, renderer/version and the approved representation.

Retained historical text is distinct from current authority to reuse it. Authentication, membership or a ledger transaction must not silently supply the missing permission. Cross-repository enforcement remains integration work until those boundaries are demonstrated together.

External prior-work comparisons identify close precedent families, not a definitive novelty result. Exact sources and mechanism-level comparisons remain necessary; a public-description review is not a code audit or patent search.

Research: Regenerative enterprise, art and commercial arrangements#

Read the Mermaid Engine, Revenue Watershed, Propagator Kit and Seeding and Replication. Historical financial proposals are distinct from the current operating plan.

The paper explains proposed economic arrangements, not realised revenue or automatic distributions. Each offer needs an actual service, price, cost, custody model, permission and distribution rule. “Well,” “Reservoir” or “Eave” does not establish a particular legal, tax or cooperative status.

The current business plan and service playbook provide a specific delivery proposal and illustrative costing rather than only an aspiration to regeneration. Defined responsibilities and arithmetic are not validated demand, actual quotations or tested delivery capacity.

Symphony records describe deterministic SVG artwork: an artistic mapping, not a direct physical conversion of community life into sound. Repeatability does not validate a community-health interpretation. Provenance certificates do not confer copyright, private participant data, clinical validity or universal downstream control. The approved representation can be public without exposing its private inputs.

The current Museum renderer takes more than scores as inputs: its paramsFromScores function also uses the piece identifier for the seed and colour family. Reproduction therefore requires the complete inputs, dimensions and rendering version. The Mermaid doctrine's shorthand “same score, same image” needs that qualification. A fixed mapping still embodies its designer's choices; deterministic does not mean interpretation-free.

Expression is one permitted use of a reading, not a substitute authority. Evaluate whether rewards, collection prices or presentation pressure people to improve a score, disclose more or manufacture a saleable story. Refusing representation must not cancel separately authorised support.

Sale, display, research and model training need separate permissions. Proprietary splits and scoring mappings are not disclosed here. Freely carried methods and purchased tools or support are distinct offers.

Research: Human practice, technical demonstrations and outcomes#

The implementation and evidence map and fictional handoff distinguish the questions being examined.

A practitioner method existed and was used. Dated primary records and attributed practice accounts.

A component performs a defined operation. Inspectable implementation and tests, including refusal cases.

A handoff can be followed on paper. A labelled fictional walkthrough or observed, authorised rehearsal.

An integration preserves scope. Its actual client, server, storage, recipient and recovery paths.

People benefit. Accessible, consented evaluation of outcomes they value, including burden and harm.

Costs or staff turnover improve. Setting-specific cost and workforce evidence.

Consciousness transfers. Not established by these records, models or demonstrations.

Dated care records support a history of practice and reported participation and barrier-reduction benefits. New software and hardware need their own evidence. Incident counts require reporting completeness, exposure and severity context; fewer reports can reflect less reporting. Turnover has multiple causes. Family and worker burden belong beside measures of benefit.

A reference demonstration is not federation-wide enforcement, production privacy, universal delivery or proof of recipient honesty. Distinctiveness requires comparison; the paper makes no “first” or “only” claim.

Research: Learning, community sources and differences between implementations#

Read Helping Hands, Seeding and Replication and the Propagator Kit.

The supplied community-economy transfer contains a report and handoff, not the underlying repository. Its northern operating-draft, handbook and story excerpts are attributed recovered quotations, not new direct inspection here. The stories are authored illustrations, not community testimony, clinical evidence or Indigenous endorsement. The learning story does not show its protagonist later becoming a teacher.

Reported source variants include Watching → Learning → Practising → Teaching, Learning → Practising → Teaching, and verification-only Practising. The last was labelled “binary” in that source; it is not a two-step ladder. These variants are not automatically equivalent to derived trust tiers.

Local route inspection found poster-as-acceptor and worker-as-witness refusals. The other repository's reported inspection did not establish those checks and described administrative powers. Source inspection is not end-to-end execution or deployment equivalence. The completed schema, Ecosystem Care doctrine and session brief exist here even though they were not found in the other review.

Eave's support-circle, privacy-boundary and economic uses need their own definitions. Related ideas do not establish an integrated implementation or shared permission. Non-hierarchical intent does not prove powers are bounded, contestable or removable. Scale changes the staffing, quorum, witnessing and coordination needed to honour the same principles.

Research: The four intellectual lenses and their sources#

These are editorial questions drawn from documented work, not endorsements or claims about what the four people would say. The Schwartz-associated lens uses XRPL documentation, not his review of Codetry.

The traditions differ on information, reputation, intellectual property and enforceable downstream restrictions. Self-ownership does not settle all of those disputes. Rules for entrusted records do not confer ownership of others' thoughts, suppress independent criticism or automatically bind unaffiliated speakers.

#bitcoin#care#codetry#community#consent#context#design#economics#gate#handoff#identity#meaning#methodology#nostr#record#regenerative#software#sustainability#systems#teaching#technocracy#training#trust

Written by

Bobbie

Homeschooling kids in the forest & using Codetry to transfer recreation & community development practice into programming methodology. Building human transmission protocols to support care and continuity across system…

Comments

No comments yet. Start the conversation.

Contents

23 sections

  1. A founding paper on freedom, meaning and person-centred cooperation.
  2. Start here: five foundations
  3. In one minute
  4. 1. The commitments come before the technology
  5. 2. Naming is the beginning, not the limit
  6. 3. Support that helps without taking over
  7. 4. Hold multiple interpretations without manufacturing a universal profile
  8. 5. The Gate: a relationship with bounded authority
  9. 6. A handoff is not finished when a packet arrives
  10. 7. A care handoff, without a total biography
  11. 8. Understanding another person's situation without claiming it
  12. 9. What remains useful after the event?
  13. 10. Study the support conditions, not a person's worth
  14. 11. Keep uncertainty separate from permission
  15. 12. Shared encounters and generational handoff
  16. 13. Freedom requires replaceable infrastructure
  17. 14. Independent communities without a universal biography
  18. 15. Next steps
  19. 16. Practical value and questions worth testing
  20. 17. From specification to shared human evidence
  21. Linked research and source material
  22. Research and source notes
  23. Research and evidence by topic