Arbetsloopen

where it left off

Reads one folder's current state before any work resumes: loop position and whether the next agenda exists, whether the carry-forward chain is intact, what is carrying and how much of it is unowned, how stale the archives are, what is staged and unsent, and when the record last moved. Read-only - it writes nothing, fetches nothing and caches nothing, because an orientation file that persists can itself go stale and then lie

$ /ops orient <folder>

läser the summary, _outbox/<item>/_manifest.md, <venture>/.teamschats/, <venture>/.githubmeta/ → ger a reading of the current state

the folder's config

Declares which chat and repositories the work concerns, which post-meeting artifacts the series wants, and where its task ledger lives

$ edit <project>/.claude/ops-config.yaml, or the folder's _ops.yaml

ger the config

the fetchers

Fetch the chat and repository archives. External CLIs, run on demand or on a schedule - never by a skill

läser the config → ger <venture>/.teamschats/, <venture>/.githubmeta/

the agenda

Writes the agenda: what did not land last time, with its session count and age, then what the archives hold that the room has not heard — the script leaves a digest slot, and the agenda is a draft until prepare has read the messages and filled it (CR-101)

$ /ops prepare (runs build_agenda.py where the loop is wired); /preparation without a config

läser <venture>/.teamschats/, <venture>/.githubmeta/, the summary's carry-forward section → ger the agenda

the meeting

Recorded, so everything asynchronous is invisible to it by construction - which is what the archives exist to answer. The transcript ARRIVES BY SEVERAL ROUTES - a recorder into a knowledge base read over MCP, a file dropped in, or text pasted straight into the session. The loop does not care which; it cares that the source is NAMED in the note, because two recordings of one meeting is the normal case and a note that cannot say which one it came from cannot be corrected against it

ger a transcript

one pass over the transcript

The summary, the changelog line, the ledger and insights, the raw source archived to .transcripts/ (CR-085), and whatever the folder declared

$ /ops process <transcript> (the default); /transcript without a config

läser a transcript, the config → ger the summary, the ledger and insights, .transcripts/<stem>-raw.md, a staged recap

the summary's carry-forward

What did not land becomes the top of the next agenda. This is where the loop closes

$ written into the summary by /ops process; verified by /ops check <folder>

läser the summary → ger the summary's carry-forward section

staging and sending

Staged as a folder with a manifest; a dispatching surface delivers it and records what it did

$ /outbox list, then /outbox close <folder> once resolved

läser a staged recap → ger _outbox/<item>/_manifest.md

the dispatching surface

A dashboard reads _outbox/, previews the staged item and delivers it over the channel its manifest declares - a chat workspace through the messaging client, or an email draft a person presses send on. It writes back status, status-note, channel and contact ONLY, and may create a manifest where a folder has none (CR-115); it never rewrites one, decides what a status means, or archives

läser _outbox/<item>/_manifest.md → ger the message, delivered

the knowledge loop

Confirmed hypotheses become standing rules; the corpus renders to a wiki

$ /insights compile, then /insights synthesize

läser the ledger and insights

the shape checks

On a folder it finds a broken carry-forward chain and template forks; on the vault it finds closure debt. Both catch the failures that announce nothing

$ /ops check <folder>, then /ops check

läser the summary, the ledger and insights