A route comes from checked rules before it gets any AI wording.

Resolve the occupation

The selected title must map directly to a four-digit PSOC code. Reviewed aliases help people find a title, but they do not change the underlying occupation record. Only a deep profile can enter route selection.

Read each task separately

A build-time crosswalk connects checked PSOC tasks to current O*NET task statements. Current Economic Index data can then support one of four labels: automation pressure, AI assistance, human-led work, or limited evidence.

Missing or weak matches stay unknown. Landas does not turn an evidence gap into a neutral or positive result.

Apply hard constraints first

Credential commitment, work setting, remote equipment, weekly time, and income disruption can block a pathway. A blocked route names the answer responsible and the smallest change that admits the closest checked pathway.

Rank the remaining pathways

The engine ranks pathway fit by constraint match, chosen-strength overlap, frequent task support, evidence strength, transition effort, and PSOC code. This fixed order makes the same evidence and answers produce the same result.

Fill three distinct route slots

Landas returns at most one route to strengthen current work, one adjacent move, and one larger change. It does not repeat the same target occupation. A route stays blocked when no pathway passes the chosen limits.

Add actions and checked destinations

Deterministic templates turn the route into no more than five next actions. Destination links come from a registry with check and expiry dates. The result view disables a link that is no longer current.

Keep generative AI optional

The complete result exists before any model call. If requested, optional narration can restate only stored occupations, routes, tradeoffs, and citation IDs. It cannot add a salary, credential, URL, score, source, or occupation.