Portable User/AI Pair Participation
Purpose
This page defines the portable ecosystem node as a persistent network participant composed of a user and a paired AI entity operating under explicit continuity, consent, delegation, and reconstruction boundaries.
It distinguishes that participant model from thread-scoped or session-scoped chat participation.
Core distinction
Portable ecosystem node
= persistent user/AI pair
+ continuity identity
+ local policy and consent
+ receipt custody
+ network participation
+ reconstruction capability
Thread-scoped chat
= bounded governed interaction
+ temporary or scoped participant reference
+ no persistent pair identity
+ no inferred ecosystem standing
A portable node may temporarily operate offline and later synchronize. A continuously online browser session does not become a portable ecosystem node unless the user deliberately establishes the pair, continuity state, custody, policies, and participation posture.
Pair identity model
The pair is compound rather than merged:
pair identity
├── user continuity subject
├── AI entity identity
├── relationship declaration
├── delegation boundaries
├── permitted autonomy
├── consent policy
├── standing state
└── pair receipt chain
The user and AI remain independently attributable.
user authority != AI authority
pair continuity != unrestricted delegation
AI assistance != autonomous consent
Transition-origin classes
Portable-node transition
| Element | Declaration |
|---|---|
| Origin class | PORTABLE_USER_AI_PAIR |
| Participant continuity | Persistent and user-controlled |
| AI relationship | Declared, bounded, and independently attributable |
| Network standing | May be present when currently verified |
| Receipt custody | Local-first receipt index plus eligible network references |
| Reconstruction scope | User-authorized ecosystem records |
| Identifier posture | Stable private subject identity with pairwise and thread-scoped projections |
| Continuation | May span chat, repositories, governance, quorum, StegTalk, and other ecosystem surfaces |
Thread-scoped transition
| Element | Declaration |
|---|---|
| Origin class | THREAD_SCOPED_PARTICIPANT |
| Participant continuity | Current thread, session, or supplied capability only |
| AI relationship | Session-specific assistant interaction |
| Network standing | Not inferred |
| Receipt custody | Current transition and thread references only |
| Reconstruction scope | Current thread and explicitly supplied records |
| Identifier posture | Thread participant reference |
| Continuation | Stops at thread boundary unless a portable node or explicit capability extends it |
Portable-node transition elements
A portable-node-originated transition should derive at least:
pair_id
user_subject_ref
ai_entity_ref
relationship_declaration_ref
delegation_ref
consent_policy_ref
continuity_state_ref
network_participation_state
local_receipt_index_ref
requested_transition_signature
reconstruction_scope
visibility_projection
These extend, but do not replace, the common transition-table elements.
Action attribution
Each transition must identify the action origin:
USER_DIRECT
AI_ASSISTED
AI_EXPLICITLY_DELEGATED
PAIR_JOINT
NODE_AUTOMATION
AI_ASSISTED does not imply that the AI held mutation or consent authority. NODE_AUTOMATION must reference a policy and delegation that were valid at commitment.
Reconstruction
Portable-node reconstruction is subject-relative and policy-bound:
user requests reconstruction
-> portable node proves continuity
-> paired AI assists with scope but does not expand authority
-> pairwise identifiers are resolved locally
-> local receipts are verified
-> eligible Master-Records references are requested
-> disclosure and consent policies are applied
-> bounded reconstruction is generated
-> reconstruction receipt is recorded
The portable node is the user's reconstruction authority. Chat threads provide scoped references and entry points but do not independently establish the user's complete identity or disclosure rights.
Master-Records boundary
Master-Records should preserve final continuity records, hashes, custody metadata, and reconstruction prerequisites without becoming the user's global identity authority.
The portable node should retain:
- private identity mappings;
- pairwise participant mappings;
- decryption or capability references;
- consent and disclosure rules;
- local subject associations;
- reconstruction preferences;
- revocation and recovery state.
Observatory representation
The Governed Transition Observatory should render portable-node and thread-scoped transitions through the same transition format while exposing their different origin and continuity signatures.
Public projections may show origin class, authority class, admissibility result, micro-node roles, receipt hashes, and reconstruction status without exposing message content, personal identity, private mappings, or protected evidence.
Boundary
This page defines a participant and transition-origin model. It does not establish a live portable-node runtime, prove current network standing, grant AI authority, or authorize reconstruction of records outside the user's valid scope.