Skip to main content
Emberbase gives the workforce durable, visible context across conversations. It is not a hidden transcript dump.

​
Memory scopes

A teamspace is a path-scoped section inside Company Emberbase, not a separate database. Personal Emberbase remains isolated from company and team scopes.

​
What belongs in Emberbase

  • company, product, customer, or project facts
  • decisions and their rationale
  • team operating procedures
  • definitions used in recurring reporting
  • safe preferences and constraints that should survive one conversation
Do not store credentials, tokens, private keys, raw environment files, secret values, or unnecessary personal data.

​
Canonical pages

The company wiki includes structural pages: Search and read before writing. When a fact changes, update the narrowest existing source instead of creating a duplicate page.

​
Recall and provenance

Recall searches the canonical Wiki and returns excerpts with page paths and scope metadata. The visible page is the source of truth. Ask the agent to identify the source page when the distinction between recalled and freshly verified information matters.

​
Dashboard editing

The dashboard can browse, search, edit, and export Company Emberbase. Team views open the team’s section. My agent opens Personal Emberbase. Human and agent edits use the same canonical write path. Concurrent updates use content hashes so a stale writer must merge rather than silently overwriting newer knowledge.

​
Maintenance

Wiki maintenance checks canonical pages for structural and linking issues. Recall does not depend on a secondary memory provider.