Property management¶
Generated from the architecture model
This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
| Vertical | Property |
| Prototype reference | Property prototype (ConnectSoft.DesignPrototypes) |
| Managed edition | Managed (D33, D34) |
| Data residency | tenant-region (D31) |
| Catalog | Examples catalog · Vision-to-Production path for this vertical |
Business problem¶
Leases, maintenance and tenant communication are handled by phone and spreadsheets.
Product intent¶
Properties, units, leases, maintenance requests and tenant portal with payments through a connector.
What the Factory makes different here: tenant portal on the SaaS shell; maintenance as cases with SLAs.
Vision-to-Production path for this vertical¶
| Step | Factory platform | Agents | Blueprints |
|---|---|---|---|
| Vision and product plan | Agent Mesh, Control plane | Product Manager Agent, Backend Developer Agent | vision |
| Architecture and domain | Template & Library (BC-02) | Enterprise Architect Agent | service, module, integration |
| Experience | Template & Library, Factory Studio UX track | UX Designer Agent, Frontend Developer Agent | frontend |
| Recipe and generation | Template & Library (BC-15), Agent Mesh, Tools & MCP | Product Manager Agent, Backend Developer Agent, Frontend Developer Agent, QA Agent | module plan from the context map |
| Quality | Observability (BC-22), DevOps / GitOps | QA Agent | test |
| Delivery and provisioning | DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) | DevOps Agent, Infrastructure Architect Agent | — |
| Operations | Product Fleet Operations (BC-35..37) | — | handover, objectives, rollouts, incidents, off-boarding |
Delivery workflows exercised: customer-success-workflows.
Generated product shape¶
C4Context
title Property management system context
Person(user, "Users", "Property users and operators")
System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
System_Boundary(product, "Property management") {
System(ctx_Portfolio, "Portfolio", "properties, units")
System(ctx_Leases, "Leases", "leases, renewals, payments")
System(ctx_Maintenance, "Maintenance", "requests, vendors, work orders")
}
Rel(user, ctx_Portfolio, "uses through the product gateway GW-07")
Rel(factory, ctx_Portfolio, "descriptor, health, rollouts, incidents, off-boarding")
Bounded contexts¶
| Context | Responsibility | Published events |
|---|---|---|
| Portfolio | properties, units | UnitListed |
| Leases | leases, renewals, payments | RentDue |
| Maintenance | requests, vendors, work orders | RequestResolved |
Modules and templates¶
| Module | Template | Notes |
|---|---|---|
| Microservice ×3 | connectsoft-microservice |
|
| Tenant portal | connectsoft-blazor-saas-shell |
|
| Payment client | connectsoft-api-library |
|
| Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product. |
Prototype reference¶
Property prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.
Operations as a managed product¶
Managed.