Analytics

Usage by workflow

Every workflow appears even before its first recorded run — history accumulates from July 14, 2026. Bars are stacked completed / needs-review / error. Click a bar to open that workflow.

One row per property, joined across the durable stores: bank rec posted, housing deposits recorded, vendor sweep run, funding request generated. A blank cell means that workflow hasn't touched the property this month.

Per account, from the bank-rec status store (the same rows the duplicate-post guard reads).

Omni Close — should-have vs did

Durable record from Rogue One (the housing-deposit ledger + bank-account registry). Read-only — nothing is ever emailed from here. Click a property bar or row to drill into its payments.

Housing $ by property

By property

Every payment — largest first

Trends — month over month

A property that was receiving housing money and suddenly isn't usually means the site manager stopped recording — that's the signal this table flags. The current month is shown MTD but never flagged against.

Per-property payment status from the last pull/sweep of each property (durable board). Each invoice is classified: check cut · invoice with no check · partially paid · review; roster vendors with no invoice are counted separately. Read-only.

By property

No vendor-payment runs recorded yet. Run a property (or a portfolio sweep) on the Vendor Payment Tracker page and it will appear here.

Vendor scorecards

One line per vendor across all properties, from every recorded run. variable = the monthly amount swings hard (renegotiate / investigate); steady = 3+ months inside a 15% band. History accumulates from July 2026.

Filing Clerk

Crawl census + recent filing runs. The crawl is read-only (folder and file names, listing errors counted separately from empties); commits file only into the Omni Deliveries sandbox. The full missing-docs board lives on the Filing Clerk page.

Last crawls

No crawls recorded yet. Run one from the Filing Clerk page and it will appear here.

Master Vendor List

The consolidated recurring-vendor roster across every pulled property. Pick a property to see its vendors and monthly spend, or search a vendor to see every property that pays it. Read-only.

Rogue One data — stored for reference

Everything the MVL / APWC workflows read lives in Rogue One (the Postgres database on the Mac mini). This is a read-only window into it — the scheduled builds, what's stored right now, and a lookup across every payable. Nothing here re-pulls Yardi; it's the durable copy.

Scheduled builds

What's stored now

Look up a payable

Search the full invoice ledger by vendor, invoice #, check/control #, or property code — the same data any workflow reads.

Schedules — every timed job Aura runs

Enumerated from the real schedule configs and state files — a job added to a config appears here on its own. "Next fire" comes from each scheduler's own decider; a paused job shows the pause and its date, and unwired means the work exists but no scheduler runs it yet.

Owner funding forms — which template each property uses

Read from the same assignment rule a funding run uses: the hand-carried registry first, the tracked property_forms.json fills gaps, and a disagreement is named rather than resolved quietly. The generic bucket is listed too — "no owner form assigned" is a fact worth seeing, not an absence.