Skip to content

Document and harden the local BYO-brain configuration surface #55

Description

@jeremylongshore

Context

The local/forker path already runs an in-process governed brain without a team API or API key, but the configuration contract was implicit. Make the BYO-brain setup discoverable and observable.

Acceptance criteria

  • Document TEAMKB_BASE_PATH, TEAMKB_TENANT_ID, and optional TEAMKB_EXPORT_DIR for fork/local mode.
  • Document the derived qmd index path: <base>/qmd-index/<tenant>, and distinguish it from the Markdown export tree.
  • Expose mode, tenant, base path, export directory, and qmd index path in brain_status.
  • Keep local mode zero-egress and tenant-scoped.
  • Cover config derivation with unit tests and the built runtime with a smoke assertion.
  • Keep installer/preflight output aligned with the same routing contract.

Tracking: bead iel-25a.5.3; umbrella tracking issue intent-eval-lab#287.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions