FLhour
Operator Console · —
Not signed in

Today, — gardens are growing.

Four canonical tables, one immutable transaction log, Stripe-backed economy.

Users
—
 
Gardens
—
 
Certificates
—
 
Transactions
—
 

Gardens —

Garden review —

Gardens submitted by cultivators that haven't been approved yet. Approving creates a Stripe Product behind the scenes.

Taxonomy —

The garden vocabulary: categories and the types under them. Saving writes straight to the registry every garden points at — no app, website or backend deploy needed. Renaming a key carries its gardens with it; retire an entry with the Active toggle rather than deleting one that is still in use.

Bid Jars —

Funding grouped by garden — jar strips with claimed hours linked to the cultivators who claimed them.

iOS release policy

What the app checks on every launch. Stored in S3 and served unauthenticated from /app/config, so this takes effect immediately — no app, and no backend deploy. Check the app_version column on the Users tab before raising the minimum: that is who you are about to lock out.

Reports —

Content flagged by users in the app (App Store Guideline 1.2 — UGC moderation). Triage each report, then act on the target from its Users or Gardens row.

Lost Sessions —

Work that happened but never settled — a stop the app couldn't complete, or a session that went silent and never came back. Settling runs the normal settlement, valued at the moment the work actually ended, so a session recovered days later still mints the hours that were worked. The worked time on each card is the recorded figure and is editable: when the evidence is wrong (a phone that died mid-session), set what actually happened before settling.