Adds design/objectives.md, a design note for mission objectives, linked from contracts-and-raids §3, facilities §6 and planning §3.
What it settles:
- An objective: a kind, a major or minor weight, a target (a thing, place, person or data), ordered steps (reach, interact, carry, deliver, condition), endings with pay and notoriety, and when it banks. It also covers how objectives show on screen and in the log.
- The ending is derived from the majors:
Completed, a newPartial, orAborted. Pay is per ending throughsettle, with planning terms applied in the same pass. - Backing out: minor costs when you back out during planning, moderate costs when you flee mid-mission (flake standing, debts falling due, a light cowardice-kind card). Fleeing is never worse than capture.
- Sources are an open list with one data shape: the contract, contract truth, the site kind or owner, planning cards, runner traits, scar or lifepath hooks, and site bonuses.
- Complications have triggers, effects and tells. They are never retroactive and never leave the list structurally impossible from the live state.
- The route solver enforces soundness (each objective has an approach for some reasonable kit, under stated assumptions) and shows this runner's fit on the job board and the planning table without enforcing it. It also counts dead ends per archetype.
- Bots and tests: bot policy, new route report columns, and one golden with a mid-mission complication.
Builds on:
MissionInputsand goals and featuresEndingand the facility completion checksettleandapply_outcome- planning table terms
- reach solver and probe kits,
RouteDef.requiresandroute_allows - route report
🤖 Generated with Claude Code