20. Projects
A project, scienting-project/1, is the unit a team works in.
| Part | Holds |
|---|---|
key, store, name, description | Its identity. |
members | People with a role (owner, editor, reader or guest) and the roster keys they sign with. |
documents | The project's documents, each with the reason it is included, tags, and a reading status per member: unread, reading or read. |
paths | Reading paths: ordered steps through documents, nodes, claims and layers, for onboarding a student or preparing a reading group. |
layers, datasets, views, drafts | What the project holds. |
claims | The claim namespace or bundle it uses, as the lode setting. |
settings | The digit rule for targeted F3 (8.10), the drift threshold (6.6), the spot-check rate and minimum (8.8), what happens when a right is unknown (refuse, the default, or warn), the stage requirements in use, as the id of their stage file (14), and the project's transparency log: its origin, the roster keys that witness it, and the threshold of witnesses a checkpoint needs (23). |
Projects are small on purpose: everything about them is designed for hundreds of documents, not millions.
Owners sign policies (14.2).
Who may revoke receipts follows the roster instead: a key whose role in the roster is owner (8.7), so a project's owners hold keys with that role.