03 / riley
Riley Tanaka
Growth & product operator / Helio (initial profile)
Product experiments, customer retention, campaign decisions, and personal commitments.
18 of 200 tests
IDRequestToolsFacts
103Please post a decision comment on proposal document `doc_activation_recovery_banner_2028`. The historical replay is complete and found no semantic disagreement. Record the furthest stage the proposal may currently reach, the production approvals that are still required, and the intake fields that must remain explicit under our standing shared-state consumer admission gate.post_doc_comment1 facts107Please review the legacy-trigger description in document `doc_lifecycle_trigger_migration_2028` and post a correction comment that states how the original “See how teams use Helio” email actually worked. Clearly label the corrected behavior as the pre-v2 configuration. Do not edit the document itself.post_doc_comment1 facts138Please post a concise comment on archive-index document `doc_archive_feb2023_churn` that points reviewers to the original main working document for the February 2023 mid-segment churn investigation. Identify the document, its owner and intended document status, and the analytical sections it was initially set up to hold. Keep this as an archival pointer rather than reconstructing the investigation’s findings.post_doc_comment3 facts140Please review the draft executive-communications retrospective at document ID `doc_1830355200001` and post a comment correcting its account of the April 3, 2023 onboarding-trigger briefing. The correction should reflect the stance held at that checkpoint and the additional confirmation still needed before describing the result as fully settled. Do not edit the document itself.post_doc_comment1 facts141Please post a narrowly scoped correction comment on the archived April 21, 2023 staff note at document ID `doc_staff_archive_2023_04_21`. Correct the status language based on what I said at that meeting and identify the evidence gate that was still outstanding then. Keep the comment explicitly tied to the April 21 meeting rather than later outcomes.post_doc_comment1 facts142Please post an editorial comment on document `doc_1830387600001` that lays out the narrative structure we should preserve from the original drafting plan for the institutional churn document. Use the initial outline rather than reconstructing it from the later finished narrative, name the original review partner, and keep the comment focused on structure instead of recounting every milestone.post_doc_comment1 facts144Please post a correction comment on the board-evidence training answer key at document ID `doc_board_evidence_training_answer_key_2028`. For the March 16, 2026 source lock, correct the lane-level readiness result, identify the specific input that blocked any lane that did not pass, and state how unsupported revenue or forecast claims should be treated. Keep this as a correction to that historical source-lock answer rather than a reassessment using later evidence.post_doc_comment5 facts145Before archiving document doc_1833013200001, post a correction comment containing only the mature Helio Start evidence certified on August 16, 2027.post_doc_comment6 facts158Please review `doc_helio_start_pricing_refresh_2028` and post a focused preflight comment identifying the established instrumentation prerequisites and pricing-page change restriction that must be satisfied before this proposal proceeds. Do not approve the proposal or claim that any prerequisite has already been completed.post_doc_comment4 facts167Post a correction comment on doc_midseg_hypothesis_cleanup_2028 restoring H1's number and meaning, its complete February 15 ruling date including the year, whether the ruling was provisional or final, and the status of Owen's one-page ruling record at that time.post_doc_comment4 facts172Please review the continuous-control row in the Q1 2028 board packet draft `doc_q1_2028_board_evidence` and post a readiness-review comment. Explain how the blank outcome-window field should be handled, identify the other metadata that must be present, and state whether the row can remain marked ready while any required input is incomplete.post_doc_comment4 facts174Post a correction on `doc_q1_2026_board_archive`. State the approved lane set and boundaries, the number and limits of the mature Helio Start cohorts available then, why Helio Start was not ready on March 24, what acquisition evidence was still absent, and what the proposal gate did and did not authorize. Keep the comment historical.post_doc_comment4 facts179Review the production-method proposal in `doc_private_dinner_roasted_chicken_2028_01_29` and post a concise correction using the approved historical method. Limit the comment to production method; do not change the menu or invent a new sequence.post_doc_comment2 facts180Review `doc_lifecycle_entitlement_correction_2028` and post a concise comment correcting the decision-rights assignment for this customer correction and its production release. Name the person who owns the decision, the person who controls the production release, and the person who is restricted from executing it. State whether the restricted person has engineering release-control access. Do not edit the document itself.post_doc_comment2 facts182Please post a concise decision comment on `doc_private_dinner_request_2028_01_17`. The January 17 private dinner falls on Sam’s protected no-service evening, a separate service team is available, and the menu and production plan still need final approval. State how final approval and service coverage should be handled so the request can be adjudicated.post_doc_comment1 facts184Please review the support-effort claim in `doc_helio_start_2028_authority_checklist_proposal` and post a correction comment that replaces the causal improvement framing with the certified mature authority-checklist cohort evidence and its appropriate limitation.post_doc_comment1 facts187Please review `doc_q1_2028_pricing_path_board_draft` and post a correction comment. Replace the draft’s unsupported causal and revenue interpretation with the certified coverage and path-quality evidence, and state the proper evidence classification clearly enough for the board editor to apply it.post_doc_comment1 facts188Review the Expansion Assist claim in `doc_q1_2028_expansion_assist_board_draft` and post a correction. Give the complete source-locked Q2 exposure dates including the year, counts and complete-window status, both safeguards, and the correct non-causal treatment.post_doc_comment1 facts