On this page
Inspect identity and communication
Read the record without overstating it
- Open Identity. Read the morning brief and Ring 1 charter if present. The approval panel identifies the operator words the signed charter entry cites, with record/turn information. Missing, unreadable, differing or no-longer-local conversation evidence is shown explicitly. A quoted approval is provenance to inspect, not an invitation to assume a mismatch is harmless.
- Check Continuity: mode/reason, ledger sequence, witness anchoring, lifetime ticks, review status and snapshot/escrow indicators when available. A configured witness is different from a successful anchor; a snapshot date is different from a verified restore. Use backup and restore for action.
- Read relationship trust and autonomy as stored descriptors, not new permissions. This view shows the current operator relationship, not an editable address book or complete relationship history.
- Open Memory for the current self-model synthesis, belief statements/IDs/rings/status chips, intentions and selected recent experiences. The loaded experience sample is bounded and omits private-marked contents; its private count is not a total archive inventory. Filtering only searches loaded cards. Enter invokes recall; see memory and work for ranking, reinforcement and optional embedding disclosure.
A declared belief, its current evidence standing and its placement in Ring 2 are different facts. The chip is derived from evidence standing (or unavailable if it cannot be read), not simply the belief's own confidence declaration. The built-in cards do not display the full evidence graph, supporting origins or contradiction audit. Home counts Ring 2 as “promoted”; that count is not proof of truth or a substitute for checking evidence. Promotion is a separate identity act, gated on confirmed support from distinct sources/origins and no live contradiction. If needed, ask the identity to inspect the named belief's standing and explain its evidence; that request does not itself perform promotion. Neither Memory nor Identity provides a promotion button here. A synthesis is the stored self-description, not proof of consciousness.
Inspect arrivals and sends
Open Settings → Messages, then Refresh. Reading the message lists changes nothing: there is no ordinary compose, cancel or delete control on this page. It shows arrivals and whether they woke the identity or were read by a turn; sends grouped as waiting, being sent, parked or effect unknown; delivered sends; and notices addressed to the operator. Show more expands bounded lists up to the host's cap; shortened previews and omitted rows are labelled.
“Delivered” means an adapter took the message, not that a person read it. Later incoming activity is explicitly not an answer. Effect unknown can mean a message left before the process lost its answer: the traced runtime does not send it again or try another channel. Do not manufacture a retry from that uncertainty. Notice routing to a page does not prove anyone saw it. After a disconnect, refresh to learn actual state.
Control contacts and notices deliberately
Before saving Contacts, inspect the waiting sends. Adding a missing contact can release an already queued message automatically once a usable channel is available. Save is not limited to future messages. Do not add or change routes experimentally if pending messages are unintended; changing a route is not cancellation or a general repair for unknown-effect sends.
Sources: Queued-contact consequence
The Contacts editor below the lists sets name, channel, address, May wake the identity and This is me. Add/remove/reorder lines locally, then Save and check acknowledgement: drafts leave saved contacts in force. Saved changes apply live. A person's first line is tried first, then the next; channel availability still matters. Removing a contact line is not message deletion and does not establish cancellation of a send already handed off.
Mark only your lines This is me. In Chat → Expert, Send my notices to me off the dashboard routes notices to those lines, in order, when no page is open. The page retains notices either way. A held route or missing channel is disclosed, not silently equivalent to delivery. Contacts, channel/plugin permissions and operator authority are distinct controls; configuring an address does not make another person's words the operator's.
Historical held-mail repair is a sending risk
Settings → Held mail is for historical unresolved addressing, not normal message management. Refresh/read the complete message if its preview is cut, choose an existing current contact route, then use Correct and queue only if you intend that message to leave. This changes that message's recipient/channel and queues it; it does not edit contacts or confirm delivery. The host requires an unchanged message digest and rejects attempted, parked, delivered or uncertain-effect messages. SAFE also blocks repair.
If confirmation is lost—or correction succeeded but refresh failed—read fresh state before any further action. The UI does not automatically retry. Do not use this as a general resend workaround.