Home / Ops / More in this area

Affirmology - Priority Projects (the one prioritized list)

Updated Jul 18, 2026 · Affirmology_PriorityProjects_v1.md

Summary. The single, scannable "what matters most, in order" tracker across all chats. A durable database of active/queued PRIORITY initiatives (not the minute-to-minute build queues, and not done work). Read this to know what to pull next. Newest priorities float to t

Affirmology - Priority Projects (the one prioritized list)

The single, scannable "what matters most, in order" tracker across all chats. A durable database of active/queued PRIORITY initiatives (not the minute-to-minute build queues, and not done work). Read this to know what to pull next. Newest priorities float to the top of their tier. Keep it short: one row per real project, link its doc. (If we want a true queryable DB later, mirror this into Airtable; this markdown is the source until then.)

Tiers: P0 = do now / actively shipping. P1 = next up, decided. P2 = important, not yet scheduled.

ID	Pri	Project	Status	Owner	One-line	Doc
PP-1	P1	Post-Origin CONTEXT CAPTURE + attuned second reading (the "it gets me" week)	Concept doc + Cowork craft DELIVERED 2026-07-18 (attuned_recognition_v1 spec + results-box copy); Code plumbing unblocked; video framing + #3 gift craft still open	Cowork (craft/copy) + Code (engine/site) + DATA (site/profiles)	After the Origin Soul Song listen, a small results-screen box invites life-area + short context; we parse/filter it; the next gift is attuned + more actionable, reverses "too generic" doubt with curiosity, drives the mission-video watch, and builds an "it gets me" feeling over week one.	Affirmology_ContextCapture_AttunedReading_Concept_v1.docx

Notes

PP-1 added 2026-07-18 (Jeff's direct ask). Delivery infra partly exists: the Mirror-drip queue (built + live 2026-07-18, api/mirror_drip.py) is the "gift a few days later" delivery mechanism; the engine already has a current_context capture in the APP (Profile.current_context, set_current_context, context_engine.py) that this would surface on the DEMO results page. Craft tension to resolve: the chart-pure rule (entry pieces never read context, to protect the "how did it know" magic) means the attuned piece must LEAD chart-first and layer context second, or be a distinct context-aware sibling.
REFINED (Jeff, 2026-07-18): NO chart-pure Mirror in the demo sequence. The #2 delivery IS the context+chart reading. The live Mirror got good response but a "needs action" note (a B job); the context+chart, actionable version is the A-job replacement, target SOON. Build the #2 piece first (easier, rides the live Mirror-drip render path).
The #3 gift is a placeholder, delivered in PHASES: first fixed to the ONE form we can do well, then a user CHOICE (gym push / guided or nighttime meditation / EFT tapping / gene keys journey / ...) once we can do several well; always testing + optimizing. Gym push needs a new music bed.