docs: scenario design, Fella's bad day at the office #2
Loading…
Reference in a new issue
No description provided.
Delete branch "nibu/scenario-fella"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Docs only:
docs/scenarios/fella-bad-day-at-the-office.md. Concept by Meta (2026-11-06); the protagonist's name, Fella, is by Deru.Base:
main(b02049e). That is a README-only tree: the pain box anddocs/pain-sweep.mdlive on PR #1 (nibu/pain-box-first-slice), not onmain. The doc links them by their PR-branch URLs, which will need repointing tomainpaths once #1 merges. If you would rather this stack on #1, say so and I will rebase.What it specifies: the scenario as authored data (documents, not JSON; phases derived from actor state, stressor schedule table, break condition, the goal flip as one typed actor state change, jelly limbs as per-muscle strength); measurable outputs per phase beyond time-to-break (my answer to Deru's open question: a survival curve plus a composure margin and per-phase quantities, with low confidence until a player has felt them); coworker personality axes as data (five axes, five archetypes, one shared behaviour selection weighted by axes); what Lodur and Ymir must expose; three tuning checks.
Design choices to review: Fella reuses the pain box's mechanism (composure is the drive's resolve, sensory load is stimulus into the nerve layer, the flip is the same
HoldHandtoWithdraw-style goal flip) rather than adding a second one. The flip is one event, so nothing special-cases the break. Coworkers may touch the scenario only by three authored paths, so personality effects can be isolated.Every number is marked
[P](placeholder). Nothing is built or measured. Merge nothing.🤖 Generated with Claude Code
Self-review of the ladder and the setting/cause split, against Meta's messages of 2026-11-06. Findings: (1) the ladder was not at the head of the doc; (2) the scenario document held
actor,coworkers,stressors,breakConditionandflipas one blob, so the office and the sensory-load cause were hard-coded together, and Fella was named in the schema. Pushed a revision to this branch: a "The ladder" section with the seven rungs and their status (rung 1 now has draft PRs, rung 2 is the pain box), a "Setting and cause" section, and the Scenario field list split intosetting(place, emitters),cause(drivers, break condition, flip, drive mapping) and anactorrole, with the existing office and sensory-load content marked as one pairing. Nothing else in the doc changed. Still every number[P]; nothing built or measured here.🤖 Generated with Claude Code
Steward check before merge (nibu, 2026-11-10). Docs only.
docs/pain-sweep.md). Its reference to Ymir#1 (SoA world) now resolves to a merged PR, and the Ymir joints PR (#2) merged too.