The 30-second view — where the Patron Platform stands today. This is the binder's primary living page: as the current initiative completes, it advances to the next, while the rest of the binder stays comparatively stable.

Platform area	Status	Notes
Production Environment	Operational (holds real data)	A dedicated Production database on the paid Pro tier, isolated from Dev/Staging; migrations + security model validated in Production; auth/session hardened; database point-in-time recovery (seven days) on since 2026-10-01, replacing the daily backups; the setup restore rehearsal passed on 2026-08-12, before any business records; uploaded files are not backed up (the backup is ready and waits for a company Shared Drive) and restoring today's Production is not rehearsed (see §4); since 2026-10-05 the two nightly jobs are watched — a stall becomes a critical alert on System Health and in the bell (no automatic e-mail yet; the watch cannot see its own scheduler stop). Master Data is imported and reconciled, and Production is hard-locked to live data only — no synthetic fallback.
Identity & Security	Operational	Real login, MFA, deny-by-default role access, and an append-only audit trail — now live-validated in Production. Invitation-only; public and anonymous sign-ups disabled. The independent security review follows the internal release (required; deferred by Nick for a few weeks on 2026-09-24). Released to Production (2026-09-17): a departing person's account is deactivated, never deleted; residential-first access — operational access held back by the server until an administrator turns it on with two-factor sign-in, a reason and an audit record; and the database itself requires the second factor. Access areas (Production, 2026-09-18): an administrator chooses which of seven areas each person reaches, never beyond their role, enforced by the database; since 2026-10-05 an administrator can also grant one area outside a person's role, with a reason, revocable, the role unchanged. Released since (2026-09-21 to 2026-09-23): access requests with administrator decisions and automatic expiry, sessions ended on deactivation, one shared definition of access, and role-scoped field access (a Field Lead updates only the work assigned to them) alongside a full-access Leadership role. Released 2026-09-25: administrators can review one person's activity — their audit trail permanently, and pages and records opened for 60 days — and every review is itself recorded.
User Workspaces	Operational	Role workspaces for John, Jess, Avah, Christy, Eric — one event, one record, many perspectives. Each person lands on their own home workspace, showing real records filtered to what they are responsible for; Avah and Eric use theirs daily (Eric's shows his assigned work first and keeps completed jobs in a closed section). Jess's workspace is a live financial overview, and Chance's (released 2026-09-25) is the same overview under his name. John's workspace is phone-first. Each person can arrange their menu within its categories, saved to their account. Patron installs on a phone as an online-only app (Android one tap; iPhone through Share → Add to Home Screen).
Entities	Operational	Organizations imported and reconciled into the Production master-data foundation through the governed, permission-checked path. Visible on the live screens — the 2026-08-12 read-visibility issue was resolved on 2026-08-13.
Properties	Operational	The full approved property set is imported and reconciled into Production. The properties originally held back for a property-type schema refinement were classified and imported on 2026-08-13 — none remain held.
Units	Operational	Unit records with occupancy/vacancy are imported into Production (2026-08-14), completing the master-data foundation of organizations, properties and units.
Tenants	Operational	Real tenant records entered by Avah since 2026-09-22, with contact details, notes, a ledger summary and search.
Leases	Operational	Real leases in Production since 2026-09-22 — fixed-term and month-to-month, activation, termination and vacancy, signed lease files stored privately with each lease, and rent due on each lease's own day (2026-09-23). Start dates and terms are corrected through recorded, reasoned changes.
Rent Management	Operational	In daily use with real tenants since 2026-09-22. Monthly rent is generated automatically rather than by someone remembering to run it, and is correctly prorated when a tenant moves in or out part-way through a month. An issued charge is never rewritten; an automatic charge says the system created it rather than naming a person. Rent becomes late five days after its own due date — a status only; no late-fee policy exists, and late-fee practice will be settled from Avah's real tracker. A payment entered in error is reversed, never deleted — the months it paid reopen and nothing implies a refund (development platform, 2026-09-15). Payments and credit apply to any of the same tenant's charges, with a duplicate-charge warning and a recorded waiver for a charge created in error. Late stays a status; any late fee is entered by hand.
Deposits	Operational	Real deposits recorded since 2026-09-22. Each deposit records every payer separately — for example a tenant's refundable portion and an employer's nonrefundable funding — with an append-only history of how each portion was settled, so the refundable amount is never assumed to be the whole deposit. The move-out practice around settlement is still an open owner decision. Avah's role records who paid a deposit; approving a refund stays with executives. QuickBooks remains the accounting system of record.
Documents & Photos	Built	Signed lease files and work-order attachments are stored privately and opened only through a permission check. Uploaded files are not yet in a separate backup — a decision with Nick, Jess and the owner.
Maintenance	Operational	Patron is the system of record for work orders since 2026-09-23. Work orders open in a single working view — the job, its checklist, its photos and its history together — and each row says what the job is actually about. The responsible person is notified when something becomes theirs and can be mentioned by name; a dispatch package is prepared from selected work and handed to Gmail, where the recipient is chosen and the send happens. A job's checklist can be edited after it is created, and tenant requests arrive through an intake reviewed by a person.
Transactional email	Operational	Invitation, password-reset and failure-alert emails are connected on the development platform, keep saved and sent as separate facts, and use an email link only when a person presses its button. Accepted by Nick 2026-09-16 after live tests — a link survives an email scanner, a used link is refused, and an alert is sent once per incident. Live in Production since 2026-09-17. Gmail is connected for Dispatch in Production (drafts only; it never sends); the first real draft waits for Nick's go.
POCC Web interface	Archived (read-only history)	The browser front end to the operations command center, live in Production from 2026-09-05. Since 2026-09-23 its work lives in Patron; it shows an archive notice that points people to Patron and is kept as read-only history.
September operating model	Operational	The approved classification, reserve and reimbursement model now runs in Patron — projects with their current available balance, bank transactions, the Tools & Gas reserve and entity reimbursements, imported and reconciled on 2026-09-23; recording refunds is live since 2026-10-02. History is preserved untouched.
Executive Reporting	Operational	Eleven reports on the Reports page (observed live 2026-10-02) read the same records as the working pages — rent, occupancy, lease endings, project balances, reserves, work-order aging and vendors — including the Project Spending Report and the Custom Bank Transactions Report, printable as PDF (released 2026-10-02); plus the public Executive Operations Brief, which since 2026-10-02 also carries this binder.
Atlas / Athena	Operational	Development continuity — durable memory, daily closeout, recompiled context: consistent, reviewable, recoverable.
Property Development	Preview	Property-lifecycle vision (acquisition → operations) supporting Dave's capital planning. Not a built capability.
Cash & Entity Funding	Preview	Financial view previewed; Post It 3.0 remains the source of truth — not yet modeled.
Liberty	Planned	The special invoice-driven lease; designed and approved, sequenced later.

Status terms — Operational (real and in use) · Production Ready (secure foundation ready to switch on) · Built (working on demonstration data) · In Progress (actively underway) · Preview (shown, not yet built) · Planned (approved, sequenced) · Future (directional) · Archived (kept as read-only history).

Current Initiative

Acceptance and the category backlog, then the independent review — Patron is the system of record; Chance, John, Jess and Matt have joined, Jess's first use and Eric's use are accepted (Owner Reports), and project balance warnings are live. Now: categorizing older expenses by hand, leadership using their balance alerts, report users' own first use, how new projects are entered with Dave's approved budget, and the independent security review, which Nick has deferred for a few weeks.

Planning ✓ → Environment Audit ✓ → Persistence ✓ → Production Readiness ✓ → Master Data Import ✓ → Internal release ✓ (2026-09-17) → Residential Onboarding — Avah ✓ (2026-09-22) → POCC into Patron ✓ (2026-09-23) → People and acceptance ◄ now (Eric ✓ signed in · his phone check · John · Jess) → Independent review → Wider use

Patron runs the company's day-to-day work in Production for named internal staff: Avah's residential work since September 22, and since September 23 the work orders, projects, bank transactions and reserves that used to live in POCC. Eric works his assigned jobs in Patron. Every person's own acceptance is theirs — an administrator's preview never stands in for it — and the platform is not described as independently reviewed until that review happens.

Earlier milestones (the Production environment from August, POCC Web's launch on 2026-09-05, the internal release on 2026-09-17) remain in the Recently Completed list below.

Recently Completed

Project balance warnings and the expense review screen (2026-10-01) — released and switched on — percentage remaining against each funding cycle's starting balance, alerts to Jess, John, Nick and Chance, a personal Clear alert; many older expenses categorized at once, by hand; reserve expenses take no category
Jess's first use and Eric's use accepted (2026-10-01) — Owner Reports by Nick
Project summary reports (2026-09-29) — a one-page branded summary of any project for an owner meeting, built in the browser: current position, spending by category for a chosen period and current progress; optional employee hours appear only in the PDF and are never saved
Expense categories (2026-09-29) — Materials, Vendor Invoice, Labor or In House Labor on every new bank expense; older expenses stay Uncategorized until reviewed
Access-request notifications, Matt's Workspace and unit-to-lease navigation (2026-09-29) — deciders are notified of requests; Matt's leases and tenants in one place; a unit opens its current lease
Jess and Matt onboarded (2026-09-29) — both accepted their invitations and set up their second factor themselves
Monthly Budget Request (2026-09-28) — each month's project funding request prepared in Patron: suggestions for projects below zero from their current balance, editable lines and paying entities, a contingency that never counts itself, totals by paying entity, saved drafts and a branded one-page PDF; a request only, with its own permission
Security page, work-order creation and Responsible at creation (2026-09-28) — the dated internal assessment and recovery status shown in the product (not an independent review); title, work items and notes at creation; the Responsible person chosen when work is created
Chance and John onboarded (2026-09-28) — both accepted their invitations and set up their second factor themselves
Fourteen releases (2026-09-25) — John's phone-first workspace; one workspace pattern; Record view and store names in Bank Transactions with sorting across every row; clearer Tenant Ledger, Leases, Reimbursements and Reports; lists past 1,000 rows; an audited activity view with a 60-day usage record; the app icon from the original artwork; Chance's Workspace
Bank Transactions easier to read and filter (2026-09-24) — three releases: vendor and property choices that filter as you type; a compact filter bar with removable chips; rows named by vendor or memo; short dates; a one-click entity and classification copy; receipt as Uploaded or No receipt; the property shown once
POCC moved into Patron (2026-09-23) — work orders with their checklists, project tracking, bank transactions and the September reserve and funding records imported and reconciled; POCC Web and the Google Sheet archived as read-only history; Avah's operational access turned on
Eric onboarded as Field Lead (2026-09-23) — his own password and second factor; his fourteen queued jobs matched one by one against the archived Sheet and assigned to him, with one notification per active job
Sixteen releases (2026-09-23) — rent due on each lease's own day; live management reports and a published occupancy rate; Field Lead and Leadership roles and simpler invitations; Jess's financial overview; editing a job's checklist after creation; accurate Dispatch and Attention counts; menus that keep their categories when rearranged; property lists searchable by typing
Avah onboarded and working daily (2026-09-22) — first real tenants, leases, charges, payments and deposits; twelve releases the same day fixing what she met while working
Personal workspaces and access requests released (2026-09-21) — with signed lease files, work-tool handoffs, truthful Settings, property cities and a reviewed tenant maintenance intake
Next release prepared and tested (2026-09-18, development platform) — personal home workspaces, My Access requests with administrator decisions and automatic expiry, sessions ended on deactivation, and one shared definition of access; testing with a test employee account found and fixed several problems before release; released 2026-09-21
Gmail connected for Dispatch in Production (2026-09-18) — a separate Production connection with its own key; drafts only; the first real draft waits for Nick's go
Per-person access areas released to Production (2026-09-18) — an administrator chooses which of seven areas each person reaches, never beyond their role, enforced by the database; tested on the development platform, applied to Production with the company's records unchanged, and confirmed by Nick after signing in
Patron Platform released to Production for internal office use (2026-09-17) — after a rehearsal on a copy of real data and an internal security review that found and fixed a critical sign-in weakness; residential-first access passed its browser test first
Residential-first access control (2026-09-16, development platform) — a new account can start with residential work only; operational access stays off on the server until an administrator turns it on with two-factor sign-in, a reason and an audit record, and an ordinary access request cannot get around it. Proven in server and automated tests; final browser test pending
Payments accepted (2026-09-16, development platform) — unapplied rent credit is shown to the cent and applies only to the same tenant's charges; accepted by Nick after his retest
Email accepted on the development platform (2026-09-16) — invitation, password reset and failure alerts proven live; two problems found and fixed during testing; accepted by Nick
Payment and lease corrections for cutover (2026-09-15, development platform) — a payment entered in error is reversed, not deleted; a lease's start date or type is corrected before rent exists; browser-verified, including a fix for an amount-entry error; both now accepted
Deposit entry for Avah's role (2026-09-15, development platform) — recording who paid a deposit; refunds, approvals and administration excluded
Employee offboarding without erasing history (2026-09-14, development platform) — a departing person's account is deactivated, never deleted: access ends at once, sign-in is blocked, and everything they did stays attributed to them. Tested end to end by Nick with a test account and accepted
Patron installable on a phone (2026-09-14, development platform) — a home-screen app that opens the same system, deliberately with no offline copy of records; Nick installed it on Android, two layout issues he found were fixed, and he accepted it. iPhone not yet tested
Transactional email built, not yet connected (2026-09-14) — invitations and failure alerts, honest about the difference between saved, handed over and delivered; waiting on the email-service set-up and acceptance
Governed Production environment created — dedicated Production database on Supabase Pro (Vercel also Pro), isolated from Dev/Staging; target verified as Production before any change
Production security model live-validated — migration chain 0001→0010 applied (local == live), authorization baseline seeded once (6 roles · 35 capabilities · 127 mappings), and the full access-control/security suite passed in Production, with every test rolled back leaving no residue
Auth/session hardening — 30-day absolute and 7-day inactivity session limits, MFA, invitation-only access, public and anonymous sign-ups disabled, email confirmation on
Backups active + restore rehearsals passed (2026-08-12, history) — Pro daily backups on at the time; a restore-to-new-project rehearsal exercised the mechanism (scratch project created, then deleted), and the seeded-state restore rehearsal passed on 2026-08-12.
Master Data imported to Production and reconciled — the approved onboarding scope was validated on synthetic data, then imported for real through the governed, permission-checked path; the properties initially held for a schema refinement were classified and imported on 2026-08-13
Phase 1A — Environment & Persistence Readiness Audit (complete and accepted)
Residential persistence — tenants/leases schema + governed relationship and read/write path, fail-closed
Work-order completion notifications — teammates notified when a work order is finished (in-app/demonstration)
Funded-deposit requirements (Draft 1) — Security Deposit / Funding Sources / Settlement History approved (design)
POCC Web now SAVES to the live workbook (2026-09-05, evening) — enabled as its own separate decision hours after the read-only deployment was verified; the first save was a true operational update on a real work order, confirmed, retained after a refresh, matched in the workbook, and kept. A planned fake-record-then-delete first save was rejected. A read-only version was built and set aside before enabling, so rollback is a prepared step. Saving applies to everyone with existing edit access who can open the app.
POCC Web LIVE IN PRODUCTION, read-only and verified (2026-09-05) — a permanent web address showing real operational and financial state, with writing built off rather than switched off; testing and live are separate applications at separate addresses
POCC Web mobile and checklist-responsiveness release shipped to Production (2026-09-05) — proven against real behaviour in the testing environment before promotion: rapid taps no longer freeze the list, queued saves complete in order, and a refresh preserves what was confirmed
POCC Web brought into agreement with the September operating model for everything John needs — deployed to Sandbox and live-verified (2026-09-04) — project budget cards, a governed work queue and tenant-maintenance list that exclude finished work, all three create paths in the browser, and checklist progress; an exactly-once safeguard on the financial write was proven live by submitting the same transaction twice and getting one record
POCC Web Production-readiness prepared in the repository (2026-09-04) — Sandbox and Production built as separate, locked interfaces that cannot be mistaken for one another, and a real structural difference between the Sandbox and live workbooks found by read-only inspection and fixed before it could cause a problem. Production itself was not touched and cannot yet be written to.
Slice 3A — Lease Termination & Vacancy; Executive reporting — real Gmail-draft dispatch and the governed rent model

Up Next (approved priority order, with Nick's readiness targets)

Categorize older expenses by hand — in the new review screen; nothing is guessed. (Project balance warnings and the review screen were released and switched on 2026-10-01.)
Report users' own first use — each person's own acceptance of the project summary report. (Eric's use and Jess's first use were accepted on 2026-10-01 — Owner Reports; John and Jess joined as Leadership on 2026-09-28 and 2026-09-29.)
Independent security review — required before any external-user launch; deferred by Nick for a few weeks on 2026-09-24; findings fixed and retested. The platform is not described as independently reviewed until then.
Slack, read-only — each person connects their own Slack account; only channels Slack already lets them see; no sending.
Known data-gap cleanup — properties without a city and similar gaps corrected by people — never guessed.
Role-access editor design — the fuller per-person access editor that builds on today's access areas; designed, not yet built.
Recovery decisions — point-in-time recovery for the last seven days is on since 2026-10-01 (Nick's decision; database only); a backup of uploaded files and a restore rehearsal remain decisions for Nick, Jess and the owner.
Employee SOPs and handbook (future) — role-based standard operating procedures and an employee handbook for learning Patron; recorded as future work, not yet scheduled.

The earlier Up Next list ended at "Import approved Master Data". That step, the administrator bootstrap and the seeded-state restore rehearsal are complete; the sequence above supersedes it.