What it reads and writes

Part of team usage — that it writes nothing, which file's figures are in force, and what an unapproved or unreadable file shows.

It writes nothing at all: unlike status, it keeps no last_valid copy of the files it read, and unlike up, add and watch it opens no lock, writes no state and logs no line.

Which file's figures are in force is the approval's rule, the one status states: a file the owner approved whose budgets section is the approved one is read as it stands; a file whose budgets section differs is answered from the copy the approval stored, and one why-line says the file differs; a file never approved on this machine has no budgets in force at all, and says so:

the file was never approved on this machine: run `team approve`
the file differs from the approved one: `budgets` changed

A file that does not load, or cannot be read, cannot be resolved as the caller's own project — a caller who is not the owner reads no block of their own for it, the machine's counts and one fixed sentence per distinct line (note: .agents/team.yaml does not load (line 4): run team status for the reason) in their place — while the owner reads the loader's own messages and the figures the approval stored. When the caller's own project is resolved but no copy in force can be read, the block carries no name and no row: note: no figures (the file could not be read) and note: the approved copy of the team file cannot be read: nothing is shown by name stand for them.

What it reads — the stores and the files — is on the team usage page; the one refusal the stores folder can raise is on the refusals page.