Job list adapters: what is deliberately unfinished¶
Technical version: WING-196 adapter composition blockers
Why this note exists¶
WorkWingman is building one backend way for Desktop, YC, Flow, and Studio to load saved and recommended jobs. An adapter layer sits on top of that shared query service and projects safe metadata (company classification, benefits freshness, application readiness, apply-engine capability).
This plain page explains the known blockers so product and UI work do not pretend the missing pieces already exist.
What the adapter layer will not invent¶
- It does not invent its own filter rules for company type, industry, benefits, or health. Those belong to the shared query model when they land.
- Location, commute, office, and tax comparison stay on the location lane.
- Angular filter wiring stays blocked until backend model/query and location contracts are present — so three people do not edit the same hot files in parallel.
Honest gaps today¶
- Tenant scope is enforced by wrapping the data source, not by trusting a client-sent “tenant id.”
- Company type / industry / cohorts may show unknown until a live source writes classification.
- Benefits and health signals are projections of what we already have; filter predicates for them still need the shared query contract.
- Application readiness reports categories of missing steps, never raw profile secrets, referral contacts, or vault material.
- Non-desktop surfaces can advertise apply capability metadata but cannot drive a browser the way desktop does.