Resolver status
unsupported
No matching entry exists in the governed resolver catalog.
For property operations and regional managers
Forklift scopes a work-order and SLA control queue for tenant and staff requests around the property systems already in place. This is a candidate design-partner engagement, not a shipping connector.
Evidence before claims
Design goal: turn each request into a prioritized record with an owner, service target, evidence, and visible status.
unsupported
No matching entry exists in the governed resolver catalog.
Operational data without personal or regulated records.
Property operations leader, regional manager, or asset manager
Why now
These are discovery signals, not proof that Forklift has delivered the outcome for a customer.
First artifact
Target first deliverable: four weeks after approved scoping
Governed progression
Every engagement progresses through explicit gates. Natural language expresses intent; it never grants production authority.
Confirm the repeated problem, owner, systems, data, decision rights, baseline, and economics.
Use interviews, fixtures, or controlled exports before requesting a read-only connector.
Give bounded exceptions owners, deadlines, approvals, and reconciliation evidence.
Measure the agreed result against the approved baseline and preserve provenance.
Permit only cataloged, tested, reversible actions under the exact approved plan.
Monitor cost, health, incidents, recovery, upgrades, and exit—or record why the hypothesis failed.
Proof metrics
A metric becomes evidence only when its definition, source, window, owner, and comparison baseline are approved.
Hard boundary
These exclusions are commitments. Changing one requires a new classification, plan, review, and approval—not an expanded prompt.
Commercial entry
A design-partner proposal states scope, evidence, staffing, cost, and support terms before commitment.
The first written proposal identifies the work, evidence, operating obligation, and commercial terms before authorization.
Questions
No. The existing system remains authoritative unless a separately approved migration is ever justified.
That is a design goal, but the communication workflow and source of truth must be agreed during the build.
A design-partner proposal defines integrations, operating obligations, validation, price, and timeline before work begins.
Adjacent outcomes
Unpublished outcomes route to Open Flow. They do not produce a broken page or an implied implementation claim.