Navigation
Getting Started
Reference: directing
Watching
Reference: shaping
Optional budgets
Problems
Concepts & package reference
Reference
Watching

Watching your exocorp

Seeing what your exocorp is doing without getting in its way. Where to look on a daily basis, what to scan for, when to dig deeper.

The daily check-in

A useful daily rhythm for a running exocorp is about five minutes. Use the installed packages’ status APIs or optional operator surfaces to scan four kinds of signal:

  • Live agentsWho’s working right now, grouped by team. If something’s been running for a long time, it’s worth knowing.
  • HeartbeatsScheduled obligations that should fire on a clock. A heartbeat that’s been failing is the company telling you something is consistently broken.
  • Teams with their healthHealthy, degraded, or unhealthy. A degraded team has something stressed; an unhealthy team has multiple problems compounding.
  • Budget pressureOverall budget bar plus the three most-pressured sub-budgets. Tells you if the company is running hot financially.

What to look at depending on what you're checking

  • “Did anything need me?”Pending decisions and alerts exposed by the package that owns them. A package may merge these into an inbox, but that UI is not part of the common runtime.
  • “What's actually in flight?”Query the owning package’s work or activity records. A package-owned UI may make them filterable by its own states and organizational model.
  • “What's been shipping?”Inspect completed activity in the owning package or ask a CEO-style agent for a summary when one is installed — see Asking questions.
  • “What does my company know that it didn't yesterday?”Inspect the records owned by the selected knowledge package: new reviews, doctrine, or summaries.
  • “Where is the money going?”Use Platform billing for hosted spend and package-owned budget controls for any company-local categories.
  • “Who acted on what, when?”The audit trail. For platform-level actions, the admin landing. For per-exocorp actions, the work item’s history surfaces every run and every decision.

The right cadence

For most operators settling into running an exocorp, the rhythm that works:

  • DailyFive-minute status and pending-decision scan. Resolve anything that came up. Read any flagged summary from the company’s selected coordination package.
  • WeeklyTwenty-minute review. Inspect what shipped, what’s blocked, and any health or knowledge records exposed by installed packages.
  • As-neededWhen the CEO surfaces something, when an alert fires, when something feels off. The exocorp will pull you in when it needs to; you don’t need to pull yourself in routinely.
Next