Evidence room: PropertyCommand Desk: from a unit issue to the next coordination step
SimulationWorking reference system. Public data and external actions are simulated until implementation.
Reviewed 2026-09-25. Revalidate by 2026-12-25. Each row states the claim, the evidence behind it, when it was observed, how it was checked, and the right under which it is published.
Claims and evidence
- Verifiedsim-propertycommand/reference-exists
ScaleBridger built PropertyCommand Desk as a working reference. It can be inspected on this site at /blueprints/propertycommand.
- Evidence
- working reference: ScaleBridger Blueprint registry entry 'propertycommand'; /blueprints/propertycommand; /blueprints/propertycommand/demo
- Observed
- 2026-09-25
- Method
- Registry record read at source; the on-domain Blueprint route and demo route returned HTTP 200 on a read-only GET (2026-09-25).
- Publication right
- ScaleBridger-owned working reference. No client, client data, or client approval is involved.
- Verifiedsim-propertycommand/structure
The reference maps a sample unit issue to priority, service lane, access and responsibility boundaries, and the next coordination step.
- Evidence
- working reference: ScaleBridger Blueprint registry entry 'propertycommand' (description); /blueprints/propertycommand/demo
- Observed
- 2026-09-25
- Method
- Wording matched against the source registry description; behavior inspected in the on-domain reference.
- Publication right
- ScaleBridger-owned working reference. No client, client data, or client approval is involved.
- Verifiedsim-propertycommand/no-external-actions
The reference creates no resident, unit record, work order, vendor dispatch, message, booking, payment, access grant, or property-system change.
- Evidence
- source code: ScaleBridger Blueprint registry entry 'propertycommand' (description and stated boundary); /blueprints/propertycommand
- Observed
- 2026-09-25
- Method
- Boundary wording matched against the source registry record; the reference makes no provider call on the public route.
- Publication right
- ScaleBridger-owned working reference. No client, client data, or client approval is involved.
- Illustrativesim-propertycommand/modeled-stakes
In the modeled scenario, the expensive failure is a decision nobody can reconstruct: an issue ranked or routed without a visible reason.
- Evidence
- working reference: Modeled scenario written for this simulation case study; no observation.
- Observed
- 2026-09-25
- Method
- Reviewed as a modeled consequence: conditional wording, no figure, no client, no observed loss.
- Publication right
- ScaleBridger-owned working reference. No client, client data, or client approval is involved.
What is real
- The working reference is a real ScaleBridger build, registered as "propertycommand" in the Blueprint registry.
- It can be inspected on this site at /blueprints/propertycommand and /blueprints/propertycommand/demo.
- Its structure and behavior are stated in the verified rows above, each with its observation date and method.
What is illustrative
- Identities
- The portfolio, its units, residents, and vendors
- Records
- The unit issue and its service history
- Figures
- Any priority score, count, or date shown in the reference
- Connections
- Property-management, messaging, and vendor systems
- External actions
- Work orders, vendor dispatch, resident messages, and access grants
Known limits
- The reference creates no resident, unit record, work order, vendor dispatch, message, booking, payment, access grant, or property-system change.
- Implementation, content, integrations, hosting, and deployment are separate, scoped work.
- This is a simulation case study built on a ScaleBridger working reference. It is not a client engagement, and it reports no client result, revenue, adoption, or return.
SimulationWorking reference system. Public data and external actions are simulated until implementation.