identity, context, permission, boundary

Who am I here?

MeWho preserves who we are as we interact with systems in different contexts. It keeps identity, role, relationship, permission, boundary, and consent visible as people work with AI, software, households, teams, communities, and public life.

See the need Pair with WhoLoops

MeWho is a natural companion for WhoLoops.

Identity without context becomes a profile. MeWho exists so human intention can travel through software, AI, teams, households, and public systems without collapsing the person into one permanent, extractable self. When paired with WhoLoops, the practices we carry can move without being severed from the people and contexts that made them meaningful.

Identity Who is carrying this loop, statement, preference, role, artifact, or delegation?

Context Is this family, public, work, private, experimental, temporary, ceremonial, or something else?

Permission What may be seen, run, shared, forked, remembered, forgotten, or used by an AI system?

Boundary Where does consent begin, end, expire, require clarification, or return to the person?

how it works

Not a profile. A living identity tree.

Platforms build profiles about people. MeWho helps people maintain identity contexts with people: roles, relationships, boundaries, preferences, permissions, and delegated intentions that can be inspected, corrected, explained, and revoked.

Contextual self

You are not always the same “user.” You may be parent, builder, cook, founder, friend, researcher, public speaker, or private self. MeWho keeps the context visible.

Delegated intention

AI can carry small decisions only when authority is bounded: decide, suggest, refuse, ask, explain, or escalate depending on the context.

Consentful movement

As loops move, MeWho helps preserve who shared them, which role they came through, what may happen next, and what must stop.

principles

The self should not become a scrape.

MeWho is designed for the AI-mediated world where agents, loops, messages, workflows, recommendations, and memory systems act around us constantly. Trust depends on making identity contextual, consent inspectable, and delegation reversible.

Context before claimsA statement means different things depending on role, relationship, audience, and time.

Delegation is boundedAI may carry intention only within explicit authority, risk, and review limits.

Visibility is not surrenderPublic material still deserves context, lineage, boundary, and consent-aware interpretation.

Forgetting is part of consentNot every identity context, message, or memory should persist forever.

Explanation is requiredAn agent acting for you should be able to say why it acted, what permission applied, and when it should have asked.

The person remains upstreamMeWho is not a replacement self. It is a consent-bound way to carry identity without stealing agency.

in the stack

The identity layer for consentful loops.

MeWho is the identity-context surface. Paired with WhoLoops and the deeper trust/provenance stack, it gives human practice a way to remain attached to the right self as it is captured, run, shared, forked, witnessed, or retired.

WhoLoops Preserves lived practice as reusable, consentful loops.

MeWho Preserves identity, role, context, permission, and boundary as loops move.

BobWho A founder-led public exemplar and crash-test dummy for testing radical openness without radical permissionlessness.

LoopPress The protocol engine for publishing, running, revising, forking, and revoking consent-bound loops.

Abracadabracadoo The consent-chain basis: ephemeral identity, encrypted consent messaging, proof without exposure, revocable permissions, and forgettable storage.

↟

Keep the thread attached to the right self.

MeWho is early. The first task is simple and hard: make identity, context, permission, and boundary legible enough for AI systems to help without becoming opaque proxies for people.

hello@polelop.com See the public exemplar