Co-work Folder¶
The folder a person selects as their Co-work working boundary: what it owns on disk, what it contains, and the lifecycle entry point for setting one up.
Details¶
Co-work Folder¶
A Co-work Folder is the working boundary a person selects. It is an ordinary folder on the host that Co-work has been set up in, and it is the containment boundary for everything Co-work knows about the work inside it.
A folder owns two things on disk. .wbuddy/manifest.yaml declares which Work Buddy components the folder carries. .wbuddy/cowork/ holds the canonical store: the profile that names the folder's identity, the SQLite database behind its documents and claims, and the deterministic export that travels with the folder. Everything else beside the store is machine-local and stays uncommitted.
One folder may own many documents. Every document is addressed by a path relative to the folder root, which is why a folder can enclose no other Co-work folder: two folders that both enclose a file would each claim it under a different relative path and neither could see the other's record of it.
The folder is also the scope a person moves between. Opening a folder selects the documents, conversations, and claims beneath it; closing it puts them away as a set.
Children of this unit cover the folder's lifecycle. Start with cowork/folder/setup for how a folder is inspected, proven safe, and set up.