Skip to content

Work in a Project conversation to describe a change, review its approach, and inspect the resulting source or preview. Keep the request tied to a user action: what someone should enter, see, and be able to change. The Project can have multiple conversations; each keeps its own discussion and delegated work.

Check the working result

Open the working preview and complete the core path yourself. For a form, submit valid and incomplete inputs. For a dashboard, check that it reflects the data you expect. Ask for a correction when the behavior differs from the goal, then inspect the updated preview. Previewing changes does not update production.

Project source can include conventional routes, APIs, schemas, and background behavior within supported environments. The application owns its visitor permissions and validation. Use the Project's source and Git history to inspect what changed; save a checkpoint before a consequential revision so you can compare or recover development work. Validate the affected behavior in the working preview before release. See Data before relying on persistent application state, and Site releases when the change is ready for visitors.

Repeat a development task

For recurring development work, use a Schedule with a self-contained objective, such as reviewing dependencies and reporting necessary changes. Inspect the occurrence result before acting on it. Scheduling development work does not authorize a production release.

Tests

Isolated Project Tests evaluate a separate development working copy and return findings to the parent Project. Availability depends on configured services, required data structures, and runtime capabilities. See Testing for prerequisites and current verification limits. Review external connections separately: their credentials can authorize effects outside Playbooks.

Validate the core user path in the working preview, inspect the source and change history, and fix mismatches before considering a Site release. A working preview does not by itself prove production readiness.

Data

A Project can use development database, Storage, and background work where configured. These serve the working application and its preview. A Site has separately scoped production data, credentials, jobs, and usage; a working preview does not read or change them by default.

Design for the application

Describe the information the application must store and who may access it. The application's code owns its schema, validation, routes, and business permissions. Review changes to existing data carefully before release, especially when a schema change may affect a running Site. A code rollback does not undo data changes or external effects.

Files used as Operator context, Project source, and application Storage are different things. Services explains saved inputs and outputs; configuration covers development settings and authorized connections.

Example: change a request workflow

Ask for one observable change: “Add a priority field to requests, default it to Normal, and let authorized reviewers update it.” Review the form, saved record, and list display together.

Check both new and existing records, then verify that an unauthorized user cannot change priority. A visual field alone does not prove that validation, persistence, or access is correct. See Testing and Databases.