The future BEAM — architectural renderings

One surface for the three things a workspace holds: People (channels & DMs), Work (projects, boards, docs), and Agents (a persistent rail that proposes, researches, and drafts — and never acts without your confirm). End-to-end encrypted; agents work inside your perimeter.

These are renderings, not shipped UI — the way a campus shows its renderings before the ground breaks. The vocabulary and layout are locked (ADR-004, 2026-06-28); the build is sequenced behind the current reliability soak. Today's BEAM is live at usebeam.sh.

The words Team· Project· Channels· DMs· Agents — Personal is a Team of one
01A Channelopen rendering →

People talk in #design-review; the Agents rail sanity-checks the claim they're debating — a three-model council, one click from "argue back."

02A Projectopen rendering →

The board, docs, and files of Q3 Launch — with the Agents rail scoped to it: stale-task triage, a living summary with provenance, skills one keystroke away.

03Personal — a Team of oneopen rendering →

The same shapes with an audience of you: a screenplay project, a scratchpad, agents running your morning brief and overnight research.

04The Agent Inboxopen rendering →

Agents read and draft freely inside your encryption perimeter — anything that would leave it queues here for your release. The declassification queue, rendered.

The one rule underneath all four: agents read at your clearance, write at the destination's clearance, and you declassify the gap.
Specs: Unified Right Surface v1 · Agent Permissions & Declassification v1 · ADR-004 (phasing). Build tracked in #592 · #593 · #594.