Skip to content

[Full Runtime][M2] Support KB Installer Contract For Eva Brain Source-Scoped Install #25

Description

@100yenadmin

TL;DR

Make the support KB installer/update docs match Eva Brain source-scoped install behavior.

Owner Repo

electricsheephq/openclaw-support-kb

Milestone

Full Runtime M2: Eva Brain / Company Brain Runtime

Why This Exists

The KB repo should be installable by agents without a one-hour repair loop. Its commands should use the supported GBrain source/import/update path and avoid repo-shape assumptions.

Acceptance Criteria

  • README install path matches Eva Brain updater expectations

  • Installer does not require a separate Voyage key from GBrain

  • Cron/update docs distinguish sync for git-backed sources from import for local-only sources

  • Scenario tests cover source registration and search

Proof / Validation

  • Fresh temp install can import/search KB content with --no-embed when no key is present

Boundary Reminder

Repo boundary rule

  • evaos-golden is the clone-safe customer VM baseline only. It owns runtime install scripts, service templates, local doctors, OpenClaw UI patches, Hermes/Eva Brain installers, and browser runtime setup.
  • evaos-support-control owns private support/control-plane operations: VM health, snapshots, guarded restarts, support runbooks, drift checks, alert policy, and rollout orchestration.
  • electric-sheep-website-dashboard-6158a244 owns customer/admin UI, Supabase migrations, runtime registry, product IA, support/admin actions, and usage ledger UI.
  • evaos-ws-proxy owns authenticated customer /vm/... routing into customer VM runtimes and must not own support mutations.
  • eva-brain is the intentional maintained GBrain fork for Company Brain, OpenClaw/Codex plugins, support KB setup, updater, and no-key OAuth extraction.
  • openclaw-support-kb owns support knowledge base content and the source-scoped install/update contract only.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions