Bizzy

01 / 06

Every edit takes the same road

A cell edited by a person, a suggestion someone approved, a row from an import: all of it goes through one function, changes.ts. The function that writes the value writes a change_log row in the same transaction, one per changed field, grouped in a batch.

History is that log, and Undo writes the old values back as a new batch that points at the one it reverts. Nothing is ever edited around the log.

change_log
  entity, field     deal · year:2027
  old, new          the values
  actor             person, ai, import
  batch_id          undone together
  reverts_id        which batch it undoes

02 / 06

The assistant sees what you see

Bizzy is a tool-using agent on Mistral. It reads data only through the app’s own loaders, run as the person asking, so the numbers it states are the numbers their pages show. It explains how things work from help topics in English and Dutch.

It acts only after you confirm a card in the chat, through the same write path as everyone else. Deletions and bulk changes become suggestions instead.

03 / 06

Nothing changes until a person approves

The data steward runs cheap rule checks, such as deals without a PI, yearly values that disagree with the total, stale pipeline, typos and possible duplicates, then a Mistral pass over the open deals. Each finding is a suggestion with a fingerprint, so running the checks again never repeats one, and a dismissed one stays dismissed.

Review is one queue for the steward and the assistant. Approving applies the change as a batch signed by the approver, so it can be undone like any other.

04 / 06

Workspaces that share nothing

BISS is one workspace; any team at the university can start another. Isolation is enforced three times: each request carries exactly one workspace, a guard on the query logger flags any statement on a workspace table without the workspace condition, and the database’s own foreign keys tie every child row to its parent’s workspace.

1  request context   one workspace per request
2  SQL guard         unscoped query → error
3  constraints       composite foreign keys

05 / 06

Live, without a reload

Every committed batch makes Postgres notify the app. The live hub reads the batch back from the log, works out what each open tab may see and tells it, and the page refetches only what changed, holding back while someone is typing there.

Two people typing in the same text is a separate service on Hocuspocus. It reads and writes records only through the app’s signed internal routes, so permissions, the log and Undo still apply.

06 / 06

Open to other tools

Personal API tokens let scripts and MCP clients such as Claude use the same routes as the pages, under the same roles. A worker reads the change log and posts signed webhooks to Slack, Teams or n8n.

Sign-in is the shared BISS Keycloak that Case Law Explorer also uses. The whole app ships as one Docker image, plus the collab service, on the institute’s Coolify.