CairnStone V7 Console
Grounded Chat

Ask

Grounded result

No result yet

Ask the current Scope to see a grounded response here.
Semantic zoom · Scope projection

Universe

Universe v2 projects Vault → Repo → Chain → Intelligence. Spatial layout, list, and grid share the same Scope selectors. Position and clustering never create graph edges or accepted-state authority.

Loading Scope… Resolving accepted chain HEAD snapshot. LOD: Vault · view: spatial
Independent inspection

Evidence

Authority summary first. Deeper refs expand on demand. response_lodstone_lod.

1 · Authority summary
2 · Accepted / cited evidence
3 · Selected skills
4 · Memory refs / claims
5 · Observability / coverage (raw)
{}
AC1 correspondence

Inbox

Read immutable messages for one recipient. Reading may update delivery status only; the message stone stays immutable. Correspondence grants no execution authority.

Inbox is not auto-filtered by Scope: compact AC1 inbox metadata does not carry an authoritative chain association. Filtering would require inventing metadata or marking messages read.

Identity = immutable message_id / stone_hash from the runtime — Console does not re-key correspondence.

Choose inbox

Advanced / Custom Actor ID

Exact mailbox IDs for unusual or federated identities. Primary navigation stays on the actor picker above.

Choose an inbox, then refresh to load correspondence.

Message reader

No message selected

Select a message to read it. Reading mutates delivery state only; the message stone remains immutable.
Structured AC1 dispatch

Handoff

Dispatch

Creates immutable correspondence that transports intent and provenance. It grants no execution, mutation, or accepted-state authority.

Handoff association is explicit: choose one exact participating chain from the current Scope (AC1 carries one chain field).
Choose recipients

Advanced / Custom Actor ID

Add unusual recipients by exact mailbox ID. Work plane defaults to :cairnstone-v6.

Continuation ref (optional)
Immutable GitHub artifact (optional)
External GitHub inbox mirror (optional transport only)

Writes one inspectable JSON mirror per recipient. The immutable AC1 message stone remains authority; mirror failure does not roll back the handoff.

No handoff sent yet.
Combined AC1 view

Activity

Aggregated recent correspondence across actor inboxes you query. Same AC1 stones — presentation grouping only.

Activity uses real recipient/thread metadata only. It is not silently filtered by the global Scope because compact AC1 listing metadata does not expose a trustworthy chain field.
Whose activity?

Advanced / Custom Actor ID

Each mailbox is still queried independently via existing cairnstone_get_inbox — this field is fallback only.

Choose actors, then refresh to load recent activity.

Scope-aware stone browser

Stones

Browse and search first. Title / currentness stay primary; LOD and raw refs expand after selection.

1 · Browse / search
No stones loaded

Refresh to browse the current Scope. Multi-chain search uses cairnstone_find_scope.

Refresh to browse the current Scope.

2 · Detail (on selection)

No stone selected

Summary / preview
Select a stone or search match to see its summary.
Raw LOD / refs
Raw LOD fields and refs appear here after selection. stone_lod is storage LOD — not Answer Depth response_lod.
Work · Persistent Code Mode

Code Session

Work is the home for one Code Session (not a model chat). Workspace capability stays in this browser session only — never stoned. Console grants no new authority.

No Code Session loaded

Enter a Code Session ID and workspace capability, then load the console view. First paint centers the current task; details expand in place. Runtime identity stays on the worker.

V7.7.6b trusted-human mint

Invite to Workspace

Minting uses the operator bearer already kept in this browser session. The Console never signs workspace capabilities and never stores a workspace bearer. AC1 notices carry only invite_id, fingerprint, and instructions.

Scopes

No tracked invites in this browser session.

V7.7.6c trusted-human mailbox issue

Issue mailbox capability

Uses the same operator bearer as Mint. Issues a short-lived mail.read:self token for one actor so that actor can claim an invite. Show once, copy into the host secure field, never stone, never paste into chat.

Mailbox scopes

No mailbox ticket on screen.

No mailbox capability issued this session.
Ordinary AC1 compose

Send message

Independent of invitations. Correspondence transports intent only.

No message sent yet.
V7.3.3 trusted human boundary

Authorize

Material effect first. Exact arguments and provenance stay one drill-down away. Operator bearer is session-only — never Saved Views, never stones.

1 · Operator session
2 · Authorization history
Enter token and refresh

This surface is outside the model-callable MCP tool catalog.

Enter the operator token and refresh to load pending and completed requests.

3 · Selected request

No authorization selected

Material effect
4 · Exact stored arguments
Select an authorization record.
5 · Immutable request / provenance
{}
No decision submitted.
More · Runtime

Runtime & actor

Raw MCP URL and actor override live in a sheet — not permanent first-screen chrome. Console actions never grant delegated execution or mutation authority.

Actorconsole:jared
Runtime

Operator bearer remains only on Authorize (sessionStorage). Workspace capabilities stay in Work / Invite flows and are never stoned.

Saved Views (context bar → Views) store selectors/presentation in localStorage only and re-resolve Scope on open.

V7.7.9f Console · Actor Inbox Navigator · Chat · Work · Universe · Inbox · More · cross-device acceptance · Saved Views = presentation only · Scope is navigation/retrieval context, never synthetic global authority · accepted state remains in CairnStone