AI-Native Operator

You've shipped Modules 01–06. Personal node. Team brain. Routines that refresh it. Connectors that feed them. Templates that turn meetings into memory. A pattern library that names what you reuse. Six pieces. The question Module 07 answers: are they actually changing how you work?

Three artifacts — operator-rhythm.md (the day/week cadence that ties the six together), metrics.md (leading indicators), and operating-review.md (monthly retro on the stack itself). Three levels of ambition:

• Solo operator — apply the rhythm to your own work. Metrics measure you against yourself: am I shipping faster, deciding faster, dropping fewer balls?
• Team operator — apply across a team (3–8 people). Metrics measure team cycle-time, decision-latency, handoffs avoided.
• Org-level operator — apply across multiple teams. Metrics roll up. Failure modes get formal incident response. The stack becomes a capability, not a habit.

The metrics aren't vanity counters. They're the leading indicators that distinguish "you have the stack" from "the stack is paying for itself".