Open Questions — Decisions to Make

← tree index

Questions raised by the source material or implied by gaps in it. Each has a default recommendation where one is reasonable. Tackle the 🔴 blocking ones before building the relevant slice.

🔴 Cycle naming consistency

The v2 user-stories doc still uses the 7-stage cycle (…Activate…Reinforce…Repeat). The v3 doc uses 6 stages (…Practice…Adjust). Any UI copy, enum, or DB constant must use v3. Decision needed: confirm the 6-stage names are final and freeze them as the canonical enum. Recommendation: yes — adopt v3’s 6 stages everywhere; deprecate v2 names. See applied-learning-cycle.

🔴 How is “application” evidenced?

The Apply phase requires “evidence of application (artifact, observation, self-report).” But the source doesn’t specify the capture UX. Decision needed: which evidence types ship first, and is self-report alone enough to count as “applied” for metrics? Tension: self-report is easy but soft; artifact/observation is rigorous but high-friction. Recommendation: start with structured self-report (+ optional artifact upload) so the time-to-apply clock has data; layer observation later. See metrics.

🟡 Nudge cadence & fatigue

IS schedules 1–3 follow-up nudges [G2]. Decision needed: channel (in-app / email / both), spacing, and a global cap so the cascade across phases doesn’t overwhelm. The v2 doc hints “auto-nudge: what in-app · flag to IS + LA” but is incomplete. Recommendation: email + in-app, hard cap per participant per week, IS can mute. See intervention layer.

🟡 What anchors the 24h/48h/5d timers?

Do the application windows start from the IS “mark complete” timestamp (cohort-wide) or per-participant (e.g., when they finish the session)? Affects fairness for async attendees. Recommendation: anchor to mark-complete by default; allow per-participant offset for async.

🟡 Briefing Report — in-platform or HubSpot?

v3 raises this as an explicit open question. Decision needed: do Client Directors create the Briefing Report in-platform (structured intake, queryable, visible alongside the LA Context Profile) or keep it in HubSpot? Recommendation (from v3): in-platform. HubSpot keeps the commercial role; platform owns delivery. See business loop.

🟡 HubSpot integration depth & direction

P1 says “platform pulls engagements from HubSpot… this may be a future capability” and S2 says engagement details “may be manually inserted by Platform Manager.” Decision needed: ship with manual PM entry first, or build the HubSpot pull up front? What’s the renewal-signal push contract (object, properties)? Recommendation: manual entry first (de-risks v1); design the data model so the pull is a later adapter, not a rewrite. See data & integration.

🟢 Pulse “notable outliers” without scoring

[E4] flags “notable outliers / pattern-based” while [C3] forbids scores/pass-fail. Decision needed: how to compute an outlier flag that stays pattern-framed and never reads as a grade. Recommendation: surface distribution shape (“most of your cohort is at comfort 2/5 on X”) rather than per-person flags. See pulse check.

🟢 Async attendance semantics

Engage supports “in-person / virtual / async.” Decision needed: for async, what counts as “attended + engaged,” and how does it interact with the day-of content-visibility gate?

🟢 Certificate content & authority

Certificate is gated behind survey completion [P4/S4]. Decision needed: what does it certify (attendance? application?), who issues it, and is it shareable (PDF / credential)?

🟢 Context override precedence

School Context Profile updates apply to “future engagements unless overridden at the workshop level.” Decision needed: precedence rules + audit when school-level and workshop-level context disagree. See context layer.