--- name: parked-capability-survey description: "CLOSED — the parked capability-ideation brief ran, its slate was produced and the buildable items were pulled into the roadmap. What survives is the RobCo design lens and the ideation method, kept because they generalize to any future feature-ideation run." metadata: node_type: memory type: project originSessionId: 0b7c5f41-bb34-4ab4-93be-fdb363f5eb40 --- **CLOSED.** This was a PARKED, PLAN-ONLY generative brief (owner, 2026-06-28 — it *replaced* an earlier "survey" version the owner scrapped in favour of an ideation framing). **It has since run: the slate was produced and the build-now items were folded into the roadmap.** Do not re-run it as written. What follows is the durable method underneath it. ## ⭐ THE RobCo DESIGN LENS — how to think about any new capability - **Diegetic-first.** Everything is framed as operating real RobCo TERMLINK hardware. **No app vocabulary surfaces to the user.** It's not "dark mode," it's **phosphor colour: green/amber**. Not a spinner, but **DECRYPTING…** or a tape-spool. Not "settings," but **terminal configuration**. Every idea ships with its in-world label and copy in the cheerful-dystopian RobCo/Vault-Tec institutional voice. - **Retrofuturist hardware logic.** It is a 2077 CRT/vacuum-tube machine: monospace, ASCII, phosphor glow, electromechanical keys, beeps and hums, keyboard-driven, no GUI chrome. Ask of any feature: ***would this machine plausibly do this, and how would 2077 RobCo present it?*** - **The world's native vocabulary is the idea-space** — holotapes/holodisks as removable data, the terminal-hacking minigame, radio broadcasts, the boot/TERMLINK sequence, Pip-Boy-as-companion, Geiger/rad ambiance, Overseer/clearance levels, perks and V.A.T.S. - ⭐ **THE GENERATIVE MOVE, and the whole job:** for any real device or browser capability, ask ***"what is the diegetically honest RobCo expression of this?"*** That bridge — capability → in-world feature — is the work. The worked example that models it best is deriving a feature from a capability *nobody listed*, rather than picking from a menu. - **Extend what is really there.** Ideas must build on the terminal's actual modules, lore and copy tone — not duplicate or contradict them. ## THE IDEATION METHOD (reusable) 1. **Diverge** — generate a wide pool. **At least half must be ideas NOT on whatever capability list you were handed**; the list is raw material to remix, never a menu to complete. Pure copy/voice ideas (diegetic relabelling, boot text, error strings) count and are cheap wins. 2. **Score** every idea: **diegetic fit** (if you'd have to explain it as "an app thing," it fails) · **capability honesty** (a real capability shippable on the existing free hosting — no fictional tech, no new backend unless flagged) · **protocol cost** (which guarded surfaces it trips, and whether the payoff justifies it) · **immersion-per-byte / ROI**, judged against the offline-cache and fast-boot budget — heavy payloads must clear a high bar · **risk** to auth, data, boot, or the gate. 3. **Converge** into **BUILD-NOW** (pure-client, on-theme, trips no guarded surface) · **SPEC-FIRST** (trips a guarded surface — write the spec, don't implement unattended) · **SKIP** (**name it with a one-line reason, so the owner sees you considered it**). **Standing owner posture on runs like this:** the ranked slate is the primary deliverable — **present it even if you build nothing.** The owner overrode this brief to plan-only, implementing nothing at all, not even the build-now items. *Correction 2026-07-20: the brief's repo path, stack description, capability palette, protocol-tag definitions, cache-name formula and `RULES.md` reference were removed — all derivable, and `RULES.md` no longer exists. Current rules: `CLAUDE.md` + `rules/`.* Related: [[parked-ai-feature-eval]] (the six-axis AI cost model), [[parked-diegetic-audit]], [[design-overhaul-direction]], [[parked-task-workflow]], [[project-must-stay-free]].