SCENARIO ENGINEERING - LOCAL PLANNING WORKSHEET

Destination: local authoring notes. Not a native import, parser, or execution stack.
Guide: https://duhployed.com/learn/modules/scenario-engineering.html
Source: adaptation of supplied Scenario Engineering guide; no visible author/date.
Review date: October 31, 2026. Proposed native checks: not_run.

PROMISE AND PREMISE
Intended experience:
Why the story starts now:
One unresolved question, if useful:
Outcomes deliberately left undecided:

USER ROLE AND ACCESS
Established role without unprovided identity or choices:
Existing connection and legitimate reason for repeated encounters:
Public/available locations and information:
Access limits, permissions, and what could change them:
Available choices, including refusal, quiet activity, pause, or leaving:

CAST NETWORK
Relevant person / existing relationship / independent goal:
Current location or absence:
Plausible entry or exit condition:
Known facts and source for each person:
Beliefs or suspicions distinguished from world truth:
Possible information path (observation, conversation, document, or report):

WORLD AND OPPORTUNITIES
Only setting rules and locations that affect choices:
Relevant obligation or optional pressure:
Optional deadline and agreed time rule, if needed:
Possible future developments (not completed history):
Accepted events and consequences:

LAUNCH SNAPSHOT
Exact opening time/location:
Present cast and remote channels:
Objects, custody, accepted state, and unknowns:
Character expectations:
Immediate opportunity:
Unresolved user choice:
Greeting agrees with this snapshot:

FIELD HANDOFF
Scenario: needed opening circumstances and playable situation.
APD: character motives, behavior, and written voice.
ED: relevant lore, cast, rules, and systems; broader than rendering.
Greeting: actual opening message in the intended voice.
Memory/current notes: accepted continuing facts, updated when established.
Native group: actual shared group setup; a worksheet creates no respondent.
Copy only each prepared payload to its stated destination.

CHECK BEFORE ADOPTING
Section labels and SCE IDs are editorial organization, not native syntax.
Do not duplicate the entire plan in every field or assume field precedence.
Keep possible, pending, and occurred events distinct.
No automatic background simulation or compulsory escalation is established.
Story secrets are not secure storage for real private information.
Record actual replies, model, settings, failures, and accepted branch.
