Circle

A world opens where the CircleTask BubbleTask Bubble closes.

An admitted InvocationJob RequestJob Request opens a CircleTask Bubble for one answerable act. Caller and Called meet within it with ana IntentRequestRequest, SigilID BadgeID Badge, ContextBriefing PackBriefing Pack, selected memory, capability, and authority. Holding these together gives the act a boundary within which its consequences can be attributed.

That boundary sits inside larger ones: a BridgeChatChat séance sustains a continuing relation, and a host gives one LichAssistantThe Assistant a place to answer. The same figure thus appears at several scales.

Summoning Circle — this Lich's enduring host boundary
└── Altar / Bridge — a continuing séance
    ├── Circle — one admitted Invocation
    │   └── casting — performance of one exact Scroll
    └── Circle — another Invocation, with its own Run

Admission begins the CircleTask Bubble. Its RunJob RecordJob Record gives the act durable execution identity, whether or not a browser draws a ring. Several people, Agents, Postures, or model powers can take part. Each retains attribution, separate authority, and the ability to refuse; meeting within one CircleTask Bubble creates neither a fused super-Sigil nor an identical interior.

The casting inside the Circle

Spellweaver admits the exact ScrollWorkflow VersionWorkflow Version, an immutable PatternWorkflowWorkflow revision. Its placed SpellsStepsSteps name the semantic actions the casting may perform. A placement can request an Agent, tool, Gate, effect, delegation, or typed capability; admission and authority still determine whether that request may be met.

An admitted Animator supplies Animus, active capability power through its Connector and exact CapabilityGrant. Graph gives casting typed movement; model and tool returns remain candidates. Within Spiritmind officemind office's present Flux, Blade discriminates and Answer binds the act. Many participants may help it arrive; one local Answer remains responsible for what it binds.

What Bridge can show

The compact CircleTask BubbleTask Bubble beside a reply shows supplied RunJob RecordJob Record status and activity, with Look into the OrbRun InspectorRun Inspector and an explicit Cancel RunJob Record for an eligible nonterminal projection. Expand CircleTask Bubble to read the full RunJob Record identity, supplied PatternWorkflowWorkflow revision and delegated-job identity. View declared score opens LoomWorkflow ViewerWorkflow Viewer only when its supplied path matches that exact PatternWorkflow revision. These are navigation hints; LoomWorkflow Viewer still verifies the RunJob Record's pinned manifest before offering a contextual return.

Older retained replies may lack RunJob Record status or a declared score. Circle identifies those omissions and offers the RunJob Record evidence link without inventing the missing metadata. A mismatched RunJob Record projection is reported and cannot supply status or actions for another RunJob Record. Consent remains beside its own request and decision controls.

Circle is the conceptual pinnacle inside BridgeChatChat, not a separate AltarControl PanelControl Panel instrument. No composed CircleTask Bubble workspace, active-Spell map, ContextBriefing PackBriefing Pack/authority inspector, participant-attribution view, or cross-instrument focus mode is delivered.

Follow Bridge to offer ana IntentRequestRequest, answer consent, or recover an uncertain offering. Choose Look into the OrbRun Inspector beside the turn to inspect that RunJob Record's evidence.

A future focus within BridgeChat may gather the authorized views of one InvocationJob RequestJob Request in one place. LoomWorkflow Viewer would supply its exact score and casting state; the account would show Caller, Called, SigilID BadgeID Badge, ContextBriefing Pack, budgets, and consent; NexusModel Status BoardModel Status Board would supply capability and AnimatorModel RuntimeModel Runtime observations; OrbRun Inspector would supply bounded traces. Each view must remain reconstructible from its owners. A selected node, animation, open stream, or model utterance alone cannot establish progress or authority.

What can outlast the act

The RunJob RecordJob Record remains ledger truth. Oculus and the Orb expose traces of activity, with their gaps and limits intact. A trace cannot replace RunJob Record, consent, effect, or artifact truth.

Memory policy may preserve attributable residue as a Seed, a trace with potency to shape a later InvocationJob RequestJob Request. Ouroboros names that formative return through evaluation, attribution, consent, memory policy and RecallMemory SeedMemory Seed. Repeating a GraphStep MapStep Map cycle alone does not accomplish it.

The greater Summoning Circle

In Summoning, the MagusYou, the OperatorYou, the Operator draws the enduring boundary around this host: CodexSettings FolderSettings Folder, CryptData FolderData Folder, local identity, AnimatorsModel RuntimesModel Runtimes, mounts, secrets, and reach. Code builds the BridgeChatChat; these choices determine the conditions under which its LichAssistantThe Assistant may answer. They must become inspectable configuration and security boundaries.

Each InvocationJob RequestJob Request opens a smaller living CircleTask BubbleTask Bubble within those conditions. At either scale, authentication, policy, capability admission, consent, and effect authorization retain their own work. The symbol makes their relation visible; it cannot perform it.