Shape the idea before the first commit.
Write the spec, design the screen, and test the prototype in the same workspace as the work that ships it. Components, reviews, and handoff stay connected to the source.
Design beyond the first frame.
The canvas now carries reusable components, clickable flows, and a review path for changes made by people or agents.
Decide in the open, with a paper trail.
Draft an RFC from a structure the team already trusts, and write it where the work is - not in a thread scattered across three chat apps. Once it is signed off, turn its sections into tracked issues in one step. The doc, the decision and the work stay linked for good - so a spec read six months later still shows what actually happened to the work it describes.
- Runner sandbox RFC
- Secrets runbook
- Cycle 12 brief
- Agent conduct
- Why one workspace
Runner sandbox RFC
kapA job runs inside a sandbox that holds the only copy of a decrypted secret, and the sandbox is destroyed with the job.
Why not decrypt on the server
Because the server is the thing that gets read. A value that never leaves the sandbox cannot be found in a heap dump, a log line, or a backup.
Rotation
Rotating re-encrypts the store under a new workspace key. Runners hold the old key only until their next heartbeat.
Comments
Say what happens to a job that is killed rather than finishing - that is the case people will ask about.
Filed REZ-48 for the decommission case, which this sentence does not cover.
Filed from this page
Bring your next project.
Start free, with no card. Connect the agent you already use, hand it an issue, and approve its first merge today.