Loop Desk is an always-on business workspace that takes incoming signal (email, forms, feeds, notes) and turns it into briefs, watch items, and next actions.

Does Loop Desk send emails on my behalf?

Loop Desk can draft responses, but nothing sends until you approve and explicitly trigger it. The approval boundary is fundamental.

What signal sources does Loop Desk support?

Email, RSS/Atom feeds, form submissions, manual notes, and webhooks. The desk treats all sources equally in its processing loop.

rev 185 — Loop Desk changelog

rev 1852026-05-08Accelerating

Closes the named rev-184 next-sprint candidate (per-rev historical trajectory chip on the rev-178 /changelog/cadence stats rollup) at three coordinated surfaces (per-day calendar tooltip + per-rev /changelog index chip + per-day v1 cadence projection) so the rev-184 trajectory primitive becomes load-bearing on every cadence read shape — the public calendar tooltip, the chronological /changelog index, AND the protocol-bound /api/v1/changelog/cadence response — without operators or MCP hosts needing to call /changelog/{rev} per shown rev to reconstruct the trajectory state at that moment + closes two more rev-184 named radar candidates at the templates axis (owner-led residential property managers with 90-day lease-renewal + named maintenance-vendor continuity + fair-housing review + security-deposit audit-trail discipline + independent boutique consultancies with statement-of-work integrity + retainer-cycle discipline + scope-creep early-warning + named-engagement-partner continuity) — the templates cluster reaches forty-three named verticals — extends the rev-184 computeShippingTrajectoryAt() helper across four call sites (per-rev detail page chip rev 184, per-rev v1 historicalTrajectory rev 184, per-rev /changelog index chip rev 185, per-day v1 cadence cell rev 185) so every public cadence surface speaks one trajectory vocabulary + the OpenAPI 3.1 spec types the new per-day historicalTrajectory field with full schema in lockstep — the cadence pattern from rev 78 onward (every dashboard primitive gets typed in the OpenAPI 3.1 spec in the same cycle it ships) reaches its 95th unbroken rev — 107th unbroken cadence rev (rev 185)

Per-rev historical trajectory chip on the rev-101 /changelog index — closes the named rev-184 next-sprint candidate at the load-bearing chronological-reading surfaceUntil rev 185 the rev-184 per-rev historical trajectory chip lived only on the per-rev /changelog/[rev] detail pages — visitors landing on the chronological /changelog index (the surface every visitor lands on first) saw rev label + date + title + highlights but no cadence context. Rev 185 closes that. Every rev row in the rev-101 ChangelogList client component now carries the same brand-green Accelerating / amber Cooling / neutral Steady chip the rev-184 per-rev detail page renders, computed once per release via the shared rev-184 computeShippingTrajectoryAt() helper so the index page, the per-rev detail page, and the rev-184 v1 historicalTrajectory field never drift on what 'this rev's trajectory at the time it shipped' means. Quiet weeks (every bucket zero) skip the chip so fresh-state rows stay compact. Click-through opens the public /changelog/cadence calendar so an interested reader can see the broader cadence picture. The chip stays at 0.72 opacity by default (matches the rev-101 .ld-changelog-permalink ambient-affordance pattern) and brightens on rev-row hover so it doesn't compete with the rev label and date for first-glance attention. Strategic significance: anchors every rev row on the chronological reading surface as a data point on the cadence story, not just an isolated event. Procurement reviewers + customers + early adopters scrolling the /changelog now see at a glance which weeks Loop Desk's product was accelerating + which weeks it was steady — the load-bearing visible-velocity trust signal that pairs with the rev-179 /changelog/cadence calendar for the full descriptive (per-day calendar) → trajectory (per-rev chip) story across both public reading surfaces.
Per-day historical trajectory in /changelog/cadence calendar tooltips + v1 cadence cell projectionUntil rev 185 the rev-179 /changelog/cadence calendar showed per-day rev counts in tooltips ('Thu, May 8 — 4 revs: rev 184, rev 183, ...') but didn't carry the trajectory state at that moment. Visitors hovering a busy day saw the count but had to mentally cross-reference against the rev-182 trajectory chip in the stats grid (which only describes today's trajectory) to know if THAT day was during an accelerating or cooling week. Rev 185 closes that gap. Every active calendar cell (revCount > 0) now carries an inline ' (accelerating week)' / ' (cooling week)' / ' (steady week)' suffix in the tooltip computed via the rev-184 computeShippingTrajectoryAt() helper anchored at the day's date so the trajectory reflects what the cadence looked like AT THAT MOMENT (not with hindsight). Quiet days skip the suffix so the tooltip stays compact. Plus the rev-178 GET /api/v1/changelog/cadence v1 endpoint projects the same historicalTrajectory block on every active calendar bucket (quiet days project null so the field stays compact for the steady-state case where most cells in the window are empty). The OpenAPI 3.1 spec types the new field with full schema in lockstep — the cadence pattern from rev 78 onward (every dashboard primitive gets typed in the OpenAPI 3.1 spec in the same cycle it ships) reaches its 95th unbroken rev with rev 185. Strategic significance: pairs the rev-184 per-rev historical trajectory chip with the per-day axis on the protocol-bound surface so MCP hosts rendering a calendar tooltip don't have to call /api/v1/changelog/{rev} per shown rev to reconstruct the trajectory state at that moment — the rev-184 cadence-data-point primitive now reaches every cadence read shape (per-rev detail rev 184, per-rev index rev 185, per-day calendar rev 185, per-day v1 rev 185).
Two more onboarding templates — Owner-led residential property managers + Independent boutique consultanciesCloses two more of the rev-184 named radar candidates at two more underserved verticals where regulated discipline (Fair Housing Act + state security-deposit statutes on the property-management side) and statement-of-work integrity (the load-bearing differentiator for boutique consulting practices that compete on outcomes rather than billable hours) is the load-bearing differentiator against generic AI tools. Owner-led residential property managers (independent residential + small-multifamily property management operators — 4 high-importance memory entries: 90-day pre-expiration renewal package with named in-unit walkthrough + named rent-comparable analysis + named owner approval discipline, named primary + backup maintenance-vendor continuity per recurring category with named insurance-currency tracking, fair-housing communication review red flag on any inbound resident or prospect communication referencing protected classes triggering 4-hour named-manager escalation, security-deposit audit trail with named move-in + move-out photo pairs + named itemised-deduction documentation per state statutory window + 1 sample 90-day renewal-window resident outreach signal). Independent boutique consultancies (owner-led boutique consulting practices spanning strategy + operations + executive coaching + M&A advisory — 4 high-importance memory entries: written statement-of-work signed before any billable work begins with named deliverables + named acceptance criteria + named change-order protocol, structured monthly status report + quarterly named decision-maker check-in + 30-day pre-renewal package on every active retainer, scope-creep early warning red flag at 80% of estimated hours before 60% of named timeline elapsed, named primary partner + named secondary contact continuity discipline with 14-day silent-partner red flag + 1 sample mid-engagement scope-addition signal). Two new OnboardingTemplateKey enum values (residential_property_manager, boutique_consultancy) extend the rev-19 enum without migration. The templates cluster is now forty-three named verticals deep — closes the day-1 starvation-point story across two more underserved owner-led segments where the regulated discipline (Fair Housing Act + state deposit statutes) and engagement-integrity discipline (SOW + retainer-cycle + scope-creep + partner-continuity) are the load-bearing differentiators against generic AI tools that don't know the regulatory or engagement vocabulary.
Cumulative visual polish — ambient-affordance opacity on per-rev trajectory chip + 12 new SEO keywords + radar copy refreshCumulative micro-polish (every rev 22+ has carried at least one). The new rev-185 per-rev trajectory chip on the rev-101 /changelog index sits at 0.72 opacity by default (matches the rev-101 .ld-changelog-permalink ambient-affordance pattern that ships since rev 101) and brightens to full opacity on rev-row hover or focus-visible — so the chip reads as ambient cadence context on first glance and only competes for attention when an interested reader hovers the row. Distinct from the rev-184 per-rev detail page chip which is always-visible because once the reader has landed on the detail page, the trajectory intent is already strong. Plus the rev-185 templates copy refresh — 'forty-three verticals today' replaces 'forty-one' across hero + metadata title + OpenGraph + Twitter description + JSON-LD CollectionPage block + radar copy refresh names the next vertical wave (independent landscape / hardscape contractors with seasonal route density + material pass-through, small specialty pharmacies with DEA-controlled-substance reconciliation + named-pharmacist discipline, independent franchise restaurants with multi-unit operators with per-location P&L + brand-standard variance discipline, small-batch artisan bakeries with production-yield + retail-channel-mix discipline) now that residential property managers + boutique consultancies are shipped. Twelve new SEO keywords for the property-management + boutique-consultancy axes.