chargen.md carried an explicit "[OPEN] taste calls for Cameron" - three sub-decisions never touched since the spec was written (git history shows only a wiki-migration file move), echoed in DESIGN.md's 2026-07-05 decisions log, and never filed as a Tangled issue. Put to Cameron directly this tick: (1) adopt the diegetic frame's three extra columns (built-to fiction, cover expectation, day-job domain lean) onto the four decided origins - adopted, with first-pass [TUNE] content for all four, each line grounded in that origin's existing mechanical biases; (2) add a fifth Sentinel-shaped origin - deferred, since four origins already satisfy acceptance criterion 4 and no-dead-code governs adding a fifth on spec rather than on need; (3) AI-origins only, or keep a transhuman-ascension start - AI-origins only, the spec's own recommendation, now decided. New acceptance criterion 6 requires the added columns be wired to real systems (the picker, economy.md's cover check, day-job.md's job-kind draw) rather than decorative, per "Justification and legibility." Defense: wiki/process/tick.md's Question row - "if it is directional or a matter of taste... file a Tangled issue" - is satisfied more directly here by asking the human the question is addressed to, in the same session, rather than filing an async issue for an answer already given. DESIGN.md's decisions log is amended in place with an inline `Resolved 2026-07-08 (tick):` clause beside the original `[OPEN]` marker, matching the existing 2026-07-05 "repo/binary rename executed" precedent in the same entry; the Bond-villain-flavor half of that marker was not asked about and stays open. chargen.md remains Status: READY - this tick resolved open design questions ahead of implementation, per no-dead-code it did not build the picker speculatively.