# Know where every project stands without asking anyone.

OCTYN runs many systems at once, and the question that costs the most time is the simplest: where does each one stand? HQ is the firm’s own instrument panel. Every machine reports in every quarter hour, outside services are read on the same beat, and the answer is on one page, worst first.

Domain: Our own · HQ
Label: Running (our own)

## Architecture

- **Report**: Every machine the firm works on reports in every quarter hour: what changed, what is running, what has gone quiet.
- **Read**: Outside services are read on the same beat: domains and their uptime, scheduled jobs, deploys.
- **Overview**: One page, worst first: what is slipping, what needs attention, and the latest activity.
- **Portfolio**: Each project with its evidence label, how recently it moved, and whether what is claimed matches what runs.
- **Digest**: A short morning message: yesterday’s changes, deploys, alerts and drift.

Boundary (reads, never writes): It reads and reports; it never changes a project. It is private to the firm, and nothing on it is published.

## Scope

Built and run as our own.

## Anonymized

The screenshot is the real panel with every project renamed to a code, and the business side, spend and anything identifying removed before capture.

## What it is

Every machine reports in every quarter hour, so drift, momentum and uptime for every project sit on one private panel.

## Related

- [Operations systems](https://octyn.co/systems/operations)
- [Put each participant’s full context in front of their counsellor.](https://octyn.co/casestudies/participant-context/demo)
- [The Consult](https://octyn.co/consult)

Canonical: https://octyn.co/casestudies/octyn-hq