Blueprints
A blueprint is a scene written as files: one JSON document for the structure, the notes and views beside it. Push one into your workspace and the scene is there, with its schedule running. These are the ones we ship, and each page shows exactly what is in it before you push.
PR Triage
Daily triage of open PRs on a single repo. Fork it, point it at your repo, connect GitHub. Optionally pipe summaries to a Slack channel.
Server Health
The scene we watch our own production with: a runbook, a rolling health log, and a daily probe. Needs no connected accounts: edit the runbook's endpoint table to point at your own systems.
Daily Sales Brief
Every weekday morning, the agent diffs the Sales Pipeline against yesterday, decides which changes are material, writes a brief, and emails it to the team. The scene IS the pipeline: edit a deal and re-run to see the brief catch it.
Customer Onboarding
Give it a name + email. It fills the contract, sends a welcome email, and creates the customer record. A mostly-symbolic program with one LLM step (the welcome copy).
Pushing one
Every blueprint on this page is served as the document itself. Push it straight from the URL, no clone:
daslab scene push https://daslab.run/blueprints/pr-triage.json --input repo=your-org/your-repoApply is idempotent, so pushing the same blueprint again updates the same scene instead of making a second one. What the document contains is on Blueprints; the folder form and the merge rules are on Export and import.