Collections, notes & activity

A project that grows needs structure, notes, and a record.

Collections

Collections are folders across every kind of thing in a project. Every project has the same skeleton, in this order: Scope (the scope doc and kickoff material), one collection per workstream, and Deliverables (what the client receives) — the project root stays empty. Create one from the sidebar (New collection), nest them, reorder them with Move up / Move down in a collection's ⋯ menu, and file what belongs to each.

Open Details on anything to see its collection and change it; each thing lives in at most one. A project's Data and Artifacts pages list everything, filterable by kind and searchable; each collection's page does the same for what is in it.

Notes

Everything has Notes — where agents keep what they need to carry on: how a thing was built, its sources, its caveats, what to check next time. Open Details, then Open notes. A project's notes are the job's state, kept by agents for agents: where it stands, what was decided, what is still open. What you read and approve lives in docs — the scope (a doc in Scope), the findings. Agents read notes before they act, so any session, yours or a colleague's, picks up where the last one stopped. When the data changes after the notes were written, they show May be out of date.

Activity

Activity, at the bottom of a project's sidebar, is its record of who did what: every import, run, save and edit, in order, agents included. Every entry links to what it touched.

Finding things

⌘K opens the command palette from anywhere: everything in the project, pages and actions in one box. The Overview's Lineage card opens the whole graph full screen; Details on anything shows what it reads and what reads it.

Faster with an agent — ask your agent to "write the scope for this project: the decision, the questions, what's in and out." It writes a doc in Scope for you to approve, and keeps the project's notes current as it works.