Quest & Dialogue Designer Specialist

Illustrative preview: this representative editorial result is not a recorded runtime session.

Use one lobby scene with two remembered outcomes. Reconvergence keeps content scope small while the supplied roof-route consequence remains real.

Quest packet OBS-FAVOR-01 / version 1
Status: COMPLETE_LOCAL for authored content; persistence ownership/integration remain NEEDS_DECISION and NOT_RUN.
Producer: Quest & Dialogue Designer Specialist. Recipient: developer and narrative owner.
Objective: optional once-only favor with clear cost and later consequence.
Confirmed: Iona repairs the roof instrument; lens count is zero or one; donation unlocks next-outing roof route; keep does not; both paths return to lobby. New state IDs are local proposals.

Proposed state: obs_favor = unresolved | given | kept; spare_lens = 0 | 1. Narrative selection reads both; one shared persistence transaction must update lens and favor together. The actual owner/format remains unselected.

Actual scene and choice content
OBS-L01, unresolved entry: Iona turns a cracked ring beneath the lamp. “The roof instrument will work again. It only needs one clear lens.”
OBS-L02, context: “If you have a spare, I can open the roof route for your next outing. If you need it yourself, I understand.”
OBS-C1: “Give Iona my spare lens to open the roof route.” Available only when unresolved and spare_lens=1. Commit one lens consumption plus obs_favor=given once.
OBS-L03, donation acknowledgment: “Iona holds the lens to the light. ‘I’ll have the stair ready when you return.’” Exit to lobby.
OBS-C2: “Keep the lens. I’m not ready to give it away.” Available when unresolved, whether or not the player has a lens. Set obs_favor=kept; inventory unchanged.
OBS-L04, keep acknowledgment: “‘Then keep it safe,’ Iona says. She sets the broken ring beside the lamp.” Exit to lobby.
OBS-C3: “Leave without deciding.” Available outside atomic resolution. Exit to lobby with state unchanged; the once-only decision remains available on a later visit.

Revisit and later content
Given: OBS-L05 “The stair is ready. You’ll see more of the sky from up there.” No donation option reappears; next exploration offers the roof route.
Kept: OBS-L06 “‘You still have your own path,’ Iona says. The roof door remains closed.” No donation option reappears; no roof route is granted by this favor.
Unresolved with no lens: show OBS-L01/02, keep and leave; hide donation rather than promising an unavailable transfer. Proposed optional note OBS-L07: “You have no spare lens to offer.”
Every exhausted resolved scene exposes OBS-C4 “Return to the lobby.” No flag or inventory mutation.

Graph: Lobby → unresolved scene → [give / keep / leave] → Lobby. On re-entry, obs_favor selects given, kept or unresolved scene. Both resolved branches reconverge spatially; their later route availability and acknowledgment differ.
Branch inventory: one shared opening, two immediate outcomes, two resolved revisits, one no-lens note, one common exit. Required voice/localization budget is seven line IDs plus four option strings, if those channels are adopted; no voice assets or estimate is supplied.

Persistence and interruption contract, proposed for owner agreement
Before choice commitment, closing the dialogue leaves state unchanged. The give transaction validates unresolved state and one lens, then commits consumption/flag together. Repeated selection or loading a resolved scene cannot consume again. After successful commitment, a presentation interruption must not undo only half the transaction. Save/reload preserves favor and inventory consistently; next-outing route selection reads that same favor state. Exact save ownership is a material integration dependency.

Checks OBS-AC1–5: zero lens never exposes a legal donation; give applies once; keep preserves inventory and does not unlock roof route; leave permits a later decision; both resolved visits always expose an exit and select the correct acknowledgment after save/reload. These are proposed traces, not an executed script. Player understanding/emotional response is unobserved.
Next action: confirm transaction/persistence owner and next-outing route boundary; implement with the selected format, then collect candidate-bound proof. The complete prose can proceed without inventing an engine.