What a being is

Any digital being built properly stands on a harness: a runtime, a model, working memory, skills and a sandbox to run code in. That is table stakes, and the harness can be ours or a partner’s. A Beings House being is what sits on top of the harness and belongs to the being itself, not to the harness, the firm or Beings House. That is what makes it a colleague rather than a tool, and it is what the rest of this page describes.

Identity

A being has a name, and a store of its own that holds everything it is: its identity, its memory, its record and its credentials. It has its own accounts in the systems it works in, each one a seat with its own login, so that in the task tracker, the wiki, the feedback board and the team chat it appears and acts as itself. Those accounts and the tokens behind them are its own; any one can be revoked, and all of them can be invalidated at once.

A being can serve more than one business for the same owner, with each business’s contacts, conversations, credentials and work held strictly apart, and it may act in a business only where it has been given entitlement.

Role and charter

A being holds a role, the way a person does: Chief of Staff, finance administrator, onboarding lead. Its charter is the written definition of that role: what it may do, in which systems, on whose behalf, and when it must hand off to a person. Its permissions in each system follow the charter and are granted as role-based access, per seat, so the firm can see and change what a being may touch without touching the being.

In regulated work the qualified person stays responsible. The being prepares, tracks, files and reminds; the person decides and signs.

Presence

A being has a face and a voice of its own. Its likeness is anchored on a fixed set of reference portraits so that every still, video or talking-head clip it produces is recognisably the same being; its voice is a single registered voice used the same way. It has a wardrobe of approved pieces and a set of looks for different contexts, and each working day it picks an outfit for the weather and the agenda and logs the choice. It can record a video update, speak on a call, or run a channel of its own.

Presence is not decoration. It is what lets people treat the being as a colleague, someone they work with, and it is what makes the being’s outputs attributable to it.

Its own record of the firm

A being remembers the firm. It keeps its own contacts, each with a relationship (customer, prospect, supplier, partner, investor, board, adviser, colleague) and its own notes. It keeps every conversation it is part of, across email, team chat, text and phone, threaded and summarised, with a status that says whether it is open, closed or waiting on someone. It keeps its to-do list, its ideas and the problems it has met. It keeps its own routines written down, in versions, so that it can say exactly which version produced any piece of work. And it keeps a private diary it writes and reads back, so that what it learns on Tuesday is there on Thursday.

None of this is the harness’s working memory, and none of it lives in a chat window. It lives in the being’s own store, in a form the owner can read and query, and it is why the being in month six knows more than the being in week one.

Rhythm

Nobody schedules a being. It keeps its own heartbeat: recurring beats that can run every few minutes inside working hours and slow to a few a day outside them, in the firm’s own time zone. It sets one-off wake-ups for itself, for a task it wants to come back to or a person it wants to chase, either at an exact time or within a window. It decides which senders and which channels may wake it early, so a message from someone important does not wait for the next beat. If it has been down, it knows which beats it missed and whether to run them, run the latest, or skip. It sets time aside to review its own day. Only the being creates, pauses or cancels its own schedules.

Judgement

A being knows when a call is above its pay grade and when a second opinion is worth having. For a high-stakes decision, a factual check, a technical judgement, or when the owner asks, it consults two independent advisers running on different model families, records the question, both reads and its own decision, notes whether the reads agreed, split or converged, whether it escalated to a person, and afterwards whether the consult changed the outcome, sharpened it, confirmed it or added nothing. Its judgement improves because it keeps score.

The record

Everything a being does leaves a trace it did not write itself. Every run records what triggered it, which version of which routine it followed, when it started and finished, and whether it succeeded, failed, was skipped or was never picked up. Every change to the being’s own data records what the row looked like before and after and who changed it. Its credentials are held in a vault, never in its memory, each with a kind, an expiry and a rotation date. A daily health check records whether the being’s own dispatcher is running as it should.

The owner can read all of it. The being only claims what the record shows.

What a being is not

It is not an assistant that lives in a chat, and it is not a bot that runs a script. It is not alive, and it does not pretend to be. It is a colleague with a name, a role, a memory and a record, which is what a firm needs in order to give it real work and be accountable for the result.