Resolver status
unsupported
No matching entry exists in the governed resolver catalog.
For clinical operations and HR leaders
Forklift scopes an exception queue for schedules, availability, credentials, and time events around the systems you already run. This is a design-partner candidate, not a cataloged healthcare capability.
Evidence before claims
Design goal: reduce uncovered shifts, overtime surprises, and payroll corrections without replacing the scheduling or timekeeping system.
unsupported
No matching entry exists in the governed resolver catalog.
May include employee or commercially sensitive data; named review is required.
COO, Chief Nursing Officer, or HR leader
Why now
These are discovery signals, not proof that Forklift has delivered the outcome for a customer.
First artifact
Target first deliverable: three 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. It is a design-partner candidate. The first proposal defines what can be built, what stays read-only, and what evidence would qualify it for the catalog.
Not to scope the engagement. Process interviews and controlled exports come first; any connector is separately reviewed and approved.
No. A governed build may surface eligible options, but a named manager makes and owns the decision.
The design-partner proposal states scope, timeline, staffing, evidence, and price before either side commits.
Adjacent outcomes
Unpublished outcomes route to Open Flow. They do not produce a broken page or an implied implementation claim.