Loope
Portfolio operations

Your portfolio, running itself.

Loope is a small, auditable staff for everything you've shipped. It watches every product, names what broke, proposes the fix, and writes you the Monday brief. Every action is typed, costed, and on the books.

Bring your products. The first sweep runs within ten minutes.

specimen · the maker's workspace · July 2026sweep every 10 min
Holdoutholdouthq.com145 ms100%
Beatbeatlog.io246 ms100%
Sonavesonave.co—0%
Sentinel · diagnosis

Sonave is down: HTTP 500 after 3 attempts.

Cause
The application is crashing, not the infrastructure. http-5xx
Fix
Check the function logs for /api/auth/guest.
3 incidents open · 1 fix awaiting approval
The loop

One loop, closed every ten minutes. It stops once, for you.

Each stage is a typed hand-off. Nothing skips a stage, and every pass through the loop leaves a row in the ledger.

  1. 01

    Watch

    Sentinel probes every production URL. A bad observation is confirmed with retries before it becomes an incident.

    GET holdouthq.com/ 200 · 145 ms
  2. 02

    Diagnose

    Not “down”: the cause. Stale DNS, wrong project on the domain, the app throwing 5xx, latency over budget.

    http-5xx the application is crashing, not the infrastructure
  3. 03

    Propose

    When a fix is executable it is typed: redeploy, attach domain. “Investigate” is a recommendation, never an action.

    attach-domain cineengine.com to cineengine
  4. 04

    Approveyour yes

    Nothing production-facing runs without you. One click from the queue, and the decision is recorded with your name on it.

    pending approve and run · reject
  5. 05

    Execute

    The Operator runs it through your own credentials and records the outcome, including failure.

    vercel: attach cineengine.com to cineengine
  6. 06

    Report

    Monday, 13:00 UTC. The Analyst writes the brief from the week’s numbers and ends it with decisions, not charts.

    brief three products are down with open incidents; the rest of the portfolio is healthy
The staff

Six roles, in order. Three are live.

Volume is automated. Anything that speaks for you waits for you.

RoleJobCadenceGateStatus
SentinelWatches every product, confirms before alarming, names the cause. Live.every 10 minutesUnattendedLive
OperatorExecutes approved fixes through your credentials and records the outcome. Live.on your yesGatedLive
AnalystWrites the Monday brief from the week’s numbers. Labelled when it falls back to the rule-based writer. Live.Mondays, 13:00 UTCUnattendedLive
ScoutRuns outreach. Next.—GatedNext
ConciergeAnswers support. After Scout.—GatedAfter Scout
ScribeWrites content. Later.—Permanently gatedLater
Principles

Nothing runs off the books.

Every agent run, clean or failed, is one ledger row: duration, model calls, cost. Accounting was built on day one, not retrofitted.

Nothing outward without your yes.

Production-mutating actions wait in a queue. Agents handle volume; you keep outcomes.

Failure is data.

A wrong heal proposal taught the system a new diagnosis class. Fallbacks are labelled, never disguised.

Your keys stay yours.

Workspace credentials are encrypted at rest, write-only, and never leave your tenant.

Proof

Loope runs its maker's own portfolio in production. Including itself.

loope · loope.dev/api/health
probed every 10 minutes by its own Sentinel
in production since 4 Aug 2026
the incidents on this page are its own findings