# session-ops

> The multi-repo operations layer: the feed, the clock, and the portfolio view across repos. It triages and drafts; it never implements and never publishes.

- Type: open source component
- Status: v0.3.0
- License: MIT
- Language: Python
- Repository: https://github.com/matshoppenbrouwers/session-ops
- Author: Mats Hoppenbrouwers (hoponthestack)
- Canonical URL: https://www.frameworkreboot.com/products/session-ops

A multi-repo operations layer for Claude Code and a companion to session-flow. session-flow owns routing and judgement inside a repo; session-ops owns the feed, the clock, and metrics across repos, plus the multi-repo portfolio, the one thing session-flow structurally cannot see.

## Glossary

- [Escalation](https://www.frameworkreboot.com/glossary/escalation): An item the automation refuses to decide, written to a numbered file and surfaced for approval on the unit's pinned dashboard.
- [Portfolio view](https://www.frameworkreboot.com/glossary/portfolio-view): The cross-repo status rollup: backlog progress, inbox depth, open escalations, last release and activity, run quota and failure streak, for every managed unit.
- [The clock](https://www.frameworkreboot.com/glossary/the-clock): The scheduled triage and sweep workflows on an enrolled unit, plus the guard that caps their cost and the heartbeat that reports their failure.
- [Unit](https://www.frameworkreboot.com/glossary/unit): A repository that session-ops manages: one with a backlog, direction documents and an entry in the registry.
