Owner Stefan CoetzeeUpdated 2026-10-14

CTO powersuit cockpit · from GitHub Issues · 2026-10-14 17:55 UTC

Cockpit

This is the CTO powersuit cockpit running on Stefan Coetzee's public work: the issues and pull requests of his public repositories on GitHub, by area of the CTO job, as of 2026-10-14 17:55 UTC. An install can run the same cockpit on beads, a local issue tracker, or on GitHub Issues.

Open18not started, not blocked
In progress0labelled, or an open pull request
Blocked8waiting on a decision or an input
Closed in 7 days35done since 2026-10-07

The last 14 days

Items with an area label not yet closed at the end of each day (bars), and items done that day (the row below), for the 14 days to 2026-10-14.

2026-10-01: 0 not closed, 0 done that day
2026-10-02: 0 not closed, 0 done that day
2026-10-03: 0 not closed, 0 done that day
2026-10-04: 0 not closed, 0 done that day
2026-10-05: 0 not closed, 0 done that day
2026-10-06: 0 not closed, 0 done that day
2026-10-07: 0 not closed, 0 done that day
2026-10-08: 0 not closed, 0 done that day
2026-10-09: 18 not closed, 19 done that day
2026-10-10: 18 not closed, 0 done that day
2026-10-11: 21 not closed, 4 done that day
2026-10-12: 24 not closed, 7 done that day
2026-10-13: 27 not closed, 4 done that day
2026-10-14: 26 not closed, 1 done that day

The eight areas

The areas of the CTO job, as on the CTO powersuit pages, each with the plugins that do its work and its open items. An item's area and kind are labels on the issue: area:delivery, kind:finding. A finding is a gap that an audit or a review found, a decision is a choice still to make, and an action is work to do. Leads are counted only. Blocked and in progress come from the labels status: blocked and status: in progress; an open pull request counts as in progress. Closed in 7 days counts issues closed as done and pull requests merged.

Direction

Where the company stands, and the big technical decisions.

Powersuit pluginsfit decisions

Open: 0
In progress: 0
Blocked: 0
Closed in 7 days: 2

Open by kind

Findings: 0
Decisions: 0
Actions: 0
Oldest open: none open

Nothing open in this area.

Delivery

How code gets from an idea to production.

Powersuit pluginssdlc gate docs

Open: 5
In progress: 0
Blocked: 1
Closed in 7 days: 8

Open by kind

Findings: 1
Decisions: 1
Actions: 4
Oldest open: 5 days

Gate check for docs owner and review dates (open decision)blockeddecisionmachinebehavior.io · issue 275 days old
Templates spaceopenactionmachinebehavior.io · issue 205 days old
Withdrawn-page patternopenactionmachinebehavior.io · issue 235 days old
Accessibility pass to WCAG 2.2 AAopenactionmachinebehavior.io · issue 245 days old
Toil: the bot commit on main forces a rebase before every pushopenfindingmachinebehavior.io · issue 395 days old
CI check: generated pages match their sourcesopenactionmachinebehavior.io · issue 405 days old

Operations

Keeping it running, and seeing what it does.

Powersuit pluginsreliability observability

Open: 4
In progress: 0
Blocked: 1
Closed in 7 days: 5

Open by kind

Findings: 0
Decisions: 2
Actions: 3
Oldest open: 5 days

Alert routing: Alertmanager, a Watchdog and receivers chosen by the operatorblockeddecisionmachinebehavior.io · issue 365 days old
Postmortem indexopenactionmachinebehavior.io · issue 225 days old
SLOs for the tier-1 services and the agent sessionsopenactionmachinebehavior.io · issue 375 days old
Error budget policy: what happens when a service spends its budgetopendecisionmachinebehavior.io · issue 385 days old
Incident records: when and how each incident was detectedopenactionmachinebehavior.io · issue 415 days old

Money

What the platform costs, and where the money goes.

Powersuit pluginsfinops

Open: 1
In progress: 0
Blocked: 0
Closed in 7 days: 0

Open by kind

Findings: 1
Decisions: 0
Actions: 0
Oldest open: 5 days

Cost counters: drop them or alert on their resets (incident follow-up)openfindingmachinebehavior.io · issue 295 days old

Security and risk

Protecting systems and data, staying compliant, testing for failure.

Powersuit pluginssecurity compliance red-team

Open: 5
In progress: 0
Blocked: 6
Closed in 7 days: 8

Open by kind

Findings: 1
Decisions: 1
Actions: 9
Oldest open: 5 days

Impressum on all three sitesblockedactionmachinebehavior.io · issue 105 days old
Privacy notice on all three sitesblockedactionmachinebehavior.io · issue 115 days old
security.txtblockedactionmachinebehavior.io · issue 125 days old
Security headersblockedactionmachinebehavior.io · issue 265 days old
One GitHub account for the operator and every agent sessionblockeddecisionmachinebehavior.io · issue 791 day old
Make Workflow security (zizmor) a required check on mainblockedactionmachinebehavior.io · issue 821 day old
Retention statement for the metrics and log storesopenactionmachinebehavior.io · issue 255 days old
Gate check private.terms: private terms stay out of the repository and the pages (dry run only)openactionmachinebehavior.io · issue 633 days old
Dependabot cannot open pull requests for the tool pins under .github/openfindingcto-powersuit · issue 132 days old
Move CONFORMITY_PUSH_KEY to an environment limited to mainopenactionmachinebehavior.io · issue 762 days old
Internal dashboards and stores: access by identity in place of the home networkopenactionmachinebehavior.io · issue 831 day old

AI

Running AI in the company, and being found by AI.

Powersuit pluginsai-ops aieo

Open: 2
In progress: 0
Blocked: 0
Closed in 7 days: 3

Open by kind

Findings: 0
Decisions: 0
Actions: 2
Oldest open: 3 days

Link the published CTO powersuit repositoryopenactionmachinebehavior.io · issue 483 days old
Agent sessions: deny pull-request merges through gh apiopenactionmachinebehavior.io · issue 513 days old

People

Hiring the team, and handing the work over.

Powersuit pluginshiring handover

Open: 1
In progress: 0
Blocked: 0
Closed in 7 days: 1

Open by kind

Findings: 0
Decisions: 0
Actions: 1
Oldest open: 5 days

Onboarding path for a new engineer or agent sessionopenactionmachinebehavior.io · issue 215 days old

Knowledge layer

The layer under every module: what agents know and how they answer.

Powersuit pluginsvestige vault stance

Open: 0
In progress: 0
Blocked: 0
Closed in 7 days: 8

Open by kind

Findings: 0
Decisions: 0
Actions: 0
Oldest open: none open

Nothing open in this area.

What the cockpit is

The cockpit is the view in which Stefan Coetzee runs his work: every task, finding, and decision is an issue with one label for its area of the CTO job and one for its kind, and the cockpit shows the issues by area, with a scorecard for each area and the trend. His own install runs on beads, a local issue tracker, and its data stays on his machine. This page runs the same view on his public work, so everything on it is public already.

The CTO powersuit is a set of agent skills, one module per CTO function from the deploy gate to the hand-over, that one person uses to run a company's whole engineering platform. The cockpit is that person's view of the work. For a company, the plan is that the plugins' read-only audits write their findings into the areas, so the scorecard shows what is open in each part of the CTO job.

Read from the public repositories of uncovertechtalent on GitHub: agent-observability, cto-powersuit, machinebehavior.io, tychat.io, vault-kit, vestige-kit.

Board: the issues of this site by status, with filters.
Mission Control: the live operations view, with the gate and deploy state of the three sites.
CTO powersuit: the plugins by area, with install commands for the latest release.

Cockpit · data: cockpit.json, read from the GitHub API at each deploy of this site and checked against a contract before the page is written; the deploy gate runs the same check on the committed copy. How it works: Cockpit page. Decision record: ADR-0031.