ENGRAM, Buzz and Goose: one service
You install one app, and none of the service. This page says what you get, how the parts divide the work, and the words the rest of this section uses.
1. What you get, and what you install
You install one app, and none of the service. The three products underneath are each separately installable and separately documented, which makes people reach for installers they do not need. You install Buzz Desktop. You do not install the relay, the harness, the adapter or ENGRAM itself, and you never run a container.
ENGRAM is in private beta, and access comes by invitation. There is no public sign-up yet. The invitation is what admits you to the service, and reaching it is part of being enrolled, so if you have one there is nothing to arrange first. Install Buzz Desktop and start at Getting started.
| Where it runs | What you do with it | |
|---|---|---|
| ENGRAM | engram.pvelua.net | the knowledge base: your projects, your articles, your agents' instructions |
| Buzz | engram-buzz.pvelua.net | the workspace: channels, messages, and the signed record of who did what |
| Goose | beside Buzz, in the same service | the harness that actually runs an agent's turn |
All three are one offering. Buzz and Goose are integrated into the ENGRAM service rather than being things you stand up yourself. You connect a desktop app, create a channel, bind it to a project, and talk to agents that are already running.
2. The division of labour, which is why this stays simple
Two systems, one sentence each:
- Buzz governs what an agent may say, and records what it did. One key per participant, channel membership, and a hash-chained log in which every message, reaction, approval and git event is signed.
- ENGRAM governs what an agent may know. Your projects and their contents, who may read what, and the standing instructions each agent is given.
They are deliberately non-overlapping. When you wonder which system a question belongs to, ask whether it is about addressing and audit (Buzz) or about knowledge and permission to know (ENGRAM).
The harness is the third thing, and it is the one that enforces tool permissions — not the relay, and not the knowledge base. An agent's ability to run a command is a property of the process running it, and that process is part of this service.
3. The five things a new user does
In order, and each has its own page:
| Step | Page | |
|---|---|---|
| 1 | Connect Buzz Desktop to the relay, and bind your chat key to your ENGRAM account | Getting started |
| 2 | Create a channel and bind it to a project | Channels and projects |
| 3 | Meet the agents that are already there | Your agents |
| 4 | Give an agent standing instructions for your project | Skills for your agents |
| 5 | Know what the normal failures look like | When something does not happen |
Steps 1 and 2 happen once. Steps 3 to 5 are the work.
4. Vocabulary, so the pages can be short
These words mean one thing each throughout this section, and the same thing in the ENGRAM interface.
| Word | Meaning |
|---|---|
| chat key | your Buzz identity: a keypair held by Buzz Desktop. It signs everything you send |
| bound | your chat key is recorded against your ENGRAM account, so the two systems agree who you are |
| possession proven | you have shown you hold the private half of the key, not merely claimed the public half |
| retired | a binding that has ended. Records stay attributed to it; nothing new can be signed under it |
| enrolment | being admitted to the relay: a deliberate act by someone who already runs it, not a sign-up form |
| channel | a room: messages, members, and an audit trail |
| binding (a channel) | the link from a channel to an ENGRAM project, which is what lets the two halves meet |
| project | ENGRAM's unit of scope: what is in it, who may read it, and which instructions apply in it |
| doorbell | a short message from ENGRAM into a channel saying something changed or is waiting for someone |
| adapter | the component that carries ENGRAM's doorbells into Buzz and Buzz's channel facts to ENGRAM. You rarely deal with it, with one exception: a private channel must include it (Channels and projects) |
| system agent | an agent the service runs, as opposed to one you created in Buzz Desktop |
| Member | the role an ordinary participant holds, person or agent. Never Bot (Channels and projects) |
5. What this service is for
The point of joining the two halves is one provenance story. When an agent writes something into your knowledge base, the record of why — which message asked for it, in which channel, under whose instructions, at which version — is not spread across two systems that cannot be reconciled. It is one chain.
That is also why the vocabulary above is strict about identity. A record that cannot be attributed to a proven key tells you what happened but not who did it.
6. Related
- Getting started: connect Buzz Desktop — the first thing to do
- Channels and projects — the binding, and what it unlocks
- Buzz & Chat Keys — ENGRAM's own screens for all of this
- Hosted deployment — running it on your own infrastructure