@rizom/ops 0.2.0-alpha.7 → 0.2.0-alpha.700

package/templates/rover-pilot/docs/user-onboarding.md

@@ -1,312 +1,90 @@
-# Rover Pilot User Onboarding
+# Welcome to your brain
 
-Welcome to the Rover pilot.
+---
 
-This document is written for **first-time users**. You do **not** need prior experience with Rover, MCP, git, or the rest of the system to get started.
+Most of us have more thinking happening than we can hold onto. Ideas show up in the wrong moment, notes land in five different places, and half of what you've figured out is effectively invisible by the time you need it again.
 
-## What Rover is
+Your brain is a private space where that thinking accumulates — notes, links, fragments, and half-formed ideas — plus an AI that can work with all of it. It can find things you saved months ago, connect topics, or help turn a rough note into a draft. The more useful material you add, the more useful it becomes.
 
-Rover is your private AI assistant for working with your own notes, links, and ideas.
+---
 
-In this pilot, Rover is intentionally simple:
+## What it is
 
-- you talk to it through an **MCP client**
-- **there is no website to browse**
-- Discord is optional
-- Obsidian fits through the git-sync/content-repo workflow, not as the main chat interface
+Your brain is a private knowledge companion. It holds your notes, links, and ideas and helps you think with them, not just store them.
 
-You can think of Rover as a private knowledge companion that helps you:
+Ask a question and it searches what you've saved. Give it a fragment of thinking and it can help develop it.
 
-- save notes
-- save links
-- reflect on your own material
-- find patterns in what you have collected
-- think through questions with AI
+## Getting in
 
-## What you will receive from us
+We'll send you a personal URL such as `https://<handle>.rizom.ai/`.
 
-We will send you the details you need to connect.
+The first time you open it, you will be asked to set a passkey. No password is required after that.
 
-That usually includes:
+Your main interfaces are:
 
-- your Rover URL: `https://<handle>.rizom.ai/mcp`
-- your **Bearer token**
-- confirmation of whether Discord is enabled for you
-- any extra instructions if we are testing a specific workflow with your cohort
+- **Chat** (`/chat`) — talk to your brain;
+- **Dashboard/site** (`/`) — the configured browser surface;
+- **Studio** (`/studio`) — edit durable content in a browser.
 
-Treat the **Bearer token** like a password. Do not share it.
+Start with Chat.
 
-## One important idea: MCP is just the connection method
+## Your first five minutes
 
-If you have never used MCP before, the shortest explanation is:
+1. Open Chat and say: _Help me save my first note._
+2. Save a thought, link, or idea. It does not need to be polished.
+3. Ask about it and inspect what comes back.
 
-- **Rover** is the assistant
-- **MCP** is the way your AI client connects to Rover
+That save–ask–use loop is the core workflow.
 
-You do not need to understand the protocol details.
+## Chat or Studio?
 
-For the pilot, the practical meaning is simple:
+**Chat** is for thinking aloud, asking questions, saving things quickly, and day-to-day work.
 
-- open a supported client
-- add your Rover URL
-- paste your Bearer token
-- start talking to Rover
+**Studio** is for deliberate browsing and editing. It becomes more useful as your content grows.
 
-## What to use first
+## Other interfaces and peer brains
 
-For most users, the easiest first setup is:
+Chat is primary. Your configured posture may also enable Discord, Slack, MCP clients, or agent-to-agent calls. We will send setup steps for integrations enabled for your instance.
 
-- **Claude Desktop** for talking to Rover
-- **Obsidian** only if you also want to work directly with markdown files later
-- **Discord** only if we explicitly enable it for you
+With permission, you can save another participant's brain as a contact and call it by its shared address:
 
-## How to connect
+- _Add jane.rizom.ai to my contacts._
+- _Call jane.rizom.ai and ask [your question]._
 
-Use an MCP client that supports:
+## Connecting other tools
 
-- **HTTP / Streamable HTTP MCP**
-- **Bearer token authentication**
+MCP is a standard protocol that lets compatible AI clients use your brain's tools and lets configured integrations connect to external services. If MCP is part of your setup, we will send specific instructions alongside your URL.
 
-When your client asks for connection details, use:
+## Common questions
 
-- **Server URL:** `https://<handle>.rizom.ai/mcp`
-- **Authentication type:** Bearer token
-- **Bearer token:** the token we sent you
+**How do I access my data?**
 
-If the client asks for a name, use something simple like:
+Use the Studio. If your cohort includes GitHub access, the same durable markdown also lives in a private repository.
 
-- `Rover (<handle>)`
+**Does it search the public internet?**
 
-## Claude Desktop setup
+Not by default. Answers are grounded in your own knowledge unless an explicitly configured integration provides another source.
 
-If your Claude Desktop version supports connecting to a **remote HTTP / Streamable HTTP MCP server**, enter:
+**What does this cost?**
 
-- **Server URL:** `https://<handle>.rizom.ai/mcp`
-- **Authentication:** Bearer token
-- **Token:** the token we sent you
+Nothing during the pilot; hosting is covered by the programme.
 
-Then try a first message like:
+## This is a pilot
 
-> What can you help me do, and what should I use you for?
+The product works, but it is not finished. You will encounter rough edges and missing behavior. If something breaks or falls short, tell us what you tried, what you expected, and what happened.
 
-Or:
+A built-in wishlist can record unsupported requests as product feedback.
 
-> Help me save my first note.
+## Your access details
 
-If your Claude Desktop version only supports local MCP servers and not remote HTTP MCP cleanly, tell us what version you are using and we will help you.
-
-## Your first 5 minutes
-
-Once you are connected, try this sequence:
-
-### 1. Check that Rover responds
-
-Ask:
-
-> What can you help me do?
-
-### 2. Save a first note
-
-Ask:
-
-> Save a note: I want to use Rover to collect ideas from my work, reading, and conversations.
-
-### 3. Save a useful link
-
-Ask:
-
-> Save this link and note why it matters to me: <paste URL>
-
-### 4. Ask Rover to reflect back what it knows
-
-Ask:
-
-> Based on what I’ve stored so far, what themes are starting to emerge?
-
-### 5. Use it as a thinking partner
-
-Ask:
-
-> I am thinking through a problem in my work. Help me structure the question and identify what context is missing.
-
-## Wishlist: when Rover cannot do something yet
-
-Rover has a built-in **wishlist**.
-
-This is important for first-time users because Rover will not be able to do everything yet.
-
-If you ask for something Rover cannot do, it should add that request to the wishlist instead of just failing silently.
-
-You can think of the wishlist as:
-
-- a backlog of missing capabilities
-- a record of things users want Rover to do
-- a way for the pilot team to see which missing features matter most
-
-### When the wishlist is useful
-
-The wishlist is especially useful when you ask Rover to do something like:
-
-- connect to a tool it does not support yet
-- perform an action it cannot perform yet
-- add a workflow or feature that does not exist yet
-
-Examples:
-
-> I want Rover to draft and send emails for me.
-
-> I want Rover to connect to my calendar.
-
-> I want Rover to summarize voice notes automatically.
-
-If Rover cannot actually do those things yet, it should tell you that and add the request to the wishlist.
-
-### What happens when something is added to the wishlist
-
-When a request is added to the wishlist:
-
-- it is saved as a **wish**
-- it starts in a **new** state
-- similar requests can be grouped together instead of creating endless duplicates
-- repeated demand can increase the count of how many times that wish was requested
-
-That helps us see which gaps are one-off ideas and which ones keep coming up across real usage.
-
-### How you should use it
-
-You do **not** need special commands.
-
-Just ask naturally.
-
-If Rover cannot do what you asked, a good response from Rover is something like:
-
-- it explains the limitation clearly
-- it says the request was added to the wishlist
-
-If that does **not** happen, that is useful feedback for us too.
-
-## Obsidian
-
-Obsidian is part of the pilot through the **git-synced content repo workflow**, not through MCP.
-
-That means:
-
-- use **Claude Desktop** as the main way to talk to Rover
-- use **Obsidian** if you want to browse, draft, and edit markdown files directly
-- Rover can pick up those file changes through the normal git-sync / directory-sync flow
-
-A simple mental model:
-
-- **Claude Desktop** = talk to Rover
-- **Obsidian** = edit the underlying notes
-
-If we have already shared your content repo workflow with you, the simplest setup is:
-
-1. clone your Rover content repo locally
-2. open that folder as an Obsidian vault
-3. optionally install the **Obsidian Git** plugin if you want in-app commit/push/pull support
-4. edit or organize your markdown notes there
-5. commit and push your changes through normal git or the Obsidian Git plugin
-6. let the normal git-sync flow carry those changes into Rover
-
-If we have **not** given you a direct content repo workflow yet, that is fine. You can ignore Obsidian for now and use Rover purely through MCP.
-
-## Discord (optional)
-
-Discord is optional in this pilot.
-
-If it is enabled for you, think of it as a lightweight secondary interface for:
-
-- quick note capture
-- dropping in links to save
-- short questions when you do not want to open Claude Desktop
-
-Important:
-
-- **MCP remains the main interface**
-- Discord is **off by default**
-- if you want Discord, tell us explicitly
-- for this pilot, Discord-enabled users may need to supply their own bot token
-- if Discord is enabled, we will send the exact invite/setup steps separately
-
-If Discord is **not** enabled for you, that is completely normal.
-
-## What to expect in the pilot
-
-This is a real working system, but it is still an early pilot.
-
-So you should expect:
-
-- some rough edges
-- a setup process that may still be a bit manual
-- a Rover that becomes more useful as you add more notes and links
-- occasional follow-up questions from us about your experience
-- improvements and changes during the pilot
-
-That is normal. The point of the pilot is to learn from real use.
-
-## Privacy and boundaries
-
-For the pilot:
-
-- your Rover is deployed specifically for you
-- access to `/mcp` is protected by your Bearer token
-- you should avoid putting highly sensitive material into the pilot unless we have explicitly agreed that it is in scope
-
-If you are unsure whether something belongs in Rover, ask us first.
-
-## Troubleshooting
-
-### I opened the domain and it does not look like a normal site
-
-That is expected. In this pilot, **there is no website to browse**. Rover core is MCP-first.
-
-### I got an authentication error
-
-Usually this means one of three things:
-
-- the Bearer token was missing
-- the Bearer token was pasted incorrectly
-- the client is using the wrong authentication type
-
-Double-check that you are using:
-
-- URL: `https://<handle>.rizom.ai/mcp`
-- auth type: **Bearer token**
-- token: exactly the token we sent you
-
-### My MCP client says it cannot connect
-
-Some clients support local MCP servers better than remote HTTP MCP servers.
-
-If that happens, send us:
-
-- the name of the client
-- the version you are using
-- the exact error message
-- a screenshot if possible
-
-## What feedback helps us most
-
-We especially want to hear:
-
-- what was confusing during setup
-- what felt useful immediately
-- what felt weak, awkward, or unclear
-- what you expected Rover to do but could not get it to do
-- whether you would keep using it after the pilot
-
-Short, honest feedback is perfect.
-
-## Quick handoff template
-
-When we onboard you, the message will look roughly like this:
+We will send details in this shape:
 
 ```text
-Rover URL: https://<handle>.rizom.ai/mcp
-Auth type: Bearer token
-Bearer token: <token>
-Discord enabled: yes/no
+Chat URL: https://<handle>.rizom.ai/chat
+Dashboard URL: https://<handle>.rizom.ai/
+Studio URL: https://<handle>.rizom.ai/studio
+Discord: yes/no — setup steps if enabled
+MCP: enabled/not enabled — setup details if enabled
 ```
 
-If anything is unclear, reply with the exact error text or a screenshot and we will help.
+If anything is unclear, reply with what you see and we will help.

package/templates/rover-pilot/package.json

@@ -3,7 +3,11 @@
   "private": true,
   "type": "module",
   "packageManager": "bun@__BUN_VERSION__",
+  "dependencies": {
+    "age-encryption": "^0.3.0"
+  },
   "devDependencies": {
+    "@brains/utils": "workspace:*",
     "@rizom/ops": "__BRAINS_OPS_VERSION__"
   }
 }

package/templates/rover-pilot/pilot.yaml

@@ -1,8 +1,14 @@
-schemaVersion: 1
 brainVersion: 0.1.1-alpha.14
-model: rover
+bundleContract: capability-bundles-v1
 githubOrg: <github-org>
 contentRepoPrefix: rover-
 domainSuffix: .rizom.ai
-preset: core
-aiApiKey: AI_API_KEY
+bundles:
+  - core
+  - media
+  - web
+  - chat
+openaiApiKey: OPENAI_API_KEY
+gitSyncToken: GIT_SYNC_TOKEN
+contentRepoAdminToken: CONTENT_REPO_ADMIN_TOKEN
+agePublicKey: age1replace-with-your-public-key

package/templates/rover-pilot/users/alice.yaml

@@ -1,3 +1,7 @@
 handle: alice
+anchorProfile:
+  name: Alice Example
+  description: Replace this with Alice's real public profile summary.
 discord:
-  enabled: false
+  enabled: true
+  # anchorUserId: "123456789012345678"

package/dist/origin-ca.d.ts

@@ -1 +0,0 @@
-export { createOriginCertificateRequest, generateOriginKeyPair, issueCloudflareOriginCertificate, setCloudflareZoneSslStrict, type CloudflareOriginCaResult, type FetchLike, type OriginCertificateRequest, type OriginKeyPair, } from "@brains/utils/origin-ca";

package/dist/push-secrets.d.ts

@@ -1,9 +0,0 @@
-import { normalizePushTarget, type PushTarget } from "./push-target";
-import { type RunCommand } from "./run-subprocess";
-export type SecretPair = readonly [name: string, value: string];
-export interface PushSecretsOptions {
-    runCommand?: RunCommand | undefined;
-    logger?: ((message: string) => void) | undefined;
-}
-export declare function pushSecretsToBackend(target: PushTarget, secrets: readonly SecretPair[], options?: PushSecretsOptions): Promise<void>;
-export { normalizePushTarget };

package/dist/push-target.d.ts

@@ -1,2 +0,0 @@
-export type PushTarget = "gh";
-export declare function normalizePushTarget(value?: string): PushTarget | undefined;

package/dist/run-subprocess.d.ts

@@ -1,5 +0,0 @@
-export type RunCommand = (command: string, args: string[], options?: {
-    stdin?: string;
-    env?: NodeJS.ProcessEnv;
-}) => Promise<void>;
-export declare const runSubprocess: RunCommand;

package/dist/user-secret-names.d.ts

@@ -1,6 +0,0 @@
-export interface UserSecretNames {
-    gitSyncTokenSecretName: string;
-    mcpAuthTokenSecretName: string;
-    discordBotTokenSecretName: string;
-}
-export declare function deriveUserSecretNames(handle: string): UserSecretNames;

package/templates/rover-pilot/.kamal/hooks/pre-deploy

@@ -1,9 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-BRAIN_FILE="${BRAIN_YAML_PATH:-brain.yaml}"
-SSH_USER="$(ruby -e 'require "yaml"; config = YAML.load_file("deploy/kamal/deploy.yml") || {}; puts(config.dig("ssh", "user") || "root")')"
-IFS=',' read -ra HOSTS <<< "$KAMAL_HOSTS"
-for host in "${HOSTS[@]}"; do
-  scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null "$BRAIN_FILE" "${SSH_USER}@${host}:/opt/brain.yaml"
-done

package/templates/rover-pilot/deploy/Caddyfile

@@ -1,66 +0,0 @@
-# Internal Caddy — path-based routing to brain services.
-# kamal-proxy terminates TLS externally; this runs inside the container.
-:80 {
-	@preview host preview.*
-	handle @preview {
-		reverse_proxy localhost:4321
-
-		header {
-			X-Frame-Options "SAMEORIGIN"
-			X-Content-Type-Options "nosniff"
-			Referrer-Policy "strict-origin-when-cross-origin"
-		}
-	}
-
-	# MCP endpoint
-	handle /mcp* {
-		reverse_proxy localhost:3333
-
-		header {
-			X-Content-Type-Options "nosniff"
-			Access-Control-Allow-Origin "*"
-			Access-Control-Allow-Methods "GET, POST, DELETE, OPTIONS"
-			Access-Control-Allow-Headers "Content-Type, Authorization, MCP-Session-Id"
-		}
-	}
-
-	# A2A endpoints
-	handle /.well-known/agent-card.json {
-		reverse_proxy localhost:3334
-	}
-
-	handle /a2a {
-		reverse_proxy localhost:3334
-
-		header {
-			X-Content-Type-Options "nosniff"
-			Access-Control-Allow-Origin "*"
-			Access-Control-Allow-Methods "GET, POST, OPTIONS"
-			Access-Control-Allow-Headers "Content-Type, Authorization"
-		}
-	}
-
-	# Plugin API routes
-	handle /api/* {
-		reverse_proxy localhost:3335
-	}
-
-	# Production site: proxy to webserver if running, otherwise serve
-	# a minimal static fallback so the healthcheck and bare-domain
-	# requests succeed even on the core preset (no webserver).
-	handle {
-		reverse_proxy localhost:8080
-
-		header {
-			X-Frame-Options "SAMEORIGIN"
-			X-Content-Type-Options "nosniff"
-			Referrer-Policy "strict-origin-when-cross-origin"
-		}
-	}
-
-	handle_errors {
-		root * /srv/fallback
-		try_files /index.html
-		file_server
-	}
-}

package/templates/rover-pilot/deploy/Dockerfile

@@ -1,38 +0,0 @@
-ARG BUN_VERSION=1.3.10
-FROM oven/bun:${BUN_VERSION}-slim AS runtime
-
-WORKDIR /app
-
-RUN apt-get update && apt-get install -y --no-install-recommends \
-    curl ca-certificates git gnupg debian-keyring debian-archive-keyring apt-transport-https \
-    && curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg \
-    && curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | tee /etc/apt/sources.list.d/caddy-stable.list \
-    && apt-get update && apt-get install -y --no-install-recommends caddy libcap2-bin \
-    && setcap cap_net_bind_service=+ep $(which caddy) \
-    && rm -rf /var/lib/apt/lists/*
-
-COPY deploy/Caddyfile /etc/caddy/Caddyfile
-
-RUN mkdir -p /srv/fallback && \
-    printf '<!doctype html><html><head><meta charset="utf-8"><title>brain</title></head><body></body></html>\n' \
-    > /srv/fallback/index.html
-
-ENV XDG_DATA_HOME=/data
-ENV XDG_CONFIG_HOME=/config
-RUN mkdir -p /app/data /app/cache /app/brain-data && \
-    chmod -R 777 /app/data /app/cache /app/brain-data
-
-CMD ["sh", "-c", "caddy start --config /etc/caddy/Caddyfile && exec ./node_modules/.bin/brain start"]
-
-# --- standalone: bake full project into image (brain-cli deploy) ---
-FROM runtime AS standalone
-COPY package.json ./package.json
-RUN bun install --production --ignore-scripts
-COPY . .
-
-# --- fleet: install published brain at pinned version (ops deploy) ---
-FROM runtime AS fleet
-ARG BRAIN_VERSION
-RUN test -n "$BRAIN_VERSION" \
- && printf '{"name":"rover-pilot-runtime","private":true}\n' > package.json \
- && bun add @rizom/brain@$BRAIN_VERSION

package/templates/rover-pilot/deploy/kamal/deploy.yml

@@ -1,39 +0,0 @@
-service: rover
-image: <%= ENV['IMAGE_REPOSITORY'] %>
-
-servers:
-  web:
-    hosts:
-      - <%= ENV['SERVER_IP'] %>
-
-proxy:
-  ssl:
-    certificate_pem: CERTIFICATE_PEM
-    private_key_pem: PRIVATE_KEY_PEM
-  hosts:
-    - <%= ENV['BRAIN_DOMAIN'] %>
-  app_port: 80
-  healthcheck:
-    path: /health
-
-registry:
-  server: ghcr.io
-  username: <%= ENV['REGISTRY_USERNAME'] %>
-  password:
-    - KAMAL_REGISTRY_PASSWORD
-
-builder:
-  arch: amd64
-
-env:
-  clear:
-    NODE_ENV: production
-  secret:
-    - AI_API_KEY
-    - GIT_SYNC_TOKEN
-    - MCP_AUTH_TOKEN
-    - DISCORD_BOT_TOKEN
-
-volumes:
-  - /opt/brain-data:/app/brain-data
-  - /opt/brain.yaml:/app/brain.yaml