From 1e282ffb88ab78874eda755c764ded34a4aa8a95 Mon Sep 17 00:00:00 2001 From: Jorge Torres Date: Mon, 29 Jun 2026 21:16:03 -0700 Subject: [PATCH 1/3] docs docs --- docs/use-cases.html | 83 ++++++++++++++++++++++++++++++++------------- 1 file changed, 60 insertions(+), 23 deletions(-) diff --git a/docs/use-cases.html b/docs/use-cases.html index 937cb98740c..ff2c77bdfdd 100644 --- a/docs/use-cases.html +++ b/docs/use-cases.html @@ -241,18 +241,18 @@
Use Cases
-

Two things.
Automate and Create.

+

Two things.
Create and Automate.

Minds Cowork is built around two core primitives. Everything below is an expression of one or both.

-
Automate
-
Recurring tasks that run without you — reports, monitoring, workflows, digests.
+
Create
+
Documents, apps, and workflow tools built around how you actually work — yours to publish, share, and keep.
-
Create
-
Artifacts that used to take hours — apps, decks, docs, analyses, dashboards.
+
Automate
+
Recurring tasks that run without you — reports, monitoring, workflows, and scheduled operations.
@@ -269,6 +269,21 @@

Creators

+
+ Create +
Personal knowledge base
+
Upload your notes, docs, and bookmarks. Ask questions in plain language and get answers that actually reference your material.
+
+
+ Create +
Your brand playbook, always current
+
Connect your tone guidelines, past work, and campaign feedback. The agent synthesizes a living brand doc your whole team references — and updates it as you evolve.
+
+
+ Create +
A content ops app, built your way
+
Pitches, drafts, deadlines, and briefs in one tool — laid out exactly the way your team works, not a generic template someone else designed for someone else.
+
Automate
Content pipeline on autopilot
@@ -281,11 +296,6 @@

Creators

Feed a transcript or essay and get a Twitter thread, LinkedIn post, and email summary — automatically.
video → clips → captions → posts
-
- Create -
Personal knowledge base
-
Upload your notes, docs, and bookmarks. Ask questions in plain language and get answers that actually reference your material.
-
@@ -299,6 +309,17 @@

Operators

+
+ Create +
An ops dashboard wired to your data
+
A live view of your team's KPIs, queues, and blockers — connected to your actual data sources, laid out the way you think about the work. Publish it to a URL in minutes.
+
data → dashboard → publish → always live
+
+
+ Create +
Codify your process as a tool
+
That SOP buried in a Notion doc or a teammate's head — turn it into a working app anyone on the team can use. Step-by-step, context-aware, no engineering required.
+
Automate
Live data reports, written for you
@@ -334,18 +355,23 @@

Strategists

Ask across all your data
Query across docs, tickets, spreadsheets, and databases in plain language. No SQL, no dashboards.
-
- Automate -
Competitive research digest
-
Run a competitor sweep on a schedule. Every week you get a structured digest of what changed — pricing, features, messaging.
-
sources → extract → compare → report
-
Create
Synthesize feedback at scale
Feed support tickets, reviews, and survey responses. Get back themes, sentiment, and concrete product signal.
feedback → themes → insights → action
+
+ Create +
Turn analysis into a shareable app
+
Package a market analysis or research project into a live document teammates can query in plain language — no re-presenting the same deck every quarter.
+
+
+ Automate +
Competitive research digest
+
Run a competitor sweep on a schedule. Every week you get a structured digest of what changed — pricing, features, messaging.
+
sources → extract → compare → report
+
@@ -354,20 +380,31 @@

Strategists

◇
-

For everyone

-
Any knowledge worker with repetitive work
+

For every team

+
Anything you build is uniquely yours
- Automate -
Automate any multi-step task
-
If it involves reading something and writing something else on a schedule, the agent can own it.
+ Create +
Documents from your actual data
+
Proposals, playbooks, briefs, investor updates — written by the agent, sourced from your connected data, published in minutes. Not a template. Your content.
Create -
Build internal AI tools
-
Describe what your team needs. The agent builds it — a web app, a form, a dashboard — and deploys it, no engineering required.
+
Apps built for how you actually work
+
A deal scorecard. A support triage tool. An onboarding portal. Describe it, and the agent builds and deploys it — no engineering required, live URL included.
+
describe → build → publish → share
+
+
+ Create +
Encode your secret sauce
+
Every team has logic no off-the-shelf tool captures: a scoring rubric, a workflow step nobody else does, a way of reading the data that took years to develop. That uniqueness becomes a live tool — yours, not a template everyone else runs too.
+
+
+ Automate +
Own any multi-step recurring task
+
If it involves reading something and writing something else on a schedule — a report, a digest, a status update — the agent can own it end to end.
From b1dc096c5ec07c8665daaeeb6862e46dcaa577fd Mon Sep 17 00:00:00 2001 From: Jorge Torres Date: Tue, 30 Jun 2026 13:51:26 -0700 Subject: [PATCH 2/3] best practices on linear --- CLAUDE.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 9580f70d58e..a7810bc4f4d 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -127,6 +127,22 @@ new SHA in the superproject as one reviewable commit. remind you a teammate's pin bump left a module behind — run `make baseline` after pulling the superproject to align. +## Branch naming + +Linear is connected to GitHub (`mindsdb` org). Every branch must include a Linear issue ID so the PR is automatically linked to the ticket. + +**Format:** `-` — copy it directly from the issue in Linear (branch icon on any issue card). + +``` +eng-123-fix-sso-no-credits +eng-456-add-attachment-thumbnails +``` + +- The team prefix is **`ENG`** (lowercase in branch names: `eng-`) +- Linear generates the full branch name for you — always use that, don't invent one +- PRs opened from a correctly named branch auto-attach to the Linear issue; no manual linking needed +- Hotfixes that don't have a ticket yet: create the ticket first, then branch from it + ## Running locally (web browser mode) After initializing submodules, start the full stack with: From 57f0c305380a8b5dbc1b4f59a9cadd6f8a1ac9ad Mon Sep 17 00:00:00 2001 From: Jorge Torres Date: Wed, 1 Jul 2026 15:24:32 -0700 Subject: [PATCH 3/3] bump submodule pins to latest staging frontend, core_api, core_agent all pulled to current staging HEAD. Co-Authored-By: Claude Sonnet 4.6 --- backend/core_agent | 2 +- backend/core_api | 2 +- frontend | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/backend/core_agent b/backend/core_agent index 6b83930e510..b996122dd5e 160000 --- a/backend/core_agent +++ b/backend/core_agent @@ -1 +1 @@ -Subproject commit 6b83930e510a984aa822a2cc46a2143a4e94343f +Subproject commit b996122dd5ee5afcfa061722f0420b1e9b41e11d diff --git a/backend/core_api b/backend/core_api index cb075bdf792..cbea825630a 160000 --- a/backend/core_api +++ b/backend/core_api @@ -1 +1 @@ -Subproject commit cb075bdf79242d865f5e8809cedfa1debb63e519 +Subproject commit cbea825630a380b4c7cb8bf6cff2402177683ac7 diff --git a/frontend b/frontend index 4114336ee0c..f6d37c2861f 160000 --- a/frontend +++ b/frontend @@ -1 +1 @@ -Subproject commit 4114336ee0cf1a8a04c20a96f4a92f30fe059c66 +Subproject commit f6d37c2861fa3f92c22ffbb661d6d9c8d0f28b93