Work assignment history
The Work Order Changed Hands. Who Owned the Delay?
A time-bounded assignment ledger keeps current ownership from rewriting the history of multi-location facility work.
Writing topic · 36 articles
Systems that preserve identity, state, time, and evidence.
Patterns for connecting facility work across systems without collapsing identity, authority, state, events, decisions, or receipts into one undifferentiated record.
Topic boundary
What belongs in this collection.
These are authored reference models and implementation questions. They are not diagrams of a released Facily OS product, a modSTORAGE production environment, or a verified vendor integration.
- 01Which system governs each field and operating state?
- 02How are events, commands, decisions, and readbacks separated?
- 03Can a reviewer reconstruct and reverse the decision chain?
9 min read
Occupancy relationship identity
The Unit Number Did Not Change. The Occupancy Did.
A time-bounded occupancy episode keeps customer history from following the next customer through a multi-location self-storage system.
AI correction closure
The Source Was Corrected. Did the AI Stop Repeating the Old Answer?
A correction-propagation contract for self-storage artificial intelligence across source records, retrieval indexes, caches, saved answers and pending actions.
Portfolio incident truth
One Incident, Five Tickets: Stop Counting Workflow Records as Separate Facility Failures
A portfolio incident-family record keeps duplicate reports, distinct symptoms, suspected causes and verified corrections connected without pretending they are the same thing.
Portfolio urgency governance
Priority One Does Not Mean the Same Thing Everywhere: A Portfolio Urgency Contract for Self-Storage
A portfolio urgency contract translates local self-storage priorities into comparable consequence, time, authority and operating boundaries.
Portfolio reconciliation
The Daily Portfolio Close: A Reconciliation Method for Multi-Location Self-Storage
A refreshed dashboard is not proof that every facility finished the day cleanly. A daily portfolio close turns cross-system differences into owned, time-bounded operating work.
Portfolio data governance
Imported Is Not Reconciled: A Quarantine Gate for Portfolio Data in Self-Storage
A practical quarantine gate for validating, approving, reading back and reconciling portfolio data imports across self-storage facilities.
AI provenance architecture
The Summary Cannot Become the Source: Stop AI-Generated Facility Text from Feeding Itself
Prevent AI-generated facility summaries from reentering a self-storage evidence chain as if they were independent observations.
Portfolio rollout governance
Your Pilot Passed. Your Portfolio Hasn't: A Facility Cohort Gate for Multi-Location Self-Storage
Move an approved operating change through bounded facility cohorts using explicit entry, observation, stop, recovery and expansion evidence.
Responsible AI architecture
The Tool Schema Changed. Did the Agent’s Authority Change Too?
A compatibility gate that binds an artificial-intelligence tool call to the exact operation, argument schema, defaults, executor behavior, permission scope, projected effect and governing readback.
Responsible AI architecture
An AI Answer Must Stay Inside Its Organization
A boundary test for self-storage retrieval that checks what the system may see before it composes a convincing answer.
Multi-location systems note
When Unit 214 Becomes Two: The Identity Cutover for Self-Storage Inventory
A practical self-storage systems method for retiring one unit identity, creating successors and reconciling every release-critical surface after a split, merge or renumbering.
Responsible AI architecture note
When Guardrails Disagree: Build a Decision Lattice for Self-Storage AI
A system with several guardrails still needs one governed way to resolve their results. Otherwise the easiest policy to satisfy can quietly become the only policy that matters.
Responsible AI architecture note
Below the Fold Is Still a Decision: Audit the AI Priority Queue in Self-Storage
An AI system does not need permission to change a facility record to change what the team works on. Ranking, suppression and screen position already allocate attention.
Multi-location systems note
A Portfolio Standard Is Not a Facility Setting: Build a Configuration-Drift Register
One approved standard, twelve facilities and one green dashboard can still produce twelve different operating realities.
Responsible AI architecture note
An Override Is Not Ground Truth: Build a Label-Dispute Layer for Self-Storage AI
A label-dispute layer lets self-storage operators act on human overrides immediately while keeping verified labels, evaluation evidence and training eligibility under separate control.
Multi-location systems note
A Login Is Not an Admission: Build a Systems Gate Before a New Facility Joins the Portfolio
A practical systems-admission gate helps multi-site self-storage operators prove identity, authority, timing, meaning, coverage, access and test readiness before a new facility joins portfolio reporting or automation.
Responsible AI architecture note
The Answer Needs a Retrieval Receipt: Prove What Facility AI Was Allowed to Know
A facility AI citation is not enough. Record eligible sources, retrieval coverage, missing evidence and the bounded use each answer can support.
Multi-location systems note
Midnight Is Not a Portfolio Cutoff: Build a Business-Time Contract for Every Facility
A practical multi-location self-storage method for assigning events, schedules and deadlines to the right facility clock, business date and versioned calendar.
Expert AI architecture paper
A Dead-Letter Queue Is Not a Resolution: Recovering Failed AI Work in Self-Storage
Build a controlled recovery path for failed AI work across self-storage systems without replaying obsolete, duplicated or unauthorized actions.
Expert AI architecture paper
The Alias Is Not the Model: Prove Which AI Runtime Touched Facility Work
Model aliases can hide runtime changes. Bind requested, resolved and approved model identities to every consequential self-storage AI decision.
Multi-location systems note
A Quiet Dashboard Is Not a Healthy Portfolio: Build a Data-Freshness Contract for Every Facility
A practical multi-location self-storage method for deciding when facility signals are fresh, aging, stale, unknown or suspended—and what downstream systems must do next.
Expert architecture paper
Rollback Is Not Undo: The Compensation Contract for Self-Storage AI
An AI system can reverse a database value and still leave the real-world consequence in place. Responsible architecture classifies every action before execution as reversible, cancelable, compensatable or irreversible.
Expert architecture paper
One Facility, Two Agents: The Command-Arbitration Layer for Self-Storage AI
An AI workflow can be individually well governed and still collide with another workflow acting on the same facility. Responsible architecture needs one place that decides which command, if any, may proceed.
Expert architecture paper
The Facility Work Graph: An Operational Ontology for Self-Storage
A self-storage-specific operating model for separating facilities, records, observations, events, decisions, authorizations, work, evidence, source authority, and effective time before automation or AI acts.
Expert architecture paper
The Facility Observation Coverage Map: What Your Systems Can Observe, Infer, and Fail to Establish
A self-storage operating and AI architecture for proving whether a facility claim is directly observed, derived, inferred, declared, unknown, or indeterminate before a dashboard or automation acts.
Expert architecture paper
The Facility Intervention Contract: Prove What an AI-Requested Action Actually Changed
A self-storage AI architecture for separating intent, authority, command delivery, controller execution, physical effect, independent readback, reconciliation, and safe reversal.
Expert architecture paper
The Operational Memory Contract: Why Retrieval Is Not Authority in Self-Storage AI
A self-storage AI architecture for deciding which retrieved assertions may support which actor, purpose, time, and consequence without confusing relevance with operating authority.
Expert architecture paper
The Temporal Authority Envelope: When a Facility Fact Is Still Safe to Act On
A self-storage operating method for deciding whether one facility fact remains temporally admissible for one decision through action and readback.
Expert architecture paper
The Multi-Location Policy Compiler: Turn One Operating Rule Into Site-Specific Controls Without Erasing Local Reality
An evidence-bounded method for compiling one versioned portfolio policy into site-specific controls while preserving local capabilities, authority, exceptions, conformance, activation, readback, and rollback.
Expert architecture paper
The Five-Layer Operating Context Stack for Multi-Facility AI
An evidence-bounded architecture for assembling identity, authority and policy, event and time, governing state, and decision and action context for one multi-facility operating question.
Operating method
The Portfolio Handoff Audit: Where Work Loses Its Owner
A practical self-storage operating method for separating routing, receipt, acceptance, execution, returned disposition, and reconciliation across facility, regional, central, vendor, system, and human-AI boundaries.
Expert reference architecture
The Facility Event Spine
A governed event-driven pattern that separates observations, commands, policy decisions, projections, and reconciliation evidence across a self-storage portfolio.
Expert technical paper
Observe the Decision Chain, Not Just the API Call
An eight-stage trace model for separating AI recommendation, authority, human review, provider acceptance, source readback, reconciliation, and closure in self-storage operations.
Architecture playbook
Build a Source-of-Truth Map Before You Build a Dashboard
A field-level map for governing sources, transformations, event evidence, freshness, conflict ownership, reconciliation, and rollback.
Product thesis
An Operating System Is Not Another Dashboard
The difference between displaying activity and governing work across a multi-facility operator.
Publication boundary
These are owned articles by Jared Mastroianni. They are not independent coverage, certification, customer proof, or evidence that a described product capability is live.