Scenes

Every workflow becomes a scene: its data, its tools, the agent that runs it, and the history of everything it did. Everything else in Daslab exists to fill scenes with useful state, or to act when that state changes.

Cells on top, jobs below

A scene has two halves:

  • Its cells: values, tables, notes, views and connected sources such as a repository or a mailbox, each at the size and position someone chose.
  • Its jobs: every request, schedule and event that ran against the scene, with what it did.

Anyone with access to the scene sees the same cells and the same jobs.

The answer stays on top

In a chat, the answer arrives and then scrolls away under the conversation that follows. A scene puts the answer at the top: structured, current, the same for everyone. The jobs stay below it, as the record of how the answer was built and the place to ask for changes.

A scene tracks one thing your team cares about: "What's happening with deploys this week." "Top accounts by revenue, with their renewal dates." "Compliance status across the fleet." Each is a scene.

A workspace's setup serves every scene in it

Its root scene, the world, sits above every other scene. An account connected there can be used from any scene, and a model added there shows in every scene's model picker. A role given in the workspace carries into the scenes open to it; Roles has the rules.

Scenes nest further. A child scene shows in its parent as a cell you can peek into, and a formula in one scene can read a cell in another by its address, world/scene:cell.

What every scene has

  • Current values. A formula cell runs again when the scene is read and its value is older than its time to live, fifteen minutes unless the formula says otherwise. A connected cell reads its source itself.
  • Cells shared between scenes. The same cell can be in several scenes, at a different size and position in each. It is deleted only when no scene has it any more.
  • Sizes that decide what loads. A cell at icon size fetches nothing; bigger sizes show and fetch more. Cells has the sizes.
  • Scope. Tools and credentials resolve from the scene you're in. A scene holds what its workflow needs, and the agent's tools follow from that.
  • Members. Each scene has its own roles: make someone a member of one scene and a viewer of another.
  • Persistence. A scene is there between sessions. Leave it open, come back tomorrow, and its values are current.
  • Schedules. A job can start on a schedule, on an event or when someone asks, and the scene keeps every run.
  • Links. Every scene has a URL, and every job in it has a permalink backed by the commit chain. Send someone the permalink and they see what you saw.

The agent can write back to the systems a scene's cells come from. Those writes go through approval gates.

What's next

  • Cells: what a scene is made of.
  • Jobs: what runs in a scene.
  • Layers: one scene, several audiences.
  • Blueprints: a scene written as one JSON file.

Updated 2026-11-14