From sign-in to a shared story
Five steps describe the whole path through 4keys as it works today. Each one matches a control that exists in the Studio.
- Step 1
Sign in
The Studio lives at /studio/ and sits behind Cloudflare Access. Access is invite-only: if your address has not been added, the sign-in attempt is refused before the application is reached.
- Step 2
Create a project
Use the Projects control in the Studio header to create, switch, rename, or delete a project. A new project starts from the checked-in deck structure, and every project belongs to your account alone.
Edits save to the cloud automatically. The save indicator in the header always states whether the current revision reached the server.
- Step 3
Direct a block
Select a block on the artifact stage, choose a Skill for how the work should be done and a Model to run it, then write the direction. The selected block is the boundary: nothing outside it can be changed.
The result arrives as a proposal in the Director panel. Apply it, reject it, or undo it afterwards. Long-running jobs report their status and can be cancelled or retried.
- Step 4
Publish
Open Publish project, pick the slug, and publish the revision that is currently saved. The server refuses a publish whose revision does not match the stored one, so save first.
Publishing writes an immutable snapshot. Later drafts do not alter it; republishing creates a new version number.