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 runsWhat you do with it
ENGRAMengram.pvelua.netthe knowledge base: your projects, your articles, your agents' instructions
Buzzengram-buzz.pvelua.netthe workspace: channels, messages, and the signed record of who did what
Goosebeside Buzz, in the same servicethe 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.

Would you rather run it on your own infrastructure? A hosted deployment, with ENGRAM, the Buzz relay and its agents in your environment, is supported, with an operator guide for the team that runs it. See Hosted deployment. Nothing on this page is needed for that, and nothing in the operator guide is needed for this.

2. The division of labour, which is why this stays simple

Two systems, one sentence each:

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:

StepPage
1Connect Buzz Desktop to the relay, and bind your chat key to your ENGRAM accountGetting started
2Create a channel and bind it to a projectChannels and projects
3Meet the agents that are already thereYour agents
4Give an agent standing instructions for your projectSkills for your agents
5Know what the normal failures look likeWhen 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.

WordMeaning
chat keyyour Buzz identity: a keypair held by Buzz Desktop. It signs everything you send
boundyour chat key is recorded against your ENGRAM account, so the two systems agree who you are
possession provenyou have shown you hold the private half of the key, not merely claimed the public half
retireda binding that has ended. Records stay attributed to it; nothing new can be signed under it
enrolmentbeing admitted to the relay: a deliberate act by someone who already runs it, not a sign-up form
channela 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
projectENGRAM's unit of scope: what is in it, who may read it, and which instructions apply in it
doorbella short message from ENGRAM into a channel saying something changed or is waiting for someone
adapterthe 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 agentan agent the service runs, as opposed to one you created in Buzz Desktop
Memberthe role an ordinary participant holds, person or agent. Never Bot (Channels and projects)
One of these is a trap, and worth reading twice. Bound and possession proven are two different states, and only the second means your ENGRAM account and your Buzz identity are provably the same person. A binding that was never proven still shows your name.

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.