Concepts

Five ideas explain everything PowerExecutor does.

1. The operating loop

PowerExecutor doesn't run workflows — it runs a loop, once per cycle:

Observe → Understand → Prioritize → Act → Verify → Reflect

• Observe — poll the product's signals (analytics, health, content state).
• Understand — turn raw signals into situations using an LLM, grounded in evidence.
• Prioritize & Act — decide what to do and carry it out within the granted freedom.
• Verify — confirm the action had its intended effect.
• Reflect — record the outcome, which feeds earned autonomy.

2. The Product Digital Twin

A bounded picture of the product — not "complete". Every fact carries a timestamp, a source, and a confidence, and missing knowledge is recorded as an explicit unknown rather than guessed. If a signal can't be observed, the cycle degrades gracefully instead of inventing state.

3. Capabilities & the adapter

Everything the operator can do to a product is a capability — publish a post, send a broadcast, update content. Capabilities live in a declarative adapter spec (a YAML file) that maps each one to the product's real API, and declares its risk and how to undo it:

Reversibility	Meaning
reversible	Prior state is captured and can be fully restored.
compensable	Can't restore exactly, but a compensating action mitigates.
irreversible	No meaningful undo (e.g. a sent email) — always needs your approval.

4. Earned autonomy

Trust isn't granted by a flag — it's earned. Every capability sits at one of three levels:

Shadow simulates the action (dry-run only, never touches the product)   Recommend proposes the action and waits for your approval   Autonomous acts on its own

New capabilities start at Shadow. Three consecutive clean outcomes promote a capability one level; any failure demotes it and resets the streak. You can also promote or demote manually. Irreversible capabilities stay approval-gated at every level.

5. The safety envelope

Hard limits wrap the whole loop:

• Kill switch — denies every action instantly until you disengage it.
• Degraded mode — pauses acting after an anomaly; observation continues.
• Action budget — a per-day cap on real actions.
• Action receipts — every real action writes an immutable record (before/after state, result) so it can be reviewed and reversed.