NEXUS
Documents

MiStorage Documents

The formal record of the MiStorage project. These live in the backend repository's docs/ folder and are not yet published on this portal — the paths below are where to find them.

Start here

The single-operator modelMarkdownWhat the product is now, the client's brief verbatim, the four decisions, and the full configuration checklist for a working environment.docs/single-operator-model.md
Customer portal gap analysisMarkdownThe plan of record (31 July 2026) with its status addendum: which phases are done, and what is blocked.docs/requirements/customer-portal-gap-analysis.md
Applying migrations to productionMarkdownThe deliberate procedure: generate an idempotent script, audit it, back up, record row counts, run with ON_ERROR_STOP, verify.docs/deploy/README.md

Requirements and specifications

Super Admin Panel development briefPDFThe original client brief for the HQ console.docs/requirements/MiStorage - Super Admin Panel Development-10042025.pdf
Customer portal gap analysis (PDF)PDFClient-facing export of the gap analysis as it was delivered.docs/requirements/MiStorage-Customer-Portal-Gap-Analysis.pdf
MiStorage technical documentationPDFTechnical overview of the platform as originally built.docs/MiStorage Technical Documentation.pdf
Customer portal preview guidePDFClient update from 2026-08-26 walking through the storefront and renter portal.docs/client-updates/2026-08-26-customer-portal-preview-guide.pdf

Payment gateway references

QuickPayments library documentationPDFBrowser-side tokenization library used so no card number reaches the API.docs/QuickPayment docs/QP-Library Documentation-290525-183559.pdf
QuickPayments REST API documentationPDFThe PhoenixGate / QuickPayments gateway API.docs/QuickPayment docs/QP-ReST API Documentation-290525-183451.pdf

Deploy scripts

One idempotent migration script per production deploy, each audited before it ran. Idempotent means every script carries the full history; the note says which migration is newest in each.

Migration script — 2026-09-11SQLThrough AddApplicationFieldPolicy. Applied to production on 2026-09-15, together with the 09-09 migration it also carries.docs/deploy/migrate-idempotent-20260911.sql
Migration script — 2026-09-09SQLThrough AddRenterSessionManagement.docs/deploy/migrate-idempotent-20260909.sql
Migration script — 2026-09-08SQLThrough AddMoveOutNoticeAndPaymentCard: the rental application fields, the address book and move-out notice.docs/deploy/migrate-idempotent-20260908.sql
Migration script — 2026-08-25SQLThrough AddLeasesAndRenterBilling, with PolymorphicPasswordResetTokens (Phase 3.5) before it.docs/deploy/migrate-idempotent-20260825.sql
Migration script — 2026-08-24SQLThrough DropShadowNotificationCustomerFkAndGlobalTemplateNameIndex: the duplicate EF configuration fix.docs/deploy/migrate-idempotent-20260824.sql
Migration script — 2026-08-22SQLThrough AddRenterIdentity (Phase 3), with AddUnitSizeTaxonomy (Phase 1) before it.docs/deploy/migrate-idempotent-20260822.sql

Session write-ups

One write-up per working session in docs/memories/: what changed, why, what was verified and what was left open. The most reliable account of how any feature got its shape — see Release Notes for the summary.

HQ enters a location's console; the Staff tabMarkdown2026-09-17docs/memories/2026-09-17-hq-enters-location-and-staff-tab.md
Production schema drift; one owner, many locationsMarkdown2026-09-15docs/memories/2026-09-15-prod-schema-drift-and-location-email.md
The single-operator pivotMarkdown2026-09-10docs/memories/2026-09-10-single-operator-pivot.md
Renter session managementMarkdown2026-09-09docs/memories/2026-09-09-renter-session-management.md
Three-step checkout and the verification switchMarkdown2026-09-08docs/memories/2026-09-08-three-step-checkout-and-verification-switch.md
Customer portal planningMarkdown2026-07-31 — where it all starteddocs/memories/2026-07-31-customer-portal-planning.md