UB UrBrain

MVP management console

Operate UrBrain from one dashboard.

The first console should cover the day-one user and admin workflows: monitor workspace memory, review document deltas, manage access, and keep the UrBrain API plus StructuredMerge ingest stack observable.

Runtime choice

Rust Use Rust for the first interchangeable StructuredMerge provider behind the UrBrain core API.

MVP scope

Users + admins One console for workspace operators with admin-only management panels.

Ingest mode

Internal StructuredMerge is a private service behind UrBrain, not a separate customer product.

User surface

2 user workflows for the MVP.

Users need to understand whether their workspace memory is current, which sources changed, and what retrieval will see. The console keeps those controls close to the document versions and StructuredMerge artifacts that produced them.

Admin surface

2 admin workflows for safe operations.

Admins need access control, API key rotation, retention policy, audit exports, and service health without logging into the private API, worker, database, or StructuredMerge provider hosts.

Users

Workspace dashboard

Shows document health, recent ingest jobs, memory freshness, retrieval readiness, and adapter connection status for each workspace.

  • Upload a document
  • Review changed chunks
  • Search workspace memory

Users

Document and memory management

Lets a workspace operator inspect source versions, compare StructuredMerge deltas, re-run failed imports, and tombstone stale memories.

  • Open source versions
  • Replay an ingest job
  • Tombstone selected memory

Admins

Tenant administration

Gives admins account, organization, workspace, role, API key, retention, and deployment controls without exposing internal service credentials.

  • Invite a user
  • Rotate an API key
  • Set retention policy

Admins

Operations console

Tracks API, worker, PostgreSQL, pgvector, object storage, and StructuredMerge service health for hosted and isolated deployments.

  • Inspect service health
  • View ingest queue
  • Export audit trail

Why Rust for StructuredMerge now?

Ruby remains the most comfortable exploration language here, but the MVP should minimize hosted compute overhead and operational surfaces. The Rust provider lets the first product use the active StructuredMerge Rust stack behind the Ruby product API while keeping the provider contract open to Ruby, Go, TypeScript, or other runtimes later.

  • Ruby remains useful for product exploration and may become a provider when same-runtime deployability matters.
  • Go remains a good future portability target for compact self-hosted providers.
  • TypeScript remains best for browser/SDK surfaces and may support JS-first plugin ecosystems later.

Next engineering queue

The next clear backend steps.

The console can be built now. The core API remains the product control plane, while StructuredMerge runs behind it through provider contracts.

Next

API stack

Keep the Ruby UrBrain core API as the product control plane for health, account, workspace, document, ingest, and retrieval endpoints.

Next

StructuredMerge bridge

Expose the Rust StructuredMerge implementation as ur_brain-sm-rust, an internal provider with deterministic request and artifact contracts.

Started

System tests

Keep static console coverage now; extend to API-plus-worker happy paths against the configured StructuredMerge provider.