Caura / docs
Getting Started

Review

The place in Caura Prism for decisions waiting on a person — conflicting memories, skills to approve, near-duplicates and held writes — what each tab lets you decide, and who sees it.

Review answers one question: what is waiting on a person? Its line under the title reads "Decisions waiting on a person." Each tab is one kind of decision, for the tenant chosen in the switcher at the top of the sidebar. With no tenant chosen, a tab says so and offers Choose a tenant.

The same counts show as Waiting for you on Home and as Needs you above Memory › Memories, each linking here.

Who sees what

TabWho sees it
Conflictseveryone in the tenant
Skills to approveorg admins
Near-duplicateseveryone in the tenant
Held writeseveryone in the tenant, when governance is on for your organization

Conflicts

Contradictions Caura detected between a new memory and an existing one, waiting for a person to decide. Each card shows the Existing and the New memory side by side, with a link to each agent's memories in Memory.

  • Resolve: choose what should happen (for example replace, supersede, merge or mark as disputed), add a note if you like, and resolve. This records which action was right.
  • Dismiss: the detector was wrong; it is not a real conflict. Dismissals are how the detector's precision is measured.

The list starts on Pending; Resolved, Dismissed and All show past decisions.

Skills to approve

The review queue for skills your agents propose, across their lifecycle: To approve, Active, Quarantined, Rejected and All. Open a skill to read it, then approve, edit, reject, quarantine or defer it. See Skills to approve for the card and the actions.

Skill Factory is switched on per tenant. Where it is off, the tab says so: "Skill Factory isn't switched on for this tenant". It links to Settings › Tenant settings › Features, where it can be turned on.

The tab is for org admins only. Anyone else who follows a link to it is told it is for organization admins.

Near-duplicates

Memories that say nearly the same thing, from the latest near-duplicate scan. Each pair shows Memory A and Memory B and how similar they are. The page does not merge them: to have Caura merge near-duplicates automatically, turn on Auto-merge near-duplicates in Settings › Tenant settings.

Below the pairs:

  • Last scan: the latest scan's score for this tenant's memory.
  • Find near-duplicates runs a new scan, and shows what the last one found, merged and archived.
  • Past scans: when each scan ran, what started it, its score, the issues found, how long it took and how it ended.

See Memory hygiene.

Held writes

Writes held before they reach memory, each with the agent and session that wrote it. Nothing held is recalled until a person releases it.

  • Release lets the write go live.
  • Reject stops it; it never goes live.
  • Roll back session undoes every write of that session (you confirm first).
  • Open in inspector shows the held memory in full.

Every decision is recorded in Memory › Audit trail.

Held writes need governance, which is on for every organization unless it was turned off for yours. Where it is off, the tab is hidden, and a direct link says "Held writes aren't switched on for this organization", with Ask us to turn it on. See Governance.