Commerce
24 active agent(s); 16 runtime drift, 16 heartbeat proof gap, 24/8 expected agents
Irie Tower
Company lanes, infrastructure, and source health in one controller view.
Airspace
Window: Jul 30, 12:39 PM to Jul 31, 12:39 PM
Tower Note
fetch failed
Live Strip
Airspace Menu
Runways
Commerce
24 active agent(s); 16 runtime drift, 16 heartbeat proof gap, 24/8 expected agents
Threads
12 active agent(s); 4 runtime drift, 4 heartbeat proof gap, 12/8 expected agents
Transportation
10 active agent(s); 3 runtime drift, 3 heartbeat proof gap, 10/7 expected agents
Swag
11 active agent(s); 3 runtime drift, 3 heartbeat proof gap, 11/8 expected agents
Suite
14 active agent(s); 5 runtime drift, 5 heartbeat proof gap, 14/9 expected agents
Builder
15 active agent(s); 4 runtime drift, 4 heartbeat proof gap, 15/11 expected agents
Airport systems
Development Brief Engine
Brief registry is local-only from this runtime; set TOWER_DEVELOPMENT_BRIEF_INDEX_URL for cloud reads.
IRiE OS operating snapshot
35 systems; 5 visible, 30 partial; 2 event emitter(s); blocked/silent/unknown 0/0/0.
Paperclip / IrieClip
runway; Mac-local Paperclip is active through paperclipai run on port 3100; authenticated dashboard and /api/health returned HTTP 200 on 2026-06-11. The older VPS compose port check is not the active operator surface. Next: Wire IRiE OS/Tower health collection to the verified local Paperclip surface and bridge receipts instead of treating the stale VPS compose port as source truth.
IRiE OS: Approval API
status-only; Standalone Approval API repo is stale/superseded; live Irie OS API now exposes /agent-approvals routes. Next: Keep standalone -Approval-API archived as historical reference; operate approvals through Irie OS /agent-approvals and approval-spine where needed.
IRiE OS: Change Detection API
status-only; Source freshness/change detection is represented in live OS by /api/system-registry/freshness. Next: Use the Registry freshness endpoint as the current change-detection surface; build deeper repo diff sensors later if needed.
IRiE OS: CloakBrowser
status-only; VPS root exists but is empty; no systemd service, compose file, process, public URL, or app source found on 2026-06-11. Next: Archive or remove the empty CloakBrowser root after confirming no current product owner needs it.
IRiE OS: Corey Agent
status-only; live evidence captured 2026-06-10. Next: Emit read-only operator heartbeat/status events into IRiE OS.
IRiE OS: CRM Stack
status-only; compose app; local origin returned HTTP 200 on 2026-06-11; no native health endpoint yet. Next: Add /api/health and CRM lead/customer action events.
IRiE OS: Firm Scope
status-only; systemd active; /api/health returned JSON ok on 2026-06-11. Next: Add Mission Control event emission for lead/opportunity actions; health is already visible to IRiE OS.
IRiE OS: IRiE Agentic Strategy Site
status-only; systemd active; local origin returned HTTP 200 on 2026-06-11; static public site. Next: Keep as status-only static public site.
IRiE OS: Irie Approval Spine
status-only; External Supabase Edge Function approval spine per repository audit; not a VPS app root. Next: Keep as stable external approval reference while Irie OS /agent-approvals owns the current API surface.
IRiE OS: IRiE Bandstand
status-only; compose/Tailscale-bound app; local origin returned HTTP 200 on 2026-06-11; no native health endpoint yet. Next: Add native /api/health and event receipts for media/library actions.
IRiE OS: Irie Builder
status-only; Builder storage routes are built into the live Irie OS API under /ops/builder/storage and return auth-required when unauthenticated. Next: Document Builder product boundary between OS storage routes, irie-builder-lab, and Vision Website Builder before promoting a separate runtime.
IRiE OS: IRiE Calculator
status-only; systemd active; local origin returned HTTP 200 on 2026-06-11; static utility has no native health endpoint. Next: Keep as status-only static utility unless calculator events become useful.
IRiE OS: IRiE Content Remixer
status-only; systemd active; /api/health returned JSON ok on 2026-06-11. Next: Add job_created/job_completed Mission Control events; health is already visible to IRiE OS.
IRiE OS: IRiE Marketplace
status-only; compose app; local origin returned HTTP 200 on 2026-06-11; /health currently serves the app shell, not JSON health. Next: Clarify Commerce relationship, then add native JSON health/event emitter if it stays first-class.
IRiE OS: IRiE Media Studio
status-only; compose/Tailscale-bound app; /api/health returned JSON ok on 2026-06-11. Next: Connect media job events from Start Irie/Media Studio into Mission Control receipts.
IRiE OS: IRiE PDF Engine
status-only; compose app; local origin returned HTTP 200 on 2026-06-11; no native health endpoint yet. Next: Confirm backup root, then add /api/health and PDF generation event receipts.
IRiE OS: IRiE Stack
status-only; compose/mixed app; local origin returned HTTP 200 on 2026-06-11; no native health endpoint yet. Next: Reconcile branch state, then add app/scheduler/relay health and events.
IRiE OS: IRiE Strategic Services Site
status-only; systemd active; local origin returned HTTP 200 on 2026-06-11; static public site. Next: Keep as status-only static public site.
IRiE OS: IRiE Suite Homepage
status-only; systemd active; local origin returned HTTP 200 on 2026-06-11; static homepage child lane. Next: Keep as Suite child/public site; app.iriesuite.com carries native health.
IRiE OS: Irie Suite M2
status-only; Reference/audit row only; not a current VPS app. Current Suite runtime is represented by irie-suite and irie-suite-homepage rows. Next: Use only as historical source-truth reference when Suite social bridge or old Mac B context is needed.
IRiE OS: IRiE Swag
status-only; systemd active; local origin returned HTTP 200 on 2026-06-11; no native health endpoint yet. Next: Add /api/health and clarify Commerce/Threads child ownership.
IRiE OS: IRiE Threads
status-only; systemd active; local origin returned HTTP 200 on 2026-06-11; no native health endpoint yet. Next: Add /api/health and storefront/draft-post Mission Control events.
IRiE OS: Irie Tower
status-only; External Vercel-protected Tower surface returned HTTP 307 to /tower on 2026-06-11; not a VPS app root. Next: Keep Tower as external/protected legacy visibility surface while IRiE OS becomes the primary operating hub.
IRiE OS: Irie Transportation
status-only; systemd active; local origin returned HTTP 200 on 2026-06-11; no native health endpoint yet. Next: Add /api/health and booking/intake event emission.
IRiE OS: LedgerPilot AI Runtime Alias
status-only; VPS root contains only a data directory and no running service. Cloudflare ledgerpilot-vps.iriecommerce.com routes to Firm Scope on port 4177, so current runtime ownership is Firm Scope. Next: Treat LedgerPilot as historical Firm Scope naming unless Corey reactivates it as a separate product.
IRiE OS: Linkfig Demo
status-only; compose demo; local origin returned HTTP 200 on 2026-06-11; no native health endpoint yet. Next: Keep demo/proof lane status-only until product ownership is clear.
IRiE OS: VPS Ops Health
infrastructure; live evidence captured 2026-06-10. Next: Keep as support infrastructure under IRiE OS, not a product lane.
IRiE OS: Paperclip Irie Config
status-only; Irie config sidecar supports the active Mac-local Paperclip instance. The failed VPS port 3100 probe was stale for the current operator surface. Next: Update IRiE OS/Tower collectors to read the Mac-local Paperclip dashboard, /api/health, and bridge receipts as the active Paperclip source truth.
IRiE OS: Simple Memory API
status-only; Standalone Simple Memory API audit says stale/archive; Product Scout uses optional Simple Memory settings but production currently reports memory off. Next: Do not promote standalone Simple Memory API until an active memory service is verified; use as historical design reference only.
IRiE OS: Vision Website Builder
status-only; Local repo exists at /Users/irieagent/Documents/vision-website-builder; no current VPS app root found. Related Vision research timers exist on VPS but are not the builder app. Next: Decide whether Vision Website Builder should be deployed as its own app or remain a source/reference lane behind Irie Builder.
Local Bridge
Snapshot received; generated 2026-07-31T16:39:50.593Z
Media Studio
Public HTTP 200; Private HTTP 200. Studio remains source-owned by Media Studio and receiver-owned by Irie-OS / Start Irie.
Paperclip config
8 hardening squad descriptor(s) readable from Paperclip config
Approval Spine
fetch failed
Paperclip heartbeat
ok; last seen 2026-07-31T16:38:39Z
launchd jobs
21 ecosystem job(s) visible; 2 show non-zero exit status
Embedded Postgres
Reachable
Current repos
5 current repo(s) checked; 4 with local changes
Vercel
12 recent deployment(s) checked; 12 Ready
Media Studio public
HTTP 200
Media Studio private runtime
Private HTTP 200
Media Studio receiver boundary
Production packages should leave through Irie-OS / Start Irie receiver APIs; Tower watches and Paperclip creates work, but neither becomes the Studio database.