Actionist Industry Registry
← Back to industry registry
property_management · evidence-backed demand prior · observed 2026-08-27

Property Management

Property management demand centers on tenant inquiries, rent chasing, work orders and lease filing; emergency and legal paths must stay human-owned.

9Observed repo slots
1Distinct repos
4Observed demand cells
7Open matrix cells
Sparse observed evidence: 9 observed repository slots across 1 distinct repository. A bounded gap-fill wave is running at the Stage-0 discovery boundary; this page shows the recorded matrix result, not a complete market picture.

Demand atoms and workflow

High-value read-only workflow

Read-only property-exception desk: join tenant inquiry, rent-aging, work-order, and lease-index views; show overdue or unowned items.

Demand signal / validated demand

E — Catalogue signal: Answer tenant inquiries, chase rent, log work orders, and file leases.

U — Not established in this lane; no attributable industry denominator or repeated accepted-outcome receipt.

Atom join

intake_normalizetriage_routefollow_up_chasesync_handoffextract_structure

Specification crosswalk: I — intake_normalize, triage_route, follow_up_chase, sync_handoff, extract_structure

Industry model

Entities

propertyunittenantleaserent_chargepaymentwork_ordervendorinquiryexception

States

inquiry_received → triaged → owner_assigned → resolved; rent: due → aged → review; work_order: open → scheduled → complete

Terminal owner

property_manager_or_portfolio_ops_lead

Authority boundary

Read-only tenant, lease, payment, and work-order metadata; no rent collection, eviction action, tenant message, vendor dispatch, or lease change.

Source of truth / exception paths

Source of truth: Property-management/lease system and payment ledger; vendor system is authoritative for dispatch status.

Exception paths: tenant identity/permission; duplicate work order; payment pending; lease version conflict; emergency request; missing vendor owner

Discovery preparation

Precomputable context

  • inquiry/rent/work-order state machines
  • PMS + payment-ledger system model
  • vendor-dispatch actor model
  • archetype fit (intake desk + portal)
  • portfolio size inferable from public listings

Questions that must be asked

  • PMS and payment reality; where leases actually live
  • work-order volume and vendor network
  • emergency escalation rules
  • rent-aging policy and legal thresholds

Contradiction risks

  • payment pending vs paid ambiguity
  • 'automate tenant comms' wanted vs legal notice constraints

Observed repository matrix

These are the non-null rows from repo-matrix-observations.jsonl for this industry. The 1,000-row partition includes reserved cells; only 9 observed repository slots are shown here.

RepositoryObserved slotsDimensionsCapability familiesObserved atoms
api-evangelist/alto-vebra ↗9agent_authority, data_model, demand_atom_fit, economics_maintenance, integration_surface, provenance_rights, runtime_deployment, ui_assembly, workflow_behaviorbrowserbrowser_data_entry, follow_up_chase, intake_normalize, triage_route

Empty-cell gap matrix

The ten category cells retain both demand and supply state. NO_OBSERVED_DEMAND_SIGNAL means the research denominator is empty; it is not a claim that the workflow does not exist.

Category / empty-cell keyObserved demandCandidate coverageSearch waveCandidate examples
Intake and normalizationintake_and_normalizationOBSERVED9 slots · 1 reposSHARED_CANDIDATE_COVERAGE10 candidate repos · 10 source rowsNOT_SEARCHEDno targeted search proposalLimeSurvey/LimeSurvey, ProcessMaker/processmaker, al1abb/invoify, formbricks/formbricks
Triage and routingtriage_and_routingOBSERVED9 slots · 1 reposSHARED_CANDIDATE_COVERAGE31 candidate repos · 31 source rowsNOT_SEARCHEDno targeted search proposalAlfresco/alfresco-community-repo, Leantime/leantime, ProcessMaker/processmaker, Worklenz/worklenz
Records, extraction and auditrecords_and_auditNOT_OBSERVED_IN_750_SLOTS0 slots · 0 reposNO_OBSERVED_DEMAND_SIGNAL47 candidate repos · 47 source rowsSEARCHED_DRYno targeted search proposalAlfresco/alfresco-community-repo, AppFlowy-IO/AppFlowy, BookStackApp/BookStack, BuilderIO/builder
Classification and prioritizationclassification_and_prioritizationNOT_OBSERVED_IN_750_SLOTS0 slots · 0 reposNO_OBSERVED_DEMAND_SIGNAL39 candidate repos · 39 source rowsSEARCHED_DRYno targeted search proposalDolibarr/dolibarr, PostHog/posthog, SuiteCRM/SuiteCRM, apache/superset
Scheduling and coordinationscheduling_and_coordinationNOT_OBSERVED_IN_750_SLOTS0 slots · 0 reposNO_OBSERVED_DEMAND_SIGNAL14 candidate repos · 14 source rowsSEARCHED_DRYno targeted search proposalcalcom/cal.diy, alextselegidis/easyappointments, lukevella/rallly, thunderbird/appointment
Follow-up and communicationfollow_up_and_communicationOBSERVED9 slots · 1 reposSHARED_CANDIDATE_COVERAGE23 candidate repos · 23 source rowsNOT_SEARCHEDno targeted search proposalRocketChat/Rocket.Chat, TryGhost/Ghost, activepieces/activepieces, chatwoot/chatwoot
Reporting and digestreporting_and_digestNOT_OBSERVED_IN_750_SLOTS0 slots · 0 reposNO_OBSERVED_DEMAND_SIGNAL15 candidate repos · 15 source rowsSEARCHED_DRYno targeted search proposalPostHog/posthog, apache/superset, bigcapitalhq/bigcapital, cube-js/cube
Monitoring and alertsmonitoring_and_alertsNOT_OBSERVED_IN_750_SLOTS0 slots · 0 reposNO_OBSERVED_DEMAND_SIGNAL0 candidate repos · 0 source rowsSEARCHED_DRYno targeted search proposalnone recorded
Approval and controlled publishingapproval_and_controlled_publishNOT_OBSERVED_IN_750_SLOTS0 slots · 0 reposNO_OBSERVED_DEMAND_SIGNAL21 candidate repos · 21 source rowsSEARCHED_DRYno targeted search proposalBudibase/budibase, ProcessMaker/processmaker, activepieces/activepieces, apache/airflow
Sync and browser operationssync_and_browser_operationsOBSERVED9 slots · 1 reposTHIN_OR_PARTIAL_COVERAGE1 candidate repos · 1 source rowsSEARCHED_DRYtargeted search eligibleactivepieces/activepieces

Shelf candidates joined to this industry

These records come from the permanent source registry's industry-demand join. A joined candidate remains a discovery/research record; qualification and admission are shown explicitly.

Joined shelf recordObserved slotsFamilies / atomsCurrent verdictQualification / admission
api-evangelist/alto-vebra ↗9browserbrowser_data_entry, follow_up_chase, intake_normalize, triage_routediscovery_candidateNOT_QUALIFIED / NOT_ADMITTED

Open gaps

Records, extraction and audit

NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 47 candidate repositories.

SEARCHED_DRY. Exact P03 document/record kinds; source-specific authority and provenance remain unqualified.

Classification and prioritization

NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 39 candidate repositories.

SEARCHED_DRY. Exact P03 CRM/analytics/search candidates are adjacent supply, not proof of a classifier workflow.

Scheduling and coordination

NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 14 candidate repositories.

SEARCHED_DRY. Exact P03 scheduling kind only; calendar UI alone is not a booking/authority proof.

Reporting and digest

NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 15 candidate repositories.

SEARCHED_DRY. Exact P03 analytics kind; a reporting surface is not a measured client outcome.

Monitoring and alerts

NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 0 candidate repositories.

SEARCHED_DRY. No dedicated P03 capability kind is mapped; analytics is not silently promoted to monitoring.

Approval and controlled publishing

NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 21 candidate repositories.

SEARCHED_DRY. Exact P03 approval/signing kinds; an approval-shaped product does not grant host authority.

Sync and browser operations

THIN_OR_PARTIAL_COVERAGE · 9 observed demand slots · 1 candidate repositories.

SEARCHED_DRY. Connector candidates cover a possible sync seam; no direct P03 browser-operation kind is available.

Safe-pilot boundary

Rationale

Exception visibility is useful without modifying tenant or payment records; emergency and legal paths stay human-owned.

Falsifier

Synthetic cases cannot preserve tenant/unit identity or distinguish payment pending from paid, or value depends on dispatch/message side effects.

Sources: research/actionmodel-builder-research-2026-08-26/phase-2/outputs/industry-atom-specifications.md · research/workstreams/p01-client-intelligence/runs/2026-08-27-sprint-1-fable/industry-discovery-priors.jsonl · research/actionmodel-builder-research-2026-08-26/expansion/outputs/repo-matrix-observations.jsonl · research/workstreams/2026-08-28-program-driver/shelf-prebake/industry-gap-matrix.json · knowledge/capability-shelf/source-registry.jsonl