●   ACTIVE BOARD

tasks.

live mirror of vault/00-Action-Items.md active board. edit priority, status, reorder, mark done. saves write straight back.

94total 34must 42should 18could 0parked 84open / in progress 8done
id pri m title due owner status
AB-001 m1 V2 polish: wire Manage Quotas modal — clipboard-pen icon-btn currently has no onClick (P0 in `weekly-v2-polish-backlog.md`) 2026-05-11 Ishai (design) → Duskin (eng)
AB-009 m1 Design visual indicators on quota view for already-assigned tasks (from 2026-05-05 Notion meeting) 2026-05-11 Ishai
AB-004 m1 V2 polish: Backlog group headers — V/R/Done counters + "Assign all →" button (P0) 2026-05-11 Ishai
AB-008 m1 Top 9 P1 items from `weekly-v2-polish-backlog.md` (typography drift, empty-state shape, drag-targets, etc.) 2026-05-11 Ishai
AB-002 m1 V2 polish: Lane day-count chip popover — popover stepper, vacation switch, capacity recompute (P0) 2026-05-11 Ishai
AB-003 m1 V2 polish: Right-click "Send to backlog" context menu (P0) 2026-05-11 Ishai
AB-005 m1 V2 polish: `body.rail-collapsed .app-topbar-start` padding override (P0) 2026-05-11 Ishai
AB-006 m1 Apollo Figma: deliver edge-case variants for Gili (returned-to-pool group, expanded card states, status pills) 2026-05-09 Ishai
AB-007 m1 "Cosmo v2 — New Weekly priority view" presentation prep 2026-05-07 Ishai
AB-010 m1 Grant Gali Pruzansky edit access to "Apollo priority" Figma file 2026-05-06 Ishai
AB-011 m5 Design + spec UX Showcase Site v1 — `vault/08-Design-specs/sett-ux-showcase-site.md` brief; iterate in Claude Design after MVP ships 2026-06-01 Ishai
AB-012 m4 Schedule discovery session with Sergey on client platform integration 2026-05-15 Ishai
AB-013 m2 Pulse TL Layer 1 — surface design from `2026-04-28-pulse-tl-implementation-plan.md` 2026-05-25 Ishai
AB-014 m2 TL monitoring dashboard ("Keep the line moving" + "Review completed tasks") — from buckets below 2026-05-25 Ishai
AB-026 m2 Schedule **Meeting 1 with Elad Verbel** (PG day-to-day discovery). Beginning of day Fri 2026-05-08 or Sat 2026-05-09. Goal: PG walkthrough , how do you spend your day, what hurts, what's missing. Layered questions: INQ-001 (effort estimation, PG view), INQ-007 (PG day-to-day pain), role-silo question, Ideation Request-Ideas + Add-Prompt placement. **Not booked yet , send invite.** 2026-05-08 Ishai
AB-063 m2 Schedule **Meeting 2 with Elad Verbel** (review of wireframes + reactions). Beginning of day Sun 2026-05-10 (before Sergey + Lee PM). Goal: walk Elad through `pg-operational-v1/v2.html` + `cosmo-ia-map.html`, capture reactions, refine before PM. **Not booked yet , send invite.** 2026-05-10 Ishai
AB-027 m2 Design PG operational page. New surface where PGs do their job (separate from TL weekly view). Role-routing: TL sees weekly, PG sees operational. Open question = should both see everything or strictly siloed? 2026-05-25 Ishai
AB-028 m2 Design Settings panel mockup with higher impact. Houses: auditor↔TL allocations, PG↔TL allocations, auditor↔PG allocations, build status view, plus other things currently homeless in the system. 2026-05-25 Ishai
AB-029 m4 Get involved in client platform project from step 1. New customer-facing system where iteration consumers leave feedback. Sergey leading; Ishai's want = active involvement from kickoff, not passive wait. Need to surface design touchpoints before the platform's IA is locked. 2026-05-15 Ishai
AB-030 m2 Decide PG-vs-TL view scope. Should TLs and PGs both see the full system (weekly + operational), or strict role-based silos? Affects PG operational page (AB-027) design. 2026-05-12 Ishai (with Sergey + TLs)
AB-031 m1 Finish remaining V2 Cosmo corrections (AB-001..AB-004). Today + tomorrow if possible. Frees next week for next-phase work. 2026-05-08 Ishai (design) → Duskin (eng)
AB-042 m2 Cosmo IA restructure — Sunday 2026-05-10 plan presentation to Sergey. Page disposition matrix + sitemap diagram + clickable wireframe + reasoning. Subject: `vault/11-Subjects/SUB-003-cosmo-ia-restructure.md`. 2026-05-10 Ishai
AB-043 m2 Author canonical IA spec `vault/08-Design-specs/cosmo-information-architecture.md`. Surface index + role routing + page disposition + per-surface content detail. Born from AB-042. 2026-05-09 Ishai
AB-044 m2 Build IA wireframe prototype `cosmo-design/screens/explorations/cosmo-ia-map.html`. Clickable, made-up content fine, Cosmo DS tokens. 2026-05-10 Ishai
AB-045 m1 Feedback engine in V2. Plan revised 2026-05-07: V1 bug-report endpoint already exists (`POST /api/delivery/bug-report` → `#cosmo-bug-reports`, Yoni 2026-05-04). Two paths: per-card bug button (reuse endpoint), floating general FAB (Slack webhook). Concept: `vault/04-Concepts/feedback-engine.md`. Ship before trial 2026-05-11. 2026-05-11 Ishai
AB-046 m1 V2 launch success measurement plan. Sensors + feedback + interviews. Doc: `vault/04-Concepts/v2-launch-success-measurement.md`. Decide webhook-vs-analytics-tier first. 2026-05-10 Ishai
AB-047 m5 Site A Ventures collection — auto-render `vault/11-Subjects/SUB-*.md` flagged `share: site-a` as a Ventures section on the showcase site. Spec into `vault/08-Design-specs/sett-ux-showcase-site.md`. 2026-06-01 Ishai
AB-048 m2 Inquiry system bootstrap. Concept `vault/04-Concepts/inquiry-system.md`, folder `vault/12-Inquiries/`, INQ-001 (revision effort estimation) seeded. Lock name (Inquiry vs alt), ratify starter list, set brainstorm cadence. 2026-05-13 Ishai
AB-049 m2 First Claude+Ishai inquiry brainstorm. Proposed Wed 2026-05-13 30-45 min. Output: ratified INQ list + approved questionnaires + cadence lock. 2026-05-13 Ishai + Claude
AB-050 m1 Layer INQ-007 (PG day-to-day pain) + INQ-001 (effort estimation, PG view) questions into Elad Verbel interview 2026-05-10. Pre-meeting questionnaire prep. 2026-05-10 Ishai
AB-051 m2 User outreach program , steady cadence: 1 TL/week, 1 PG/2wk, 1 Auditor/2wk. Schedule first TL slot for week of 2026-05-12. 2026-05-25 Ishai
AB-052 m6 Inquiries shelf on Site B. Extend subjects-shelf concept; renders `vault/12-Inquiries/INQ-*.md` with status filters + questionnaire view + data-gathered timeline. Spec into `vault/04-Concepts/personal-cockpit-site.md`. 2026-06-15 Ishai
AB-053 m2 Verify business goals with Sergey. Canonical 6 BGs sourced 2026-05-07 from `vault/01-Context/05-Q2-2026-roadmap.md` and consolidated into `vault/00-Success-Criteria.md`. Verify with Sergey: "are these still the goals, anything missing, anything stale?" Update `00-Success-Criteria.md` after. 2026-05-25 Ishai
AB-054 m2 Build `/inquiry` skill. Args: `add <title>` (creates next INQ-NNN with template), `list` (renders index from frontmatter), `open <ID>` (jumps to file), `interview-prep <INQ-ID...> <role>` (generates pre-meeting questionnaire). Skill file `.claude/skills/inquiry.md`. 2026-05-20 Ishai (spec) → Claude (build)
AB-055 m2 Settings: Capacity defaults section. Auditor working hours (per day, per week) + effort estimate per task type (R/V/NC). Spec: `vault/08-Design-specs/settings-page.md`. Consumed by weekly red-line + AB-014. 2026-05-25 Ishai
AB-056 m2 Tag system overhaul. Audit + collapse chip/tag/badge primitives. Lock color-per-axis rule. Replace label-only tags with icons. Shrink defaults. Subject: `vault/11-Subjects/SUB-009-tag-system-overhaul.md`. 2026-05-25 Ishai
AB-057 m3 Author Cosmo Observability spec. Skeleton at `vault/08-Design-specs/cosmo-observability.md`. Consolidates Status / Dashboard / Auditors / Revisions-analytics / Scorecard / Builds-history / Feedback-archive / Ideation-numbers / McSett into per-role observability surfaces. Depends on JTBD inventory + outreach interviews. 2026-06-15 Ishai
AB-058 m2 DS list/table primitive. Lists/tables across V1 (Admin, Settings, Builds, Feedback, etc.) look inconsistent. Author canonical primitive in production DS (`cosmo-prod/packages/front/src/design-system/components.css` + `components/ui/`). Add showcase entry. 2026-05-25 Ishai
AB-059 m2 PG Operational design directions for Sunday 2026-05-10. 1-2 layout sketches (low fidelity, DS-tokenized) consolidating Delivery + Game-Page-PG-context + quota-vs-actual + Send-with-brief swap + Request Ideas + Add Prompt placement. Output: `cosmo-design/screens/explorations/pg-operational-v1.html` + `pg-operational-v2.html`. 2026-05-10 Ishai
AB-060 m2 Relocate Ideation operational fragments. "Request Ideas" button + "Add Prompt" button → primary actions in PG Operational. Filterable ideas-flow view → observability M3 (reachable as panel/modal trigger from PG Op). Spec into `vault/08-Design-specs/cosmo-information-architecture.md` once authored. 2026-05-25 Ishai
AB-061 m2 Decide home for "browse my past feedback" feature. Settings sub-section vs sidebar icon vs observability tab. Tied to SUB-003 disposition of Feedback page. 2026-05-15 Ishai
AB-062 m1.5 Find existing PG feedback / interview material in vault before Sunday. Mine `vault/06-Meeting-notes/` + `vault/02-Users/` + Ishai's recent calls for any signal on PG day-to-day pain. Feeds AB-059 (PG Operational directions) + AB-026 (Elad interview prep). 2026-05-09 Ishai (or Claude background)
AB-064 parked **NA-002 night action** , wireframe DS strategy spike. Decide between: (a) keep `cosmo-design/screens/wf.css` separate, (b) clone production DS as `wf-theme/` variant, (c) add `data-theme="wireframe"` to production DS (zeroes radii/shadows/orange, never exposed to product). Spawn `design-system-curator` agent. Output: `vault/08-Design-specs/wireframe-theme-strategy.md`. Concept: `vault/04-Concepts/night-actions.md` § NA-002. post-M1 Ishai (queue) → agent (run)
AB-066 m2 Investigate "Status meeting prep" V1 use case. Someone uses the Status page for meeting prep , who, what meeting, what numbers? Layer into Elad / Harel interview questions or ask any PG. Findings inform whether PG Operational observability strip needs a "meeting-prep" mode or just a copy-numbers-as-text shortcut. Salvage source: `vault/03-Cosmo-pages/05-v1-page-salvage-2026-05-08.md` § Status. 2026-05-25 Ishai
AB-067 m2 Clarify "Add Prompt to Game Program" semantics with PG. Does it (a) add to game's idea pipeline for Atlas/agents to pick up, or (b) create a draft idea visible only to PG until pushed to quota, or (c) something else? Affects Ideas side-panel design in PG Operational. Layer into Elad interview. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Ideation. 2026-05-15 Ishai
AB-068 m2 Decide Settings home for "Import tasks" (legacy Monday import). Candidates: Settings:Imports & Migration sub-section (already planned in IA spec § Bucket C), or new Settings:Tools area. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Ideation. 2026-05-15 Ishai
AB-069 m2 Investigate "78 stuck/failed builds" backlog visible in V1 Builds page. Who currently owns clearing this queue? Is "stuck" actionable (retry succeeds) vs "failed" (needs code/config fix)? Worth a problem-catalogue entry on its own. Ask Duskin / DevOps. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Builds. 2026-05-15 Ishai
AB-070 m2 Decide PG Operational primary view shape. Options: (a) Delivery-list-as-spine (one big sortable/filterable playable table = PG Op), or (b) game-centric overview page + separate Delivery surface. Affects nav slot count and IA bucket structure. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Delivery. 2026-05-12 Ishai
AB-071 m2 Decide tabs-vs-status-filter for Delivery list. V1 has 4 tabs (Ready to Send / Revisions / Waiting for Customer / Completed) plus 3 sub-tabs in Revisions. Per-row actions differ across states (Send only on Ready, Completed only on Sent, History only on Sent), so flat-list-with-status-filter may need conditional action affordances. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Delivery. 2026-05-15 Ishai
AB-072 m2 Verify Revisions sub-state semantics with PG / Duskin. What is "In Progress" (49) vs "Pending Allocation" (34) vs "Dead Ends" (26)? Hypothesis: In Progress = Apollo working, Pending = waiting for auditor assignment, Dead Ends = cancelled/failed. Layer into Elad interview. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Delivery. 2026-05-15 Ishai
AB-073 m2 Define bulk-operations scope for Delivery list. V1 has bulk rebuild + bulk rebuild-without-analytics. Audit other useful bulk ops (send, reject, reassign auditor, mark complete). Ask PGs which bulk actions would actually save time. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Delivery. 2026-05-18 Ishai
AB-074 m2 Confirm "default sort = SLA urgency" with PGs. Is SLA proximity the right "what should I touch first" signal, or do partner tier / game importance / revision count override? Layer into Elad interview. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Delivery. 2026-05-15 Ishai
AB-075 m2 Map playable type taxonomy (Version / Concept / Core / others?). Defined where in DB? Orthogonal to pipeline status states? Confirm with Duskin and document in `vault/04-Concepts/Playable-Schema.md`. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Delivery. 2026-05-15 Ishai
AB-076 m2 Clarify "No Sett AL Analytics" badge semantics. When fires, what triggers it, is it a quality flag (analytics gate failed) or a missing-data flag (no analytics yet)? Affects how we treat it in PG Op surface. Ask Duskin. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Delivery. 2026-05-15 Ishai
AB-077 m2 Clarify "Swap playable in brief / Swap label in brief" semantics (P44). Source: Yuval R2 "Replace the Apollo prompt with the short delivery brief on send." Hypothesis: send-to-client message currently uses Apollo prompt text; PGs want it replaced with curated short delivery brief. Verify exact mechanic + where the brief lives + who edits. Layer into Yuval / Elad interview. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Delivery (Q9). 2026-05-15 Ishai
AB-078 m2 Verify two-types-of-feedback state machine with Duskin + PG. Hypothesis: Internal Sett feedback keeps asset as Version (WIP, same timeline); Client feedback creates Revision (new task, timeline zeros). Confirm exact state transitions + where in DB this lives. Foundational for AB-079. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Feedback (Q1). 2026-05-12 Ishai
AB-079 m2 Design "feedback without creating Revision" affordance. PG (and other internal reviewers) need way to leave feedback at any stage , including post-approval , without bumping playable into Revision state. Pollution of Revision queue with PG-internal notes is current pain. UX questions: which stages permit it? inline comment box vs side drawer vs floating button? distinct from "Reject / Request Revision" action. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Feedback (Q2). 2026-05-15 Ishai
AB-080 m2 Verify if anyone actually uses V1 Feedback page as a chronological flat list of all feedback. Hypothesis: it exists only because there was no other place to see comments. Once Detail Panel surfaces per-playable feedback thread, the flat-list page is redundant. Ask TLs (Tatiana?) + PGs in interviews. If yes-used, lands in Settings:Monitoring split (AB-081); if no, drop entirely. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Feedback (Q3). 2026-05-15 Ishai
AB-081 m2 Decide Settings split: config-only vs config + monitoring-views. Many "salvaged-to-Settings" items (Builds activity log, Imports status, possibly Feedback log, allocation views) are not configuration , they're read-only monitoring/log views. Options: (a) keep as one Settings surface with config + monitoring sub-sections, (b) split into Settings (config) + Monitoring/Activity (read-only lists) as two separate nav slots. Affects nav slot count and role-routing (PG vs TL who needs which). Salvage source: `05-v1-page-salvage-2026-05-08.md` § Feedback (Q4). 2026-05-12 Ishai
AB-082 m2 Clarify game-grouping color-coding semantics in V1 Revisions page (red / orange / green dots per game). Disney Solitaire = red, Triple Match = orange with 1 red revision inside , inconsistent. Hypotheses: severity bucket vs SLA breach vs something else. Read V1 code + verify with Duskin. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Revisions (Q1). 2026-05-15 Ishai
AB-083 m2 Define history-timeline event taxonomy for Detail Panel. Candidate event types: communication (Slack, email), builds (queued, completed, failed), status changes, feedback (internal + client), revisions (created, resolved), sends (to client, to Apollo), assignments (auditor / owner change). Confirm full set + DB sources with Duskin. Foundational for history-filter UX (AB-079, Detail Panel feedback affordance). Salvage source: `05-v1-page-salvage-2026-05-08.md` § Revisions (Q2). 2026-05-15 Ishai
AB-084 m3 Maintain running M3 observability pile doc as M2 page walks surface deferred items. Candidate path: `vault/03-Cosmo-pages/03-m3-observability-pile-2026-05-08.md`. Already-deferred items: revision KPI squares + trend + cause investigation, dashboard delivered/declined/approved comparison, auditors per-auditor counts, status pace bars (PG Op already takes the operational version), full Scorecard KPI strip + trend charts + daily pace + status distribution + revision rate. Decide whether to start the doc now or wait until M2 ships. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Revisions (Q4) + § Scorecard. 2026-05-25 Ishai
AB-085 m3 Replace misleading "In Pipeline / % of quota" KPI on Scorecard. 165% of quota is normal because each playable spans 8+ stages, so in-flight count >> quota by design. Replace with useful metric: in-flight per active game, or average days-in-pipeline, or in-flight by stage with health flags. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Scorecard (Q1). 2026-05-25 Ishai
AB-086 m2 Document gap-to-pace + daily-pace derivation formulas. Confirm: gap = quota × (today / month-working-days) , delivered. Working-days vs calendar-days. Required-pace = remaining-quota / remaining-working-days. Standardize before re-using on PG Op per-game header card. Ask Duskin. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Scorecard (Q2 + Q3). 2026-05-15 Ishai
AB-087 m2 Document Revision Rate target source (15% in V1 Scorecard). Who sets it? Per-game vs portfolio-wide? Per-month or rolling? Source: PG team / leadership / contractual? Affects whether target stays single-value or becomes per-context. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Scorecard (Q4). 2026-05-15 Ishai
AB-088 m2 Document game-health bucket thresholds (Behind / At Risk / On Track / Not Started). What pace-deficit triggers each? Currently in V1 with 28 Behind / 7 At Risk / 9 On Track / 7 Not Started (51 total). Need rules to reuse on PG Op. Read V1 code or ask Duskin. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Scorecard (Q5). 2026-05-15 Ishai
AB-089 m2 **Status taxonomy alignment (foundational).** V1 has at least 3 unaligned status taxonomies: (a) per-playable pipeline stage (Ideas / Apollo / Building / In Review / PG Review / Ready / Delivered / Accepted + Revision/Failed terminal), (b) per-game health (Behind / At Risk / On Track / Not Started), (c) per-playable delivery flow state (Ready to Send / Revisions / Waiting for Customer / Completed). Plus orthogonal: type tag (Version/Concept/Core, AB-075), revision status (Open/Resolved, AB-082), quality flag ("No Sett AL Analytics", AB-076). V2 needs single canonical state machine with derived views. Pre-requisite for clean PG Op design. Spike + decide before wireframing PG Op final shape. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Scorecard (Q6). 2026-05-12 Ishai
AB-090 m2 **Verify revision↔orchestration relationship.** V1 Orchestration page does not list revisions of itself. Unclear whether a `request_revision` action spawns a NEW orchestration with its own ID, or modifies the same orchestration's state. Foundational for Detail Panel design , determines whether the panel shows "revisions of this playable" as a sub-list (one orchestration, many revisions) or each revision is its own top-level row (one orchestration per revision). Verify with Duskin + read V1 backend code. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Orchestration (Q1). 2026-05-12 Ishai
AB-091 m2 Document Orchestration page action semantics: Reset, Cancel & Reuse, Archive, Report Bug. Cancel & Reuse , does it spawn a new orchestration with same idea or rewind? Reset , wipes state to start or re-queues build? Archive , soft-delete or just hides from active queue? Report Bug , routes to where? Confirm with Duskin + decide V2 affordances. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Orchestration (Q2 + Q3). 2026-05-15 Ishai
AB-092 m3 Decide whether V2 needs deep-link admin route `/orchestration/<id>`. Same content as Detail Panel but full-screen, for power users (Duskin debugging, support tickets). Detail Panel may cover all PG-side needs; admin route is debugging convenience. Likely M3 or later. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Orchestration (Q5). 2026-06-15 Ishai
AB-093 m2 Verify if V1 has an "add game" flow buried somewhere (or game-creation is backend-only). New Settings:Games panel needs an explicit "Create game" affordance. Ask Duskin. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Game Management (Q1). 2026-05-15 Ishai
AB-094 m3 Decide if Customer/Partner deserves a top-level Settings section (Bold Games, Papaya, Moon Active, ...). Currently surfaces only as INFO field on game record. May warrant own entity for tier policies, contact info, billing context. Likely M3+. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Game Management (Q2). 2026-06-15 Ishai
AB-095 m2 Clarify "ACK" acronym in Game Details "Game Knowledge (ACK)" panel. Hypotheses: "Acknowledged Knowledge", "Agent Context Knowledge". Verify with Duskin. Affects header copy and conceptual framing. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Game Details (Q2). 2026-05-15 Ishai
AB-096 m2 Map Game Knowledge (ACK) source-of-truth + edit affordance. Sections: Production Rules / Preferences / Rejected Patterns / Ideation Requirements. Examples reference `raw-files/*-ip-world-rule.md` source paths , markdown files in repo vs DB-stored content vs both? Does V1 have UI edit affordance or is it backend-only file editing? Decision affects Settings:Games edit flow + Game Details read pane. Ask Duskin + read backend code. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Game Details (Q3 + Q4). 2026-05-15 Ishai
AB-097 m2 Decide Game Details surface routing for V2: (a) game-centric mode inside PG Op, (b) shared side-panel slide-over from anywhere "View Game" is clicked, (c) standalone deep-link route `/game/<id>`, (d) combined (b)+(c) via shared content component. Recommend (d) , one component, two mount modes. Decide post-Sunday wireframes. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Game Details (Q1). 2026-05-15 Ishai
AB-098 m2 Decide pagination / load-more strategy for per-game Activity timeline. Big games may have thousands of state transitions across all playables; "show all" is wasteful. Default last 30? Last 7 days? Filter by event category (AB-083). Salvage source: `05-v1-page-salvage-2026-05-08.md` § Game Details (Q5). 2026-05-15 Ishai
AB-099 m2 Sweep IA spec (`vault/08-Design-specs/cosmo-information-architecture.md`) + earlier salvage entries to disambiguate "Game Page" references. Replace with: "Settings:Games" (management) or "Game Details" (view-only deep-dive). Two distinct surfaces, currently conflated. Salvage source: `05-v1-page-salvage-2026-05-08.md` § Game Details (Cleanup). 2026-05-10 Ishai
AB-065 parked **NA-001 night action** , vault staleness scan. Spawn `general-purpose` agent to walk all `vault/**/*.md` flagging references to renamed paths, retired concepts (Concept A/B/C, V1 prototype shapes, deleted `cosmo-backend-readonly/`), superseded decisions, broken AB/SUB/M references. Output: `vault/_audit/vault-staleness-YYYY-MM-DD.md` with per-file recommendations (fix / archive / delete / leave with caveat). Concept: `vault/04-Concepts/night-actions.md` § NA-001. overnight any time Claude (agent)
AB-035 m6 Write Site B (Personal Studio) design brief. Mirror M4 brief shape; reference `vault/04-Concepts/personal-studio-site.md`; output to `vault/08-Design-specs/personal-studio-site.md` with Claude Design prompt at the bottom. 2026-06-15 Ishai
AB-036 m6 Bootstrap subjects shelf. SUB-001 + SUB-002 written. Decide whether to backfill subjects from recent activity log, or start fresh. Write convention into `vault/11-Subjects/README.md` (done) + activate auto-create rule in next sessions. 2026-05-25 Ishai (rule) → Claude (execution)
AB-037 m6 Decide M6 (Site B) subdomain. Candidates: `studio.sett.ai`, `me.sett.ai`, `desk.sett.ai`. Check Cloudflare DNS access. 2026-06-01 Ishai
AB-038 m6 Decide prototype-hub Figma metadata format. Per-prototype `<name>.meta.json` sidecar vs frontmatter on matching `vault/08-Design-specs/<surface>.md`. Lower-friction wins. 2026-06-08 Ishai
AB-039 m6 Spike Site B prototypes-hub production status detection. Read git status of `cosmo-prod/packages/front/` for ahead-of-main count + last-deploy timestamp. Local only (no remote auth). 2026-06-08 Ishai
AB-040 m6 Spike run-action buttons execution layer. Options: GitHub Actions trigger via PAT, local agent endpoint (small Express server), defer to v2. Pick lowest-friction or punt. 2026-06-15 Ishai
AB-041 m5 Add Giscus comments to Site A (Showcase). Free, GitHub-backed. Spec already updated. Wire during v1 implementation. 2026-06-01 Ishai
AB-100 m2 Allocations matrix chrome still drifts from DS even after 2026-05-11 triple-fix (border / group-row bg / group-spacer bg). User reports residual dark patches. Likely 4th rule still overriding (`.alc-corner` bg, `.alc-row-header` bg on group rows, or wrapper-vs-table cascade). Re-audit all `.alc-*` rules in `settings-v1.html` against DS `.dt-table`/`.alc-group-row` and reconcile. Possibly promote the matrix-spacer/group-row rules into DS `components.css` so settings-v1 has nothing local. 2026-05-18 Ishai
AB-101 m2 Design "Quota viewer" for PGs / TLs who need to see actual quota totals (Daria flagged: can't see actual quota in V2). Sergey + Ishai to productize the "Total vs wanted quota" view. Surface: separate read-only quota summary panel or header widget. Source: Slack #cosmo-v2 2026-05-11. 2026-05-14 Ishai + Sergey
AB-102 m2 Design "Last Mile status" indicator showing who a task is waiting on: auditor / PG / TL / CP. Ishai's UX issue from New Cosmos Workflow Check-In 2026-05-12. Add to Weekly board spec and manage-quotas spec. 2026-05-14 Ishai
AB-103 m2 Fix: quota task name display on quota card - show single name if one task, show hover/expand or "+N" if multiple tasks. Sergey's UX issue from #cosmo-v2 2026-05-11. 2026-05-14 Ishai (design) + Duskin (eng)
AB-104 m2 Check-in with Ariel re: terminology/strategy for "ideas" vs "detached tasks." Both are available potential for quota assignment. Currently displayed separately in prototype but Sergey confirmed they should be unified. Source: Notion meeting note 35e8755e 2026-05-12. 2026-05-14 Ishai
AB-105 m2 Design rollover semantics display. Rolled-over quotas from prior week do not count as current week's quota. Need a visual treatment that distinguishes rollover from current-week quotas in the weekly view and quota manager. Source: Notion meeting note 2026-05-12. 2026-05-19 Ishai
AB-106 m2 Design Cosmo Quota Management page - replacement for old weekly quota assignment view. Kick-off held 2026-05-12 with Sergey, Yuval, Lior, Omer. Lior Finkelman writing PRD. Ishai spec: `vault/08-Design-specs/workshop-quotas-list.md`. Prototype: `cosmo-design/screens/explorations/workshop-v1.html` (shipped in lab 2026-05-12). 2026-05-19 Ishai (design) + Lior (PRD) + Yuval/Omer (eng)
AB-107 m2 Meet with Elad Werber for PG UX JTBD discovery. Meeting accepted for 2026-05-12 14:30-15:00 IDT. Follow-up with second meeting TBD. Source: cal:4uqkh0otmm6vdlc8trr6qplprm 2026-05-12. 2026-05-12 Ishai
AB-108 m2 Review Creative Library UX sync (Yiftach Ginger, 2026-05-12 11:30-12:00 IDT). New surface request - creative library UX context to capture from that meeting. 2026-05-13 Ishai
94 rows · click pri/status to change · drag rows to reorder · ✓ marks done