Skip to guide

Minds and review

Minds and review is where onemind keeps team AI guidance versioned and peer-reviewed. Open Mind to browse recent Minds or choose a Project; read the active content, version, related Projects, files, and History before proposing a change.

  1. A Team administrator can choose Add Mind, select its Project when applicable, and enter a name and content. The filename becomes [name].md. Click Create to create the Mind; creation is confirmed by the server and is an administrative action.
  2. To change an existing Mind, choose Update. This opens the pull-request page directly: enter a required title, optional details, and review the file list with a side-panel editor. Choose Cancel to discard, Save to keep a draft, or Send to submit for review.
  3. Submission does not change the approved Mind.
  4. A current administrator reviews the exact change and check findings in Notification. Clicking Approve and publish publishes the next immutable version; rejection leaves the active version unchanged. An administrator may review their own proposal when authorized.
  5. Check History, then sync the approved version.

Supported file types for Mind updates are Markdown, JSON, YAML, TOML, and plain text (UTF-8 only). Content for a new Mind is limited to 8,000 characters; files attached to an update are limited to 512 KiB each. Uploading a file into a draft does not approve or apply it.

If the base version changes or a check fails, preserve your draft, read the current Mind, and resolve the conflict before resubmitting. Deleting a Mind sends a review request; it stays visible until approval. A saved draft or pending request is not a published change. Team task progress and AI-tool interactions are tracked in Matrix tasks.

Browse and arrange Minds

The Mind section in the side navigation is the entry point to every Mind. Recent Minds appear at the top of the list; choose Show all to see every Mind in the team or Show less to collapse the list. Select a Project under Projects to see the Minds within it; click a Mind name to open its detail view.

Any signed-in team member can personalize the order of Projects and Minds in the sidebar. Drag a row to the desired position, or focus a row and press the Up or Down arrow key to move it. The order is per-user and saved to the server; it does not affect other team members' views. A save-confirmation message appears when the order is recorded. If the order could not be loaded on open, the default server order is shown.

From a Mind detail view, use the Previous Mind and Next Mind arrows to move between Minds without returning to the list.

The About panel in the detail view shows the Mind's current version, status (Active or Waiting for proposal), last updated date, who created and last updated it, related Projects, and attached files. File preview is text-only (UTF-8); binary files and files that are too large show a fallback message. Expand or collapse the About panel using the section toggle. The Mind purpose field, set at creation, is shown here as well.

When a Team plan change is in progress, all Minds enter a temporary read-only state. The About panel shows a notice; Update and Send are unavailable until the plan change completes.

Drafts and pull requests

Choosing Update on an existing Mind opens the pull-request page directly. The page lists the base Mind file and any attached files, shows the base version, and provides fields for a required title and optional details. You can add or remove AI-harness files (skills, hooks, prompts, rules — JSON, YAML, TOML, Markdown, or plain text, 512 KiB each) using the side-panel editor. The draft is not auto-saved; choose Save explicitly to keep it on this device without submitting.

If you navigate away with a draft in progress, a Leave this Mind proposal? dialog appears — choose Save and leave to preserve the draft on this device, or Keep working to return to the editor. When you return to the same Mind, a Load your saved proposal draft? dialog offers to restore the text and files from the saved draft. Choose Load proposal to continue from where you left off, or dismiss it to start fresh.

You can rename the Markdown file before sending (the filename must keep a .md or .markdown extension). Choose Send to submit the proposal for Safe Check and review.

Sending is blocked if the Mind is read-only, temporarily unavailable, or your session has expired; the page shows a specific message for each state.

Change a Mind title

Changing a Mind's displayed title is a separate approval flow from changing its content. Any signed-in team member can propose a title change: click the title in the Mind detail view, enter a new title (1–160 characters, no control characters), and choose Request approval. A pull request with the fixed proposal title Update Mind title is created automatically.

The current title stays unchanged until a manager approves the proposal. If the Mind changes while you are editing the title, a stale-data message appears; close and reopen the editor to use the current version before resubmitting. A title change cannot be sent while the Mind is in a read-only state.

Safe Check and Conflict Check

When you submit a pull request, the server automatically runs Safe Check — an AI-powered review that produces findings before the proposal reaches a human reviewer. Safe Check runs on every submission; no user action is needed to trigger it.

Conflict Check is the structural component of Safe Check. It compares the proposed Mind against all other active Minds and reports findings in three severity groups:

  • Blockers — deterministic conflicts that prevent approval. The proposal must be edited or rejected before the review can proceed.
  • Review — advisory findings that require explicit human acknowledgement before approval.
  • Overlap — lower-severity findings for awareness.

Each finding has a confidence level: Exact (deterministic), Heuristic, or Semantic. The 11 finding types are: duplicate identity, stale version reference, authority or scope violation, invalid assignment, duplicate assignment, protected claim collision, missing version reference, dependency cycle, competing resource ownership, contradictory instruction, and duplicated guidance. Each finding shows a stable fingerprint, exact source versions, and affected composition contexts for the reviewer's reference.

If advisory (Review-level) findings are present, the reviewer must check the review-confirmation checkbox — confirming they have reviewed every advisory finding and understand that no Mind authority is auto-resolved — before the Approve and publish action becomes available.

To run Conflict Check locally before submitting, use the Mind Check CLI command. Run onemind mind-check member with the --harness flag to check your harness files (up to 256 KiB each); run onemind mind-check manager with the --subject flag to check a subject Mind or package file. Mind Check is warn-only in the current release and never blocks sync by itself. Use --json to parse output programmatically. See the CLI command reference for the full flag list.

Review in Notification

Managers review incoming pull requests in Notification. Each request shows the exact proposed diff, Safe Check findings, and Conflict Check findings. To approve or reject:

  1. Open Notification in the side navigation.
  2. Select the incoming Mind review request.
  3. Inspect the proposed diff and any Conflict Check findings.
  4. If advisory (Review-level) findings are present, check the review-confirmation checkbox to acknowledge them.
  5. Choose Approve and publish to publish the next immutable version, or Reject to leave the active version unchanged.

An administrator may review and approve their own proposal when their team authorizes it. Blocker-level Conflict Check findings prevent the Approve and publish action; the proposal must be edited or the PR rejected before a clean version can be submitted.

If the approved Mind changes after a proposal was checked, Approve and publish can no longer publish it. The review shows that the proposal is out of date, and its author or any manager can choose Propose again on the current version. onemind creates a new proposal on the current version with the same title, details, files and author, runs Safe Check again, and marks the old one as replaced, with a link to the new one. If the proposal's edits overlap changes in the current version, nothing is replaced: the review shows the current version beside the proposal so the author can submit a corrected one. If the current version already contains the changes, Reject the old proposal to close it.

Notification also handles deletion review requests. The decision for a deletion request is separate from a content-change request; see Delete and recover a Mind below.

Move or duplicate a Mind

Any signed-in team member can move or duplicate a Mind to a different Project by dragging the Mind row to the target Project in the sidebar.

  1. Drag the Mind row to the target Project in the sidebar.
  2. Select Duplicate to keep the Mind in the source Project, or Move to remove it from the source Project.
  3. Mind Checker runs automatically before the request is sent; a completion note shows the checked version and hash.
  4. If Mind Checker cannot complete, no approval request is created.
  5. The request enters the manager approval queue in Notification.
  6. A manager approves or denies the change; the Mind appears in the target Project only after approval.

Any signed-in member can initiate a move or duplicate request, but only a manager can approve it. Moving a Mind is not automatically reversible; a second move request is needed to move it back.

Delete and recover a Mind

Deleting a Mind sends a review request to the team manager; the Mind remains visible until a manager approves the deletion. To request deletion, choose Delete from the Mind actions menu and confirm the dialog.

The manager reviews the deletion request in Notification and chooses Approve deletion or Deny deletion. Approving hides the Mind without permanently removing it; its governed history is preserved for recovery.

After a deletion is approved, the notification shows recovery options. To restore the Mind, choose Recover Mind. If the Mind's Project was also deleted, you must recover the Project first before recovering the Mind. Choosing Recover Project restores the Project and its Minds to the Mind panel without altering governed history. Recovery failure surfaces a specific error message; review the current deletion state and try again.