Team notes
Team notes hold facts about the tools and the place, at two levels (the install's and each project's). Which chats and runs read which, and how a manager writes each.
01what they are#
A team note is a short text of facts about the tools and the place, never opinions about the work: "runs have no network", "the tracker is a separate deploy". The note named common reaches every side chat and run node; a note named for a role (designer, reviewer) reaches that role. Each save keeps the earlier text as a version.
02two levels#
- The install level:
<team notes dir>/common.mdand<team notes dir>/<role>.md. Every project reads it. - The project level:
<team notes dir>/projects/<project>/common.mdand<team notes dir>/projects/<project>/<role>.md. Only that project reads it. The folder is named for the project's name in the registry, and is created on the first write.
03who reads what#
- A chat in project P that works as a role gets the install note under the heading
this install:, then P's note underproject P:. - A general chat, which belongs to no project, gets the install level alone, with no heading.
- A run's persona nodes get the same pair for the run's project, from the
team_projectkey of harness.json that the desk lays in. - A chat with no role gets no team notes.
04writing#
Only a project's manager writes notes, with team_note_write and team_note_edit. Both take an optional scope:
project, the default, writes the note in the manager's own project folder.installwrites the install-level note that every project reads.- Any other value is refused.
The result says where the note landed: its scope and path. A project name that is not a flat folder name (for example ../x or a/b) is refused, with an error naming it. team_note_edit in project scope edits that project's note only; if the project has none yet, write it first.
05existing notes#
Notes written before the project level stay at the install level. Nothing moves on its own; moving an install note into a project's folder is a hand edit.