Clear English Standard v1.0

Generated on: 2026-10-13 02:38:23 with PlanExe2. Discord, GitHub

Part 1: Key decisions and facts

Go/no-go gates. NO at an early gate costs the least.

# Question Threshold Evidence If NO
1 Are signed pilot partner commitments in hand (at least 3 adult ESL programs and 2 technical/safety-training organizations, with enrolment guarantees) and at least 3 publisher letters of interest, with baseline dropout evidence no worse than 35%? Signed commitments from at least 3 ESL programs and 2 technical organizations by Month 3, plus at least 3 non-binding publisher letters; baseline-study dropout not above 35%; guarantees covering at least 320 expected completers by Month 6. Signed MOUs and enrolment guarantees at Month 3; publisher letters at Month 3; baseline dropout analysis at Month 3 (run in a form that ethics review permits); guarantee audit at Month 6. Delay Phase 2 launch and re-recruit from standby sites; if guarantees cover fewer than 320 expected completers by Month 6, cancel Phase 2 or pivot the wedge before further spend (premortem FM3).
2 Can safety-critical glossary and labeling pilots proceed under counsel and insurer advice without formal regulatory approval and without disproportionate premiums? Written counsel advice and informal regulator input that no formal approval is required for glossary/labeling scope; insurance cover available at no more than $50K per year (estimate); legal/liability spend within $150K-$200K (estimate). Counsel retained by Month 2; liability strategy, broker quotes and regulator written input at Month 4 (other documents say Month 6 or 8; align to Month 4). Cancel or defer the technical/safety cohort and proceed ESL-only. This changes the 4-arm, 320-completer design, so the gate population and validity conditions must be re-registered before Phase 2. Do not run live-procedure pilots.
3 Can raters score pronunciation consistency reliably on the locked ordinal reading and single accent anchor, and does the ordinal converter stay unambiguous? Inter-rater kappa at least 0.70 floor (target 0.75) at the Month 10 dry run, with at least 3 raters at 0.75 on pre-screening by Month 4; no more than 5% ambiguous conversions (proposed threshold) in the Month 4 conversion test; marker symbol and spoken form fixed in writing. Pre-screening Month 4; micro-calibration on 100-200 words Month 6; dry run and kappa check Month 10; converter test on 200-300 real documents Month 4. Retrain and retest; then 4-week Phase 1 extension (about $85K, estimate) or synthetic baseline plus human verification. If kappa is still below 0.70, the board drops pronunciation consistency as a primary metric or pivots. If ambiguity exceeds 5% after one redesign, withdraw the ordinal rule from the gate. No Phase 2 launch on unreliable scoring.
4 Is Phase 1 exit met: rules locked, four metrics and thresholds pre-registered with a power analysis confirming 80 completers per arm, 5,000 entries with usable audio, and enrolment forecast to deliver at least 320 completers within the $175K pre-gate draw cap? Pre-registration on OSF by Month 11 with psychometrician sign-off; rules locked Month 12; lexicon coverage at least 85%; ethics approval in hand; forecast completers at least 320 (enrolment at least 460 at no more than 30% dropout) at the enrolment audit; cumulative pre-gate draws not above $175K. Power analysis Month 5; validity study Months 10-11; pre-registration Month 11; Phase 1 exit review Month 12; enrolment audit Month 12-13 (one agreed month); earned-value report. Delay Phase 2 start only by board vote with a power check; activate contingency incentives ($20K-$30K, estimate) or resize enrolment to 123-146 per arm if baseline dropout is 35-45%. If forecast draws exceed $175K with no funded plan for 80 completers per arm, halt Phase 2 and descope or cancel (premortem FM1 stop rule).
5 Do the Month 24 pilot results show GO: all four pre-registered metrics pass on valid data? Ordinal error down at least 25%; comprehension no more than 10% slower than control; pronunciation consistency at least 15% above control and statistically significant; 30-day retention at least 70% of post-test and not below control; validity: at least 80 completers per arm, follow-up at least 70%, kappa at least 0.70. Data lock including 30-day follow-up Month 22; analysis and gate dossier Months 22-24; board decision Month 24. Valid data with any metric failing is NO-GO: close the project and return up to $1.2M (less draws and wind-down). Invalid or inconclusive data leads to a board-decided 3-6 month extension (about $300K-$600K, estimate), whose funding source must be decided in advance.
6 Is a written steward commitment signed for post-v1.0 maintenance, as the precondition for the v1.0 release? Signed MOU with a steward showing a funding source for $150K-$250K per year (estimate); at least 2 written letters of interest by Month 24; funding commitments at least 50% of $150K per year at Month 30. Candidate brief at Month 12; letters of interest by Month 24; MOU negotiation Months 27-30; signed MOU at Month 30 (Month 33 is only the latest point at which a delayed release can still be triggered). Do not release v1.0; go to the board for a scaled stewardship model or a funder consortium. If nothing is signed by Month 33, cancel the public release and close with archived materials, unless a funded deferral beyond Month 36 is explicitly decided.

What you need to decide, and by when.

5 open decisions: 4 high and 1 medium severity. The safety-cohort fallback (Month 4 = 2027-02-13) and baseline study form (Month 1 = 2026-11-13) are the most urgent, since they shape the Month 3 (2027-01-13) partner gate and the 4-arm design. The reserve waterfall should be settled by Month 6 (2027-04-13), and the steward fallback and steward funding before Month 27 (2029-01-13). Until then the plan can proceed on canonical values: Phase 1 rule drafting, lexicon, board setup and counsel retention.

# Decision Severity Owner Decide by Blocks
1 Reserve waterfall 🔴 High Project Sponsor and Funding Authority, on Steering Committee recommendation Month 6 (2027-04-13), before the pre-registration and enrolment commitments that set Phase 2 exposure. Phase 1 exit (Month 12 = 2027-10-13) and the Month 24 (2028-10-13) inconclusive-data branch.
2 Safety-cohort fallback 🔴 High Steering Committee with Compliance & Risk Management Committee; Sponsor if budget changes Month 4 (2027-02-13) (liability strategy and written regulator advice), before Phase 2 design is registered. Phase 1 exit gate (Month 12 = 2027-10-13) and pre-registration (Month 11 = 2027-09-13).
3 Steward fallback rule 🔴 High Project Sponsor and Funding Authority Month 27 (2029-01-13), before MOU negotiation (Months 27-30 = 2029-01-13 to 2029-04-13). v1.0 release (Month 30 = 2029-04-13) and Phase 3 closeout.
4 Steward funding from project budget 🔴 High Project Sponsor and Funding Authority Month 12 (2027-10-13), so candidate stewards see terms in the candidate brief. Steward MOU (Month 30 = 2029-04-13) and v1.0 release.
5 Baseline study form 🟡 Medium Steering Committee with Compliance & Risk Management Committee and the psychometrician Month 1 (2026-11-13), before any learner contact. Month 3 (2027-01-13) partner and dropout gate.

1. Reserve waterfall (🔴 High)

Decision: How is the $0.35M reserve ranked and released across pre-gate protection, a Phase 2 extension after inconclusive data, Phase 3 top-up and Phase 2.5?

Why it is open: Canonical rule caps pre-gate draws at $175K and releases the balance only after a Month 24 (2028-10-13) GO. Reviews charge a $300K-$600K extension and Phase 2.5 to the 'entire reserve', which an inconclusive result cannot release.

Option Consequences What changes in the plan
A. Board may release a defined part of the post-gate balance for a validated extension without a GO. Extension of up to about $175K becomes fundable; still below a 3-month extension ($300K) unless Phase 3 underspend adds. Weakens the gate-protection of funds. reserve_draw_rule; gate_funds_at_risk; Reviews 1, 2, 4, 5, 10.
B. Cap any extension at what the $175K pre-gate cap and Phase 3 underspend can cover. Extension limited to a shorter period than 3-6 months; the reserve order is fixed and no Phase 2.5 is funded. phase2_extension_fallback; free_reserve_after_fallbacks.
C. Treat extension as unfunded; require descoping or termination. Keeps the reserve rule intact; inconclusive data leads to descope or wind-down, with up to $1.2M returnable. phase2_go_no_go_rule wording; extension text in reviews.

2. Safety-cohort fallback (🔴 High)

Decision: If safety-critical pilots cannot proceed, does the gate become an ESL-only 2-arm design, or is the technical cohort deferred to a Phase 2.5?

Why it is open: Canonical design is 4 arms and 320 completers. Reviews defer the cohort after 4 or 6 months and date regulator advice at Month 4, 6 or 8 (2027-02-13, 2027-04-13, 2027-06-13).

Option Consequences What changes in the plan
A. ESL-only 2-arm gate (160 completers), technical cohort non-gating. Keeps Month 24 (2028-10-13) gate timing; narrows evidence to ESL; re-register validity conditions; lowers enrolment and participant costs. pilot_design; pilot_min_completers; pilot_enrolment_and_dropout; pitch claims.
B. Defer the technical cohort to a Phase 2.5 after Month 24 (2028-10-13). Needs funding outside the current budget; the gate rests on ESL arms; safety benefit claims remain unvalidated at gate. pilot_design; phase3_budget; adoption_wedge.
C. Hold the 4-arm gate and delay the gate until approval is secured. Pilot window shrinks or the gate slips past Month 24 (2028-10-13); extension cost of $85K-$170K per 4-8 weeks (estimate). pilot_schedule; safety_limits; budget.

3. Steward fallback rule (🔴 High)

Decision: If no steward MOU is signed by Month 30 (2029-04-13), is v1.0 cancelled at Month 33 (2029-07-13), or may release be deferred beyond Month 36 (2029-10-13) with funding?

Why it is open: FM4 cancels at Month 33 (2029-07-13). Reviews 5, 6, 9, 14 and Self-audit 20 allow deferral to Month 36 (2029-10-13) or later, outside the funded program.

Option Consequences What changes in the plan
A. Cancel and archive at Month 33 (2029-07-13) if unsigned. Hard stop; no unfunded tail; the adopter target by Month 36 (2029-10-13) is likely missed. v1_release; Reviews 5, 6, 9, 14; Self-audit 20.
B. Allow a funded deferral beyond Month 36 (2029-10-13). Requires a funder for the team (cost not set); re-date the adopter target. program_structure; adoption_target; total_budget.

4. Steward funding from project budget (🔴 High)

Decision: Does the steward receive any project money (reserve or Phase 3 underspend), or is stewardship funded entirely externally?

Why it is open: Pitch states the steward receives the $0.35M reserve plus pro-rata Phase 3 funding. The plan treats $150K-$250K per year (estimate) as unfunded; the reserve is also claimed elsewhere.

Option Consequences What changes in the plan
A. Steward receives nothing from the project budget. Reserve remains for the gate and extension; steward must find $150K-$250K per year (estimate) externally, raising the Month 30 (2029-04-13) MOU risk. Pitch Collaboration Opportunities.
B. Fixed capped seed from unspent Phase 3 or reserve, ranked after gate protection and extension. Improves MOU odds; only available after a GO; needs a stated cap. reserve_draw_rule; stewardship_funding_gap; pitch.
C. Funding entirely external (consortium or funder). Project funds untouched; adds funder outreach work before Month 24 (2028-10-13). stewardship_funding_gap; outreach plan.

5. Baseline study form (🟡 Medium)

Decision: In what form is the dropout baseline study run: with ethics approval first, as a non-participant evidence review, or after Month 6 (2027-04-13)?

Why it is open: The study (20-30 learners, Months 1-2 = 2026-11-13 to 2026-12-13) precedes ethics approval (Month 6 = 2027-04-13), consent forms and partner signatures (Month 3 = 2027-01-13), and cannot observe 30-day or 12-month dropout.

Option Consequences What changes in the plan
A. Obtain ethics exemption or approval before starting, with consent and partner agreement first. Real data, but the start slips beyond Months 1-2 (2026-11-13 to 2026-12-13); Month 3 (2027-01-13) retargeting is at risk. Compliance actions; Month 3 (2027-01-13) retargeting date.
B. Non-participant evidence review of partner attrition and literature in Months 1-3 (2026-11-13 to 2027-01-13). No ethics issue; weaker evidence; fits Month 3 (2027-01-13) gate. Risk 1; Reviews 3, 8; Premortem A3.
C. Move the study after Month 6 (2027-04-13) and drop the 30-day/12-month claim. Late input to the Month 12 (2027-10-13) enrolment audit; Month 3 (2027-01-13) dropout threshold of 35% cannot be tested. pilot_partner_commitments gate evidence; Month 3 (2027-01-13) deadline.

Choices made on your behalf

Set when the scenario was selected, not by you. Confirm or change them.

Lever Chosen Strongest alternative Why it matters Revisit by
Ordinal Marker Architecture Numeric ordinals with an invariant prefix marker; legacy forms accepted and mechanically convertible. Fully spelled ordinals with a single regular -th ending (Pioneer's Gambit). Sets the ordinal-error metric and converter ambiguity risk (at most 5% ambiguous (proposed threshold)). Month 8 (2027-06-13) (ordinal lock) / Month 10 (2027-08-13) kappa check
Grapheme-to-Phoneme Intervention Depth Standard spellings unchanged; optional software-generated pronunciation overlay, printed key in print. Respell a ranked shortlist of high-friction patterns (Pioneer's Gambit). Drives how much pronunciation consistency can improve against the +15% gate. Month 12 (2027-10-13) rules lock
Adoption Wedge and Sequencing Adult ESL programs and publishers first, as a supplementary module; technical cohort secondary. Free reader-facing site and browser toggle before institutions commit. Determines who must sign by Month 3 (2027-01-13) and the pilot recruitment path. Month 3 (2027-01-13) partner gate
Outcome Metric Battery Design Purpose-built assessments for each of four metrics, with independent psychometrician review. Off-the-shelf validated instruments (Prudent Consolidator) or passive logging. Sets gate credibility and the $150K-$200K (estimate) psychometrics cost. Month 5 (2027-03-13) power analysis
Phase Budget Weighting and Reserve Roughly even phase split ($1.1M / $1.2M / $0.85M) with a $0.35M board-held reserve released after GO. Large staged contingent tranche released against milestones, or a lean Phase 1 weighted to Phase 2. Controls Phase 1 resourcing and funds at risk at the Month 24 (2028-10-13) gate. Month 12 (2027-10-13) Phase 1 exit

Key numbers and dates.

Kind: user constraint = from your prompt; decision = chosen in this plan; proposed threshold = a pass/fail line proposed in this plan, to be confirmed; estimate = not verified.

Fact Value Kind Basis
total_budget $3.5M total across 36 months (USD) user constraint Stated in the brief; Phase 1 $1.1M + Phase 2 $1.2M + Phase 3 $0.85M + reserve $0.35M = $3.5M (recomputed).
program_structure 36 months in 3 gated 12-month phases: Phase 1 Months 0-12 (2026-10-13 to 2027-10-13) (rules + reference corpus), Phase 2 Months 12-24 (2027-10-13 to 2028-10-13) (pilots), Phase 3 Months 24-36 (2028-10-13 to 2029-10-13) (public standard + limited adoption) user constraint Brief fixes three 12-month phases; the later 'extend by 3-6 months' ideas in the risk register are fallbacks, not the baseline.
phase1_budget $1.1M (31.4% of $3.5M) decision Pragmatic Foundation 'roughly even' spread; 1.1/3.5 = 31.4%, keeps Phase 1 rules, 5,000-word lexicon and audio adequately funded.
phase2_budget $1.2M (34.3% of $3.5M) decision Largest tranche because pilots, assessments and cohort administration generate the gate evidence; 1.2/3.5 = 34.3%.
phase3_budget $0.85M (24.3% of $3.5M); effectively $1.2M if the reserve is released after a GO decision 0.85 + 0.35 reserve = $1.2M, equal to Phase 2, which is how the split is 'roughly even'; the lower base is deliberate because Phase 3 funds are the ones returned on a no-go. Percentages 31.4 + 34.3 + 24.3 + 10.0 = 100%.
reserve_amount $0.35M (10% of budget), held by the editorial board decision Chosen over the risk register's $175K-$250K (5-7%) range because the phase split only sums to $3.5M with $0.35M; the 5% floor ($175K) is retained as the pre-gate draw cap.
reserve_draw_rule Before Month 24 (2028-10-13): draws capped at $175K (5% of budget, half of the reserve) and only for pre-approved, evidence-backed gate-protection needs (e.g. psychometric re-validation); remaining balance of at least $175K released only after the Month 24 (2028-10-13) GO decision Documents conflict (release 'only after go/no-go' vs. use for overruns); a capped pre-gate draw closes the 'no contingency in Months 18-24 (2028-04-13 to 2028-10-13)' gap while keeping at least half of the reserve ($175K) returnable (corrected from 'most').
free_reserve_after_fallbacks Free reserve after a 4-week Phase 1 extension ($85K draw) = $265K ($350K - $85K); remaining pre-gate headroom under the $175K cap = $90K; a following 3-month Phase 2 extension ($300K) would leave a $35K shortfall (estimate) estimate Added to avoid counting the same $350K reserve twice: $85K + $300K = $385K exceeds $350K by $35K, so the two fallbacks cannot both be fully funded; a psychometric do-over ($200K-$300K in Risk 3) also exceeds the $175K pre-gate cap and needs a board decision.
gate_funds_at_risk Up to $1.2M unspent/returnable on a no-go at Month 24 (2028-10-13) (Phase 3 $0.85M + reserve $0.35M), less any pre-gate draws and wind-down costs estimate Arithmetic from the phase split; the review's '$1.2M-$1.4M' range is rejected because it counts Phase 2 money already spent.
overrun_exposure $300K overrun scenario = 8.6% of budget (estimate); exceeds the $175K pre-gate draw cap by $125K estimate 300/3,500 = 8.6%; 300 - 175 = 125; the shortfall must come from scope cuts outside the pilot arms or a new board decision to lift the cap (still within the $350K reserve if no other draws have been made).
phase1_exit_gate Month 12 (2027-10-13) Phase 1 exit: rules locked, draft standard comment window closed, 4 metrics pre-registered, 5,000 entries with usable audio, lexicon coverage >=85%, inter-rater kappa >=0.70 floor (target 0.75), partner commitments signed, ethics approval in hand proposed threshold Distinct from the Phase 2 outcome gate: Phase 1 tests readiness and rule/instrument quality, not learner outcomes; kappa floor aligned to 0.70 (the extension trigger and Phase 2 validity condition) with 0.75 as target, so the exit gate does not contradict the fallback rule.
phase2_go_no_go_rule Month 24 (2028-10-13) go/no-go: GO only if all four metrics meet their pre-registered thresholds AND validity conditions hold (>=80 completers per arm, follow-up completion >=70%, kappa >=0.70); valid data with any metric failing = NO-GO; invalid/inconclusive data = board-decided extension proposed threshold Brief requires a go/no-go after Phase 2 on four metrics; the review asked for pre-registered numeric rules, so a conjunctive rule with a separate 'inconclusive' branch is set.
gate_ordinal_error >=25% relative reduction in ordinal error rate vs. standard-English control (proposed threshold, finalized in pre-registration) proposed threshold Review example 25% and pre-assessment 20% are both illustrative; 25% chosen because the ordinal rule is mechanical and fully taught, so a 20% bar risks a false-positive.
gate_comprehension_speed Clear English reading/comprehension time no more than 10% slower than standard-English control (proposed threshold) proposed threshold Pre-assessment example value, adopted as the proposal because recognizability is the key adoption risk; to be confirmed by the psychometrician.
gate_pronunciation_consistency Pronunciation consistency score >=15% above control with statistically significant difference (proposed threshold, calibrate at pre-registration); scoring reliability kappa >=0.75 target, floor 0.70 proposed threshold No documents give an outcome magnitude, so 15% is a placeholder to be calibrated; kappa 0.75/0.70 come from the risk register and assumptions.
gate_retention_30day 30-day retention: >=70% of immediate post-test performance retained at 30 days and not below control (proposed threshold) proposed threshold 70% appears in the pre-assessment as both 'learner continuation' and the recruit-retention goal; the knowledge-retention metric is defined separately from participant dropout (<=30%).
intelligibility_target Average adult comprehension of Clear English text reaches >=90% of standard-English control accuracy within 2 weeks of exposure (90% is a proposed threshold) user constraint The 2-week intelligibility window is the user's constraint; the 90% operationalisation is an added proposal.
pilot_min_completers At least 80 completers per arm (estimate, to be confirmed by power analysis); 320 completers across 4 arms estimate Documents give 50-100 per condition; 80 is the pre-assessment/review figure for ~80% power at alpha 0.05 and is not yet validated; 80 x 4 = 320.
pilot_enrolment_and_dropout Enrol >=115 per arm (80 / 0.70 = 114.3, rounded up) = 460 total across 4 arms; tolerated dropout <=30%; all enrolment complete by Month 13 (2027-11-13) estimate The '15% over-recruitment' (92 per arm) would only retain 80 completers at ~13% dropout (80/92 = 87%), contradicting the 30% dropout tolerance, so enrolment is sized from 30% dropout instead; 115 x 4 = 460, and 460 x 0.70 = 322 >= 320 completers.
pilot_design 2 cohorts (adult ESL; native-speaker technical/safety-glossary) x 2 conditions (Clear English vs standard-English control) = 4 arms decision Brief names both cohorts; the control group is required by the purpose-built, control-calibrated metric design.
pilot_partner_commitments Signed commitments by Month 3 (2027-01-13): >=3 adult ESL programs (target 3-4) and >=2 technical/safety-training organizations (target 2-3), plus non-binding publisher letters of interest proposed threshold Risk 2 and pre-assessment give 3-4 / 2-3; the lower bounds are set as the go threshold, escalation to the board if missed. Capacity check: each cohort needs 2 arms x 115 = 230 enrolled, i.e. ~77 per partner at 3 ESL programs and ~115 per partner at 2 technical organizations (~58 and ~77 at the upper bounds), above the pre-assessment's 50-per-partner minimum, so written guarantees must be sized to these figures.
pilot_schedule Enrolment complete Month 13 (2027-11-13); midpoint check Month 18 (2028-04-13); extra validation (if needed) by Month 21 (2028-07-13); data lock incl. 30-day follow-up by Month 22 (2028-08-13); analysis and gate dossier Months 22-24 (2028-08-13 to 2028-10-13) decision Pre-assessment ran sessions through Month 24 (2028-10-13), which leaves no time to analyse before the gate; data lock at Month 22 (2028-08-13) makes the Month 24 (2028-10-13) decision feasible.
ordinal_rule Option A: numeric ordinals with one invariant prefix marker on every digit string; fixed spoken reading published; legacy 1st/2nd/3rd forms accepted and mechanically convertible; marker symbol and spoken form fixed by Month 10 (2027-08-13) decision Scenario 'Pragmatic Foundation' (fit 9/10); spelled forms like 'oneth' and the suffix-only variant rejected for native-reader rejection risk and legacy-suffix clashes.
g2p_approach Standard spellings unchanged; pronunciation delivered as an optional software-generated overlay (ruby-style in digital, printed key in print); no respelling in v1.0 decision Overlay chosen over respelling (Pioneer's Gambit) to protect recognizability and publisher compatibility; adoption over linguistic purity.
morphology_threshold Retain all irregular forms within the top 1,000 lexicon words by frequency; regularize only lower-frequency irregulars with low recognition penalty; cap at 25% of irregular verbs/plurals changed (all proposed); go/went is retained proposed threshold Frequency-band option chosen for recognizability; the cutoff and cap are arbitrary until pilot error data exist; dual-form pilots rejected because retiring a form later causes churn.
homograph_policy Disambiguation marker mandatory only in safety-critical/procedural documents for a published list of <=50 high-impact pairs (proposed cap); optional elsewhere; no authoring plugin funded in v1.0 decision Option 1 keeps the list manageable and avoids tooling dependency the $3.5M budget cannot maintain; examples lead/lead and read/read are from the brief.
lexicon 5,000-word core lexicon: 4,500 frequency-led general words + 500-word (10%) reserved technical/safety block; coverage of pilot running text >=85% (audit Month 8 = 2027-06-13; expansion fix by Month 10 = 2027-08-13) proposed threshold 5,000 words is the user constraint; 85% from assumptions (risk register range 85-90%); 4,500 + 500 = 5,000 and 500/5,000 = 10%; the block serves the technical cohort without letting the list change mid-pilot.
audio_production Single-accent recording of all 5,000 entries (about 10,000 files at 2 takes), Months 6-11 (2027-04-13 to 2027-09-13), budget $80K-$120K (estimate); if cost exceeds $20 per entry ($100K total), switch to synthetic baseline plus human verification of the highest-friction subset; recording only 3,000-4,000 words violates the 5,000-word user constraint and is not an in-scope fallback estimate Pre-assessment $80K-$120K and $20/entry trigger; $80K-$120K / 5,000 = $16-$24 per entry, so the upper $100K-$120K part of the range lies above the $20 trigger and would activate the synthetic-baseline switch; 5,000 x 2 takes = 10,000 files (upper end of 7,500-10,000). The review's 3,000-4,000-word fallback needs an explicit user/board scope-change decision (merged here from the former separate fallback fact).
accent_anchor One reference accent chosen and justified by Month 3 (2027-01-13); mapping of other accents documented by Month 12 (2027-10-13); additional accents deferred to post-v1.0 (optional 200-300 word proof-of-concept sample, $10K-$15K, estimate) decision Single anchor keeps the pronunciation score auditable; full multi-accent coverage would add $50K-$100K (estimate) and is declined.
adoption_wedge ESL-first: Clear English offered as a supplementary module beside standard English; technical glossary cohort is secondary decision Pragmatic Foundation wedge; satisfies 'optimize for adoption' and the no-replacement constraint.
safety_limits Safety-critical pilots limited to glossary and labeling exercises, no live operational procedures before Month 24 (2028-10-13); legal counsel retained by Month 2 (2026-12-13); liability strategy by Month 4 (2027-02-13); legal/liability spend capped at $150K-$200K (estimate); all materials disclaimed and human-reviewed decision Low-likelihood/high-severity risk is bounded by deferring live use; if liability insurance is unavailable or above $50K per year (estimate), safety-critical use stays glossary-only after the gate too.
governance_board Practitioner-leaning editorial board of 7-9 members with linguist review-and-veto limited to ambiguity/contradiction findings; charter with voting, tiebreak arbiter, conflict-of-interest rules by Month 1 (2026-11-13); first meeting Month 2 (2026-12-13); arbiter agreed by Month 5 (2027-03-13); arbiter cost $10K-$20K (estimate) decision Option 2 aligns with adoption priority; Month 1 (2026-11-13) charter and external arbiter close the deadlock gap raised in the review.
licensing Text and dictionary open-licensed; 'Clear English' name reserved as certification mark against a free, light public conformance checklist; model decided by Month 6 (2027-04-13), published by Month 12 (2027-10-13); divergence beyond 10% of rules (proposed) requires a distinct name decision Month 6 (2027-04-13) chosen over Month 12 (2027-10-13) (Risk 1) because publishers are approached from Month 3 (2027-01-13); 10% taken from the low end of the 10-15% range as the stronger anti-fragmentation setting.
controlled_language Clear English is an independent standard with a one-way mapping table from ASD-STE100 and plain-language rules; no MoU or standing liaison funded; compatibility labelled 'partial' unless verified decision Avoids dependence on an external maintainer's schedule (2-4 month delay risk) and an unverifiable '100% compatible' claim.
change_control v1.0 frozen for 12 months after publication (proposed): errata only, one consolidated v2.0 review; no rule changes during pilots decision Stability for publishers and valid pilot data outweighs responsiveness; rapid revisions would invalidate calibrated items and printed curricula. With v1.0 at Month 30 (2029-04-13), the 12-month freeze runs to Month 42 (2030-04-13), beyond the funded 36-month horizon, so errata handling in Months 36-42 (2029-10-13 to 2030-04-13) depends on the unfunded stewardship arrangement.
staffing Core team 8-10 FTE peak (proposed): project lead, 2-3 linguists, psychometrician (hired by Month 2 = 2026-12-13), curriculum designers, 1.0 FTE cohort manager (by Month 6 = 2027-04-13), educator liaison 0.5-1.0 FTE, developer proposed threshold Cohort manager at Month 6 (2027-04-13) (not Month 12 = 2027-10-13 as in Risk 2) because partner enrolment must finish by Month 13 (2027-11-13). Recomputed: Phase 1 non-staff lines (audio $80K-$120K + psychometrics $150K-$200K + legal cap $150K-$200K + ethics $10K-$20K + arbiter $10K-$20K = $400K-$560K) leave $1.1M - $0.40M-$0.56M = roughly $0.5M-$0.7M for staff, i.e. about $68K-$88K per FTE-year at 8 FTE (rough estimate, replaces the earlier $0.7M-$0.8M); staffing must therefore ramp rather than start at peak.
psychometrics_cost $150K-$200K (estimate) for instrument design, validity study (N=20-30, Months 10-11 = 2027-08-13 to 2027-09-13) and inter-rater work; pre-analysis plan draft by Month 5 (2027-03-13), pre-registered by Month 11 (2027-09-13) estimate Risk 3 range; independent psychometric review is required by the chosen metric design.
participant_costs Phase 2 participant-related cost about $208K-$351K (estimate): incentives 460 x $50-$150 = $23K-$69K; partner payments 460 x 4 sessions x $30-$50 = $55K-$92K (subtotal $78K-$161K); plus cohort manager $60K-$80K/yr, educator liaison $50K-$70K, teacher stipends $20K-$40K (subtotal $130K-$190K) estimate Recomputed: 23 + 55 + 60 + 50 + 20 = $208K and 69 + 92 + 80 + 70 + 40 = $351K (earlier $78K-$161K omitted the three 'plus' lines); about 17%-29% of the $1.2M Phase 2 budget; per-unit figures from the pre-assessment multiplied by the 460-learner enrolment; all program-financed, while partners supply classrooms and instructors.
location_currency Provisional hub: mid-cost US metro (Austin-type) with virtual board meetings; confirmed at Month 3 (2027-01-13) against partner commitments; all budgeting in USD decision Documents leave location open; a US hub fits the budget and avoids GBP exposure (2-3% contingency and rate-locking apply only if Cambridge/Oxford is chosen).
rules_freeze_preregistration Board rule disputes resolved by Month 10 (2027-08-13); draft standard published Month 11 (2027-09-13) for 30-day comment; metrics and thresholds pre-registered Month 11 (2027-09-13); rules locked at Month 12 (2027-10-13) (Phase 2 start); dry run of tools Month 10 (2027-08-13) decision Source documents say both 'finalize by Month 11 (2027-09-13)' and 'comment window after Month 11 (2027-09-13)'; the comment window must close before final lock, so lock is Month 12 (2027-10-13).
phase1_extension_fallback If kappa <0.70 at the Month 10 (2027-08-13) check after 2-4 weeks of retraining: extend Phase 1 by 4 weeks, about $85K (1.1M/12 x 0.923 months = 1.1M x 4/52, estimate) estimate Recomputed $91.7K per month x 0.923 = $84.6K; fits within the $175K pre-gate draw cap (uses about 24% of the $350K reserve) and can be absorbed by the Month 11 (2027-09-13) buffer (2-4 weeks); otherwise Phase 2 start and gate shift by up to 4 weeks.
phase2_extension_fallback Inconclusive gate data: Phase 2 extension of 3-6 months; 3 months costs up to about $300K ($1.2M/12 x 3, estimate), 6 months up to $600K; Phase 3 would end at Month 39 (2030-01-13) or later estimate 3 months fits the $350K reserve only by exhausting 86% of it (300/350) and only if no earlier draws were made (after an $85K Phase 1 extension the free reserve is $265K); it exceeds the $175K draw cap; 6 months ($600K) exceeds the whole reserve; both breach the 36-month horizon, so a new funding and schedule decision is needed.
v1_release Clear English Standard v1.0 public release by Month 30 (2029-04-13) (proposed), conditional on a written steward commitment; limited-scope adoption Months 30-36 (2029-04-13 to 2029-10-13); licensing, style guide and dictionary released with it proposed threshold Documents give no release month; Month 30 (2029-04-13) leaves 6 months for adoption and handover and precedes the steward MoU (Month 33 = 2029-07-13) and 5-year roadmap (Month 36 = 2029-10-13).
stewardship_funding_gap Revenue $0 (open licenses, free checklist; non-profit); no debt; post-Month-36 stewardship $150K-$250K per year (estimate), unfunded: gap of $150K-$250K per year, $1.5M-$2.5M over 10 years estimate No price x volume revenue exists, so the gap equals the full stewardship cost; 10 x $150K = $1.5M and 10 x $250K = $2.5M (recomputed); certification/dispute overhead ($50K-$100K/yr in Risk 9) is assumed included, not additional. Funding is an open decision: steward letter of interest Month 27 (2029-01-13), commitment Month 30 (2029-04-13), MoU Month 33 (2029-07-13), 5-year roadmap Month 36 (2029-10-13).
adoption_target >=3 licensed third-party adopters (at least 1 ESL publisher) by Month 36 (2029-10-13) (proposed); no mandates, no K-12 replacement, no universal-adoption claims; 10,000-50,000 learner reach is an unvalidated estimate, 100,000+ is not a target proposed threshold Brief excludes mandates and universal claims; the adopter count is a proposed measurable Phase 3 outcome, and the reach figures come only from risk-register estimates.

Focus and Context

Clear English is a parallel English variant for adult ESL learners and technical writers, tested through rigorous pilots with pre-registered metrics and gated at Month 24 (2028-10-13) on defensible evidence before any public release. If pilots meet thresholds (ordinal error ≥25% reduction, comprehension ≤10% slower, pronunciation consistency ≥15% above control with a statistically significant difference, 30-day retention ≥70% of post-test performance and not below control), the standard advances; GO requires all four metrics to pass and validity to hold (≥80 completers per arm, follow-up ≥70%, kappa ≥0.70); valid data with any metric failing is NO-GO, with up to $1.2M returnable (less draws and wind-down) and the project closing; invalid or inconclusive data leads to a board-decided extension. The core tension: lightweight rules and supplementary positioning maximize adoption, but weak evidence risks credibility loss and abandonment post-launch.

Purpose and Goals

Design, pilot, and conditionally publish Clear English Standard v1.0 within 36 months and $3.5M (fixed envelope), using an ESL-first adoption wedge and a defensible Month 24 (2028-10-13) go/no-go gate. Success means ≥3 licensed third-party adopters (at least 1 ESL publisher) and a written stewardship commitment for post-v1.0 maintenance ($150K–$250K/year, estimate), confirmed before v1.0 release at Month 30 (2029-04-13).

Key Deliverables and Outcomes

Phase 1 (Month 12 = 2027-10-13 exit): rules locked; 5,000-word lexicon with single-accent audio; pre-registered metrics on Open Science Framework; ethics approval; ≥3 ESL and ≥2 technical-training partner commitments. Phase 2 (Month 24 = 2028-10-13 gate): ≥80 completers per arm on four pre-registered metrics; defensible go/no-go dossier. Phase 3 (Month 36 = 2029-10-13): v1.0 published; ≥3 adopters licensed; stewardship MOU signed and transitioned; 5-year roadmap published.

Timeline and Budget

36 months: Phase 1 Months 0–12 (2026-10-13 to 2027-10-13) ($1.1M rules + corpus), Phase 2 Months 12–24 (2027-10-13 to 2028-10-13) ($1.2M pilots), Phase 3 Months 24–36 (2028-10-13 to 2029-10-13) ($0.85M release + adoption), $0.35M reserve (capped pre-gate draws $175K, 5% of budget). Critical path: Month 2 (2026-12-13) psychometrician hire; Month 3 (2027-01-13) pilot partner commitments; Month 11 (2027-09-13) pre-analysis plan registration; Month 24 (2028-10-13) gate; Month 30 (2029-04-13) v1.0 release conditional on stewardship MOU.

Risks and Mitigations

Risk 1 (High likelihood, high impact): Pilot recruitment/retention shortfall (actual dropout 35–45% vs. plan 30%) reduces completers to 63–75 per arm (6–21% below 80-per-arm minimum) from the 115-per-arm (460 total) enrolment, risking statistical power. Mitigation: conduct baseline recruitment study Months 1–2 (2026-11-13 to 2026-12-13); hire cohort manager by Month 6 (2027-04-13) (acceleration to Month 4 = 2027-02-13 is a proposal, with cost to be assessed); activate contingency incentives ($20K–$30K, estimate) if enrollment lags. Risk 2 (Medium likelihood, high impact): Pre-registered thresholds not locked or disputed at Month 24 (2028-10-13) gate. Mitigation: hire psychometrician Month 2 (2026-12-13); deliver power analysis Month 5 (2027-03-13); pre-register Month 11 (2027-09-13); publish on OSF with board sign-off. Risk 3 (High likelihood, medium impact): Stewardship unfunded post-Month 36 (2029-10-13) causes standard atrophy within 12–24 months (Month 48–60 = 2030-10-13 to 2031-10-13). Mitigation: begin steward search Month 12 (2027-10-13); secure MOU by Month 30 (2029-04-13) before v1.0 release.

Audience Tailoring

Audience is project leadership, editorial board, and funders evaluating a 36-month, $3.5M language-standardization initiative. Tone is pragmatic and evidence-focused, emphasizing adoption over linguistic purity and gating rigor over timeline compression. Details are operationalized (Month N deadlines, signed commitments, pre-registered metrics) to support go/no-go decisions at key gates (Month 12 = 2027-10-13 rules lock, Month 24 = 2028-10-13 pilot gate, Month 36 = 2029-10-13 stewardship handoff).

Action Orientation

Immediate actions (by Month 2 = 2026-12-13): (1) Hire independent psychometrician with signed contract specifying power analysis and pre-analysis plan deliverables. (2) Retain legal counsel (product liability + data protection). (3) Engage Institutional Review Board for ethics approval. By Month 1 (2026-11-13): (4) Publish Editorial Board Charter with voting rules and tiebreak arbiter provisions. By Month 3 (2027-01-13): (5) Secure signed pilot partner commitments (≥3 ESL, ≥2 technical orgs). By Month 5 (2027-03-13): (6) Agree the tiebreak arbiter. By Month 6 (2027-04-13): (7) Hire Phase 2 Cohort Manager (1.0 FTE) with retention KPIs. All actions have 2-week slip escalation triggers to the board.

Overall Takeaway

Clear English Standard can succeed if three critical conditions are met: (1) pre-registered, empirically justified gate thresholds locked by Month 11 (2027-09-13) and defensible through independent review; (2) pilot sample size ≥80 per arm with dropout ≤30% achieved through early baseline validation and dedicated cohort management; (3) stewardship commitment secured by Month 30 (2029-04-13) as a precondition for v1.0 release. Without these, the project risks a scientifically disputable gate, underpowered pilots (invalid data, which leads to a board-decided extension of 3–6 months rather than a NO-GO), and post-launch standard atrophy—outcomes that put up to $1.2M of Phase 3 and reserve funding at risk and leave $1.5M–$2.5M of stewardship value unfunded. The evidence-gated, adoption-first positioning is the project's core strength; protecting that credibility requires rigor at every gate and early transparency on stewardship risk.

Feedback

Five areas for strengthening the plan: (1) Commission power analysis by Month 5 (2027-03-13) specifying effect-size benchmarks and confirming 80 per arm is adequate; publish sensitivity analyses in pre-analysis plan (Month 11 = 2027-09-13) to foreclose post-hoc disputes. (2) Conduct baseline recruitment study (Months 1–2 = 2026-11-13 to 2026-12-13) with N=20–30 learners to validate dropout assumptions and reallocate Phase 2 participant budget ($78K–$161K) if baseline confirms >30% attrition. (3) Establish monthly earned-value budget tracking (by Month 1 = 2026-11-13) with >10% variance thresholds to catch cost overruns before consuming the $175K pre-gate draw cap ($35K–$90K headroom estimate). (4) Begin steward identification (Month 12 = 2027-10-13) with formal capability audits and letters of interest by Month 24 (2028-10-13); make stewardship MOU a v1.0 release precondition to avoid post-launch orphaning. (5) Publish KPI dashboard (enrollment, dropout, budget, pre-analysis plan registration) updated monthly for board transparency; tie release decisions to explicit, pre-registered metrics to defend against stakeholder claims of goalpost-moving or political bias.

Unoptimized waterfall. Parallel work not modelled here.

Part 2: Supporting analysis

Persuasive elevator pitch.

Clear English Standard: A Parallel English Variant for Adult ESL Learners and Technical Writers

Project Overview

Imagine a pathway for adult learners to finally read English with confidence—without replacing the English they know.

Clear English Standard is a parallel English variant designed for adult ESL learners and technical writers who lose critical information to spelling irregularities, unpredictable ordinals, and ambiguous words. Over 36 months and $3.5M, this project will deliver a public standard with regularized ordinals, pronunciation guidance, and homograph disambiguation—validated through rigorous pilots at Month 24 (2028-10-13), optionally adopted by ESL publishers and safety-critical sectors, and stewarded for long-term stability.

This is not a replacement. Clear English sits alongside standard English as a supplementary module and optional overlay. Learners and organizations choose it. The standard is built on defensible evidence: four pre-registered gate metrics (ordinal error reduction ≥25%, comprehension speed within 10% of control, pronunciation consistency ≥15% above control with a statistically significant difference, 30-day retention ≥70% of post-test and not below control), independently reviewed assessments, and a 5,000-word reference lexicon validated in real classrooms and technical settings.

Clear English matters because inconsistency costs learners time and errors cost lives. A native speaker absorbs "read (present)" vs. "read (past)" through years of exposure; an ESL learner sees contradiction. A technical glossary resolves that gap—saving seconds on every procedure and potentially preventing miscommunication in safety-critical work.

This project is evidence-gated, not ideologically driven. GO requires all four pre-registered metrics to meet their thresholds and validity to hold (≥80 completers per arm, follow-up ≥70%, kappa ≥0.70). Valid data with any metric failing is a NO-GO: the project stops before public release and up to $1.2M is returnable, less draws and wind-down costs. Invalid or inconclusive data leads to a board-decided extension. If the gate is passed, Clear English becomes a certified, openly licensed resource that any publisher or standards body can adopt on transparent terms, without mandates or takeover of K-12 education.

Target Audience

Risks and Mitigation Strategies

Educator and publisher pushback

Risk: Teachers resist a "non-standard" variant or publishers see it as a competitor.

Mitigation: Position as supplementary, not replacement; co-design protocols with teachers from Month 1 (2026-11-13); engage TESOL/IATEFL early; fund an educator liaison.

Pilot recruitment shortfall

Risk: Enrollments fall below 80 completers per arm, invalidating gate metrics.

Mitigation: Sign commitments by Month 3 (2027-01-13); over-recruit to ≥115 per arm; use incentives ($50–$150 stipends) and a dedicated cohort manager by Month 6 (2027-04-13).

Assessment validity

Risk: Pronunciation raters disagree (kappa <0.70), making the go/no-go gate disputable.

Mitigation: Pre-register thresholds by Month 11 (2027-09-13); run a validity study by Month 10 (2027-08-13); retrain raters; extend Phase 1 by 4 weeks if needed.

Safety-critical liability

Risk: Misreading in operational procedures causing harm.

Mitigation: Limit pilots to glossary and labeling only; retain legal counsel by Month 2 (2026-12-13); disclaim all materials; human-review every entry.

Metrics for Success

Gate metrics (Month 24 = 2028-10-13)

Operational metrics (Phase 1 exit, Month 12 = 2027-10-13)

Adoption metrics (Month 36 = 2029-10-13)

Fidelity and risk metrics

Stakeholder Benefits

ESL programs and learners

A defensible, certified supplementary curriculum module with validated gains in ordinal recognition, pronunciation consistency and 30-day retention; optional overlay that does not disrupt standard English teaching.

Technical and safety-training organizations

A 500-word safety-critical glossary with mandatory homograph markers in procedures, reducing ambiguity-driven errors without the cost of full controlled-language training.

ESL publishers

License-to-use the reference lexicon, style guide and assessment items on permissive terms; gain competitive advantage by offering Clear English modules certified against a public checklist.

Standards bodies (TESOL, IATEFL)

A precedent for evidence-gated language innovation; no institutional turf conflict (independent non-profit steward).

Linguistics and language-policy researchers

A real-world test case of constructed-variant adoption, governance and fragmentation control.

Ethical Considerations

Transparency and evidence

All pilot data, decision logs and assessment instruments made public (with participant consent); pre-registered metrics and thresholds locked before pilots start to prevent p-hacking and selective reporting.

Inclusivity and accent bias

Reference accent chosen by Month 3 (2027-01-13) with documented mapping of other major English varieties; pronunciation consistency score scored on shared phonemic contrasts to avoid privileging one region; additional accents proposed as optional post-v1.0 (not funded in this phase).

Informed consent and data protection

Ethics approval by Month 6 (2027-04-13); encrypted audio storage with GDPR compliance; participants compensated fairly ($50–$150 stipends); right to withdraw.

Liability and safety

Safety-critical pilots limited to glossary and labeling, no live procedures; legal counsel retained; all materials disclaimed; human review of every homograph marker.

Equity

Free, open-licensed standard with no paywall; certification mark is non-profit and awards based on a published conformance checklist, not gatekeeping; no mandates or K-12 replacement claims.

Collaboration Opportunities

ESL program partnerships

Co-develop pilot curriculum, recruit and support learner cohorts (Months 12–24 = 2027-10-13 to 2028-10-13); receive published curriculum materials and conformance training.

Technical-writing and safety-training organizations

Co-design the 500-word safety-critical glossary; pilot homograph-marking protocols; receive validated glossary with licensing rights.

ESL publishers

License reference lexicon, dictionary and style guide; adopt Clear English as a supplementary module; use public conformance checklist for certification.

Linguistics and applied-language research

Commission or collaborate on pronunciation-rater calibration, morphology-error analysis and adoption-barrier research; access anonymized pilot data for secondary analysis (after Month 24 = 2028-10-13 gate).

Standards bodies (ASD-STE100, ICAO, plain-language networks)

Validate one-way mapping table from existing standards; co-author compatibility guidance; refer members to Clear English resources (no formal liaison funded).

Post-v1.0 steward organization

Assume governance, change-control and archive roles; receive $0.35M reserve release post-gate plus pro-rata Phase 3 funding if a written commitment is signed by Month 30 (2029-04-13); Month 33 (2029-07-13) is only the latest point at which a delayed release can still be triggered.

Long-term Vision

Institutional sustainability

Clear English Standard is transferred to a committed, non-profit steward organization by Month 36 (2029-10-13) with a published 10-year governance roadmap, change-control calendar and annual budget ($150K–$250K per year, estimate). The steward enforces the certification mark, approves third-party adopters against a public checklist and coordinates maintenance without centralized control.

Adoption pathway

By Month 36 (2029-10-13), ≥3 third-party adopters (at least 1 ESL publisher) integrate Clear English into courseware and glossaries, reaching an estimated 10,000–50,000 learners within 5 years; safety-critical sectors adopt the 500-word glossary in procedure manuals and training, reducing ambiguity-driven errors.

Evolution and resilience

v1.0 is frozen for 12 months post-release; v2.0 consolidates pilot feedback and post-launch usage data by Month 42 (2030-04-13). Fragmentation is controlled by the certification mark and the requirement that variants beyond 10% of rules adopt a distinct name.

Knowledge and precedent

Clear English becomes a documented case study in evidence-gated language planning, governance and constructed-variant adoption, contributing to applied linguistics research and informing future language-standardization initiatives.

Call to Action

ESL program leaders and technical-training organizations

Express interest in pilot partnership by Month 3 (2027-01-13). Sign a Memorandum of Understanding committing to ≥115 learner enrollments and onsite assessment sessions; we provide curriculum, incentives ($50–$150 per participant) and expert facilitation.

ESL publishers and standards bodies

Review the draft standard at Month 11 (2027-09-13) during the 30-day public comment window; submit conformance letters of interest by Month 12 (2027-10-13).

Potential steward organizations

Contact the project lead to discuss post-v1.0 governance roles and funding partnerships by Month 24 (2028-10-13).

Goal Statement: Design, pilot and publish Clear English Standard v1.0, a parallel (not replacement) English variant with regularized ordinals, spelling-to-sound guidance, capped morphology changes and homograph disambiguation, within 36 months and $3.5M (user constraint), led by an ESL-first adoption wedge.

SMART Criteria

Dependencies

Resources Required

Related Goals

Tags

Risk Assessment and Mitigation Strategies

Key Risks

Diverse Risks

Mitigation Plans

Stakeholder Analysis

Primary Stakeholders

Secondary Stakeholders

Engagement Strategies

Regulatory and Compliance Requirements

Permits and Licenses

Compliance Standards

Regulatory Bodies

Compliance Actions

Primary Decisions

The vital few decisions that have the most impact.

The five Critical levers (Ordinal Marker Architecture, Grapheme-to-Phoneme Depth, Adoption Wedge, Outcome Metric Battery, Phase Budget) cover the main tensions: rule ambition versus recognizability and adoption, evidence rigor versus a fixed budget, and breadth versus depth of market entry. High levers refine content and governance. No distinct lever addresses risk and liability management for safety-critical pilots, or educator-outreach and training capacity.

Decision 1: Ordinal Marker Architecture

Lever ID: 1a9e4740-06a2-43cd-9ac0-fb5ab53fb48e

The Core Decision: Sets the single rule that replaces 1st/2nd/3rd, 11th–13th and 21st/31st patterns, and thereby the most visible, testable feature of the standard. Scope covers written form, a fixed spoken reading and machine conversion of legacy forms. Success metrics: ordinal error rate in pilots, native-reader acceptance, reading speed, and ease of automatic conversion in dates, lists and procedures.

Why It Matters: Choosing between a numeric form with one invariant marker (A) and fully spelled ordinals with regular endings (B) decides how many learners can use the rule on day one. Numeric forms are shorter and match how ordinals already appear in dates, lists and procedures, but they leave the spoken form unresolved. Spelled forms fix speech and writing together but add new unfamiliar words such as 'oneth' that native readers may reject.

Strategic Choices:

  1. Adopt numeric ordinals with one invariant suffix on every digit string, so 1, 2, 3, 11, 21 all take the same marker, and publish a fixed spoken reading for that suffix.
  2. Adopt numeric ordinals with an invariant prefix marker placed before the digits, avoiding clashes with the legacy 1st/2nd/3rd suffixes and letting software convert both forms mechanically.
  3. Adopt fully spelled ordinals with a single regular -th ending, retain digits only in tables and codes, and justify the choice through pilot reading-speed comparisons.

Trade-Off / Risk: Option A is cheaper to teach and machine-convert, but it leaves pronunciation open; option B resolves speech yet risks native-reader rejection of forms like 'oneth', so the choice should be tested rather than argued.

Strategic Connections:

Synergy: Feeds Outcome Metric Battery Design, since ordinal error rate is a go/no-go metric, and strengthens Adoption Wedge and Sequencing by giving safety-critical procedures and numbered steps an immediately usable, low-cost rule.

Conflict: Pulls against Grapheme-to-Phoneme Intervention Depth: a spelled-out ordinal form implies respelling, while a numeric marker leaves spoken form to the pronunciation layer. Also strains Reference Accent Anchor when fixing the spoken reading.

Justification: Critical, Sets the most visible, testable rule of the standard and feeds the ordinal error rate gate metric. Connects to Outcome Metric Battery, Adoption Wedge, G2P Depth and Accent Anchor, and controls the numeric-versus-spelled trade-off between native-reader acceptance and spoken-form resolution.

Decision 2: Grapheme-to-Phoneme Intervention Depth

Lever ID: f2c8fd84-4f48-425c-87f3-17d8bb34c18b

The Core Decision: Determines whether Clear English changes spelling itself or only layers guidance on top of it, which sets conversion cost, tooling needs and educator acceptance. Scope is the 5,000-word lexicon and its respelling key or overlay. Success metrics: pronunciation consistency score, recognition distance of changed forms, compatibility with search and dictionary tools, and publisher willingness to adopt.

Why It Matters: This lever sets how far the standard departs from conventional spelling. Leaving spellings intact and adding a pronunciation layer protects recognizability and publisher buy-in, but learners still face irregular spelling. Respelling words directly fixes the sound mapping but breaks compatibility with existing text, search tools and dictionaries, and raises the risk of fragmentation.

Strategic Choices:

  1. Keep standard spellings unchanged and add a consistent pronunciation-guidance layer to the 5,000-word lexicon, using one minimal respelling key in dictionaries and teaching materials.
  2. Respell only a ranked shortlist of the highest-friction spelling patterns in the core lexicon, keeping every changed form within easy recognition distance of its standard spelling.
  3. Render pronunciation as an optional software-generated overlay, such as ruby-style annotations in digital materials, so printed text stays standard while learners see the regularized mapping on demand.

Trade-Off / Risk: A guidance layer is the safest route to adoption, but it does not truly fix spelling-to-sound inconsistency; deeper respelling delivers that fix while multiplying conversion costs and the risk that educators reject the variant.

Strategic Connections:

Synergy: Works with Reference Accent Anchor, which supplies the sound targets the mapping encodes, and with Core Lexicon Selection Basis, which defines which words get guidance first. A light-touch layer also eases Licensing and Name Stewardship.

Conflict: Deeper respelling conflicts with Change-Control and Release Cadence, because each respelling change forces reprints and invalidates materials, and with Adoption Wedge and Sequencing, where publishers and educators resist incompatible text.

Justification: Critical, Controls the core trade-off between fixing spelling-to-sound and preserving compatibility and publisher buy-in. Hub linking Accent Anchor, Core Lexicon, Change-Control, Adoption Wedge, Licensing and Homograph markers; deeper respelling directly raises fragmentation and rejection risk against the adoption priority.

Decision 3: Adoption Wedge and Sequencing

Lever ID: 3a239b73-ec97-45dc-9dbd-d3e4250b89a3

The Core Decision: Chooses which user group meets Clear English first and therefore which evidence, partners and liability exposure the program builds. The choice shapes pilot recruitment, the form of materials and the credibility story for the Phase 2 go/no-go. Success metrics: pilot cohort enrollment, partner commitments, time to first real-world use and absence of stalled approvals.

Why It Matters: The first market chosen shapes the evidence, the partners and the risk exposure of the program. Safety-critical documentation offers clear measurable benefits but brings liability concerns and slow organizational approval. ESL publishers move faster and supply learners for pilots, but they may demand full curricula and treat the variant as a competitor to standard English teaching.

Strategic Choices:

  1. Lead with adult ESL programs and publishers, offering Clear English as a supplementary module that sits alongside standard English curricula rather than replacing them.
  2. Lead with a technical glossary for safety-critical documentation, co-developed with one or two industry or standards-body partners and tested in real working procedures.
  3. Lead with a free, standalone reference site and browser extension that lets any reader toggle between standard and Clear English forms, building a user base before institutional partnerships.

Trade-Off / Risk: Each wedge builds a different evidence base, so choosing one early narrows the others; the risk is that a safety-critical pilot gets stalled by liability review while the ESL track starves for rules.

Strategic Connections:

Synergy: Sets priorities for Outcome Metric Battery Design and Core Lexicon Selection Basis, because the chosen wedge determines which metrics and which glossary vocabulary are collected first, and supports Licensing and Name Stewardship through early partner agreements.

Conflict: Competes with Phase Budget Weighting and Reserve: pursuing one wedge deeply starves the others, and a safety-critical lead raises liability and slow approvals that clash with Change-Control and Release Cadence.

Justification: Critical, The central hub: determines which partners, evidence, liability exposure and glossary vocabulary the program builds first. Synergies run to metrics, lexicon, licensing and homograph policy; conflicts with budget and change-control. Directly serves the plan's 'optimize for adoption' directive.

Decision 4: Outcome Metric Battery Design

Lever ID: 8066426e-2101-40b0-a31b-2c802373d134

The Core Decision: Defines the instruments, scoring rules and sampling that turn the four gate metrics (comprehension speed, ordinal error rate, pronunciation consistency, 30-day retention) into decision-grade evidence. Scope includes control-group design, inter-rater reliability for pronunciation scoring, and pre-registered pass/fail thresholds fixed before Month 12 (2027-10-13). Success means the Phase 2 go/no-go cannot be disputed as measurement artefact by educators or standards bodies.

Why It Matters: This lever decides how comprehension speed, ordinal error rate, pronunciation consistency and 30-day retention are actually measured in the pilots. Instrument choices determine whether the Phase 2 go/no-go decision rests on defensible evidence or on noisy proxies. Richer instruments need more psychometric expertise and more supervised sessions, which draws on pilot budget and learner time.

Strategic Choices:

  1. Adopt validated off-the-shelf reading, listening and recall instruments and adapt them minimally, accepting less precision on Clear English-specific features in exchange for external credibility.
  2. Develop a purpose-built assessment set for each of the four metrics, calibrated against a standard-English control group, and have an independent psychometrician review item validity before the pilots begin.
  3. Embed measurement in normal course work through passive digital logging of response times and error patterns, supplemented by a small supervised audio-capture sample for pronunciation scoring.

Trade-Off / Risk: Purpose-built instruments fit the four gate metrics but are untested and costly to validate; borrowed instruments are credible yet may miss exactly the ordinal and pronunciation effects the standard is meant to change.

Strategic Connections:

Synergy: Strengthens Phase Budget Weighting and Reserve, because credible metrics justify staged release of funds. Also amplifies Adoption Wedge and Sequencing by giving partner organizations defensible evidence that Clear English works in their setting.

Conflict: Competes with Phase Budget Weighting and Reserve, since purpose-built instruments and psychometric review consume pilot money. Also clashes with Grapheme-to-Phoneme Intervention Depth and Reference Accent Anchor if rules shift mid-pilot, invalidating calibrated items.

Justification: Critical, Converts the four gate metrics into decision-grade evidence for the Phase 2 go/no-go. Pulls together ordinal, morphology, accent and G2P choices and competes with budget; weak instruments make the gate disputable and undermine partner confidence.

Decision 5: Phase Budget Weighting and Reserve

Lever ID: 093258bc-f4c3-4775-bec5-b125346fcf20

The Core Decision: Allocates the fixed $3.5M across rule specification, pilots and public release, and sets the size and release conditions of any contingency reserve. The split determines how many pilot sites, assessment sessions and print runs are affordable, and whether a no-go at the Phase 2 gate returns funds or strands them. Success means each gate is adequately funded without overspending before evidence exists.

Why It Matters: This lever splits the fixed $3.5M across rule specification, pilots and public release, and decides how much is held back as a reserve. Front-loading Phase 1 gives sturdier rules but squeezes pilots, where the evidence for the go/no-go gate is generated. A larger reserve protects against rework after Phase 2 but reduces what can be spent on outreach and curriculum quality.

Strategic Choices:

  1. Weight spending toward Phase 2 pilots and assessments, keeping Phase 1 lean through a small expert team and a deliberately narrow first rule set that can be piloted quickly.
  2. Spread spending roughly evenly across the three phases, with a modest unallocated reserve released by the editorial board only after the go/no-go decision.
  3. Hold a large contingent tranche that is released in stages against evidence milestones, so that a no-go outcome at Phase 2 returns unspent funds rather than financing a weak launch.

Trade-Off / Risk: Weighting toward pilots strengthens the evidence base, but a thin Phase 1 risks piloting flawed rules; a large staged reserve disciplines spending yet can leave teams under-resourced during the work that must come first.

Strategic Connections:

Synergy: Enables Outcome Metric Battery Design by funding the supervised sessions and psychometric review the gate depends on. Also supports Adoption Wedge and Sequencing by reserving money for Phase 3 outreach once the evidence is in.

Conflict: Constrains Outcome Metric Battery Design and Core Lexicon Selection Basis, since a lean Phase 1 or a large held reserve limits corpus work and instrument validation. Staged release also slows Editorial Board Seat Allocation's capacity to commission early work.

Justification: Critical, Fixed $3.5M envelope governs every other lever's feasibility: metric validation, multi-accent audio, tooling, outreach and licensing administration all compete for it. Controls the evidence-versus-lean-rules trade-off and whether a no-go returns funds.


Secondary Decisions

These decisions are less significant, but still worth considering.

Decision 6: Irregular Morphology Retention Threshold

Lever ID: 440edab7-8f36-408e-81ab-03bd984e89ac

The Core Decision: Defines the cutoff that decides which irregular verbs and plurals are regularized and which are retained, protecting recognizability while still removing real learning friction. The rule must be publishable, explainable and reproducible by third parties. Success metrics: share of the defined subset changed, misread rate on regularized forms, native-speaker acceptance, and learner retention after 30 days.

Why It Matters: The retention rule determines which irregular verbs and plurals are regularized and which are left alone. A frequency-based threshold keeps the most common forms, such as go/went, intact because learners already meet them constantly, and regularizes rarer ones where relearning cost is low. A looser threshold raises regularity but erodes the recognizability constraint and invites native-speaker resistance.

Strategic Choices:

  1. Retain every irregular form that falls within a high-frequency band of the core lexicon and regularize only lower-frequency irregulars, publishing the cutoff and the resulting list openly.
  2. Select forms for regularization using error data from ESL learner corpora, regularizing only those irregulars that learners most often get wrong and that have a low recognition penalty.
  3. Accept both regularized and legacy irregular forms during the pilot, then retire whichever form pilot readers resolve more slowly or misread more often before locking v1.0.

Trade-Off / Risk: A frequency cutoff protects intelligibility, but the cutoff value itself is arbitrary until pilot data exists, and the plan's own example go/went would probably be retained rather than regularized.

Strategic Connections:

Synergy: Draws directly on Core Lexicon Selection Basis, whose frequency data defines the high-frequency band, and relies on Outcome Metric Battery Design to supply error and reading-speed data for tuning the cutoff before v1.0 lock.

Conflict: Trades off against Change-Control and Release Cadence: accepting dual forms during the pilot means later retiring one, creating churn. Aggressive regularization also strains Editorial Board Seat Allocation when native-speaker members resist.

Justification: High, Governs the recognizability-versus-regularity trade-off for verbs and plurals, drawing on lexicon frequency and metric data and straining board consensus. Strong interactions, but a bounded rule subset with a likely conservative cutoff limits systemic reach.

Decision 7: Homograph Disambiguation Policy

Lever ID: 79d385f2-41b8-499f-9ae8-c2c2a22cf147

The Core Decision: Specifies when a homograph or homophone pair needs a marker, a rewrite or nothing, and how that obligation is enforced in different document types. Scope is a short, published high-impact pair list such as lead/lead and read/read. Success metrics: misreading rate in safety-critical test passages, authoring burden per page, compliance consistency and list size kept manageable.

Why It Matters: This lever decides when a marker, a rewrite, or nothing at all is required for pairs such as lead/lead or read/read. Mandatory markers in safety-critical text reduce misreading risk but add visual clutter and authoring burden. Optional markers are easier to adopt but produce inconsistent practice that undermines the standard's value for safety documents.

Strategic Choices:

  1. Require a disambiguation marker only in safety-critical and procedural documents for a short, published list of high-impact pairs, and leave it optional elsewhere.
  2. Replace markers with controlled-language writing rules that require authors to rephrase sentences so context resolves each homograph, as in simplified technical writing standards.
  3. Insert markers automatically through an authoring-tool plugin that flags ambiguous words and proposes the marked form, so authors approve rather than memorize the pair list.

Trade-Off / Risk: Tool-assisted marking lowers authoring burden, but it adds software development cost and a dependency on tooling that the $3.5M budget and small team may not sustain beyond the pilot.

Strategic Connections:

Synergy: Amplifies Controlled-Language Alignment Posture, since rewrite rules and marker rules can share one authoring checklist, and strengthens Adoption Wedge and Sequencing when the safety-critical track needs a concrete, measurable risk reduction.

Conflict: Constrains Phase Budget Weighting and Reserve if tool-assisted marking is chosen, since plugin development and maintenance compete with pilot and outreach funds. Mandatory markers also conflict with Grapheme-to-Phoneme Intervention Depth by adding visual clutter.

Justification: High, Delivers the concrete, measurable risk reduction that makes the safety-critical track credible. Links to controlled-language rules, lexicon, G2P clutter and budget if tooling is chosen; scope is a short pair list, so influence is narrower than the critical levers.

Decision 8: Reference Accent Anchor

Lever ID: d12e1659-c616-44f6-95e8-5eb35c1e2615

The Core Decision: Chooses which pronunciation model underpins the grapheme-to-phoneme rules, audio recordings, dictionary guidance and pilot scoring. Beyond measurement convenience, it determines which learner populations see the biggest gains and whether adoption is perceived as regional. Success metrics: pronunciation consistency score reliability across raters, share of core-lexicon entries with usable audio by Month 12 (2027-10-13), and no significant accent-based drop in pilot comprehension or retention.

Why It Matters: The accent chosen for pronunciation guidance and audio models decides which vowel and consonant contrasts the grapheme-to-phoneme rules treat as fixed and which learners gain the most. A single anchor makes the pronunciation consistency score straightforward to measure, but it can alienate speakers of other major varieties and narrow adoption outside the anchor region.

Strategic Choices:

  1. Anchor all pronunciation guidance, recordings and pilot scoring to one widely taught reference accent, and document how other accents map onto it.
  2. Specify only the phoneme contrasts shared across major English varieties, leave other vowel realizations deliberately unspecified, and score pilot pronunciation consistency on the shared contrasts alone.
  3. Record every core-lexicon entry in several regional accents, let publishers and learners select an accent profile, and keep the written form identical across all profiles.

Trade-Off / Risk: A single anchor accent keeps measurement clean but quietly privileges one speaker population, while a multi-accent design widens appeal at the cost of recording effort and a muddier pronunciation consistency metric for the go/no-go gate.

Strategic Connections:

Synergy: Amplifies Grapheme-to-Phoneme Intervention Depth, since a fixed anchor decides which contrasts the mapping must encode. It also strengthens Outcome Metric Battery Design by giving the pronunciation consistency score a clean, auditable reference.

Conflict: Trades off against Core Lexicon Selection Basis and Phase Budget Weighting and Reserve: multi-accent recording multiplies per-word audio effort across 5,000 entries, while a single anchor narrows appeal beyond one region.

Justification: Medium, Supplies the sound targets for G2P rules and a clean pronunciation score, but is largely a supporting input to the G2P depth decision. Main tension is recording effort versus regional appeal, which is an optimization within budget.

Decision 9: Core Lexicon Selection Basis

Lever ID: 533fda13-50d1-49c7-98aa-d1c490efbbd9

The Core Decision: Sets the selection principle for the 5,000-word core lexicon, which is the unit the dictionary, pronunciation guidance and pilot curriculum all operate on. The choice defines first beneficiaries (general ESL learners versus safety-critical readers) and how quickly pilot cohorts perceive value. Success metrics: coverage of running text in pilot glossaries, share of entries needing rule exceptions, and auditability of the list's provenance.

Why It Matters: The principle used to pick the 5,000 core words determines whom the dictionary serves first and how quickly pilot cohorts see practical value. A frequency-led list maximizes general coverage, while a domain-led list improves safety-critical usefulness but may omit everyday words learners need to read the surrounding text.

Strategic Choices:

  1. Build the 5,000-word list from general-English frequency corpora, then add a small reserved block of technical and safety terms to cover pilot glossaries.
  2. Seed the list with safety-critical and technical glossary terms first, then fill the remaining slots with the highest-frequency general words needed to read those documents.
  3. Derive the list from incident reports, near-miss records and procedure manuals where ambiguous wording caused confusion, then fill gaps from ESL syllabus word lists.

Trade-Off / Risk: Frequency lists are defensible and easy to audit but generic; incident-driven selection is persuasive to safety stakeholders yet depends on access to sensitive records that organizations may be unwilling or slow to share.

Strategic Connections:

Synergy: Enables Homograph Disambiguation Policy and Adoption Wedge and Sequencing: an incident-informed or domain-seeded list surfaces the high-impact ambiguous pairs and gives the safety-critical wedge a concrete, credible vocabulary to start with.

Conflict: Conflicts with Controlled-Language Alignment Posture, which may impose an existing controlled vocabulary, and with Irregular Morphology Retention Threshold, since frequency-led lists contain the most entrenched irregular forms that resist regularization.

Justification: High, Defines the 5,000-word unit on which dictionary, pronunciation guidance and curriculum operate. Enables homograph identification and the safety-critical wedge, and conflicts with morphology retention and controlled-language vocabulary. Important, but largely downstream of the wedge choice.

Decision 10: Change-Control and Release Cadence

Lever ID: c310f188-a76c-47fb-ab70-544c06a4980f

The Core Decision: Governs how the standard changes after v1.0: freeze periods, errata handling, scheduled revisions or a candidate-and-comment path. It is the mechanism that converts pilot findings into rule fixes without destabilizing printed materials already in circulation. Success metrics: time from change proposal to ruling, number of concurrent live versions, publisher confidence in stability, and the count of unofficial forks.

Why It Matters: The rules for amending the standard after v1.0 determine whether publishers and teachers can trust it as stable or see it as a moving target. Frequent revision answers pilot feedback quickly but multiplies version confusion, while a hard freeze protects materials yet locks in any rule errors the pilots expose.

Strategic Choices:

  1. Freeze v1.0 for a fixed period after publication, accepting only errata, and collect change proposals for a single consolidated v2.0 review.
  2. Issue scheduled minor revisions at fixed intervals, each with a published deprecation notice and a conversion table from the previous release.
  3. Release v1.0 as a candidate standard with an open public-comment window and a sandbox for registered experimental forks before ratifying the final rule set.

Trade-Off / Risk: Stability and responsiveness pull in opposite directions; the board must choose which failure it can better absorb, and an unclear cadence invites the fragmentation the risk register already flags.

Strategic Connections:

Synergy: Reinforces Licensing and Name Stewardship by giving certification or share-alike terms a defined version baseline to test conformance against. It also supports Editorial Board Seat Allocation with a predictable decision calendar.

Conflict: Constrains Outcome Metric Battery Design and Ordinal Marker Architecture: a hard freeze locks in any rule errors the Phase 2 pilots expose, while rapid revisions undermine comparability of pilot data and printed curricula.

Justification: Medium, Matters for post-v1.0 stability and fragmentation control, reinforcing licensing and board decisions. Operates mostly after the Phase 2 gate, so it is less central to the near-term strategic outcome than rule and evidence choices.

Decision 11: Licensing and Name Stewardship

Lever ID: e6d5785e-6fe6-4aaa-bc8d-121c6c4eaa77

The Core Decision: Determines the legal and brand terms under which the standard, dictionary and the 'Clear English' name circulate. It balances low-friction uptake by ESL publishers and standards bodies against protection from diluted or non-conforming material using the name. Success metrics: number of third-party adopters licensed, share of labelled materials passing a conformance check, and absence of confusing look-alike variants by Month 36 (2029-10-13).

Why It Matters: How the standard, dictionary and the name 'Clear English' are licensed shapes both third-party uptake and the project's ability to prevent diluted or divergent versions. Permissive terms lower adoption friction, but without some name control any publisher can label non-conforming material as Clear English.

Strategic Choices:

  1. Release all deliverables under a fully permissive open license with no restrictions on the name, relying on the editorial board's reputation to signal the authoritative version.
  2. License the text and dictionary openly, but reserve the name as a certification mark awarded to materials that pass a published conformance checklist.
  3. Use a share-alike license that requires derivative works to declare which rules they diverge from and to adopt a distinct name once they diverge.

Trade-Off / Risk: Open terms and quality control conflict: certification marks protect integrity but add an administrative burden and a gatekeeper image that may deter the ESL publishers and standards bodies whose adoption the project needs.

Strategic Connections:

Synergy: Amplifies Adoption Wedge and Sequencing by letting early adopters reuse materials with clear terms, and works with Change-Control and Release Cadence, where versioned conformance checklists make name stewardship enforceable.

Conflict: Tensions with Controlled-Language Alignment Posture and Editorial Board Seat Allocation: certification gatekeeping can deter standards bodies and publishers, and it demands board capacity and administrative budget that Phase Budget Weighting and Reserve must absorb.

Justification: High, Controls the open-uptake versus anti-fragmentation trade-off central to third-party adoption by publishers and standards bodies. Connects to wedge, change-control and board capacity, but its impact materializes mainly in Phase 3 after the evidence exists.

Decision 12: Controlled-Language Alignment Posture

Lever ID: 8fb6c1ea-42bc-4ded-8e9d-ae685aa0f1f3

The Core Decision: Defines how Clear English relates to existing controlled languages such as ASD-STE100 Simplified Technical English and plain-language guidance, which technical writers already follow. The choice sets the effort for safety-critical adopters, whether one or two rule sets must be run, and how much design freedom the project retains. Success metrics: share of pilot technical documents passing both rule sets, and writer conversion effort.

Why It Matters: This lever sets how Clear English relates to existing controlled languages such as Simplified Technical English and plain-language guidance already used in safety-critical writing. Tight alignment lowers the barrier for technical writers who already follow a controlled vocabulary, but it ties the standard to another body's conventions. A distant posture preserves design freedom but forces safety-critical adopters to run two rule sets.

Strategic Choices:

  1. Build Clear English as a compatible overlay that reuses the vocabulary and sentence-writing constraints of an existing controlled language, adding only the orthographic and ordinal rules on top.
  2. Design Clear English as an independent standard with its own rules, and publish a one-way mapping table so technical writers can translate from existing controlled-language documents.
  3. Co-develop the safety-critical glossary jointly with a controlled-language maintainer, so one shared term list is validated under both rule sets and each side can cite the other.

Trade-Off / Risk: Alignment speeds acceptance among technical writers, yet it imports another standard's limits and politics, and the claimed compatibility is hard to verify until pilot documents are actually run through both rule sets.

Strategic Connections:

Synergy: Strengthens Adoption Wedge and Sequencing by giving technical writers a familiar on-ramp, and supports Core Lexicon Selection Basis when a shared safety-critical term list is validated under both rule sets.

Conflict: Constrains Homograph Disambiguation Policy and Grapheme-to-Phoneme Intervention Depth, since an overlay inherits another body's vocabulary and conventions, limiting orthographic freedom and requiring coordination with an external maintainer's schedule.

Justification: Medium, Offers a familiar on-ramp for technical writers and shared glossary validation, but mainly serves the safety-critical wedge and overlaps with homograph and lexicon choices. Useful positioning optimization, with external-maintainer dependence limiting leverage.

Decision 13: Editorial Board Seat Allocation

Lever ID: cc0df26c-1351-481b-8450-753f7da0225e

The Core Decision: Sets who holds voting and veto authority over rule decisions, and how linguistic review, practitioners and learners are represented. Beyond composition, it fixes decision procedures, term lengths and conflict-of-interest rules that determine perceived legitimacy among educators, publishers and standards bodies. Success shows in rule-decision turnaround, retained seats, and endorsement by named partner institutions rather than linguistic elegance.

Why It Matters: This lever determines who sits on the editorial board and linguistic review panel and who holds decision authority over rule changes. A board weighted toward linguists favors internal consistency, while one weighted toward ESL teachers, technical writers and standards-body staff favors usability and adoption. The balance also shapes whether educators treat the standard as their own or as something imposed from outside.

Strategic Choices:

  1. Seat a linguist-majority board with advisory seats for practitioners, giving rule decisions a rigorous basis while risking the perception that the standard is academic and detached from classrooms.
  2. Seat a practitioner-majority board of ESL instructors, technical writers and safety trainers, with linguists holding a formal review-and-veto role limited to rule-conflict and ambiguity findings.
  3. Rotate board seats on fixed terms and add a standing learner panel whose pilot feedback must be formally answered in the published rationale for each rule.

Trade-Off / Risk: Practitioner weighting aligns with the adoption priority, but without strong linguistic review, rule ambiguity and drift can creep in; rotating seats add legitimacy at the cost of institutional memory and decision speed.

Strategic Connections:

Synergy: Amplifies Adoption Wedge and Sequencing and Controlled-Language Alignment Posture, since practitioner and standards-body seats open partner channels. Also strengthens Change-Control and Release Cadence by giving revisions a legitimate, accountable decision body.

Conflict: Tension with Change-Control and Release Cadence, because rotating or large boards slow decisions and dilute institutional memory. Also trades off against Irregular Morphology Retention Threshold and Homograph Disambiguation Policy, where linguist-weighted consistency pulls against practitioner usability preferences.

Justification: High, Fixes who holds rule authority and whether educators and standards bodies see the standard as legitimate. Opens partner channels for wedge and controlled-language alignment and sets the usability-versus-consistency balance in morphology and homograph decisions.

Choosing our strategic path.

The Strategic Context

Understanding the core ambitions and constraints that guide our decision.

Ambition and Scale: Moderately ambitious, institution-scale standards initiative: a parallel (not replacement) English variant with a 5,000-word core lexicon, a $3.5M (user constraint) budget and a 3-year, 3-phase timeline. Targets niche but high-value audiences (adult ESL, technical and safety-critical writing) and explicitly rejects mandates, K-12 replacement and universal-adoption claims.

Risk and Novelty: Novel and unproven: constructed-variant standardization with unknown native-reader acceptance. Main risks are educator pushback, rule ambiguity, fragmentation and liability in safety-critical use. The plan manages these through gating (go/no-go at Month 24 = 2028-10-13), optional markers and a capped change threshold, so the posture is moderate risk with evidence-first discipline.

Complexity and Constraints: Moderate-to-high operational complexity: rule specification, reference corpus, pronunciation guidance, print and digital curriculum, four gate metrics (comprehension speed, ordinal error rate, pronunciation consistency, 30-day retention), governance, licensing and outreach. Fixed budget, fixed 12-month phases, physical pilot sites with in-person assessment, and a pre-registered metrics requirement before Month 12 (2027-10-13).

Domain and Tone: Public-interest language standardization and education; business purpose without profit motive. Tone is pragmatic, evidence-driven and adoption-first ('optimize for user adoption, not linguistic purity'; 'don't pick the most aggressive scenario').

Holistic Profile: A cautious-but-credible, adoption-first standards program: modest linguistic intervention that coexists with standard English, ESL-led pilots, defensible gate evidence at Month 24 (2028-10-13) and balanced funding across three phases. It seeks real third-party uptake rather than maximal linguistic fix or minimal spend.


The Path Forward

This scenario aligns best with the project's characteristics and goals.

The Pragmatic Foundation

Strategic Logic: Build credible evidence with moderate-risk choices: an invariant ordinal prefix that coexists with legacy forms and converts mechanically, an on-demand pronunciation overlay that leaves printed text standard, and an ESL-first supplementary wedge that fits the pilot cohorts. Purpose-built, independently reviewed assessments give the go/no-go gate defensible data on the ordinal and pronunciation effects, while an even budget spread and a modest board-controlled reserve keep Phase 1 adequately resourced. This is the path best aligned with the brief's adoption-first, no-mandate stance.

Fit Score: 9/10

Why This Path Was Chosen: Prefix ordinals coexisting with legacy forms, an optional overlay leaving print standard, an ESL-first supplementary wedge, purpose-built validated gate metrics and an even budget align closely with the adoption-first, no-mandate, evidence-gated brief.

Key Strategic Decisions:

The Decisive Factors:


Alternative Paths

The Pioneer's Gambit

Strategic Logic: Pursue the deepest functional fix and the fastest user-base growth: fully spelled regular ordinals, respelling of the highest-friction patterns, and a free reader-facing toggle that builds usage before institutions commit. Spending is front-loaded to pilots and passive measurement at scale to generate evidence quickly, accepting the risks of native-reader rejection, fragmentation and a thin Phase 1. It is shown as the upper bound of ambition; given the brief's instruction to avoid the most aggressive scenario and to optimize for adoption over linguistic purity, it is not the recommended path.

Fit Score: 3/10

Assessment of this Path: Respelling, spelled-out ordinals such as 'oneth', a consumer toggle-first wedge and a thin Phase 1 are the aggressive path the brief rules out; they heighten native-reader rejection and fragmentation and favor linguistic fix over adoption.

Key Strategic Decisions:

The Prudent Consolidator

Strategic Logic: Minimize conversion cost, educator pushback and financial exposure: keep standard spellings intact, add a single pronunciation-guidance layer, use the cheapest-to-teach ordinal scheme, and measure with validated external instruments for maximum credibility. A large contingent tranche is released only against evidence milestones, so a no-go at Month 24 (2028-10-13) returns unspent funds rather than financing a weak launch. The trade-off is that the fix to spelling-to-sound inconsistency is shallow and less precise on Clear English-specific effects.

Fit Score: 6/10

Assessment of this Path: Low-risk and credible, but off-the-shelf instruments may miss ordinal and pronunciation effects that drive the go/no-go gate, and a large held reserve can under-resource Phase 1 rules and corpus work; the spelling-to-sound fix is shallow.

Key Strategic Decisions:

Purpose

Purpose: business

Purpose Detailed: Three-year, gated, $3.5M language-standardization program (rule specification and reference corpus, pilot learning materials and usability testing, public standard release with limited-scope adoption) for education, ESL, technical writing and safety-critical documentation. Deliverables are a public standard, reference dictionary, style guide, pilot curriculum and an open licensing policy, with editorial-board governance, a risk register, outreach to academic partners, ESL publishers and standards organizations, and a go/no-go decision after Phase 2. This is a standards and public-interest language initiative aimed at wide adoption, not a profit-seeking venture.

Topic: Design and launch of "Clear English", a standardized parallel variant of English with regularized ordinals, spelling-to-sound mapping, morphology and homograph disambiguation

Domain

Primary domain: Language Standardization

Secondary domains: Applied Linguistics, ESL Pedagogy, Orthography Design

Rationale: Language Standardization is the only outcome candidate that owns the project's overall success criterion: a governed, versioned standard variant of English. Lexicography is a component deliverable, Orthography Design and Applied Linguistics are methods, and ESL Pedagogy and Standards Development are adoption or process support.

Disciplines this project involves:

Domain Importance Specificity Role Reason
Language Standardization 5 5 outcome Core deliverable is a formal standardized English variant with rules, lexicon, and governance.
Orthography Design 5 5 method Grapheme-to-phoneme mapping, ordinal notation, and minimal diacritics are the core rule-design mechanism.
Applied Linguistics 5 4 method Phonology, morphology, and orthography design underpin grapheme-to-phoneme mapping and regularization rules.
Controlled Language Authoring 4 5 market Safety-critical and technical documentation, comparable to Simplified Technical English, is a target adoption market.
ESL Pedagogy 4 4 market Adult ESL learners are pilot cohort and primary adoption audience for curriculum.
Lexicography 4 4 outcome The 5,000-word reference dictionary with pronunciation guidance and mappings is a core deliverable.
Standards Development 4 4 stakeholder Editorial board governance, versioned standard, licensing, and standards-organization outreach require formal standards practice.
Instructional Design 4 4 method Print and digital pilot curriculum with assessments must be designed for adult learners.
Educational Psychometrics 4 4 method Go/no-go depends on valid comprehension, error-rate, and retention measurement from pilots.

Plan Type

This plan requires one or more physical locations. It cannot be executed digitally.

Explanation: The plan is a three-year, $3.5M program to design and launch "Clear English", a standardized variant of English. It is not executable purely online with zero benefit from physical presence or resources, so it is classified as physical. The physical requirements are:

Although the deliverables (standard, dictionary, style guide, licensing policy) are largely documents, the plan depends on human participants, physical materials, travel and facilities. Under the "if in doubt, physical" rule, the plan is physical.

Physical Locations

This plan does not imply any physical location.

Requirements for physical locations

Location 1

United Kingdom

Cambridge / Oxford area, England

University-adjacent offices near Cambridge or Oxford; partner language schools and ESL publishers (e.g., Cambridge, Oxford)

Rationale: Dense cluster of ESL publishers, assessment bodies, applied linguists and psychometric expertise. Strong access to adult ESL schools and standards-oriented organizations. Supports the ESL-first wedge and credible pilot measurement. Office costs are higher than in smaller cities.

Location 2

United States

Washington, D.C. metro area (including Arlington and Northern Virginia)

Co-working or university-affiliated office space near Georgetown University / Center for Applied Linguistics-type organizations; partner adult ESL programs in the metro area

Rationale: Large, diverse adult ESL population and many adult education programs. Proximity to standards bodies, federal safety and technical-writing communities and applied linguistics departments. Good air and rail links for outreach. Cost is higher but offset by access to partners and pilot participants.

Location 3

United States

Austin, Texas or similar mid-cost metro

Co-working space near University of Texas at Austin; adult ESL centers, community colleges and industrial or energy-sector training sites in the region

Rationale: Lower cost than coastal hubs, with a large adult ESL population, a university linguistics base and nearby industrial and energy safety-training settings for the technical-glossary cohort. Fits the budget limit while serving both pilot cohorts.

Location Summary

The plan names no site, but it is physical: in-person pilot cohorts, print curriculum, board meetings, audio capture and outreach all need real sites. Three options are suggested. Cambridge/Oxford offers publisher and assessment expertise. Washington, D.C. offers diverse ESL cohorts plus standards and safety communities. Austin offers lower cost with ESL and industrial training access. Final choice should weigh partner commitments and budget fit.

Currency Strategy

This plan involves money.

Currencies

Primary currency: USD

Currency strategy: All budgeting and financial reporting will be conducted in USD, aligning with the fixed $3.5M constraint. Phase splits and milestone payments will be tracked in USD. For operations in the UK (Location 1 option), GBP exchange rates should be locked at contract signature to avoid variance in office, partner and pilot costs; a modest contingency (2–3% of UK-based spending) is recommended to absorb currency fluctuation. If outreach to European standards bodies or ESL publishers occurs in Phase 3, EUR spending should be pre-approved and capped as a percentage of outreach budget. No hedging instruments are necessary given the modest scale and the administrative burden they impose on a small team; instead, fixed-rate agreements with vendors and partners will be prioritized to minimize exchange-rate surprise.

Identify Risks

Risk 1 - Regulatory & Standards Adoption

Educational and standards bodies (ESL publishers, national curricula authorities, standards-setting organizations) may reject Clear English as a non-standard variant or threat to unified English instruction, delaying or blocking third-party adoption. Regulatory bodies in jurisdictions requiring alignment with national language standards may refuse to permit use in accredited programs. The standard's legal standing and protection against dilution or divergent forks remain undefined until licensing is finalized.

Impact: Rejection by key adopter groups could reduce pilot enrollment and Phase 3 adoption to near zero, effectively ending the initiative despite completion of rule specification. Regulatory delays of 4–8 months could push pilot timeline into Month 28–32 (2029-02-13 to 2029-06-13) and jeopardize the Month 24 (2028-10-13) go/no-go gate. Uncontrolled fragmentation and unofficial variants could emerge within 18–24 months of public release, damaging credibility and undermining adoption claims.

Likelihood: High

Severity: High

Action: Engage national language-curriculum authorities and standards bodies (e.g., Common European Framework, TESOL leadership) in advisory roles from Month 1 (2026-11-13) to gauge regulatory appetite and identify formal approval pathways. Prepare formal submissions to relevant standards bodies by Month 15 (2028-01-13). Establish a licensing and name-stewardship framework by Month 12 (2027-10-13) that reserves the 'Clear English' mark for conforming materials and includes a public conformance checklist. Create a formal dispute-resolution procedure within the editorial board for handling divergent forks.

Risk 2 - Pilot Recruitment & Participant Retention

Recruiting and retaining sufficient adult ESL and native-speaker cohorts for statistically valid gate metrics (comprehension speed, ordinal error rate, pronunciation consistency, 30-day retention) may prove difficult if partnership institutions lack capacity, funding or learner availability. The plan requires in-person supervised sessions, audio capture and 30-day follow-up, imposing high participant burden. High dropout rates could render pilot data inconclusive at the Month 24 (2028-10-13) go/no-go gate.

Impact: Insufficient cohort size (fewer than 50–100 learners per condition) may make the four gate metrics statistically unreliable, forcing either extension of Phase 2 by 3–6 months or a disputed no-go decision. Dropout rates above 30% could reduce effective sample sizes further. A failed or inconclusive gate decision could strand Phase 3 funding ($800K–$1.2M, estimated) and delay market entry to Month 36 (2029-10-13) or beyond. Recruitment delays alone could consume 4–8 weeks of the 12-month Phase 2 window.

Likelihood: High

Severity: High

Action: Secure commitments from at least 3–4 adult ESL programs and 2–3 technical/safety-training organizations by Month 3 (2027-01-13), including written enrollment guarantees and contact-hour or per-learner payment terms. Offer learner incentives (certificates, small stipends, discounted course fees) to reduce dropout. Design assessments to fit existing course schedules to minimize added burden. Hire a dedicated Phase 2 project manager focused on cohort administration and retention by Month 12 (2027-10-13). Build a 10–15% contingency into projected cohort size to absorb attrition.

Risk 3 - Technical & Assessment Validity

Purpose-built gate metrics (comprehension speed, ordinal error rate, pronunciation consistency, 30-day retention) must be validated and pre-registered before Month 12 (2027-10-13) to ensure credibility for the Phase 2 go/no-go decision. Developing psychometrically sound instruments tailored to Clear English-specific effects requires expert effort and pilot testing that may exceed initial timeline or budget. If instruments are weak or inconsistently applied, the go/no-go decision will be scientifically disputable and lose partner confidence.

Impact: Instrument validation failures could delay metrics pre-registration by 2–4 months, compressing the Phase 2 pilot window to 8 months or fewer. Weak or disputed metrics could make the Phase 2 gate non-credible, forcing either a do-over at additional cost ($200K–$300K, estimated) or a gate decision that partners reject, stalling Phase 3 planning. Inconsistent scoring of pronunciation consistency across raters could inflate measurement noise, obscuring true effects and leading to a false-negative go/no-go outcome.

Likelihood: Medium

Severity: High

Action: Hire an independent psychometrician or applied measurement specialist by Month 2 (2026-12-13) and budget $150K–$200K (estimated) for instrument design, validation and inter-rater reliability studies. Pre-register the metric design, pass/fail thresholds and primary analysis plan on an open repository (e.g., OSF) by Month 11 (2027-09-13), 30 days before the Month 12 (2027-10-13) deadline. Conduct a small pilot validity study (N=20–30) in Month 10–11 (2027-08-13 to 2027-09-13) to confirm instruments discriminate between Clear English and standard English conditions before Phase 2 enrollment begins.

Risk 4 - Rule Ambiguity & Editorial Board Consensus

The morphology retention threshold, homograph disambiguation policy and ordinal marker pronunciation require editorial board consensus before Phase 1 rules can be finalized at Month 12 (2027-10-13). If board members (linguists, practitioners, learners) hold conflicting preferences—e.g., linguists favoring consistency versus teachers favoring recognizability—rule specifications may remain ambiguous, vague or internally contradictory. Unresolved conflicts delay rule publication and weaken the rule set's credibility for pilots.

Impact: Unresolved editorial disputes could push rule finalization by 4–12 weeks into Phase 2, compressing the pilot window. Ambiguous or internally inconsistent rules (e.g., unclear morphology exceptions or conflicting ordinal-marker guidance) could force rule clarifications or errata mid-pilot, invalidating earlier assessments and inflating measurement noise. A visibly divided editorial board could undermine educator and publisher confidence in the standard before pilots begin.

Likelihood: Medium

Severity: Medium

Action: Establish editorial board composition and decision procedures by Month 1 (2026-11-13), including clear voting rules, conflict-of-interest management and a formal 'decision logging' process that documents disagreements and the rationale for each ruling. Conduct a first editorial board meeting by Month 2 (2026-12-13) to surface rule tensions and assign rule-specification workstreams to board subcommittees. Set a hard rule-finalization deadline of Month 11 (2027-09-13), requiring all rule ambiguities to be resolved in writing and published as a draft standard by Month 11 (2027-09-13) for a 30-day public-comment window before finalization.

Risk 5 - Financial & Budget Overrun

The fixed $3.5M budget must be split across three 12-month phases, including rule specification, 5,000-word core lexicon with pronunciation recordings, reference corpus, purpose-built pilot assessments, print and digital curriculum design, pilot administration and outreach. Any of several line items could overrun: audio recording (multi-accent recordings at scale), psychometric validation (more expensive than estimated), pilot incentives and cohort management (retention costs), or unforeseen operational expenses (office space inflation, staff turnover requiring recruitment costs, technology licensing). A $200K–$500K overrun could force budget cuts mid-project.

Impact: A $300K overrun (8.6% of budget) during Phase 1–2 could force either reductions in pilot scope (fewer cohorts, smaller assessment battery), curriculum quality (less refined pilot materials) or postponement of outreach. Cutting Phase 2 pilot scope would undermine the go/no-go gate evidence. Cost overruns discovered in Month 18–24 (2028-04-13 to 2028-10-13) leave limited time to recover and no clear contingency plan. If contingency reserve is depleted before Phase 2 ends, a no-go decision would leave no unspent funds to return.

Likelihood: Medium

Severity: Medium

Action: Implement a detailed Phase-wise budget with monthly tracking and rolling 6-month forecasts beginning Month 1 (2026-11-13). Establish a spending review gate at Month 9 (2027-07-13) to assess Phase 1 expenses against budget and adjust Phase 2 allocations if needed. Allocate a clear contingency reserve of $175K–$250K (5–7% of budget) controlled by the editorial board and released only for pre-approved, evidence-backed needs (e.g., additional psychometric validation if Phase 1 pilot signals a tight gate). Negotiate fixed-rate contracts with curriculum vendors and audio studios by Month 3 (2027-01-13) to lock recording and design costs.

Risk 6 - Pronunciation Consistency Measurement & Accent Selection

The pronunciation consistency score, a key go/no-go gate metric, depends on a chosen reference accent (e.g., Received Pronunciation, General American) and reliable inter-rater scoring. If raters disagree on whether learner pronunciation matches the reference, the metric becomes noisy and unreliable. Choosing a single reference accent alienates speakers of other major varieties (Australian, Indian, South African English), narrowing adoption perception. Audio capture, storage and scoring infrastructure must be secured and tested before Phase 2 pilots begin.

Impact: Poor inter-rater reliability (Cohen's kappa <0.70) on pronunciation scoring would inflate measurement error, obscuring true Clear English effects and risking a false-negative gate outcome, delaying or killing Phase 3. Accent selection disputes (e.g., objections to British or American bias) could trigger criticism from standards bodies or ESL organizations, damaging the standard's perceived neutrality. Audio infrastructure failures (missing recordings, inaudible files, storage loss) could make pronunciations impossible to score, invalidating the metric.

Likelihood: Medium

Severity: High

Action: Anchor the reference accent selection by Month 3 (2027-01-13), with explicit written justification and documentation of how other major accents map to the anchor. Conduct inter-rater training and a calibration study (N=30–50 recordings) in Month 11 (2027-09-13), targeting Cohen's kappa ≥0.75 and publishing the scoring rubric openly. Secure audio storage infrastructure and backup protocols by Month 6 (2027-04-13); conduct a dry-run with a small pilot cohort (N=5–10) in Month 10 (2027-08-13) to test recording, storage and scoring workflows. If inter-rater reliability falls below 0.70 at Month 11 (2027-09-13), extend Phase 1 by 4 weeks to conduct additional rater training rather than proceeding to Phase 2 with weak measurement.

Risk 7 - Safety-Critical Adoption & Liability

If the project pursues a safety-critical adoption wedge (technical glossaries, procedures, incident reports), it assumes responsibility for the safety and clarity of documents using Clear English. Misreading or ambiguity in safety-critical text (e.g., a procedure or hazard label) caused by Clear English rules or gaps could result in injury, regulatory investigation or litigation. Liability exposure increases if Clear English forms are adopted in real working environments (factories, laboratories, medical settings) during Phase 2 pilots or Phase 3 early adoption. Insurance, legal review and risk-approval processes may be costly and slow.

Impact: A serious incident linked to Clear English documentation could result in litigation, regulatory action (e.g., from OSHA, EPA or equivalent bodies), and immediate pause or withdrawal of the standard, ending the initiative. Legal review and liability insurance could cost $100K–$300K (estimated) and delay safety-critical partner engagement by 2–4 months. Regulatory approval or safety-case review for safety-critical use could stretch to 6–12 months, pushing pilot enrollment into Month 30–36 (2029-04-13 to 2029-10-13). Any incident, even if not fatal or injurious, would trigger media scrutiny and credibility loss.

Likelihood: Low

Severity: High

Action: If pursuing the safety-critical adoption wedge, secure legal counsel specializing in product liability and regulatory compliance by Month 2 (2026-12-13) and develop a risk-mitigation and liability-insurance strategy by Month 4 (2027-02-13), with costs capped at $150K–$200K. Conduct a formal safety-case review with partner organizations (e.g., industry standards bodies) before any safety-critical pilot material is used in real working environments. Require all safety-critical pilot documents to carry explicit disclaimers and to be reviewed by qualified human experts (not Clear English alone) before deployment. Establish an incident-reporting protocol and a rapid-response team to address any misreading or clarity issues discovered during pilots. Consider capping safety-critical pilots to non-life-critical procedures or glossaries (e.g., warnings, labeling) rather than core operational procedures until post-Phase-2 evidence is strong.

Risk 8 - Educator Pushback & Teacher Training

Teachers, curriculum designers and ESL instructors may resist Clear English adoption for multiple reasons: perceived threat to standard English teaching, unfamiliarity with the rules, skepticism about evidence claims, or concern that learners will be confused by a non-standard variant. Without active teacher buy-in and training, pilots will fail. Educator pushback could manifest as low engagement, non-compliance with pilot protocols, or vocal criticism that damages public credibility. Training teacher cohorts on Clear English rules and pedagogy is a significant operational burden not fully budgeted in the plan.

Impact: Low educator engagement or non-compliance could reduce pilot quality and statistical power, making gate metrics unreliable or inconclusive. Public criticism from respected teachers or professional organizations (TESOL, IATEFL) could trigger negative media coverage, damaging credibility before the go/no-go gate decision. Inadequate teacher training could lead to rule misapplication in pilot materials, invalidating assessment results. Educator resistance could reduce Phase 3 adoption by 30–50% even if the gate decision is positive.

Likelihood: High

Severity: Medium

Action: Engage ESL teacher professional organizations (TESOL, IATEFL, national equivalents) as advisory partners by Month 2 (2026-12-13) and co-design pilot protocols with practicing teachers to increase buy-in. Develop a comprehensive teacher training program (online and in-person) by Month 10 (2027-08-13) covering Clear English rules, rationale, pilot administration and learner communication. Recruit and hire a dedicated educator-liaison person (0.5–1.0 FTE, estimated $50K–$70K for Phase 2) responsible for teacher engagement, training delivery and feedback loops. Offer continuing education credits or stipends to pilot teachers (estimated $20K–$40K across Phase 2) to incentivize active participation.

Risk 9 - Fragmentation & Unofficial Variants

Once the Clear English standard is published, third parties may create divergent variants or forks—e.g., a 'Simplified Clear English' for children, a 'Medical Clear English' with specialized terminology, or non-conforming materials labeled as Clear English but not adhering to the official rule set. Licensing and name-stewardship controls are planned but may be weak or unenforceable, especially against offshore publishers or open-source projects. Fragmentation undermines the standard's value for consistent communication and creates confusion for learners and users.

Impact: Uncontrolled fragmentation could emerge within 12–24 months of Phase 3 public release, reducing the perceived value of the standard and making adoption claims (e.g., 'Clear English is widely used for safety documentation') false. Certification and dispute-resolution overhead could consume 5–10% of ongoing governance budget ($50K–$100K annually post-Phase 3, not budgeted). Confusion over which variant is 'official' could depress adoption if educators and publishers perceive the standard as unstable or political.

Likelihood: Medium

Severity: Medium

Action: Finalize the Licensing and Name Stewardship decision (Decision 11) by Month 6 (2027-04-13), choosing either a certification-mark approach or a permissive share-alike license with divergence-disclosure requirements. Publish a clear conformance checklist and versioned certification procedure by Month 14 (2027-12-13). Establish a standing 'Standards Stewardship Committee' within the editorial board (3–5 members, 2–4 hours/month) with authority to review third-party claims to the Clear English name and issue guidance or public statements on non-conforming forks. Draft dispute-resolution procedures and consider low-cost arbitration options for contested conformance claims. Set a policy that substantial divergences (more than 10–15% of rule changes) trigger a requirement to adopt a distinct name.

Risk 10 - Coordination with Existing Controlled Languages

The plan considers alignment with existing controlled-language standards (e.g., ASD-STE100 Simplified Technical English) to ease adoption by technical writers. However, coordinating rule changes, vocabulary lists and pronunciation guidance with another standards body's maintenance schedule is operationally complex and constrains the project's independence. If alignment is chosen (Decision 12), changes to the external standard could force Clear English revisions, and conflicts between the two standards could confuse adopters.

Impact: Dependency on an external standards body's revision schedule could delay Clear English v1.0 release by 2–4 months if coordination is required. Unresolved conflicts between Clear English and an external controlled language (e.g., differing ordinal conventions) could make the '100% compatible' alignment claim false, embarrassing both standards. If the external standard is acquired, discontinued or significantly changed, Clear English would need rapid revision, straining the Change-Control and Release Cadence decision.

Likelihood: Low

Severity: Medium

Action: If the Controlled-Language Alignment Posture decision (Decision 12) opts for close coordination, formalize a Memorandum of Understanding with the external standards body by Month 4 (2027-02-13), defining scope, change-request procedures, and escalation paths for conflicts. Establish a standing liaison role (0.25–0.5 FTE) to coordinate vocabulary and rule changes. Conduct a detailed compatibility audit at Month 10 (2027-08-13) to identify and resolve conflicts before v1.0 finalization. Include explicit language in the Clear English license and documentation noting any dependency or alignment with external standards. If full compatibility cannot be demonstrated, clearly label the alignment as partial and specify which rules differ.

Risk 11 - Core Lexicon Coverage & Adequacy

The 5,000-word core lexicon is designed to cover ESL and safety-critical use, but its selection basis (Decision 9—frequency-led, domain-led, or incident-driven) determines whether it adequately serves pilots and early adopters. If the lexicon omits high-frequency words needed to read pilot materials or technical glossaries, assessments will suffer from confounding (learners struggle with out-of-lexicon words rather than Clear English effects). An incomplete or misaligned lexicon could undermine pilot credibility and adoption appeal.

Impact: If the core lexicon covers fewer than 85–90% of running text in pilot materials or technical glossaries, comprehension assessments will be confounded and gate metrics unreliable. Discovering inadequate coverage at Month 18 (2028-04-13) would require expansion of the lexicon, adding 4–8 weeks to Phase 2 and inflating pronunciation-recording costs ($20K–$50K per 500 words, estimated). Missing domain-specific terms (e.g., safety jargon) would reduce the appeal of the technical wedge and damage early-adopter credibility.

Likelihood: Medium

Severity: Medium

Action: Finalize the Core Lexicon Selection Basis decision (Decision 9) by Month 2 (2026-12-13) and conduct a pilot lexicon-coverage audit by Month 8 (2027-06-13), analyzing running text from existing ESL curricula and technical glossaries to confirm 85%+ coverage. If coverage falls short, allocate time and budget (estimated $30K–$50K) for targeted lexicon expansion by Month 10 (2027-08-13). Publish the lexicon and its selection methodology openly by Month 12 (2027-10-13), inviting third-party feedback and challenges. Reserve 5–10% of the core-lexicon slots for domain-specific additions identified during Phase 2 pilots before v1.0 lock.

Risk 12 - Timeline Compression & Phase Gate Slippage

The plan specifies three fixed 12-month phases with a hard go/no-go gate at Month 24 (2028-10-13). However, multiple dependencies and unknowns could compress the timeline: rule finalization delays, slow institutional partnerships, audio recording backlogs, psychometric validation setbacks, or pilot recruitment lag. If Phase 1 slips by 4–6 weeks, Phase 2 pilots face a compressed window, reducing data quality. If the Month 24 (2028-10-13) go/no-go gate must be postponed due to incomplete pilot data, Phase 3 outreach and adoption are delayed.

Impact: A 6-week slip in Phase 1 compresses Phase 2 to 10 months, reducing pilot robustness and possibly making the go/no-go gate decision inconclusive, triggering a 6–12 month extension (Month 30–36 = 2029-04-13 to 2029-10-13) that strands Phase 3 funding and delays market entry. Any gate delay beyond Month 24 (2028-10-13) pushes Phase 3 launch to Month 36 (2029-10-13) or later, reducing the project's ability to capitalize on early momentum. Compressed timelines force trade-offs: fewer cohorts, shorter follow-up periods, or weaker assessment instruments.

Likelihood: Medium

Severity: Medium

Action: Establish monthly project-status reviews with critical-path analysis and rolling forecasts of key milestones (rule finalization, psychometric validation, cohort recruitment, audio completion) from Month 1 (2026-11-13) onward. Build in explicit 2–4 week buffers at key decision points (Month 6 = 2027-04-13 for design freeze, Month 11 = 2027-09-13 for metrics finalization, Month 18 = 2028-04-13 for pilot midpoint) to catch and correct slippage. Identify high-risk dependencies early (e.g., audio recording capacity, partnership commitment letters) and secure contingency plans or backup vendors by Month 3 (2027-01-13). Create a formal escalation path to the editorial board if any critical path item slips >2 weeks, triggering review of timeline and scope.

Risk 13 - Data Privacy & Participant Confidentiality

Phase 2 pilots collect sensitive data: learner literacy levels, pronunciation recordings, test scores, demographic information and 30-day follow-up assessments. Audio recordings of pronunciation are biometric data requiring careful consent, storage and retention protocols. Institutional Review Board (IRB) or ethics-board approval may be required in the US and UK, depending on whether the pilot is classified as research. Data breaches, unauthorized use of recordings, or privacy violations could expose the project to legal liability and damage participant trust.

Impact: Delays in IRB/ethics approval (2–8 weeks) could compress the Phase 2 pilot window or push recruitment into Month 14–16 (2027-12-13 to 2028-02-13). Privacy violations or data breaches could trigger regulatory investigation (GDPR in UK, state privacy laws in the US) and litigation. Restrictive data-handling requirements (e.g., deletion of audio after transcription, restricted re-use) could limit future analysis and replicability of the go/no-go metrics. Participant concerns about data privacy could reduce cohort recruitment or increase dropout.

Likelihood: Medium

Severity: Medium

Action: Engage an IRB or ethics-review board early (Month 1–2 = 2026-11-13 to 2026-12-13) to clarify whether the pilot qualifies as research requiring formal review and to draft consent forms and data-handling protocols. Budget $10K–$20K (estimated) for ethics consulting and compliance management. Implement secure audio storage (encrypted, access-controlled, backed up) by Month 6 (2027-04-13) and conduct a data-protection audit by Month 8 (2027-06-13). Publish a clear privacy policy and data-retention schedule on the project website by Month 12 (2027-10-13), explicitly stating how long recordings are kept and who may access them. Offer participants the option to have their audio deleted post-analysis if they request it.

Risk 14 - Reference Accent & Multi-Accent Demand

Choosing a single reference accent (Decision 8) for pronunciation guidance and pilot scoring simplifies measurement but may trigger pressure to add additional accents (British, American, Australian, Indian) to broaden appeal and inclusivity. Multi-accent audio recording (5,000 words × 2–3 accents = 10,000–15,000 audio files) is expensive, complex to manage and complicates the pronunciation consistency score (Which accent is 'correct'?). Scope creep toward multi-accent coverage could inflate audio costs by 2–3× and compress other budget areas.

Impact: Pressure to add accents could emerge at Month 9–12 (2027-07-13 to 2027-10-13) during Phase 1, forcing a decision whether to absorb the cost (estimated $50K–$100K additional, straining Phase 1 budget) or decline and risk criticism from standards bodies and ESL organizations concerned about inclusivity. Multi-accent audio infrastructure (storage, playback, rater training) adds complexity and could delay pronunciation-guidance publication by 4–8 weeks. Scope creep here could cascade to other line items: additional accent guidance in the dictionary, revised pronunciation-consistency scoring procedures, extended pilot timelines.

Likelihood: Medium

Severity: Low

Action: Lock the single-accent decision early (Month 2–3 = 2026-12-13 to 2027-01-13) with explicit, published justification and a documented commitment to document how other accents map to the anchor by Month 12 (2027-10-13). Set a policy that accent additions are deferred to post-v1.0 (Phase 3 or beyond) and require a formal scope-change proposal with budget impact analysis. Consider recording a small secondary sample (200–300 high-frequency or safety-critical words) in one additional accent as a 'proof-of-concept' for Phase 3, costing $10K–$15K (estimated), rather than committing to full coverage.

Risk 15 - Publisher & Curriculum Vendor Capacity

The plan envisions publishers and ESL material vendors adopting or co-producing Clear English curricula in Phase 3. However, their capacity to invest in new materials, their interest in a non-standard variant, and their willingness to delay publication pending the Phase 2 go/no-go decision are all uncertain. Vendors may be slow to commit resources without market proof, or they may demand guarantees of adoption or a minimum revenue threshold that the project cannot offer. If major publishers decline to participate, Phase 3 adoption will be limited to small providers or open-source projects.

Impact: Low publisher engagement could reduce Phase 3 curriculum diversity, limiting adoption to niche ESL programs or technical contexts. Delayed vendor commitments could push Phase 3 curriculum launch to Month 36–42 (2029-10-13 to 2030-04-13), missing the window for near-term adoption momentum. Vendor demands for guarantees or revenue sharing could strain the project's governance or budget. Without major publishers, the standard's reach may plateau at 10,000–50,000 learners rather than reaching the 100,000+ needed for credible market presence.

Likelihood: High

Severity: Medium

Action: Engage major ESL publishers (Cambridge, Oxford, Pearson, smaller regional publishers) and material-development vendors as advisory partners by Month 3 (2027-01-13), seeking non-binding letters of interest or commitment to pilot or co-develop curricula. Conduct a Phase 3 publisher-readiness assessment at Month 18 (2028-04-13) to gauge commitment levels and identify gaps. Develop a clear, low-friction licensing pathway (Decision 11) and publish it by Month 12 (2027-10-13) to reduce vendor uncertainty. Offer a '30-day rights' window post-publication (Phase 3 start) where early-adopting publishers can claim specific glossaries or grade levels to incentivize rapid adoption.

Risk 16 - Measurement Construct Validity & Outcome Definition

The four gate metrics (comprehension speed, ordinal error rate, pronunciation consistency, 30-day retention) assume that improvements in these measures indicate that Clear English is superior and worthy of adoption. However, the construct validity of each metric—i.e., whether it actually measures what it claims (e.g., whether ordinal error rate captures ordinal learning or test-taking noise)—is untested. Confounds could inflate or deflate measured effects: e.g., learners might improve ordinal accuracy due to simple repeated exposure rather than Clear English superiority, or pronunciation consistency could be high for both Clear English and standard English if the accent is close to learners' first language.

Impact: Weak construct validity could lead to false-positive or false-negative go/no-go outcomes. A false-positive (gate passes but Clear English provides no real benefit) could launch a standard that fails to deliver on adoption promises, damaging credibility. A false-negative (gate fails but Clear English is actually effective) could kill a viable initiative. Unresolved construct questions at Month 24 (2028-10-13) could force a redo of Phase 2 or a disputed gate decision that stakeholders reject.

Likelihood: Medium

Severity: High

Action: Build construct-validity analysis into the Outcome Metric Battery Design (Decision 4) by Month 5 (2027-03-13). Conduct a detailed literature review and expert panel (applied linguists, psychometricians, ESL researchers) to identify potential confounds and design control conditions that isolate Clear English effects from other learning factors. In Phase 2 pilots, include explicit manipulation checks (e.g., explicit instruction on ordinal rules versus implicit learning) to validate that observed effects are due to Clear English comprehensibility and not other factors. Publish a pre-analysis plan documenting the construct-validity framework and all confound-control measures before Phase 2 begins.

Risk 17 - Sustainability & Post-Phase-3 Governance

The plan addresses governance during the three-year project (editorial board, linguistic review, pilot administration) but does not specify how the standard will be maintained, updated and governed after Month 36 (2029-10-13) when external project funding ends. Ongoing tasks—responding to adoption feedback, managing change requests, handling disputes over rule interpretation, updating the lexicon with emerging vocabulary—require sustained funding and staffing. Without a clear post-project governance model and funding plan, the standard could atrophy or become poorly maintained, undermining long-term adoption.

Impact: Lack of post-project governance could degrade the standard within 12–24 months of Phase 3 completion. Ambiguities and errors discovered after v1.0 publication would go unaddressed, reducing credibility and adoption. Emerging vocabulary and cultural shifts would not be incorporated into the lexicon, making the standard feel outdated by Month 48–60 (2030-10-13 to 2031-10-13). Third-party adopters and educators would face uncertainty about the standard's future, reducing their willingness to invest in long-term adoption.

Likelihood: High

Severity: Medium

Action: Define a post-Phase-3 governance and funding model by Month 24 (2028-10-13), before the go/no-go gate decision. Identify potential sustaining organizations (e.g., language education non-profits, standards bodies, academic consortiums) and approach them for funding commitments (estimated $150K–$250K annually for ongoing maintenance, estimated) by Month 30 (2029-04-13). Establish a permanent Standards Stewardship Committee (Decision 7 touches on this) with clear roles, decision authority and term lengths. Publish a 5-year stewardship plan by Month 36 (2029-10-13), outlining how the standard will be updated, how change requests will be prioritized and how conflicts will be resolved.

Risk 18 - Market Saturation & Competing Standards

The English-language standardization space is not empty. Existing initiatives—plain-language standards, controlled-technical languages, reformed spelling movements—compete for attention and adoption. New entrants may emerge during the three-year project timeline. If Clear English is perceived as a marginal variant or a late arrival to a crowded field, adoption may stall. Competitor standards or initiatives endorsed by larger organizations (UNESCO, British Council, ILO) could eclipse Clear English before it gains traction.

Impact: Competition could reduce Phase 3 adoption by 20–40%, capping learner reach at 20,000–50,000 instead of the 100,000+ needed for significant market presence. Competing standards endorsed by larger bodies could crowd out Clear English in institutional procurement decisions (ESL curricula, safety standards). Phase 3 outreach budget would need to be higher to differentiate Clear English and build awareness, straining the $3.5M envelope.

Likelihood: Low

Severity: Low

Action: Conduct a competitive landscape analysis by Month 3 (2027-01-13), mapping existing plain-language, controlled-language and spelling-reform initiatives and their adoption rates, funding and organizational backing. Identify Clear English's unique value proposition (e.g., 'ordinal standardization for safety-critical procedures' or 'ESL-optimized pronunciation guidance') and emphasize it in all outreach by Month 12 (2027-10-13). Monitor the field for new entrants during Phase 2 and adjust messaging as needed. Build academic partnerships (universities, research centers) that provide credibility and differentiation from commercial or political initiatives.

Risk 19 - Currency Fluctuation & International Operations

The project operates across multiple currencies (USD primary budget, GBP for UK operations if Location 1 is chosen, EUR for European outreach). Currency fluctuations, particularly if the UK (Location 1) is selected as the operational hub, could inflate costs and compress the budget. A 10–15% depreciation of GBP against USD (as occurred in 2016–2024) could add £50K–£100K in real costs for UK-based office, partnerships and staff without corresponding budget increases.

Impact: A 10% GBP depreciation against USD could reduce UK operational budget purchasing power by £50K–£100K (estimated), forcing cuts in pilot scope, personnel, or outreach. Unhedged currency risk could emerge in Months 12–24 (2027-10-13 to 2028-10-13), when most Phase 2 spending occurs, leaving limited time to adjust. Late discovery of currency pressures could trigger budget-cutting decisions that compromise pilot quality or team capacity.

Likelihood: Low

Severity: Low

Action: Implement the currency strategy outlined in the currency_strategy.md file: denominate all budgeting and reporting in USD; if Location 1 (UK) is chosen, lock GBP exchange rates in contracts by Month 3 (2027-01-13) to avoid variance in office and partner costs; allocate a modest 2–3% contingency within UK-based spending to absorb exchange-rate fluctuation. Monitor currency forecasts quarterly and assess impact on budget; if significant headwinds emerge (>5% adverse movement), propose a budget amendment or deferred spending to leadership by Month 15 (2028-01-13).

Risk 20 - Stakeholder Misalignment on 'Success'

Stakeholders—educators, standards bodies, ESL publishers, learners, safety regulators—may have divergent definitions of what constitutes successful Clear English adoption. Educators may prioritize ease of teaching and learner engagement; regulators may prioritize measurable safety improvements; publishers may prioritize revenue potential; learners may prioritize job prospects or fluency gain. If the project's definition of success (as measured by the four gate metrics) does not align with what stakeholders value, adoption may remain low even if the metrics pass the gate.

Impact: Misaligned stakeholder expectations could lead to post-launch disappointment and reduced adoption (20–40% lower than projected). Educators could resist adoption if they perceive the standard as imposing inconvenient rules rather than delivering classroom benefits they care about. Safety regulators could decline to mandate or incentivize Clear English if they don't see measurable, incident-reduction improvements. This misalignment could be discovered at Month 24 (2028-10-13) (go/no-go) or later, stranding Phase 3 planning.

Likelihood: Medium

Severity: Medium

Action: Conduct stakeholder-expectation interviews and focus groups during Month 1–3 (2026-10 to 2027-01), engaging educators, regulators, publishers and learners to understand their success criteria and concerns. Publish a 'Stakeholder Alignment Charter' by Month 6 (2027-04-13) that documents stakeholder input and explains how the project's metrics and approach address key concerns. Build stakeholder advisory panels (separate from the editorial board) for educators, regulators and publishers, meeting quarterly to surface emerging concerns and expectations. At Month 18 (2028-04-13), conduct a mid-phase stakeholder check-in to assess alignment and adjust Phase 2 or Phase 3 strategy if major gaps are identified.

Risk summary

This three-year, $3.5M language-standardization initiative is ambitious, evidence-gated and operationally complex. The top three critical risks that could jeopardize success are: (1) Regulatory & Standards Adoption (high likelihood, high severity): Educational authorities, standards bodies and ESL publishers may reject Clear English as a non-standard threat or fragmentation risk, blocking institutional adoption and reducing the pilot to voluntary, low-engagement cohorts. This risk requires early engagement with regulatory bodies and a credible licensing framework by Month 12 (2027-10-13). (2) Pilot Recruitment & Retention (high likelihood, high severity): Recruiting sufficient adult ESL and native-speaker cohorts for statistically defensible gate metrics, and retaining them through 30-day follow-up, is operationally challenging and high-cost. Failure to retain 70%+ of recruited learners invalidates the comprehension speed, ordinal error rate, pronunciation consistency and 30-day retention metrics that trigger the Phase 2 go/no-go decision. This requires early partnership commitments, learner incentives and dedicated cohort management by Month 3 (2027-01-13). (3) Assessment Validity & Rule Ambiguity (medium–high likelihood, high severity): Purpose-built gate metrics must be psychometrically sound and pre-registered by Month 12 (2027-10-13) to be credible; editorial board consensus on morphology, homographs and ordinals must be resolved by Month 11 (2027-09-13) to avoid mid-pilot rule changes. Weak or ambiguous metrics could render the Month 24 (2028-10-13) go/no-go gate scientifically disputable, forcing expensive rework or a failed gate. Secondary risks include Phase 1 timeline slip (compressing Phase 2 pilot window), educator pushback (reducing engagement and public credibility), fragmentation and unofficial variants (undermining standard stability post-launch), and safety-critical liability exposure (if that wedge is chosen). The plan's Pragmatic Foundation path—invariant prefix ordinals, optional pronunciation overlay, ESL-first supplementary wedge, purpose-built validated metrics and even budget spread—substantially mitigates these risks by avoiding aggressive rule choices, protecting compatibility with standard English and ESL pedagogy, and building credible evidence before scaling. However, active risk management (stakeholder engagement, timeline discipline, budget controls, governance clarity) is essential from Month 1 (2026-11-13) onward to prevent slippage and maintain stakeholder confidence through the Phase 2 gate.

Make Assumptions

Question 1 - How should the $3.5M (user constraint) be split across the three phases, and what reserve is held back and who releases it?

Assumptions: Assumption: Roughly even split: Phase 1 $1.1M, Phase 2 $1.2M, Phase 3 $0.85M (proposed), plus a $0.35M (10%, proposed) reserve released by the editorial board only after the Month 24 (2028-10-13) go/no-go. Even spreads match the Pragmatic Foundation path and keep rule work and pilots funded.

Assessments: Title: Financial Feasibility Assessment Description: Adequacy of the phased budget and reserve. Details: Largest lines are staff, psychometric validation (estimate $150K-$200K), audio capture and pilot administration. Risk: a $300K overrun (estimate) is 8.6% of budget and would cut pilot scope. Mitigation: monthly tracking, a Month 9 (2027-07-13) spending review, fixed-rate vendor contracts by Month 3 (2027-01-13). Benefit: a no-go at Month 24 (2028-10-13) leaves the reserve and most Phase 3 funds unspent.

Question 2 - Which fixed milestones and buffers govern the gated schedule, including metric pre-registration and the Month 24 (2028-10-13) go/no-go?

Assumptions: Assumption: Phase 1 runs Months 0-12 (2026-10-13 to 2027-10-13), Phase 2 Months 12-24 (2027-10-13 to 2028-10-13), Phase 3 Months 24-36 (2028-10-13 to 2029-10-13). Rules draft by Month 11 (2027-09-13) with a 30-day comment window, metrics pre-registered by Month 11 (2027-09-13), go/no-go at Month 24 (2028-10-13), with 2-4 week buffers (proposed) at Months 6, 11 and 18 (2027-04-13, 2027-09-13, 2028-04-13).

Assessments: Title: Timeline Feasibility Assessment Description: Credibility of the 36-month gated plan. Details: Critical path: board decisions, lexicon, audio, instrument validation, then recruitment. A 6-week Phase 1 slip compresses pilots to about 10 months. Mitigation: monthly critical-path reviews, escalation for slips over 2 weeks, partner commitments secured by Month 3 (2027-01-13). Opportunity: early pre-registration makes the gate defensible and lets Phase 3 planning begin before Month 24 (2028-10-13).

Question 3 - What core team and external expertise are needed, and how many pilot learners per condition are required?

Assumptions: Assumption: Core team of about 8-10 FTE (proposed): project lead, 2-3 linguists, psychometrician, curriculum designers, Phase 2 cohort manager, educator liaison, developer. Pilot target of at least 50-100 learners per condition (estimate), with 15% over-recruitment for attrition.

Assessments: Title: Resource and Staffing Assessment Description: Capacity to deliver rules, materials and pilots. Details: Psychometric and cohort-management skills are the scarce roles; hire the psychometrician by Month 2 (2026-12-13). Dropout above 30% would weaken statistical power. Mitigation: written enrollment guarantees from 3-4 ESL programs, stipends and certificates, assessments fitted into existing course time. Opportunity: university partners supply raters and graduate assistants cheaply.

Question 4 - What governance structure decides rules, and what licensing and name-stewardship terms apply?

Assumptions: Assumption: Practitioner-leaning editorial board (7-9 members, proposed) with a formal linguist review-and-veto limited to ambiguity and conflict findings. Text and dictionary openly licensed; the 'Clear English' name reserved as a certification mark against a public conformance checklist, decided by Month 6 (2027-04-13).

Assessments: Title: Governance and Regulatory Assessment Description: Decision authority, legitimacy and anti-fragmentation controls. Details: Practitioner weighting serves adoption, while linguist review limits rule ambiguity. Logged decisions and conflict-of-interest rules support legitimacy. Risk: certification may look gatekeeping to publishers; keep checklist light and free. Add ethics review and data-protection compliance (GDPR/US state law) for pilot audio. Post-Month 36 (2029-10-13) stewardship funding is not yet secured.

Question 5 - What safety and liability controls apply to pilots using safety-critical glossaries?

Assumptions: Assumption: Safety-critical pilots are limited to glossary and labeling exercises, not live operational procedures, until after Month 24 (2028-10-13). All materials carry disclaimers and are reviewed by qualified humans; legal counsel retained by Month 2 (2026-12-13), with liability costs capped near $150K-$200K (estimate).

Assessments: Title: Safety and Risk Assessment Description: Liability exposure from misreading in safety contexts. Details: Likelihood is low but severity is high; one incident could end the program. Mitigation: formal safety-case review with partners, incident-reporting protocol, insurance strategy by Month 4 (2027-02-13). Because the ESL-first wedge leads, safety exposure is deferred and bounded. Other risks to track: rule ambiguity, educator pushback, fragmentation, all in the register with owners.

Question 6 - What environmental impacts arise from print curriculum, travel and in-person sessions, and how will they be limited?

Assumptions: Assumption: Impact is small. Digital-first materials with limited, on-demand print runs (small pilot batches, proposed) and recycled stock; travel limited to essential partner and board meetings, with virtual meetings as default.

Assessments: Title: Environmental Impact Assessment Description: Footprint of printing, travel and facilities. Details: Main sources are print runs, flights for outreach and pilot-site travel. Benefit: the on-demand pronunciation overlay keeps printed text standard and avoids reprints when rules change. Risk: print materials still need the pronunciation key, so freeze content before printing. Mitigation: shared co-working space, regional pilot sites, track print volume and travel as simple annual indicators.

Question 7 - Which stakeholders must be engaged early and in what roles, and how is their feedback fed into decisions?

Assumptions: Assumption: Advisory roles from Month 1-3 (2026-11-13 to 2027-01-13) for ESL teacher bodies (e.g., TESOL, IATEFL), 3-4 ESL programs, 2-3 technical training organizations, ESL publishers and one standards body. Separate stakeholder advisory panels meet quarterly; a Stakeholder Alignment Charter is published by Month 6 (2027-04-13).

Assessments: Title: Stakeholder Engagement Assessment Description: Buy-in from educators, publishers and standards bodies. Details: Educator pushback and publisher capacity are high-likelihood risks. Mitigation: co-design protocols with teachers, an educator liaison (0.5-1.0 FTE, estimate), stipends or continuing-education credit, non-binding publisher letters of interest by Month 3 (2027-01-13). Positioning as supplementary, never replacement, reduces resistance. A Month 18 (2028-04-13) check-in catches misaligned success definitions before Phase 3.

Question 8 - What operational systems are needed for rule management, the lexicon, audio capture, assessments and the go/no-go?

Assumptions: Assumption: Version-controlled rule repository, lexicon database with pronunciation overlay generator, encrypted audio storage with backups by Month 6 (2027-04-13), an assessment and logging platform, and a pre-registered analysis plan. Single anchor accent chosen by Month 3 (2027-01-13); go/no-go thresholds fixed before pilots (to be set by the board).

Assessments: Title: Operational Systems Assessment Description: Tooling and processes supporting pilots and the gate. Details: Inter-rater reliability target kappa of at least 0.75 (proposed), with extension if below 0.70. Lexicon coverage of at least 85% of pilot text (proposed) to avoid confounds. Risks: audio loss, rule changes mid-pilot invalidating items; mitigate with backups, rule freeze at Month 11 (2027-09-13) and a dry run at Month 10 (2027-08-13). Keep tooling lean to fit budget and post-project maintenance.

Distill Assumptions

Review Assumptions

Domain of the expert reviewer

Project management and standards development, with specialization in educational language initiatives, evidence-based program design, stakeholder governance, and risk mitigation in multi-phase, fixed-budget public-interest projects.

Domain-specific considerations

Issue 1 - Missing Definition of Gate Thresholds and Success Criteria for Four Metrics

The plan names four go/no-go metrics (comprehension speed, ordinal error rate, pronunciation consistency, 30-day retention) but does not specify the quantitative thresholds (e.g., 'ordinal error rate must drop by at least 25% from baseline') or sample-size targets that trigger a pass. Without pre-registered, numerical pass/fail criteria, the Month 24 (2028-10-13) go/no-go decision becomes subjective and disputable, inviting stakeholders to claim the gate was too lenient or too strict. This ambiguity risks deadlock among editorial board members, regulators and adopters.

Recommendation: By Month 5 (2027-03-13), the editorial board must commission a psychometrician to draft a pre-analysis plan specifying: (1) quantitative pass/fail thresholds for each of the four metrics with explicit justification (e.g., 'ordinal error rate must decline by 20–30% relative to standard-English control; this range reflects literature on instructional effect sizes and educator feedback'); (2) minimum sample sizes per condition (e.g., n≥80 per group to achieve 80% statistical power at α=0.05); (3) primary and secondary outcome definitions; (4) intention-to-treat vs. completer-case analysis rules. This plan must be registered on a public repository (e.g., Open Science Framework) and published by Month 11 (2027-09-13), 30 days before Phase 2 pilots begin. Failure to pre-register triggers an immediate Month 12 (2027-10-13) board decision to delay Phase 2 by 6–12 weeks for instrument finalization.

Sensitivity: If gate thresholds are set too high (e.g., 40% improvement required), a false-negative outcome is likely, potentially killing a viable standard and stranding ~$1.2M–$1.4M (Phase 2–3 budget). If thresholds are too loose (e.g., 5% improvement), a false-positive launches a weak standard, damaging long-term credibility and adoption by 30–50%. A 4-week delay in pre-registration compresses the Phase 2 pilot window from 12 to 11 months, reducing cohort retention by an estimated 5–10 percentage points and inflating measurement error by ~10–15%.

Issue 2 - Absent Contingency Plan for Rule Ambiguity or Editorial Board Deadlock

The plan assumes the editorial board will finalize rules (ordinal marker design, morphology retention threshold, homograph markers) by Month 11 (2027-09-13). However, it does not specify conflict-resolution procedures if linguists, practitioners and learner representatives disagree (e.g., if linguists prefer consistency while teachers prefer simplicity, or if native speakers reject 'oneth'-style ordinals). Without a formal tiebreaker mechanism and decision authority, rule disputes could stall the board for weeks, compressing pilots or forcing ambiguous rules into Phase 2, where mid-pilot clarifications invalidate earlier assessments.

Recommendation: By Month 1 (2026-11-13), publish an explicit Editorial Board Charter (2–3 pages) specifying: (1) voting rules (e.g., simple majority with a linguist-review veto limited to ambiguity findings, not design preferences); (2) escalation path if voting deadlocks (e.g., a 'neutral arbiter' from an external linguistics or standards body casts a tie-breaking vote); (3) conflict-of-interest disclosure (e.g., publishers on the board recuse themselves from licensing decisions); (4) term limits (e.g., 2-year terms with staggered renewal to preserve institutional memory). For any rule requiring a tiebreaker, the board must document both the majority and minority positions in the published rule rationale, creating transparency. Establish a hard deadline of Month 10 (2027-08-13) for all rule disputes to be resolved, allowing a 1-month buffer for drafting and public comment before the Month 11 (2027-09-13) finalization.

Sensitivity: A 4-week board deadlock compresses Phase 2 pilots by ~3.3% (4 weeks out of ~12 months), reducing effective pilot window to 11 months and inflating measurement error. A forced, ambiguous rule (e.g., 'morphology should be regular except for high-frequency exceptions') could trigger 10–20% rule misapplication during pilots, confounding results. Escalation to an external arbiter adds ~$10K–$20K (estimated) in consulting costs and a 2-week process delay if not pre-negotiated.

Issue 3 - Underspecified Confound Controls and Construct Validity for Gate Metrics

The plan assumes that improvements in comprehension speed, ordinal error rate, pronunciation consistency and 30-day retention directly indicate Clear English superiority. However, alternative explanations could inflate or deflate observed effects: (a) repeated exposure to ordinals (even in standard form) might improve accuracy without Clear English; (b) learner motivation to participate in a 'new standard' study might boost performance regardless of rule quality; (c) accent proximity to learners' first language might make pronunciation consistency high for both conditions. The plan does not specify control conditions, manipulation checks or confound analyses that rule out these threats. Without explicit construct-validity analysis, the go/no-go decision could rest on noisy or artifactual data.

Recommendation: By Month 5 (2027-03-13), build a construct-validity section into the Outcome Metric Battery Design: (1) identify plausible alternative explanations for each metric (e.g., ordinal accuracy gains due to test familiarity, not Clear English clarity); (2) design explicit control conditions (e.g., standard-English ordinals with explicit rule instruction vs. implicit exposure) to isolate Clear English effects; (3) measure manipulation checks (e.g., ask learners post-test which rule system they learned; confirm mastery of ordinal rules before measuring comprehension); (4) analyze potential confounds (e.g., regress ordinal error rates on learner baseline literacy, first-language phonology, study motivation to isolate Clear English effect). Publish this framework in the pre-analysis plan (Month 11, 2027-09-13). If inter-rater reliability or effect-size analyses at Month 18 (2028-04-13) reveal confounds larger than expected, conduct additional validation by Month 21 (2028-07-13) rather than proceeding to Month 24 (2028-10-13) with questionable data.

Sensitivity: If confounds inflate perceived Clear English effects, a false-positive gate outcome launches a weak standard, reducing Phase 3 adoption by 20–40% and damaging credibility for 3–5 years. A 1-month delay in construct-validity analysis pushes pre-registration to Month 12 (2027-10-13), eliminating the 30-day public-comment window and risking challenges to instrument validity post-hoc. Failure to measure manipulation checks adds 10–15% measurement error, reducing statistical power to detect true effects by ~15–25%.

Issue 4 - Unaddressed Ecosystem Dependencies: Audio Production Bottlenecks and Multi-Accent Pressure

The plan commits to 5,000-word core lexicon with pronunciation guidance, recorded in a single anchor accent by Month 12 (2027-10-13). However, audio production at scale (5,000 entries × multiple takes/ratings = ~7,500–10,000 files) is bottlenecked by studio availability, rater training and inter-rater reliability calibration (target kappa ≥0.75, proposed). The plan does not estimate studio costs, scheduling lead times or contingency for technical failures (inaudible files, corrupted storage). Additionally, the plan acknowledges pressure to add accents (British, American, Australian, Indian) but defers this as 'post-v1.0', creating scope-creep and coalition risk: if standards bodies or ESL organizations demand multi-accent coverage for credibility, the decision to add accents at Month 12–15 (2027-10-13 to 2028-01-13) could inflate audio budget by $50K–$100K (estimated), straining Phase 1 contingency.

Recommendation: By Month 2 (2026-12-13), conduct a detailed audio-production scoping: (1) reserve a studio or recording partner with firm capacity guarantees (lead time, file delivery, backup protocols) for Months 6–11 (2027-04-13 to 2027-09-13); (2) estimate all-in cost per entry (speaker fees, editing, inter-rater scoring) and scale to 5,000 words—if cost exceeds $15–20 per entry (estimate), explore technology-assisted annotation (speech synthesis for baseline, human raters calibrate/correct) to reduce cost; (3) design the inter-rater training and kappa-calibration process (small sample ~100–200 words by Month 9, 2027-07-13, then full production Months 9–11, 2027-07-13 to 2027-09-13); (4) publish a clear, board-approved policy by Month 3 (2027-01-13) that defers accent additions to post-v1.0, with a documented process for considering future requests (prevents scope creep). Identify a contingency provider (secondary studio) by Month 3 (2027-01-13) in case primary partner fails. If, by Month 9 (2027-07-13), costs exceed budget or rater reliability is below target kappa 0.70, pause full production and conduct a 4-week targeted remediation by Month 10 (2027-08-13); if not resolved, flag to editorial board for a potential timeline extension or scope reduction (e.g., record only 3,000–4,000 highest-impact words).

Sensitivity: A 4-week studio delay compresses audio production from 6 months to 5, reducing rater training and inter-rater calibration time by ~17% and increasing kappa-reliability risk (below-target reliability triggers a ~3–6 week remediation). Uncontrolled multi-accent scope creep adds $50K–$100K (1.4–2.9% of Phase 1 budget, straining contingency). A failure to achieve target inter-rater kappa (e.g., kappa 0.65 instead of 0.75) inflates measurement noise by ~20%, reducing statistical power to detect Clear English effects by ~10–15%.

Issue 5 - Incomplete Post-Project Governance and Stewardship Funding Model

The plan extends only to Month 36 (2029-10-13), when external funding and formal project governance end. However, the standard will require ongoing maintenance: responding to adoption feedback, managing version/change requests, updating the lexicon with emerging vocabulary, handling disputes over rule interpretation and conformance. Without a clear stewardship funding model and organizational home, the standard could atrophy within 12–24 months (by Month 48–60, 2030-10-13 to 2031-10-13), as corrections and updates accumulate and no one is funded to address them. Adopter organizations (ESL programs, publishers, technical writers) would lose confidence in the standard's stability and long-term credibility, reducing Phase 3 adoption and damaging the project's legacy.

Recommendation: By Month 24 (2028-10-13), before the Phase 2 go/no-go decision, define a formal post-project governance and funding model: (1) identify 2–3 potential permanent steward organizations (e.g., language education non-profits, a university consortium, international standards bodies like ISO or ASTM) and approach them by Month 27 (2029-01-13) with a stewardship proposal (estimated annual budget: $150K–$250K for staff, meetings, dispute resolution and lexicon updates); (2) establish a permanent Standards Stewardship Committee (separate from the Phase 1–3 editorial board) with clear decision authority (3–5 permanent members, annual election of rotating seats), term lengths (e.g., 3-year staggered terms) and a published decision calendar; (3) publish a 5-year stewardship roadmap by Month 36 (2029-10-13) specifying how and when the standard will be reviewed, how change requests will be prioritized (e.g., safety-critical updates within 3 months, cosmetic updates in annual releases) and how conflicts will be resolved. Secure written commitment letters from at least one steward organization by Month 33 (2029-07-13); if no commitment is obtained, flag the go/no-go outcome as contingent on stewardship funding, preventing a full Phase 3 public release until stewardship is secured.

Sensitivity: Lack of stewardship funding by Month 36 (2029-10-13) could cause the standard to stagnate, with corrections and updates accumulating unbounded. By Month 48–60 (2030-10-13 to 2031-10-13), perceived instability could reduce Phase 3 adoption by 30–50%, capping learner reach at 15,000–35,000 instead of 100,000+. A 6-month delay in identifying a steward (discovery at Month 30, 2029-04-13 instead of Month 24, 2028-10-13) leaves insufficient time to negotiate and fund stewardship before Phase 3 public release, risking a delayed or conditional go/no-go decision. Annual stewardship costs of $150K–$250K (estimate) over 10 years total $1.5M–$2.5M, dwarfing the one-time $3.5M project budget; failure to secure this funding renders v1.0 undefendable as a public standard.

Review conclusion

This $3.5M, 36-month language-standardization initiative is ambitious and well-scoped for a public-interest program, but it rests on four critical missing or underspecified assumptions: (1) Gate Thresholds: Quantitative pass/fail criteria for the four go/no-go metrics must be pre-registered by Month 11 (2027-09-13) to ensure the Month 24 (2028-10-13) decision is defensible and not disputable. Absent thresholds risk false-positive or false-negative gate outcomes, costing $1.2M–$1.4M (Phase 2–3 budget) or damaging credibility long-term. (2) Rule Deadlock Resolution: An explicit Editorial Board Charter with voting rules, tiebreaker mechanisms and conflict-of-interest protocols must be published by Month 1 (2026-11-13) to prevent rules from remaining ambiguous or contradictory during pilots. (3) Construct Validity and Confounds: The gate metrics must be analyzed for alternative explanations (e.g., repeated exposure, learner motivation) via explicit control conditions and manipulation checks, documented in the pre-analysis plan by Month 5 (2027-03-13). Weak construct validity inflates or deflates observed effects, invalidating the gate outcome. (4) Post-Project Stewardship: A funded, committed organizational home for the standard must be identified and committed to by Month 33 (2029-07-13). Without stewardship, the standard will atrophy post-Phase 3, reducing adoption and long-term credibility. Secondary risks include audio-production bottlenecks (7,500–10,000 files require careful scheduling and inter-rater training), pilot recruitment and retention (targeting 50–100 learners per condition with ≤30% dropout), and timeline compression (a 4–6 week Phase 1 slip compresses pilots by 33–50%, weakening evidence). The Pragmatic Foundation path—invariant prefix ordinals, optional pronunciation overlay, ESL-first supplementary wedge, purpose-built validated metrics and even budget spread—substantially mitigates rule ambition and native-reader rejection risks. However, active management of gate credibility, rule governance, measurement validity and post-launch stewardship is essential from Month 1 (2026-11-13) onward to ensure the initiative delivers on its adoption and evidence-gating promise.

Governance Audit

Audit - Corruption Risks

Audit - Misallocation Risks

Audit - Procedures

Audit - Transparency Measures

Internal Governance Bodies

1. Project Steering Committee

Rationale for Inclusion: The Clear English program is a 36-month, $3.5M initiative spanning rule specification, pilot design, gate metrics, recruitment and public release across multiple stakeholder groups (educators, publishers, regulators, learners). Strategic decisions on ordinal architecture, G2P depth, adoption wedge, outcome metrics and phase budget allocation directly shape evidence credibility and adoption likelihood. The Steering Committee provides high-level oversight of these critical strategic levers, monitors phase-gate readiness, arbitrates resource conflicts across phases, and ensures alignment with the adoption-first, evidence-gated mandate and no-mandate, no-K12-replacement constraints.

Responsibilities:

Initial Setup Actions:

Membership:

Decision Rights: Strategic decisions with financial impact >$50K (equipment, vendor contracts, Phase-wide re-scoping, reserve draws up to $175K pre-gate limit); authorization of phase-gate transitions and go/no-go timing adjustments; approval of escalation paths to external arbiter for rule deadlock. Decisions delegated to the Editorial Board: ordinal marker pronunciation specifics, morphology retention-threshold tuning, homograph-pair list prioritization, individual rule rationale. Budget authority: Steering Committee approves spending within Phase allocations; requests exceeding phase budget or drawing >$50K from reserve require Steering Committee vote.

Decision Mechanism: Steering Committee quorum: 5 of 7 members. Standard decision rule: consensus or simple majority (>50%) with brief documented rationale. Tie-breaker: Project Lead holds a tie-breaking vote. Escalation: if Steering Committee cannot reach consensus on a strategic lever (e.g., adoption wedge sequencing, gate-threshold stringency), the matter is escalated to a neutral External Arbiter (appointed by Month 5 = 2027-03-13, TBD per Editorial Board Charter) for binding recommendation to the Committee within 2 weeks.

Meeting Cadence: Monthly standing meetings (first Tuesday of each month, 2 hours); additional checkpoint meetings at Months 11 (2027-09-13), 18 (2028-04-13), 23 (2028-09-13) (90 minutes each) for gate readiness reviews. Ad-hoc emergency meetings called by the Project Lead if any critical-path item slips >2 weeks or a budget variance >$50K is discovered.

Typical Agenda Items:

Escalation Path: Unresolved strategic disputes (e.g., rule deadlock, adoption-wedge timing, reserve-draw disputes) are escalated to a neutral External Arbiter appointed jointly by the Steering Committee and Editorial Board by Month 5 (2027-03-13). The arbiter's recommendation is binding unless both the Steering Committee and Editorial Board formally object within 5 business days. If both reject the arbiter's recommendation, the matter escalates to the program's Funding Authority (granting body or institutional sponsor) for final decision. Post-Month-36 stewardship funding gaps trigger escalation to a designated Steward-Search Lead appointed by Month 24 (2028-10-13).

2. Editorial Board and Linguistic Review Panel

Rationale for Inclusion: Clear English rules must be specific, defensible, and internally consistent to serve as a credible reference for pilots, third-party adopters and educators. The Editorial Board is responsible for finalizing ordinal marker pronunciation, morphology retention thresholds, homograph-disambiguation policy, core-lexicon selection basis, and rule exceptions. The Board also logs all decisions with explicit rationale, resolves internal conflicts over linguistic priorities (consistency vs. usability), and manages the draft-standard 30-day public comment window. A Linguistic Review Panel (embedded within the Board) provides formal review-and-veto authority on rule ambiguities and contradictions, protecting against drift or oversimplification that would compromise the standard's reference value. This separation of editorial authority from strategic steering ensures that rule quality is not subordinated to adoption or budget pressures.

Responsibilities:

Initial Setup Actions:

Membership:

Decision Rights: Full decision authority over all rule specifications, thresholds and exceptions; all rule decisions are final once the Decision Log entry is signed by the Chair and published. The Linguistic Review Panel may veto a rule only if it finds the rule to be internally contradictory, logically circular, or lacking a publishable justification; such vetoes are documented in the Decision Log and escalated to the full board for revision or dispute resolution. The board may not override the Steering Committee's strategic-lever decisions (e.g., the choice of prefix ordinals, optional pronunciation overlay, ESL-first wedge) but may propose refinements or implementation guidance to the Steering Committee if rule-specification work reveals unforeseen conflicts. The board controls the draft-standard comment window process and may integrate substantive public feedback into rule clarification, but core rules cannot be reopened except post-v1.0 via formal Change-Control procedures.

Decision Mechanism: Simple majority voting (>50% of present members); quorum: 5 of 7–9 members. Consensus is sought as the default, but if consensus cannot be reached, a majority vote decides. Linguistic Review Panel veto on ambiguity/contradiction is binding unless the full board overrides it by supermajority (2/3 of present members). If a supermajority override is invoked, the dissenting linguist opinions are documented in the Decision Log and published with the final rule. Tie-breaker: the Board Chair casts the tie-breaking vote if voting is deadlocked; if the Chair is conflicted, an external Arbiter is called to cast the tie-breaker within 2 weeks.

Meeting Cadence: Monthly full Editorial Board meetings (second Thursday of each month, 2 hours); Linguistic Review Panel subcommittee meetings monthly (fourth Thursday, 90 minutes) during Months 5–11 (2027-03-13 to 2027-09-13); additional subcommittee workstreams (ordinal, morphology, homograph, lexicon) meet biweekly (1.5 hours) Months 2–10 (2026-12-13 to 2027-08-13) to draft and refine rules. Emergency Board meetings convened by the Chair if an escalated dispute or public comment requires urgent resolution.

Typical Agenda Items:

Escalation Path: Unresolved rule disputes between practitioners and linguists are escalated to the external Arbiter within 5 business days of a failed board vote; the Arbiter has 2 weeks to make a binding recommendation on how to resolve the conflict (e.g., adopt a minority rule position, refine the rule to address both perspectives, defer the decision to pilot evidence). If the Arbiter's recommendation is rejected by both the Steering Committee and Editorial Board, the matter escalates to the Funding Authority. Disputes over whether a rule is ambiguous/contradictory (triggering Linguistic Review veto) are escalated to the Arbiter if the full board cannot resolve the veto by supermajority override within 2 weeks. Substantive public comments during the Month 11–12 (2027-09-13 to 2027-10-13) comment window that challenge rule validity are triaged by the Editorial Board; if unresolved, a representative comment is escalated to the Arbiter for a recommendation on whether the rule should be revised before v1.0 finalization.

3. Metrics & Validation Committee

Rationale for Inclusion: The Month 24 (2028-10-13) go/no-go gate depends entirely on the credibility of four pre-registered, psychometrically sound outcome metrics (ordinal error rate, comprehension speed, pronunciation consistency, 30-day retention). Any weakness in instrument design, inter-rater reliability, construct validity, confound control or data integrity directly undermines the gate decision and risks a false-positive (weak standard launched, damaging long-term credibility) or false-negative (viable standard rejected, stranding Phase 3 and damaging adoption). The Metrics & Validation Committee ensures that instruments are purpose-built and independently validated, that validity assumptions are tested, that measurement procedures are faithfully executed across pilots, and that any validity threats are identified early (Months 18–21 = 2028-04-13 to 2028-07-13) so remediation is possible before Month 24 (2028-10-13). This committee operates at arm's length from the Editorial Board and Steering Committee to maintain measurement impartiality.

Responsibilities:

Initial Setup Actions:

Membership:

Decision Rights: Full authority over instrument design, validity analysis, data-quality standards and the pre-analysis plan; authority to halt or suspend pilots if data integrity is compromised or inter-rater reliability falls below the 0.70 floor for more than 2 weeks. May recommend changes to pilot protocol (e.g., additional rater training, modified assessment schedule, extended follow-up) to the Steering Committee; the Committee's recommendation is binding on pilot operations. May request extension of Phase 1 by up to 4 weeks (at ~$85K cost, estimate) if the validity study or inter-rater calibration requires additional time; Steering Committee must approve extensions >2 weeks. The Committee cannot override Editorial Board rule decisions but may flag to the Steering Committee if rule changes during Phase 2 pilots would invalidate previously calibrated instruments.

Decision Mechanism: Consensus on technical validity matters (instrument design, confound-control procedures, thresholds, analysis plan). If consensus cannot be reached, the Psychometrician (Chair) makes the final decision with documented rationale. Disagreements between the Psychometrician and external specialist are escalated to the Steering Committee if they affect go/no-go credibility (e.g., conflicting views on minimum sample size, effect-size interpretation). Data-integrity violations or inter-rater reliability below 0.70 trigger an automatic flag to the Steering Committee within 48 hours; remediation steps are determined by consensus of the Committee or, if urgent, by the Psychometrician in consultation with the Steering Committee.

Meeting Cadence: Bi-weekly standing meetings (Mondays, 90 minutes) from Month 2 (2026-12-13) through Month 24 (2028-10-13). Additional meetings at Months 10–11 (2027-08-13 to 2027-09-13) (weekly, for validity-study completion) and Months 18–24 (2028-04-13 to 2028-10-13) (weekly, for pilot monitoring and midpoint analysis). Emergency meetings convened within 48 hours if data-integrity issues or inter-rater reliability drops are discovered.

Typical Agenda Items:

Escalation Path: Data-integrity violations (missing recordings, unauthorized access, consent breaches) escalate immediately (within 48 hours) to the Steering Committee and the internal Data Integrity Officer; serious breaches (e.g., data loss) trigger suspension of affected pilot arms and immediate notification to IRB/ethics board. Inter-rater reliability below 0.70 for more than 2 weeks escalates to the Steering Committee with a remediation plan (rater retraining, extended inter-rater calibration, or Phase 1 extension); if remediation is not effective by Month 21 (2028-07-13), the Committee recommends to the Steering Committee whether to proceed to gate decision with degraded measurement or extend Phase 2. Construct-validity threats (e.g., evidence that a confound is larger than expected, inflating apparent Clear English effects) escalate to the Steering Committee with a recommendation for additional analysis or a supplementary validity study (costing up to $50K, estimate) by Month 21 (2028-07-13).

4. Compliance & Risk Management Committee

Rationale for Inclusion: The Clear English program spans 36 months, operates across multiple jurisdictions (UK, US, possibly EU), manages sensitive biometric data (pronunciation audio), engages vulnerable populations (adult ESL learners), pilots safety-critical documentation, and carries reputational and legal exposure if incidents or violations occur. Key risks include data-privacy breaches (GDPR, US state law violations), ethics-approval delays (2–8 weeks, estimated), safety-critical liability (injury linked to Clear English documentation), educator and standards-body pushback, financial overruns exceeding the $175K pre-gate reserve cap, and fragmentation/unofficial variants post-release. The Compliance & Risk Management Committee provides active, continuous monitoring and mitigation of these risks; escalates emerging threats to the Steering Committee; ensures legal, ethical and regulatory alignment; and maintains a current risk register with ownership and action plans. This committee operates independently from rule development and measurement to maintain impartiality on governance and risk issues.

Responsibilities:

Initial Setup Actions:

Membership:

Decision Rights: Authority to recommend (but not unilaterally impose) changes to pilot protocol, budget allocation or timeline to mitigate identified risks; recommendations are binding on operations if approved by the Steering Committee. Authority to halt or suspend pilots (in coordination with Steering Committee and Metrics & Validation Committee) if data-privacy breaches, ethics violations or safety-critical incidents occur. Authority to recommend spending from the $175K pre-gate contingency reserve (in coordination with Steering Committee) for legal, ethics, insurance or urgent risk-mitigation costs. Authority to veto or modify any pilot operation that violates IRB approval, data-protection compliance, or safety-critical risk boundaries. Does not control rule specifications (Editorial Board authority) or measurement procedures (Metrics & Validation Committee authority) but may flag to those committees if compliance issues arise from rule or measurement design.

Decision Mechanism: Consensus on risk assessment and mitigation ownership; if consensus cannot be reached on risk severity or mitigation strategy, the Committee Chair makes the final call with documented rationale. Escalation to the Steering Committee is automatic if a risk is rated 'High' likelihood × 'High' severity, or if mitigation is inadequate or delayed. Emergency decisions (e.g., suspension of a pilot site due to ethics violation) can be made by the Committee Chair in consultation with the Steering Committee within 48 hours.

Meeting Cadence: Monthly standing meetings (third Wednesday, 90 minutes) from Month 1 (2026-11-13) through Month 36 (2029-10-13). Quarterly risk reviews (Months 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36 = 2027-01-13 onwards, 120 minutes) with the Steering Committee to present updated Risk Register and escalation summary. Emergency meetings convened within 48 hours if a 'High' risk event occurs (data breach, ethics violation, safety incident, budget overrun exceeding $125K).

Typical Agenda Items:

Escalation Path: All 'High' likelihood × 'High' severity risks escalate to the Steering Committee within 5 business days of identification or status change, with a documented mitigation plan and timeline. Data-privacy breaches or ethics violations escalate immediately (within 48 hours) to the Steering Committee, IRB/ethics board (if required) and relevant data-protection authorities (e.g., ICO in UK, state regulators in US). Safety-critical incidents linked to Clear English documentation escalate immediately to legal counsel, the Steering Committee, relevant workplace safety regulators (OSHA, HSE) and affected pilot organizations; trigger a formal incident investigation and communication plan. Budget overruns exceeding $125K (half the $250K contingency cap) escalate to the Steering Committee with a scope-adjustment or timeline-extension recommendation. Educator or standards-body pushback signals that could reduce pilot enrollment by >20% or delay regulatory approval by >4 weeks escalate to the Steering Committee with a corrective communication and engagement plan.

Governance Implementation Plan

1. Project Lead and Funding Authority jointly identify and appoint the Project Sponsor (external funding body representative or senior institutional leader) and define their role in governance escalation and reserve-draw authorization.

Responsible Body/Role: Funding Authority / Institutional Sponsor

Suggested Timeframe: Month 0 (2026-10-13) (Project start, within 1 week of kickoff)

Key Outputs/Deliverables:

Dependencies:

2. Project Lead drafts the Project Steering Committee Charter, specifying membership roles, voting rules (simple majority with tie-breaker), escalation procedures for rule deadlock and budget disputes, meeting cadence, and decision thresholds (e.g., >$50K spending decisions, reserve draws, phase-gate authority).

Responsible Body/Role: Project Lead

Suggested Timeframe: Month 0 (2026-10-13) (end of Month 0 = 2026-10-13, by 2026-10-13)

Key Outputs/Deliverables:

Dependencies:

3. Project Lead circulates the draft Steering Committee Charter to the nominated Steering Committee members (project lead, finance lead, editorial board chair, external academic partner, psychometrician role, ESL publisher advisor, standards-body advisor) for review and feedback; incorporates comments and finalizes.

Responsible Body/Role: Project Lead

Suggested Timeframe: Month 0.5 (2026-10-28) (within 2 weeks of draft completion)

Key Outputs/Deliverables:

Dependencies:

4. Project Lead formally publishes the Steering Committee Charter and formally appoints the Steering Committee Chair (typically the Project Lead or an external governance advisor); all 7 members confirm acceptance in writing.

Responsible Body/Role: Project Lead with Project Sponsor authorization

Suggested Timeframe: Month 1 (2026-11-13) (by 2026-11-13)

Key Outputs/Deliverables:

Dependencies:

5. Project Lead drafts the Editorial Board Charter, specifying practitioner-leaning composition (4-5 practitioners: ESL instructors, technical writers, safety trainers; 2-3 linguists; 1 optional learner rep), voting rules, conflict-of-interest disclosure, decision-logging protocol, Linguistic Review Panel authority and veto scope (limited to ambiguity/contradiction findings), and tiebreaker mechanism.

Responsible Body/Role: Project Lead

Suggested Timeframe: Month 0 (2026-10-13) (by end of Week 1)

Key Outputs/Deliverables:

Dependencies:

6. Project Lead recruits and confirms Editorial Board membership: 4-5 practitioners (ESL instructors, technical writers, safety trainers), 2-3 linguists (applied linguistics, morphology/phonology specialists with standards-development experience), and optionally 1 learner representative; all members sign conflict-of-interest attestations.

Responsible Body/Role: Project Lead

Suggested Timeframe: Month 0.5 (2026-10-28) to Month 1 (2026-11-13) (recruitment complete by 2026-11-13)

Key Outputs/Deliverables:

Dependencies:

7. Project Lead formally publishes the Editorial Board Charter and announces the confirmed board membership; all members sign the charter in acknowledgment.

Responsible Body/Role: Project Lead

Suggested Timeframe: Month 1 (2026-11-13) (by 2026-11-13)

Key Outputs/Deliverables:

Dependencies:

8. Project Lead identifies and recruits an external Arbiter (neutral linguist or standards-design specialist with no financial stake in ESL publishing or standards bodies) to serve as tiebreaker for rule deadlocks and strategic disputes; document agreed fee ($10K-$20K estimate), availability for 2-week turnaround on escalations, and contact/escalation protocol.

Responsible Body/Role: Project Lead

Suggested Timeframe: Months 2-5 (2026-12-13 to 2027-03-13) (by 2027-03-13)

Key Outputs/Deliverables:

Dependencies:

9. Project Lead schedules and holds the first Editorial Board meeting to surface rule-specification tensions and assign workstreams (ordinal, morphology, homograph, lexicon, pronunciation-guidance logic) to subcommittees; set internal deadlines for rule drafts (Month 6 = 2027-04-13).

Responsible Body/Role: Editorial Board Chair (Project Lead or designated chair)

Suggested Timeframe: Month 2 (2026-12-13) (by 2026-12-13)

Key Outputs/Deliverables:

Dependencies:

10. Project Lead hires an independent psychometrician (external or internal dedicated role, 0.5-1.0 FTE) to lead instrument design, validity analysis and inter-rater reliability work; allocate $150K-$200K (estimate) budget; establish role reporting to Project Lead and the Metrics & Validation Committee (to be formed).

Responsible Body/Role: Project Lead with Finance Lead approval

Suggested Timeframe: Month 2 (2026-12-13) (by 2026-12-13)

Key Outputs/Deliverables:

Dependencies:

11. Psychometrician (with Project Lead support) conducts a detailed construct-validity literature review and expert-panel discussion (involving external applied-linguistics and measurement specialists) to identify plausible confounds (repeated exposure, learner motivation, accent proximity, baseline literacy) and design explicit control conditions and manipulation checks to isolate Clear English effects.

Responsible Body/Role: Psychometrician (newly hired), with external measurement specialist advising

Suggested Timeframe: Month 4 (2027-02-13) (by 2027-02-13)

Key Outputs/Deliverables:

Dependencies:

12. Psychometrician drafts the pre-analysis plan specifying: (1) quantitative pass/fail thresholds for the four gate metrics (ordinal error ≥25% reduction, comprehension speed ≤10% slower, pronunciation consistency ≥15% above control, 30-day retention ≥70%); (2) minimum sample sizes (n≥80 per arm for 80% power at α=0.05); (3) primary and secondary outcomes; (4) intention-to-treat vs. completer-case rules; (5) control conditions and manipulation checks; (6) inter-rater reliability targets (kappa ≥0.75 target, 0.70 floor); (7) data-quality and missing-data protocols.

Responsible Body/Role: Psychometrician

Suggested Timeframe: Months 4-5 (2027-02-13 to 2027-03-13) (draft complete by 2027-03-13)

Key Outputs/Deliverables:

Dependencies:

13. Psychometrician circulates the pre-analysis plan draft for external peer review (to external measurement specialists, applied-linguistics researchers, and a representative from the Steering Committee); collects feedback and revises.

Responsible Body/Role: Psychometrician with external review committee

Suggested Timeframe: Month 5 (2027-03-13) (feedback deadline Month 5 = 2027-03-13, revision complete by Month 5.5 = 2027-03-28)

Key Outputs/Deliverables:

Dependencies:

14. Project Lead drafts the Metrics & Validation Committee Charter, specifying the Committee's independence from Editorial Board and Steering Committee, decision authority over instrument design and data-quality standards, authority to recommend (and escalate if needed) changes to pilot protocol, data-integrity standards, and escalation procedures (data-privacy breaches, kappa below 0.70, validity threats escalate to Steering Committee within 48 hours).

Responsible Body/Role: Project Lead

Suggested Timeframe: Month 2 (2026-12-13) (by 2026-12-13)

Key Outputs/Deliverables:

Dependencies:

15. Project Lead formally appoints the Metrics & Validation Committee: Psychometrician (Chair), 1-2 external applied-linguistics or measurement specialists (e.g., university faculty with ESL assessment publications), and a data-integrity/research-compliance officer (internal); publish the Committee Charter with all members' signed acknowledgment.

Responsible Body/Role: Project Lead

Suggested Timeframe: Month 3 (2027-01-13) (by 2027-01-13)

Key Outputs/Deliverables:

Dependencies:

16. Psychometrician designs and conducts the validity-study protocol: recruit N=20-30 adult ESL learners; expose them to both Clear English and standard-English ordinal conditions (within-subject or between-subject design); administer assessment instruments; collect pronunciation audio if applicable; run preliminary analyses (effect sizes, inter-rater kappa, construct-validity checks); document findings.

Responsible Body/Role: Psychometrician with Metrics & Validation Committee oversight

Suggested Timeframe: Months 9-10 (2027-07-13 to 2027-08-13)

Key Outputs/Deliverables:

Dependencies:

17. Psychometrician incorporates validity-study findings into the final pre-analysis plan; finalize thresholds, sample sizes, and analysis procedures; submit the complete pre-analysis plan to an external pre-registration repository (e.g., Open Science Framework, OSF) by Month 11 (2027-09-13).

Responsible Body/Role: Psychometrician

Suggested Timeframe: Month 10-11 (2027-08-13 to 2027-09-13) (pre-registration complete by 2027-09-13)

Key Outputs/Deliverables:

Dependencies:

18. Project Lead drafts the Compliance & Risk Management Committee Charter, specifying the Committee's authority to recommend changes to pilot protocol to mitigate identified risks, to escalate high-severity risks to the Steering Committee within 5 business days, and to halt pilots if data-privacy breaches or ethics violations occur.

Responsible Body/Role: Project Lead

Suggested Timeframe: Month 1 (2026-11-13) (by 2026-11-13)

Key Outputs/Deliverables:

Dependencies:

19. Project Lead recruits Compliance & Risk Management Committee members: risk-management specialist (Chair, 0.5 FTE), external legal counsel (product liability and regulatory compliance, ~4 hours/month retainer), ethics/IRB liaison (internal or academic partner, ~3-4 hours/month), stakeholder-engagement/communications lead (internal, 0.5 FTE), and finance/budget lead liaison (internal, ~2 hours/month).

Responsible Body/Role: Project Lead

Suggested Timeframe: Month 1-2 (2026-11-13 to 2026-12-13)

Key Outputs/Deliverables:

Dependencies:

20. Project Lead formally appoints the Compliance & Risk Management Committee with published Charter; all members sign acknowledgment.

Responsible Body/Role: Project Lead

Suggested Timeframe: Month 1 (2026-11-13) (by 2026-11-13)

Key Outputs/Deliverables:

Dependencies:

21. Project Lead engages external legal counsel (product-liability and regulatory-compliance specialist) to advise on liability, insurance, disclaimer language for safety-critical materials, and regulatory approval pathways for safety-critical pilots; retain by signed engagement letter by Month 2 (2026-12-13).

Responsible Body/Role: Project Lead with Compliance & Risk Management Committee guidance

Suggested Timeframe: Month 2 (2026-12-13) (by 2026-12-13)

Key Outputs/Deliverables:

Dependencies:

22. Compliance & Risk Management Committee develops a comprehensive Risk Register template categorizing risks by domain (regulatory/standards adoption, pilot recruitment/retention, assessment validity, rule ambiguity, safety-critical liability, budget/timeline, educator pushback, fragmentation, data privacy, stewardship funding); list 20 identified risks from assumptions document plus space for emerging risks; specify likelihood, severity, mitigation status, owners and escalation thresholds.

Responsible Body/Role: Compliance & Risk Management Committee Chair with Committee members

Suggested Timeframe: Month 2 (2026-12-13) (by 2026-12-13)

Key Outputs/Deliverables:

Dependencies:

23. Compliance & Risk Management Committee holds first meeting to populate the Risk Register, assign mitigation owners, confirm timelines and escalation procedures, and establish quarterly risk-review schedule (Months 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36 = 2027-01-13 onwards).

Responsible Body/Role: Compliance & Risk Management Committee

Suggested Timeframe: Month 1 (2026-11-13) (by 2026-11-13)

Key Outputs/Deliverables:

Dependencies:

24. Project Lead engages ethics review board or Institutional Review Board (IRB) to clarify whether the pilot qualifies as research requiring formal review; submit initial consultation request by Month 1 (2026-11-13).

Responsible Body/Role: Compliance & Risk Management Committee (ethics liaison) with Project Lead

Suggested Timeframe: Months 1-2 (2026-11-13 to 2026-12-13)

Key Outputs/Deliverables:

Dependencies:

25. Compliance & Risk Management Committee drafts a formal IRB protocol (including study design, informed-consent forms, data-handling procedures, audio-recording consent with options for data deletion, privacy safeguards, confidentiality measures) and submits to IRB for review by Month 3 (2027-01-13), targeting approval by Month 6 (2027-04-13).

Responsible Body/Role: Compliance & Risk Management Committee (ethics liaison) with Psychometrician input

Suggested Timeframe: Months 2-3 (2026-12-13 to 2027-01-13) (draft complete by 2027-01-13, submitted to IRB)

Key Outputs/Deliverables:

Dependencies:

26. Compliance & Risk Management Committee secures encrypted audio-storage infrastructure with access controls, backup and disaster-recovery protocols; conduct vendor selection and sign contract by Month 6 (2027-04-13); set up storage systems and test backup procedures by Month 6 (2027-04-13).

Responsible Body/Role: Compliance & Risk Management Committee (data-integrity officer) with IT/project support

Suggested Timeframe: Months 4-6 (2027-02-13 to 2027-04-13)

Key Outputs/Deliverables:

Dependencies:

27. Compliance & Risk Management Committee conducts a data-protection audit (GDPR compliance, US state privacy law requirements, data-retention schedules, participant access rights) and publishes a privacy policy and data-retention schedule on the project website by Month 12 (2027-10-13); document findings and any compliance gaps.

Responsible Body/Role: Compliance & Risk Management Committee (ethics liaison, legal counsel)

Suggested Timeframe: Months 8-12 (2027-06-13 to 2027-10-13)

Key Outputs/Deliverables:

Dependencies:

28. Project Lead (with Steering Committee and Editorial Board input) confirms the five critical strategic-lever choices documented in the Pragmatic Foundation scenario: (1) Ordinal Marker Architecture—numeric prefix marker, legacy forms coexist; (2) Grapheme-to-Phoneme Depth—optional overlay, no respelling; (3) Adoption Wedge—ESL-first supplementary; (4) Outcome Metric Battery—purpose-built, independently validated; (5) Phase Budget—even spread ($1.1M/$1.2M/$0.85M). Publish with written rationale and trade-off documentation.

Responsible Body/Role: Project Lead with Steering Committee and Editorial Board review

Suggested Timeframe: Month 2 (2026-12-13) (by 2026-12-13)

Key Outputs/Deliverables:

Dependencies:

29. Project Lead establishes a Critical Path Dashboard tracking phase milestones (rules finalization, audio completion, recruitment enrollment, pre-registration, pilot midpoint, analysis), resource allocation by phase and budget line, and go/no-go gate conditions (pre-registration thresholds locked, pilot enrollment ≥80 per arm, 30-day follow-up completion ≥70%, inter-rater kappa ≥0.70, validity audit findings clean); review monthly and escalate slips >2 weeks to Steering Committee.

Responsible Body/Role: Project Lead with Finance Lead

Suggested Timeframe: Month 1 (2026-11-13) (by 2026-11-13)

Key Outputs/Deliverables:

Dependencies:

30. Project Lead schedules phase-gate checkpoint meetings with Steering Committee: (1) Month 11 (2027-09-13) pre-registration review and rules-finalization readiness; (2) Month 18 (2028-04-13) midpoint check on pilot enrollment, retention, and preliminary data quality; (3) Month 23 (2028-09-13) validity audit review and go/no-go readiness; (4) Month 24 (2028-10-13) go/no-go decision meeting.

Responsible Body/Role: Project Lead / Steering Committee Chair

Suggested Timeframe: Month 1 (2026-11-13) (by 2026-11-13)

Key Outputs/Deliverables:

Dependencies:

31. Project Lead identifies 3-4 adult ESL programs and 2-3 technical/safety-training organizations as pilot partners; initiate outreach with brief overview of the Clear English program, pilot participation expectations (enrollment, in-person assessments, 30-day follow-up), and proposed partnership terms (per-learner payment, incentive structure, educator training, feedback loop).

Responsible Body/Role: Project Lead with Stakeholder Engagement Lead (Compliance & Risk Management Committee)

Suggested Timeframe: Month 1-2 (2026-11-13 to 2026-12-13)

Key Outputs/Deliverables:

Dependencies:

32. Project Lead and Stakeholder Engagement Lead co-design pilot protocols with representatives from each partner organization (assessment schedule, classroom integration, learner-communication plan, data-sharing agreements); ensure protocols address partner capacity and learner-retention incentives; finalize by Month 3 (2027-01-13).

Responsible Body/Role: Project Lead with Stakeholder Engagement Lead and partner representatives

Suggested Timeframe: Months 2-3 (2026-12-13 to 2027-01-13)

Key Outputs/Deliverables:

Dependencies:

33. Project Lead secures signed pilot-partnership commitments from at least 3 adult ESL programs and 2 technical/safety-training organizations, including written enrollment guarantees (≥115 per organization estimate, total ≥460 across 4 arms), contact-hour payment terms, educator training commitment, and data-sharing agreement; all signed by Month 3 (2027-01-13).

Responsible Body/Role: Project Lead with Compliance & Risk Management Committee (contract review)

Suggested Timeframe: Months 2-3 (2026-12-13 to 2027-01-13)

Key Outputs/Deliverables:

Dependencies:

34. Project Lead recruits a dedicated Phase 2 cohort manager (1.0 FTE, ~$60K-$80K/year estimate) to oversee pilot enrollment, retention, scheduling, data collection, participant incentive distribution, 30-day follow-up contact, and dropout documentation; hire by Month 6 (2027-04-13) to begin recruitment preparation.

Responsible Body/Role: Project Lead with Finance Lead approval

Suggested Timeframe: Months 4-6 (2027-02-13 to 2027-04-13)

Key Outputs/Deliverables:

Dependencies:

35. Project Lead and Stakeholder Engagement Lead develop and deliver educator training on Clear English rules, rationale, pilot administration, and learner communication; training delivered to all pilot site educators (2-3 sessions, in-person or virtual) by Month 10 (2027-08-13); offer continuing education credits or stipends ($20K-$40K estimate) to incentivize participation.

Responsible Body/Role: Stakeholder Engagement Lead with Editorial Board input on rule explanation

Suggested Timeframe: Months 8-10 (2027-06-13 to 2027-08-13)

Key Outputs/Deliverables:

Dependencies:

36. Project Lead and Stakeholder Engagement Lead engage ESL teacher professional organizations (TESOL, IATEFL, national equivalents) as advisory partners by Month 2 (2026-12-13), with monthly or quarterly contact to discuss pilot findings, educator concerns, and adoption barriers; track engagement metrics (meeting attendance, feedback quality) monthly.

Responsible Body/Role: Stakeholder Engagement Lead

Suggested Timeframe: Month 2 onwards (2026-12-13 through Month 36 = 2029-10-13)

Key Outputs/Deliverables:

Dependencies:

37. Project Lead and Stakeholder Engagement Lead conduct stakeholder-expectation interviews and focus groups (Months 1-3 = 2026-11-13 to 2027-01-13) with educators, regulators, ESL publishers, and learners to understand their success criteria and concerns; document findings in a Stakeholder Alignment Charter published by Month 6 (2027-04-13).

Responsible Body/Role: Stakeholder Engagement Lead with Project Lead

Suggested Timeframe: Months 1-6 (2026-11-13 to 2027-04-13)

Key Outputs/Deliverables:

Dependencies:

38. Project Lead and Stakeholder Engagement Lead build stakeholder advisory panels (separate from Editorial Board and Steering Committee) for educators, regulators, and publishers, meeting quarterly (Months 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36 = 2027-01-13 onwards) to surface emerging concerns and expectations; generate quarterly advisory-panel meeting summaries.

Responsible Body/Role: Stakeholder Engagement Lead

Suggested Timeframe: Month 2 (2026-12-13) onwards (panels established by 2026-12-13, first meeting Month 3 = 2027-01-13)

Key Outputs/Deliverables:

Dependencies:

39. Project Lead and Stakeholder Engagement Lead conduct a mid-phase stakeholder check-in at Month 18 (2028-04-13) to assess alignment with project expectations and to adjust Phase 2 or Phase 3 strategy if major gaps are identified; publish a brief mid-phase alignment update.

Responsible Body/Role: Stakeholder Engagement Lead with Project Lead and Steering Committee

Suggested Timeframe: Month 18 (2028-04-13)

Key Outputs/Deliverables:

Dependencies:

40. Project Lead confirms the single reference accent choice for pronunciation guidance (e.g., General American, Received Pronunciation, or shared-contrast phonemes across accents) with explicit written justification by Month 3 (2027-01-13); document how other major accents (British, American, Australian, Indian) map to the anchor.

Responsible Body/Role: Project Lead with Psychometrician and Editorial Board (linguist members) input

Suggested Timeframe: Month 3 (2027-01-13) (by 2027-01-13)

Key Outputs/Deliverables:

Dependencies:

41. Project Lead and Finance Lead implement monthly financial tracking and rolling 6-month cash-flow forecasting from Month 1 (2026-11-13) onwards; track actual spending by Phase and budget line against allocations; flag variances >$50K or timeline slips >2 weeks for Steering Committee review.

Responsible Body/Role: Finance Lead with Project Lead

Suggested Timeframe: Month 1 onwards (2026-11-13 through Month 36 = 2029-10-13)

Key Outputs/Deliverables:

Dependencies:

42. Project Lead and Finance Lead conduct a formal spending review at Month 9 (2027-07-13) to assess Phase 1 expenses against budget and to adjust Phase 2 allocations if needed; Steering Committee reviews findings and approves any reallocation or contingency draws.

Responsible Body/Role: Finance Lead with Project Lead and Steering Committee

Suggested Timeframe: Month 9 (2027-07-13)

Key Outputs/Deliverables:

Dependencies:

43. Project Lead negotiates fixed-rate contracts with curriculum vendors and audio studios by Month 3 (2027-01-13) to lock recording and design costs; specify deliverables, timeline, quality standards and penalties for delays.

Responsible Body/Role: Project Lead with Finance Lead

Suggested Timeframe: Months 1-3 (2026-11-13 to 2027-01-13)

Key Outputs/Deliverables:

Dependencies:

44. Project Lead identifies a contingency audio studio or recording partner as a backup by Month 3 (2027-01-13) in case the primary vendor encounters delays or quality issues; document backup contact and standby agreement.

Responsible Body/Role: Project Lead

Suggested Timeframe: Month 3 (2027-01-13) (by 2027-01-13)

Key Outputs/Deliverables:

Dependencies:

45. Editorial Board (ordinal workstream subcommittee) finalizes the ordinal-marker pronunciation specification (symbol, spoken reading, conversion rules from legacy 1st/2nd/3rd forms) and documents with explicit rationale by Month 10 (2027-08-13); Linguistic Review Panel vets for ambiguity.

Responsible Body/Role: Editorial Board (ordinal subcommittee) with Linguistic Review Panel oversight

Suggested Timeframe: Months 6-10 (2027-04-13 to 2027-08-13)

Key Outputs/Deliverables:

Dependencies:

46. Editorial Board (morphology workstream subcommittee) finalizes the irregular-morphology retention threshold, specifying which irregular verbs and plurals are retained (e.g., high-frequency forms like go/went) and which are regularized (lower-frequency or high-learning-friction forms); document rationale and published list of ~25% of irregulars regularized by Month 10 (2027-08-13).

Responsible Body/Role: Editorial Board (morphology subcommittee) with Linguistic Review Panel oversight

Suggested Timeframe: Months 6-10 (2027-04-13 to 2027-08-13)

Key Outputs/Deliverables:

Dependencies:

47. Editorial Board (homograph workstream subcommittee) finalizes the homograph-disambiguation policy, specifying the published list of ≤50 high-impact homograph/homophone pairs (e.g., lead/lead, read/read) and whether each requires a marker (mandatory in safety-critical docs), optional elsewhere, or a rewrite rule; document enforcement policy by Month 10 (2027-08-13).

Responsible Body/Role: Editorial Board (homograph subcommittee) with Linguistic Review Panel oversight

Suggested Timeframe: Months 6-10 (2027-04-13 to 2027-08-13)

Key Outputs/Deliverables:

Dependencies:

48. Editorial Board (lexicon workstream subcommittee) finalizes the core-lexicon selection basis (frequency-led general words + technical/safety reserve block), completes the 5,000-word list with pronunciations mapped and selection rationale documented by Month 10 (2027-08-13); audit coverage of pilot running text (target ≥85% coverage).

Responsible Body/Role: Editorial Board (lexicon subcommittee) with Psychometrician consultation

Suggested Timeframe: Months 4-10 (2027-02-13 to 2027-08-13)

Key Outputs/Deliverables:

Dependencies:

49. Editorial Board conducts the first formal Editorial Board meeting (Month 2 = 2026-12-13) and subsequent monthly or biweekly subcommittee meetings (ordinal, morphology, homograph, lexicon, pronunciation-guidance logic) during Months 2-10 (2026-12-13 to 2027-08-13) to draft and refine rules; resolve conflicts using the Board's decision mechanism (simple majority, with linguist veto on ambiguity, escalation to external arbiter if needed).

Responsible Body/Role: Editorial Board with Linguistic Review Panel

Suggested Timeframe: Months 2-10 (2026-12-13 to 2027-08-13)

Key Outputs/Deliverables:

Dependencies:

50. Linguistic Review Panel (linguist members of Editorial Board) conducts monthly 90-minute review meetings (Months 5-11 = 2027-03-13 to 2027-09-13) to examine proposed rules from subcommittees for ambiguity, logical contradiction, or lack of publishable justification; document any veto findings and escalation requests.

Responsible Body/Role: Linguistic Review Panel (embedded in Editorial Board)

Suggested Timeframe: Months 5-11 (2027-03-13 to 2027-09-13)

Key Outputs/Deliverables:

Dependencies:

51. Editorial Board (with Project Lead support) maintains a Decision Log documenting all rule decisions, voting outcomes, dissenting opinions and rationale for each outcome; update within 3 business days of each board or subcommittee decision; publish quarterly (Months 3, 6, 9, 12 = 2027-01-13, 2027-04-13, 2027-07-13, 2027-10-13).

Responsible Body/Role: Editorial Board Chair with Project Lead administrative support

Suggested Timeframe: Months 1-12 (2026-11-13 to 2027-10-13, ongoing)

Key Outputs/Deliverables:

Dependencies:

52. Editorial Board resolves all unresolved rule disputes and tiebreaker escalations by Month 10 (2027-08-13), allowing a 1-month buffer for drafting and public comment before Month 11 (2027-09-13) finalization; any deadlocked disputes are escalated to the external Arbiter for binding recommendation within 2 weeks.

Responsible Body/Role: Editorial Board with external Arbiter if escalated

Suggested Timeframe: Month 10 (2027-08-13)

Key Outputs/Deliverables:

Dependencies:

53. Editorial Board drafts the Clear English Standard v0.1 (draft) by Month 11 (2027-09-13), incorporating all finalized rules, lexicon, rationale and examples; publish the draft for a 30-day public-comment window (Months 11-12 = 2027-09-13 to 2027-10-13).

Responsible Body/Role: Editorial Board with Project Lead publication support

Suggested Timeframe: Month 11 (2027-09-13) (draft published by 2027-09-13 for 30-day window)

Key Outputs/Deliverables:

Dependencies:

54. Editorial Board manages the draft-standard 30-day public-comment window (Months 11-12 = 2027-09-13 to 2027-10-13): collect all substantive comments, triage by rule domain, draft responses addressing or acknowledging each comment, and prepare a summary of comments and responses for publication with v1.0.

Responsible Body/Role: Editorial Board with Project Lead administrative support

Suggested Timeframe: Months 11-12 (2027-09-13 to 2027-10-13)

Key Outputs/Deliverables:

Dependencies:

55. Editorial Board incorporates substantive public feedback into rule clarifications (not reopening core rules) and publishes the final Clear English Standard v1.0 by Month 12 (2027-10-13), including the Decision Log (rule rationale), list of retained irregular forms, homograph-pair list, lexicon with pronunciation guidance, style guide covering ordinals/homographs/morphology, and published responses to public comments.

Responsible Body/Role: Editorial Board with Project Lead

Suggested Timeframe: Month 12 (2027-10-13) (by 2027-10-13)

Key Outputs/Deliverables:

Dependencies:

56. Project Lead determines and fixes the Licensing and Name Stewardship model by Month 6 (2027-04-13), choosing either a certification-mark approach (name restricted to conforming materials against a checklist) or a permissive share-alike license (permitting forks with divergence disclosure and distinct naming); publish the model by Month 12 (2027-10-13).

Responsible Body/Role: Project Lead with Compliance & Risk Management Committee (legal counsel) and Steering Committee input

Suggested Timeframe: Months 4-6 (2027-02-13 to 2027-04-13) (decision finalized by 2027-04-13)

Key Outputs/Deliverables:

Dependencies:

57. Project Lead and Compliance & Risk Management Committee develop a formal safety-critical pilot boundary and enforcement procedure by Month 4 (2027-02-13), specifying that safety-critical pilots are limited to glossary and labeling exercises, not live operational procedures, before Month 24 (2028-10-13) go/no-go decision; all materials carry explicit disclaimers and are reviewed by qualified human experts before use.

Responsible Body/Role: Compliance & Risk Management Committee (legal counsel, safety-critical partners) with Project Lead

Suggested Timeframe: Month 4 (2027-02-13) (by 2027-02-13)

Key Outputs/Deliverables:

Dependencies:

58. Psychometrician conducts rater-training and inter-rater calibration study by Month 11 (2027-09-13), recruiting 3-5 raters to score a sample of ~100-200 ordinal and pronunciation items from both Clear English and standard-English conditions; target Cohen's kappa ≥0.75 (proposed) for each metric; document training protocol, scoring rubric, and any rater disagreements.

Responsible Body/Role: Psychometrician with Metrics & Validation Committee

Suggested Timeframe: Month 10-11 (2027-08-13 to 2027-09-13)

Key Outputs/Deliverables:

Dependencies:

59. Psychometrician and Project Lead conduct a dry-run of all assessment tools, data-collection procedures and audio-capture/storage workflows with a small pilot cohort (N=5-10 learners from one of the partner sites) by Month 10 (2027-08-13); test recording, storage, backup, data-labeling and analysis workflow; document findings and remediate any issues.

Responsible Body/Role: Psychometrician with Metrics & Validation Committee and one pilot partner

Suggested Timeframe: Month 10 (2027-08-13)

Key Outputs/Deliverables:

Dependencies:

60. Project Lead hires or designates an educator liaison (0.5-1.0 FTE, ~$50K-$70K/year estimate) by Month 6 (2027-04-13) to lead teacher engagement, training delivery, feedback loops and corrective outreach; educator liaison reports to Project Lead and Stakeholder Engagement Lead.

Responsible Body/Role: Project Lead with Finance Lead approval

Suggested Timeframe: Months 4-6 (2027-02-13 to 2027-04-13) (hire by 2027-04-13)

Key Outputs/Deliverables:

Dependencies:

61. Compliance & Risk Management Committee develops a contingency plan for Phase 1 timeline extension (up to 4 weeks by Month 10 = 2027-08-13 if inter-rater reliability kappa <0.70 after initial training): cost ~$85K (estimate), approval by Steering Committee required; identify where the extension impacts Phase 2 start and pilot enrollment schedule.

Responsible Body/Role: Compliance & Risk Management Committee with Finance Lead and Steering Committee

Suggested Timeframe: Month 8 (2027-06-13)

Key Outputs/Deliverables:

Dependencies:

62. Steering Committee reviews the pre-registered metrics, pre-analysis plan and go/no-go gate conditions at a scheduled checkpoint meeting (Month 11 = 2027-09-13); confirm that all four metrics have quantitative thresholds locked, sample size is n≥80 per arm, inter-rater reliability target is clear (kappa ≥0.75 target, 0.70 floor), and analysis plan is finalized and publicly registered.

Responsible Body/Role: Steering Committee with Psychometrician and Metrics & Validation Committee

Suggested Timeframe: Month 11 (2027-09-13)

Key Outputs/Deliverables:

Dependencies:

63. Project Lead and Steering Committee hold the Phase 1 exit meeting at Month 12 (2027-10-13) to confirm that all Phase 1 deliverables are complete and Phase 2 can begin: (1) Clear English Standard v1.0 published; (2) 5,000-word lexicon with audio recordings usable; (3) pre-analysis plan pre-registered; (4) inter-rater reliability ≥0.70 floor confirmed; (5) ethics/IRB approval in hand; (6) pilot partnership agreements signed; (7) assessment instruments finalized; (8) Critical Path Dashboard showing Phase 2 readiness.

Responsible Body/Role: Steering Committee with Project Lead

Suggested Timeframe: Month 12 (2027-10-13)

Key Outputs/Deliverables:

Dependencies:

64. Project Lead and Cohort Manager begin pilot recruitment at the partner sites, targeting enrollment of ≥115 learners per arm (4 arms total, ~460 learners estimate) with ≤30% target dropout, by Month 13 (2027-11-13); distribute learner-information packets, obtain informed consent, distribute incentives and certificates to encourage completion.

Responsible Body/Role: Cohort Manager with pilot partner sites

Suggested Timeframe: Months 13-14 (2027-11-13 to 2027-12-13, enrollment complete by Month 13 = 2027-11-13)

Key Outputs/Deliverables:

Dependencies:

65. Metrics & Validation Committee conducts a mid-phase validity audit by an independent external auditor (Month 18-22 = 2028-04-13 to 2028-08-13), examining pilot data for: (1) inter-rater reliability (kappa trends, scorer drift); (2) construct validity (confound analysis, effect-size checks); (3) data integrity (missing files, outliers, consent violations); (4) compliance with pre-registered analysis plan. Report findings to Steering Committee by Month 23 (2028-09-13).

Responsible Body/Role: Metrics & Validation Committee with external independent auditor

Suggested Timeframe: Months 18-23 (2028-04-13 to 2028-09-13)

Key Outputs/Deliverables:

Dependencies:

66. Steering Committee holds a Phase 2 midpoint checkpoint meeting (Month 18 = 2028-04-13) to review pilot enrollment, retention, preliminary data quality, and any validity or operational issues; adjust Phase 2 timeline or scope if major problems identified; recommend any remediation (additional rater training, extended follow-up).

Responsible Body/Role: Steering Committee with Metrics & Validation Committee and Project Lead

Suggested Timeframe: Month 18 (2028-04-13)

Key Outputs/Deliverables:

Dependencies:

67. Compliance & Risk Management Committee reviews the Risk Register quarterly (Months 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36 = 2027-01-13 onwards), assessing mitigation progress, emerging risks, and escalation status; generate a summary risk dashboard for Steering Committee review at each quarterly gate checkpoint.

Responsible Body/Role: Compliance & Risk Management Committee

Suggested Timeframe: Quarterly (Months 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36 = 2027-01-13 onwards)

Key Outputs/Deliverables:

Dependencies:

68. Project Lead and Compliance & Risk Management Committee conduct a lexicon-coverage audit (Month 8 = 2027-06-13) of the 5,000-word core lexicon against pilot running-text materials and technical glossaries; confirm ≥85% coverage (proposed threshold) or identify gaps and prioritize expansion; if coverage <85%, allocate time and budget (~$30K-$50K estimate) for targeted lexicon expansion by Month 10 (2027-08-13).

Responsible Body/Role: Project Lead with Editorial Board (lexicon subcommittee)

Suggested Timeframe: Month 8 (2027-06-13)

Key Outputs/Deliverables:

Dependencies:

69. Compliance & Risk Management Committee identifies 2-3 potential permanent steward organizations (language-education non-profits, university consortiums, international standards bodies) and approaches them by Month 27 (2029-01-13) with a stewardship proposal (estimated $150K-$250K per year for ongoing maintenance and governance); secure written commitment by Month 33 (2029-07-13) before v1.0 public release.

Responsible Body/Role: Compliance & Risk Management Committee (Chair or Stakeholder Engagement Lead) with Project Lead

Suggested Timeframe: Months 24-33 (2028-10-13 to 2029-07-13)

Key Outputs/Deliverables:

Dependencies:

70. Steering Committee holds the Phase 2 go/no-go decision meeting (Month 24 = 2028-10-13): review final pilot data, validity-audit findings, all four gate metrics against pre-registered thresholds, and statistical significance; determine GO (all thresholds met, data valid, n≥80 completers per arm, kappa ≥0.70, follow-up ≥70% complete) or NO-GO (any metric fails threshold or data invalid); document decision rationale and next steps for Phase 3.

Responsible Body/Role: Steering Committee with Psychometrician, Metrics & Validation Committee, and Editorial Board (for rule implications)

Suggested Timeframe: Month 24 (2028-10-13)

Key Outputs/Deliverables:

Dependencies:

71. If Phase 2 go/no-go is GO (Month 24 = 2028-10-13), Steering Committee authorizes Phase 3 (v1.0 public release and limited adoption) and confirms stewardship-funding commitment is in place before v1.0 release (Month 30 = 2029-04-13); Project Lead begins Phase 3 planning (curriculum finalization, publisher outreach, marketing materials).

Responsible Body/Role: Steering Committee with Project Lead

Suggested Timeframe: Month 24 (2028-10-13) onwards

Key Outputs/Deliverables:

Dependencies:

72. If Phase 2 go/no-go is NO-GO (Month 24 = 2028-10-13), Steering Committee documents the reasons, considers options for a limited Phase 2 extension (3-6 months, ~$300K-$600K estimate, not budgeted pre-gate), rework of identified rule weaknesses, or project closeout; all Phase 3 funds ($0.85M) and remaining reserve (~$175K or more, depending on pre-gate draws) are held or returned to Funding Authority.

Responsible Body/Role: Steering Committee with Project Sponsor and Funding Authority

Suggested Timeframe: Month 24 (2028-10-13) onwards

Key Outputs/Deliverables:

Dependencies:

73. Project Lead and Compliance & Risk Management Committee establish a Standards Stewardship Committee (separate from the Phase 1-3 Editorial Board) with 3-5 members (representing steward organization, Editorial Board, and key adopters), formal decision authority, published charter and meeting schedule by Month 30 (2029-04-13), to govern the standard post-Phase-3.

Responsible Body/Role: Project Lead with Steward Organization (if Phase 2 GO)

Suggested Timeframe: Months 30-36 (2029-04-13 to 2029-10-13)

Key Outputs/Deliverables:

Dependencies:

74. Project Lead publishes the final Clear English Standard v1.0, reference dictionary, style guide and associated licensing/conformance documentation (if certification mark model chosen) by Month 30 (2029-04-13), conditional on a written steward-organization commitment; begin limited-scope Phase 3 adoption (Months 30-36 = 2029-04-13 to 2029-10-13).

Responsible Body/Role: Project Lead with Editorial Board and Steward Organization

Suggested Timeframe: Month 30 (2029-04-13)

Key Outputs/Deliverables:

Dependencies:

Decision Escalation Matrix

Budget Overrun Exceeding Pre-Gate Contingency Cap Escalation Level: Project Steering Committee Approval Process: Steering Committee review of spending variance (>$50K threshold) with Finance Lead presentation; if draw requested exceeds $175K pre-gate cap, escalation to Project Sponsor and Funding Authority for approval of scope reduction, Phase 2 extension costs, or project termination decision. Rationale: The fixed $3.5M budget with only $175K pre-gate contingency (5% of total) is the binding constraint. A $300K overrun (8.6% of budget estimate) would exhaust the pre-gate reserve and force cuts to pilot scope, assessment quality, or curriculum development. This directly threatens gate credibility and adoption feasibility. Negative Consequences: Budget overrun >$175K pre-gate forces either pilot scope cuts (fewer cohorts, smaller assessment battery) that weaken go/no-go evidence, curriculum quality reduction that undermines adoption appeal, or Project Sponsor intervention to extend Phase 1 or Phase 2 at cost to Phase 3 outreach. Uncontrolled spending could strand Phase 3 ($850K) if reserve is depleted mid-pilot.

Inter-Rater Reliability Below Measurement Floor After Calibration Escalation Level: Steering Committee and Metrics & Validation Committee (joint escalation) Approval Process: Metrics & Validation Committee flags kappa <0.70 to Steering Committee within 48 hours; Steering Committee reviews remediation plan (extended rater training, Phase 1 extension by up to 4 weeks at ~$85K estimate) and votes to approve extension or to proceed to Phase 2 with acknowledged measurement degradation. If measurement remains <0.70 by Month 11 (2027-09-13), gate decision is at risk and Steering Committee recommends formal extension or scope reduction. Rationale: Pronunciation consistency and ordinal-error scoring depend on inter-rater reliability (kappa ≥0.75 target, ≥0.70 floor proposed). Scoring below the floor inflates measurement error by 20%+ and reduces statistical power to detect Clear English effects by 10–15%, risking false-negative gate outcome and stranding $1.2M–$1.4M in Phase 2–3 spending. Negative Consequences: Kappa below 0.70 invalidates the pronunciation-consistency metric; gate decision becomes scientifically disputable, potentially triggering partner and standards-body loss of confidence. A false-negative outcome kills a viable standard. A false-positive launches weak standard, damaging credibility by Month 48–60 (2030-10-13 to 2031-10-13) and reducing Phase 3 adoption by 30–50%.

Editorial Board Deadlock or Ambiguous Rules Unresolved by Month 10 (2027-08-13) Escalation Level: External Arbiter (appointed by Month 5 = 2027-03-13), with final escalation to Project Sponsor if arbiter recommendation is rejected Approval Process: Editorial Board attempts consensus or majority vote by Month 10 (2027-08-13); if deadlocked rule dispute persists, matter escalates to external Arbiter (neutral linguist or standards-design specialist, $10K–$20K cost estimate) for binding recommendation within 2 weeks. If Arbiter's recommendation is rejected by both Steering Committee and Editorial Board, matter escalates to Project Sponsor for final decision by Month 11 (2027-09-13). Rationale: Rules must be finalized by Month 12 (2027-10-13) to allow a 30-day public comment window before v1.0 lock at Phase 2 start. Unresolved disputes (ordinal pronunciation, morphology retention threshold, homograph marker policy) prevent rule publication and delay pilots. Mid-pilot rule changes invalidate earlier assessments and confound results. Negative Consequences: A 4-week board deadlock compresses Phase 2 pilots from 12 to 8–10 months (33–50% reduction in pilot window), weakening statistical power and data quality. Ambiguous rules during pilots cause 10–20% rule misapplication (estimate), confounding results and rendering gate metrics inconclusive. Forced, unclear rules damage educator and publisher confidence in the standard pre-launch.

Pilot Recruitment or Retention Falls Below Minimum Sample Size Escalation Level: Project Steering Committee with Compliance & Risk Management Committee Approval Process: Cohort Manager and Compliance & Risk Management Committee flag enrolment shortfall (<80 completers per arm estimate or dropout >30%) to Steering Committee; Steering Committee reviews retention-incentive options (increased stipends, additional contact hours, partner re-engagement), pilot schedule extension (adding 4–8 weeks to Phase 2, estimated cost $85K–$170K), or scope reduction (reducing to 2 arms or smaller sample). If shortfall cannot be remedied, Steering Committee escalates to Project Sponsor for decision on extension cost or gate delay. Rationale: The go/no-go gate requires ≥80 completers per arm (4 arms × 80 = 320 completers) to achieve 80% statistical power at α=0.05 (proposed). Enrollment <50 per arm or dropout >30% undermines all four gate metrics (ordinal error rate, comprehension speed, pronunciation consistency, 30-day retention) and renders the Month 24 (2028-10-13) decision scientifically indefensible. Negative Consequences: Insufficient sample size makes gate metrics statistically unreliable; forced gate decision becomes disputable and risks either false-positive (weak standard launched, credibility damaged) or false-negative (viable standard rejected, $1.2M–$1.4M Phase 2–3 spending wasted). High dropout reduces effective n by 15–30%, compounding power loss. Phase 2 extension by 3–6 months ($300K–$600K estimate, unbudgeted) could strain remaining contingency and delay Phase 3 release to Month 36–42 (2029-10-13 to 2030-04-13).

Safety-Critical Incident or Material Liability Claim Linked to Clear English Escalation Level: Compliance & Risk Management Committee (immediate within 48 hours) to legal counsel, Steering Committee, and relevant safety regulators (OSHA, HSE, workplace safety authority) Approval Process: Incident-reporting protocol triggered: Compliance & Risk Management Committee notifies legal counsel, Project Sponsor, Steering Committee and affected pilot organization within 48 hours. Legal counsel advises on regulatory notification, disclosure obligations and potential liability exposure. Formal incident investigation conducted within 2 weeks; findings and remediation plan reviewed by Steering Committee. If incident is serious (injury, near-miss in safety-critical context), Project Sponsor and Funding Authority make final decision on pilot suspension, materials withdrawal, or project continuation. Rationale: Safety-critical pilots (glossary and labeling exercises, no live operational procedures until Month 24 = 2028-10-13) are bounded by legal disclaimers and human expert review. However, any documented injury, near-miss or serious misreading linked to Clear English documentation triggers liability exposure, regulatory investigation and potential mandate for project pause. Insurance, legal review and risk-approval processes may be costly ($150K–$200K estimate) and slow. Negative Consequences: A serious incident (injury linked to Clear English documentation) could result in litigation, regulatory action (OSHA, EPA, or equivalent investigation), mandatory product recall or withdrawal of the standard, and immediate pause or termination of the initiative. Media scrutiny and credibility loss would follow, reducing Phase 3 adoption to near-zero even if gate is positive. Incident response costs ($100K–$500K estimate) could exceed remaining budget and force Phase 3 cancellation.

Educator Pushback or Standards-Body Regulatory Rejection Blocking Pilot Access or Third-Party Adoption Escalation Level: Project Steering Committee and Stakeholder Engagement Lead, with escalation to Project Sponsor if adoption risk exceeds tolerance Approval Process: Stakeholder Engagement Lead monitors educator and standards-body sentiment (TESOL, IATEFL, national education authorities) and flags critical feedback or rejection signals to Steering Committee within 48 hours if sentiment shifts >20% toward rejection or if a major partner withdraws support. Steering Committee reviews corrective outreach plan (revised messaging, educator training, licensing clarity, partner re-engagement). If regulatory approval is delayed >4 weeks or pilot enrollment declines >20% due to pushback, matter escalates to Project Sponsor for decision on messaging adjustment, timeline extension, or scope reduction. Rationale: Educator and standards-body adoption is essential to pilot recruitment and Phase 3 success. High-likelihood risk: educators may perceive Clear English as a threat to standard English instruction or a non-standard variant imposed from outside. Standards bodies may demand formal approval or alignment with existing curricula. Unmanaged pushback reduces pilot enrollment by 20–50% (estimate) and delays institutional partnerships, compressing Phase 2 timeline and weakening gate credibility. Negative Consequences: Low educator engagement could reduce pilot quality and statistical power, making gate metrics inconclusive or disputable. Public criticism from TESOL, IATEFL or national education authorities could trigger negative media coverage, damaging credibility before go/no-go decision. Regulatory approval delays of 4–8 months (estimate) push pilot timeline into Month 28–32 (2029-02-13 to 2029-06-13), jeopardizing the Month 24 (2028-10-13) gate. Even if gate is positive, educator resistance could reduce Phase 3 adoption by 30–50%, capping learner reach at 15,000–35,000 instead of 100,000+.

Monitoring Progress

1. Gate Metrics Credibility and Pre-Registration Tracking

Monitoring Tools/Platforms:

Frequency: Bi-weekly Metrics & Validation Committee meetings (Months 2-24 = 2026-12-13 to 2028-10-13); monthly reporting to Steering Committee; validity audit mid-phase (Months 18-23 = 2028-04-13 to 2028-09-13)

Responsible Role: Metrics & Validation Committee (Chair: Psychometrician, with external measurement specialist oversight)

Adaptation Process: The Psychometrician and Committee detect measurement validity threats (inter-rater kappa drift below 0.70, effect-size anomalies, confound signals, data integrity issues) via ongoing analysis and the independent mid-phase validity audit. Threats escalate immediately to the Steering Committee with remediation options (rater retraining, extended calibration, supplementary analysis, Phase 1 extension by up to 4 weeks estimated at ~$85K cost). If kappa falls below 0.70 at the Month 10 (2027-08-13) checkpoint and retraining during Month 10-11 (2027-08-13 to 2027-09-13) does not restore it to ≥0.70, Phase 1 is extended by 4 weeks with Steering Committee approval.

Adaptation Trigger: Inter-rater reliability (Cohen's kappa) <0.70 for more than 2 weeks; effect sizes falling outside expected range (confound signal); missing pilot data >15% by Month 21 (2028-07-13); validity audit findings (Month 23 = 2028-09-13) that challenge construct validity or reveal data-integrity violations; any deviation from the pre-registered analysis plan discovered during Phase 2 execution.

2. Editorial Board Rule Finalization and Decision Logging

Monitoring Tools/Platforms:

Frequency: Monthly Editorial Board meetings (second Thursday, 2 hours) and biweekly rule-workstream subcommittee meetings (ordinal, morphology, homograph, lexicon, pronunciation-guidance) Months 2-10 (2026-12-13 to 2027-08-13); Linguistic Review Panel monthly vetting (Months 5-11 = 2027-03-13 to 2027-09-13); quarterly published Decision Log summaries (Months 3, 6, 9, 12 = 2027-01-13, 2027-04-13, 2027-07-13, 2027-10-13)

Responsible Role: Editorial Board Chair (internal, practitioner or linguist with governance experience, 0.5 FTE) with Linguistic Review Panel (2-3 board linguists, monthly 90-minute meetings) and external Arbiter (appointed by Month 5 = 2027-03-13 for tie-breaking if consensus fails)

Adaptation Process: The Editorial Board drafts rule specifications through assigned subcommittees (ordinal marker pronunciation, morphology retention threshold, homograph-pair list, lexicon selection, G2P logic), meeting biweekly through Month 10 (2027-08-13). The Linguistic Review Panel reviews each proposed rule monthly for internal contradiction, ambiguity, or lack of publishable justification; any veto findings are escalated to the full board for resolution. If a rule dispute remains unresolved after board vote and linguist veto, the matter is escalated to the external Arbiter for a binding recommendation within 2 weeks. All decisions are logged within 3 business days with rationale documented. If disputes persist beyond Month 10 (2027-08-13), the escalation to Arbiter triggers immediately; if the Arbiter's recommendation is rejected by both the Steering Committee and Editorial Board, the matter escalates to the Project Sponsor for final decision.

Adaptation Trigger: Any rule remaining ambiguous or internally contradictory at the end of a subcommittee meeting; a Linguistic Review Panel veto on a proposed rule; a board vote that deadlocks (tie) or fails to reach simple majority; a rule-specification workstream milestone missed by >2 weeks; any rule conflict that cannot be resolved by consensus by Month 10 (2027-08-13); Arbiter recommendation issued but rejected by Steering Committee or Editorial Board.

3. Pilot Recruitment, Enrollment and Retention Tracking

Monitoring Tools/Platforms:

Frequency: Weekly enrollment updates from Cohort Manager (Months 13-14 = 2027-11-13 to 2027-12-13); monthly partner status reports and retention metrics (Months 15-24 = 2028-01-13 to 2028-10-13); 30-day follow-up tracking from Month 18 (2028-04-13) onwards; mid-phase checkpoint review (Month 18 = 2028-04-13) with Steering Committee

Responsible Role: Cohort Manager (1.0 FTE, hired by Month 6 = 2027-04-13, reports to Project Lead) with Stakeholder Engagement Lead oversight and partner-site liaisons

Adaptation Process: The Cohort Manager monitors enrollment weekly against the target of ≥115 per arm (4 arms, 460 total estimate); flags shortfalls to the Project Lead within 48 hours if enrollment lags >2 weeks behind schedule. Dropout and retention are tracked at each assessment point; if attrition exceeds 30% target by Month 18 (2028-04-13) midpoint, the Project Lead and Compliance & Risk Management Committee review retention-incentive options (increased stipends, additional session scheduling flexibility, partner re-engagement) and recommend either intensified outreach or Phase 2 extension (estimated ~$85K-$300K depending on scope, proposed). The Steering Committee reviews enrollment status at quarterly checkpoints (Months 18, 24 = 2028-04-13, 2028-10-13); if effective sample size at Month 22 (2028-08-13, data lock) falls below 80 completers per arm, the Committee escalates to Project Sponsor and decides whether to extend Phase 2 (3-6 months, estimated cost $300K-$600K unbudgeted) or proceed to a disputed go/no-go decision.

Adaptation Trigger: Enrollment cumulative shortfall >15% of target by end of Week 8 (Month 13.5 = 2027-11-28, estimate); dropout >30% at any checkpoint; 30-day follow-up completion <70% by Month 23 (2028-09-13); any pilot partner withdraws participation or reduces committed enrollment; effective completers <80 per arm by data lock (Month 22 = 2028-08-13); retention patterns diverge significantly between pilot sites or conditions (suggesting confound or delivery failure).

4. Critical Success Factor: Rule Specification Completeness and Clarity

Monitoring Tools/Platforms:

Frequency: Monthly rule-workstream progress reviews (Months 2-10 = 2026-12-13 to 2027-08-13); draft-standard preparation and publication (Month 11 = 2027-09-13); public-comment collection and response (Month 11-12 = 2027-09-13 to 2027-10-13); rules-lock verification (Month 12 = 2027-10-13); pre-Phase-2 gate checkpoint (Month 12 = 2027-10-13)

Responsible Role: Editorial Board Chair with Project Lead and Compliance & Risk Management Committee support for publication and public-engagement logistics

Adaptation Process: The Editorial Board monitors rule-specification completeness through monthly subcommittee reports: ordinal marker pronunciation (fixed form, spoken reading, legacy-form conversion rules), morphology retention threshold (frequency cutoff, retained list, regularized list with justification), homograph-disambiguation policy (published pair list ≤50 estimate, marker vs. rewrite decision per pair, enforcement in safety-critical docs), core-lexicon specification (5,000 words, selection basis documented, coverage audit ≥85% estimate), and G2P guidance (overlay logic, optional application). Any missing specification or unresolved detail is flagged in monthly Board minutes and assigned to a subcommittee for completion by Month 10 (2027-08-13). The draft standard v0.1 is published Month 11 (2027-09-13) with all core specifications; public comments are collected and responded to within 14 days; substantive comments that clarify rule intent (but do not reopen core rules) are incorporated into v1.0. If substantive public comments challenge rule validity (e.g., a comment that the ordinal marker is ambiguous or the morphology threshold is unjustifiably high), the Editorial Board escalates the comment to the external Arbiter for recommendation on whether rule revision is warranted before v1.0 finalization; if the Arbiter recommends revision, the rule is clarified or refined by Month 12 (2027-10-13).

Adaptation Trigger: Any rule specification incomplete or marked 'TBD' at the end of Month 9 (2027-07-13); Editorial Board unable to reach consensus on a core rule by Month 10 (2027-08-13); draft standard v0.1 missing a major specification (e.g., no ordinal-marker spoken-reading guidance, no morphology-retention list, no homograph-pair list); public-comment window generates substantive challenges to rule logic or clarity that the Editorial Board cannot resolve without revision; Arbiter recommendation issued indicating rule ambiguity that requires pre-v1.0 fix.

5. Critical Success Factor: Pilot Partner Commitment and Institutional Support

Monitoring Tools/Platforms:

Frequency: Monthly check-in calls with each of the 5-7 pilot partners (ESL programs and technical/safety-training organizations); quarterly advisory panel meetings with educators, regulators and publishers (Months 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36 = 2027-01-13 onwards); mid-phase stakeholder-alignment review (Month 18 = 2028-04-13); monthly engagement-metric reports to Steering Committee

Responsible Role: Stakeholder Engagement Lead (internal, 0.5 FTE) with Project Lead oversight and Compliance & Risk Management Committee escalation support

Adaptation Process: The Stakeholder Engagement Lead maintains signed partnership agreements with ≥3 adult ESL programs and ≥2 technical/safety-training organizations by Month 3 (2027-01-13), documenting enrollment guarantees, payment terms, educator-training participation, and feedback schedules. Monthly contact logs track partner engagement (meeting attendance, readiness for material delivery, instructor preparation); any partner showing signs of disengagement (missed meetings, enrollment delays, budget constraints) is flagged to the Project Lead within 48 hours for re-engagement outreach. Quarterly advisory panels (educators, regulators, publishers) surface emerging adoption barriers or standards-body concerns; if a panel signals potential rejection or major pushback (e.g., 'Clear English is a threat to standard English instruction'), the Project Lead and Stakeholder Engagement Lead convene an emergency response meeting and recommend corrective messaging or protocol adjustments to the Steering Committee. If a pilot partner withdraws or reduces commitment to <80 committed learners, the Project Lead immediately flags the shortfall and activates a backup partner or expanded recruitment at an existing site.

Adaptation Trigger: A pilot partner misses two consecutive monthly check-ins without explanation; a partner withdraws or reduces enrollment commitment by >20%; educator or standards-body advisory panel reports >20% increase in critical sentiment or adoption concerns; a major ESL publisher or standards body (TESOL, IATEFL, national education authority) signals that Clear English is not aligned with their curricula or standards and declines partnership; educator pushback signals in social media, professional forums or direct feedback reach a threshold of >10% of outreach audience expressing concern or rejection.

6. Risk Management: Budget, Timeline and Contingency Tracking

Monitoring Tools/Platforms:

Frequency: Monthly financial tracking (cumulative spend, 6-month forecast) and critical-path review; spending-review gate (Month 9 = 2027-07-13) and mid-phase check (Month 18 = 2028-04-13); formal Phase-1 exit review (Month 12 = 2027-10-13); quarterly risk reviews with Steering Committee (Months 3, 6, 9, 12, 15, 18, 21, 24 = 2027-01-13 onwards)

Responsible Role: Finance Lead (0.5-1.0 FTE internal budget controller) with Compliance & Risk Management Committee (Chair) and Project Lead

Adaptation Process: The Finance Lead tracks cumulative monthly spend against Phase allocations ($1.1M Phase 1, $1.2M Phase 2, $0.85M Phase 3) and provides a variance report flagging any line item >10% over or under budget and cumulative Phase variance >$50K. The Critical Path Dashboard is reviewed monthly for slippage >2 weeks on key milestones (rules finalization Month 12 = 2027-10-13, audio completion Month 11 = 2027-09-13, pre-registration Month 11 = 2027-09-13, recruitment/enrollment Month 13 = 2027-11-13, data lock Month 22 = 2028-08-13); any slip triggers immediate escalation to the Steering Committee with impact assessment (does it compress Phase 2 pilot window, risk kappa validation, or push go/no-go decision past Month 24 = 2028-10-13?). The Contingency Reserve Balance ($350K total, capped at $175K draws pre-gate for evidence-protection needs) is tracked monthly; the Finance Lead and Compliance & Risk Management Committee recommend draws for Phase-1 extension (≤$85K estimated) or psychometric re-validation (≤$50K estimated) if gate-protection risks emerge; all draws >$50K require Steering Committee approval. The Compliance & Risk Management Committee reviews the Risk Register quarterly and escalates any High×High risk (e.g., >$50K overrun, pilot recruitment collapse, inter-rater reliability failure, educator pushback >20%, safety incident) to the Steering Committee within 5 business days with mitigation recommendation.

Adaptation Trigger: Any single line-item spend variance >$50K or Phase cumulative variance >$50K; critical-path milestone slip >2 weeks; cumulative spend forecast indicating total project cost will exceed $3.5M by >$125K at any checkpoint; contingency reserve balance falls below $175K pre-gate threshold; identified High×High risk from Risk Register requiring immediate mitigation (e.g., safety incident, data breach, major partner withdrawal); budget variance discovered that cannot be resolved within existing Phase allocations, requiring scope cuts or timeline extension.

7. Risk Management: Safety-Critical Liability and Compliance

Monitoring Tools/Platforms:

Frequency: Monthly review of safety-critical materials and human-expert sign-offs (if any safety pilots are conducted); quarterly legal and compliance check-ins with retained counsel; ethics/IRB communication as needed (ongoing after Month 6 = 2027-04-13 approval); data-protection audit (Month 8 = 2027-06-13) and privacy-policy publication (Month 12 = 2027-10-13); immediate incident-reporting and escalation (within 48 hours if incident occurs)

Responsible Role: Compliance & Risk Management Committee (Chair, risk-management specialist, 0.5 FTE), with external legal counsel (product liability and regulatory compliance specialist, ~4 hours/month retainer), ethics/IRB liaison (internal or external, ~3-4 hours/month), and Data Integrity Officer (internal, ~2 hours/month)

Adaptation Process: The Compliance & Risk Management Committee establishes clear boundaries for safety-critical pilots: glossary and labeling exercises only (no live operational procedures) until after Month 24 (2028-10-13) go/no-go decision; all materials carry explicit disclaimers ('Clear English is a non-standard variant; use with qualified expert human review') and require sign-off by a qualified human expert (trainer, safety officer) before deployment. Legal counsel advises on regulatory pathways, insurance coverage options ($150K-$200K estimated budget cap), and product liability risk. The Committee ensures ethics/IRB approval is obtained by Month 6 (2027-04-13), covering informed consent, audio-recording protocols, data-protection measures and participant opt-out procedures. A data-protection audit (Month 8 = 2027-06-13) verifies GDPR compliance (UK, if applicable), US state privacy law compliance, encrypted storage setup, backup procedures, and data-retention schedules; any gaps identified are remediated by Month 12 (2027-10-13) with documented attestation. If a safety incident, data breach or ethics violation occurs, the Committee triggers an immediate incident-reporting protocol (within 48 hours): notification to legal counsel, Project Sponsor, Steering Committee, affected pilot organization, and (if required) regulatory authorities; formal investigation within 2 weeks; remediation plan reviewed by Steering Committee; decision on whether to suspend pilots, withdraw materials, or modify protocols.

Adaptation Trigger: Documented safety incident or near-miss in any safety-critical pilot material linking Clear English wording to misunderstanding, wrong action, or injury; data-protection audit finding a gap in encryption, access control, consent documentation or backup procedures; ethics/IRB approval delayed by >2 weeks or conditional on substantive protocol revisions; legal counsel assessment that liability insurance or regulatory approval cost will exceed $200K (estimated cap); incident report from a pilot site or external source alleging that Clear English documentation caused confusion, incorrect action or safety concern; participant complaint regarding data privacy, recording use or consent procedures.

8. Risk Management: Educator Pushback and Adoption Resistance

Monitoring Tools/Platforms:

Frequency: Monthly tracking of educator and publisher engagement metrics (open rates on outreach, meeting attendance, sentiment); quarterly advisory panel meetings (Months 3, 6, 9, 12, 15, 18, 21, 24 = 2027-01-13 onwards); real-time monitoring of social media, professional forums (TESOL, IATEFL) and direct feedback for critical signals; mid-phase stakeholder-alignment check-in (Month 18 = 2028-04-13)

Responsible Role: Stakeholder Engagement Lead (internal, 0.5 FTE) with Educator Liaison (0.5-1.0 FTE, hired by Month 6 = 2027-04-13) and Compliance & Risk Management Committee escalation support

Adaptation Process: The Stakeholder Engagement Lead maintains engagement metrics (email open rates, advisory-panel attendance, meeting frequency) and flags declining engagement or critical feedback within 48 hours. Advisory panels (educators, standards bodies, publishers) meet quarterly and provide structured feedback on adoption concerns, messaging clarity and perceived barriers. If educator sentiment shifts negatively (e.g., >20% of panel respondents report concern that Clear English is a threat to standard English instruction) or if a major professional organization (TESOL, IATEFL, national education authority) signals rejection or demands for changes, the Project Lead and Stakeholder Engagement Lead convene an emergency response meeting. Corrective actions may include: revised messaging emphasizing that Clear English is supplementary and optional (not a replacement); expanded educator training and stipends to increase buy-in; modification of pilot protocols to better integrate into existing courses; or escalation to the Steering Committee if institutional approval is jeopardized.

Adaptation Trigger: Any TESOL, IATEFL or major national education-authority public statement indicating concern or rejection of Clear English; educator advisory panel reports >20% increase in critical sentiment about adoption barriers or rule comprehensibility; social media or professional-forum activity critical of Clear English reaches >50 mentions in a month or >10 from respected educators; a pilot partner signals that educator concerns are blocking enrollment or participation commitment; an ESL publisher or major adopter candidate explicitly declines participation citing educator resistance or institutional non-alignment.

9. Critical Success Factor: Pronunciation Consistency Measurement and Reference Accent Anchoring

Monitoring Tools/Platforms:

Frequency: Accent-selection decision and documentation (Month 3 = 2027-01-13); rater-training completion and inter-rater calibration (Months 10-11 = 2027-08-13 to 2027-09-13); monthly audio storage and backup verification (Months 6-24 = 2027-04-13 to 2028-10-13); pronunciation-score reporting and inter-rater reliability checks (Months 15-24 = 2028-01-13 to 2028-10-13, weekly during active pilot scoring)

Responsible Role: Psychometrician (hired by Month 2 = 2026-12-13, 0.5-1.0 FTE) with Metrics & Validation Committee oversight and external measurement specialist consultation; Data Integrity Officer (internal, ~2 hours/month) for audio storage and backup verification

Adaptation Process: By Month 3 (2027-01-13), the Psychometrician and Editorial Board (linguist members) select a single reference accent (e.g., General American, Received Pronunciation, or shared-contrast phonemes across accents) with explicit written justification and documentation of how other accents map to the anchor. Rater training and inter-rater calibration occur in Months 10-11 (2027-08-13 to 2027-09-13): 3-5 raters are trained on pronunciation-consistency scoring rubric using 100-200 sample words from both Clear English and control conditions; Cohen's kappa is computed per rater pair, targeting ≥0.75 (proposed threshold) with a floor of 0.70. If initial kappa falls below 0.70, raters receive targeted retraining and a second calibration round within 2 weeks; if kappa remains <0.70 after retraining, the Phase 1 extension contingency ($85K estimated) is triggered to allow additional rater training by Month 12 (2027-10-13). Audio storage is verified monthly for encryption, access controls, backup functionality and completeness (no missing recordings >1% estimated); a dry-run with a small cohort (N=5-10) occurs at Month 10 (2027-08-13) to test recording quality, file organization and rater workflow. During Phase 2 pilots (Months 15-24 = 2028-01-13 to 2028-10-13), pronunciation scoring occurs weekly; inter-rater reliability is re-checked every 2 weeks (weekly during months 20-24 = 2028-08-13 to 2028-10-13); if kappa drops below 0.70 during active scoring, the Metrics & Validation Committee immediately recommends rater re-calibration or additional training.

Adaptation Trigger: Reference accent choice is not finalized and justified by Month 3 (2027-01-13); initial inter-rater kappa <0.70 after first training in Month 10-11 (2027-08-13 to 2027-09-13); inter-rater kappa remains <0.70 after retraining; audio storage audit identifies >1% missing or corrupted files; rater drift observed (kappa declining >0.05 over a 4-week interval during Phase 2 scoring); pronunciation-consistency preliminary results show no meaningful difference between Clear English and control conditions or effect sizes contradicting pilot expectations (potential confound signal).

10. Risk Management: Post-Project Stewardship Funding and Governance Sustainability

Monitoring Tools/Platforms:

Frequency: Steward identification and approach (Months 24-27 = 2028-10-13 to 2029-01-13); commitment letters sought (by Month 33 = 2029-07-13); Stewardship Committee and 5-year roadmap finalized (by Month 36 = 2029-10-13); quarterly post-launch governance check-ins (Months 36, 39, 42 = 2029-10-13, 2030-01-13, 2030-04-13, ... as funded)

Responsible Role: Compliance & Risk Management Committee (Chair, risk-management specialist) with Project Lead and Stakeholder Engagement Lead, in collaboration with the Phase 2 go/no-go decision (if GO) Project Sponsor

Adaptation Process: After the Month 24 (2028-10-13) Phase 2 go/no-go decision, if GO, the Project Lead and Compliance & Risk Management Committee begin identifying potential permanent steward organizations (language-education non-profits, university consortiums, international standards bodies such as ISO or academic organizations) with track records in standards maintenance and funding stability. By Month 27 (2029-01-13), outreach is initiated with a stewardship proposal (estimated annual budget $150K-$250K estimate for ongoing maintenance, governance, change-request review, and lexicon updates). Commitment letters from at least one steward organization are sought by Month 33 (2029-07-13); if no commitment is obtained by this date, the Project Lead escalates to the Project Sponsor for a decision: either (a) defer v1.0 public release pending stewardship commitment (delaying release beyond Month 30 = 2029-04-13), (b) release v1.0 with a conditional sunset clause (e.g., 'This standard will be maintained only if stewardship funding is secured by Month X'), or (c) proceed with release and accept the risk that the standard will atrophy if no steward emerges. A Standards Stewardship Committee is formally established by Month 30 (2029-04-13) with 3-5 members (steward-organization representative, Editorial Board continuity, key adopter representatives) and a published charter and 5-year roadmap specifying how the standard will be updated, how change requests will be prioritized and resolved, and how conflicts over rule interpretation will be handled.

Adaptation Trigger: Phase 2 go/no-go is GO (Month 24 = 2028-10-13) and no steward organization has been approached by Month 24 (2028-10-13); steward outreach begins but by Month 30 (2029-04-13) no letter of commitment is in hand; potential steward organizations decline participation (budget constraints, competing priorities); a steward-organization commitment is received but with conditions (e.g., 'only if ESL publisher adoption reaches 50,000+ learners by Month X') that are unrealistic or unverifiable; the Steering Committee or Project Sponsor determines that the standard's post-Phase-3 viability is at risk and recommends either release deferral or conditional-release strategy.

11. Risk Management: Rule Fragmentation and Non-Conforming Variants Post-Release

Monitoring Tools/Platforms:

Frequency: Licensing model finalized (by Month 6 = 2027-04-13) and published (Month 12 = 2027-10-13); conformance checklist published (Month 12 = 2027-10-13); post-release monitoring for unofficial variants and non-conforming uses (quarterly, Months 30, 33, 36, 39 = 2029-04-13, 2029-07-13, 2029-10-13, 2030-01-13, ... post-release, starting Month 30 = 2029-04-13)

Responsible Role: Compliance & Risk Management Committee (Chair) with Standards Stewardship Committee (post-Month 36 = 2029-10-13) and Stakeholder Engagement Lead; external legal counsel if name-stewardship disputes arise

Adaptation Process: By Month 6 (2027-04-13), the Compliance & Risk Management Committee and Project Lead (with external legal counsel input) finalize the Licensing and Name Stewardship model: either (a) text and dictionary openly licensed; 'Clear English' name reserved as a certification mark (requiring conformance against a public checklist) awarded to materials that pass the checklist, or (b) text and dictionary under a permissive share-alike license (permitting derivative works if divergence is disclosed and a distinct name is adopted once >10% of rules diverge, proposed threshold). A public, light, free conformance checklist is published by Month 12 (2027-10-13), specifying the key rules (ordinal marker form, morphology changes, homograph markers, lexicon boundaries) that materials must follow to claim 'Clear English' conformance. Post-release (starting Month 30 = 2029-04-13), the Standards Stewardship Committee (or Project Lead, if Stewardship Committee not yet established) monitors for third-party uses of the 'Clear English' name and for unofficial forks or non-conforming variants. A public registry of licensed adopters is maintained; if an organization uses the name without conformance (detected via social media, publishing announcements, or direct report), the Stewardship Committee issues a public clarification or, if certification model is in force, withholds the mark and may issue a public statement that the variant is non-conforming.

Adaptation Trigger: A third party publicly labels a variant or material as 'Clear English' but the variant incorporates rule changes beyond the 10% divergence threshold (proposed) or omits required core rules; a significant non-conforming fork is discovered (detected via web search, standards-body inquiry, or third-party report) suggesting that the 'Clear English' name is being applied to non-standardized material, creating confusion; the Stewardship Committee receives >3 inquiries or complaints in a quarter about non-conforming use of the name; an offline publisher or organization uses the name in printed material without seeking conformance review and the Stewardship Committee learns of it via partner or standards-body feedback; an open-source project or crowdsourced variant emerges that claims Clear English affiliation but diverges significantly from the published standard.

Governance Extra

Governance Validation Checks

  1. Completeness: All core governance components are defined (Editorial Board Charter, Steering Committee Charter, Metrics & Validation Committee Charter, Compliance & Risk Management Committee Charter, escalation matrix, monitoring framework, implementation plan). Governance bodies span rule specification (Editorial Board), strategic oversight (Steering Committee), measurement credibility (Metrics & Validation Committee) and risk/compliance management (Compliance & Risk Management Committee). Decision authority and escalation paths are explicitly mapped. The framework covers all three phases and includes post-Phase-3 stewardship planning (Standards Stewardship Committee, steward identification by Month 33 = 2029-07-13). One core gap: the role and decision authority of the ultimate Project Sponsor (external funding body) is mentioned in Phase 3 implementation but not formally chartered; clarify escalation from Steering Committee to Sponsor for strategic disputes or go/no-go outcome challenges.
  2. Internal Consistency: Rule decisions (Editorial Board) feed into measurement design (Metrics & Validation Committee pre-registers ordinal-error-rate and pronunciation-consistency scoring rubrics tied to finalized rules by Month 11 = 2027-09-13). Pilot recruitment (Compliance & Risk Management Committee and Stakeholder Engagement Lead) is contingent on partner commitments signed by Month 3 (2027-01-13) and ethics approval by Month 6 (2027-04-13), both tracked against timelines. Budget monitoring (Finance Lead, Steering Committee monthly reviews) enforces the $175K pre-gate contingency cap and flags overruns for escalation. Timeline and critical-path tracking (Project Lead, Steering Committee) monitor sequential dependencies (rules Month 12 = 2027-10-13, audio Month 11 = 2027-09-13, pre-registration Month 11 = 2027-09-13, recruitment Month 13 = 2027-11-13, data lock Month 22 = 2028-08-13, gate Month 24 = 2028-10-13). Escalation matrix specifies approval processes and negative consequences for each risk type. No detected logical conflicts; however, the adaptive mechanisms (e.g., how the board proceeds if Arbiter recommendation is rejected, how Phase 1 extension is funded if kappa<0.70) could be more explicit in terms of decision authority and contingency funding draw procedures.
  3. Clarity of Roles and Authority: Editorial Board chair and Steering Committee chair are identified as distinct roles. Editorial Board linguist members hold formal veto authority, limited to rule ambiguity and contradiction findings (not rule substance). Metrics & Validation Committee operates at 'arm's length' from Editorial Board and Steering Committee to maintain measurement independence. Project Sponsor role is mentioned for escalation but is not formally chartered; the Sponsor's approval authority for reserve draws >$175K, Phase extensions, and major scope changes should be explicitly documented in a Sponsor Charter by Month 0 (2026-10-13). Conflict-of-interest disclosure procedures are specified (Editorial Board Charter, attestations collected by Month 1 = 2026-11-13), but no described mechanism for handling conflicts (e.g., if an Editorial Board member's institution benefits from a rule decision). Stakeholder Engagement Lead and Educator Liaison roles are defined with clear responsibilities (partner engagement, corrective outreach), but their authority to modify pilot protocols or messaging without Steering Committee approval is unclear; specify delegation limits.
  4. Process Depth and Operational Clarity: Rule-finalization process is detailed (subcommittees biweekly Months 2-10 = 2026-12-13 to 2027-08-13, Linguistic Review Panel monthly vetting, escalation to Arbiter for deadlock, 30-day public comment Month 11-12 = 2027-09-13 to 2027-10-13, v1.0 lock Month 12 = 2027-10-13), with decision-logging discipline. Gate metric design includes construct-validity analysis and pre-registration (Months 4-5 = 2027-02-13 to 2027-03-13 literature review and expert panel, validity study Months 10-11 = 2027-08-13 to 2027-09-13, pre-analysis plan finalization Month 11 = 2027-09-13, registration by Month 11.5 = 2027-09-28 proposed). However, three operational processes need more detail: (a) Conflict-of-interest management: no procedure specified for what happens if an Editorial Board member's employer benefits from a rule decision or if a Steering Committee member has financial stake in ESL publishing; (b) Whistleblower or ethics-violation reporting: no designated reporting channel or investigation procedure if misconduct (data manipulation, participant coercion, unauthorized audio use) is alleged; (c) Change-control post-v1.0: the decision specifies 'v1.0 frozen 12 months' but does not detail how errata will be identified, approved and communicated; specify errata-review procedure and timeline.
  5. Process Completeness: Gaps identified in three areas: (1) Quantitative Gate Thresholds: The four metrics (ordinal error rate ≥25% reduction, comprehension speed ≤10% slower, pronunciation consistency ≥15% above control, 30-day retention ≥70%) are named and loosely specified with proposed thresholds, but the complete pre-analysis plan (including statistical test type, sample-size power analysis calculation, primary vs. secondary outcome hierarchy, intention-to-treat rules, missing-data imputation procedures, effect-size interpretation guidance) must be drafted by Month 5 (2027-03-13), externally peer-reviewed by Month 5.5 (2027-03-28), and locked by Month 11 (2027-09-13) before pre-registration. The canonical facts document specifies the thresholds but does not reference the underlying power analysis or effect-size assumptions; confirm that the $150K-$200K (estimate) psychometrics budget includes power analysis, effect-size justification studies and post-hoc sensitivity analysis. (2) Construct-Validity and Confound Controls: The implementation plan specifies 'detailed construct-validity literature review' (Month 4 = 2027-02-13) and 'expert-panel discussion' (Month 4 = 2027-02-13) but does not describe how confounds (repeated exposure, learner motivation, accent proximity) will be operationalized or measured in the pilot; detail the control-condition design (e.g., standard-English ordinals with explicit rule instruction vs. implicit exposure) and manipulation-check procedures (e.g., post-test questions asking learners which rule system they learned) in the pre-analysis plan. (3) Data Integrity and Consent Escalation: The Compliance & Risk Management Committee monitors data-protection compliance, but the framework does not specify a formal data-privacy incident-response procedure (who investigates, timeline, notification of affected participants, regulatory reporting); draft a written Data-Privacy Incident Response Plan by Month 4 (2027-02-13) and include it in the IRB protocol.
  6. Potential Gaps Requiring Clarification: (a) Project Sponsor Role: The Sponsor (external funding body representative or senior institutional leader) is mentioned as having authority to approve reserve draws >$175K and to make final decisions on Phase extensions or project termination, but is not formally chartered. Draft a Project Sponsor Charter by Month 0 (2026-10-13) specifying escalation thresholds (e.g., Sponsor approval required for budget increases >$300K, timeline extensions >8 weeks, scope reductions >15%), decision timeline (e.g., Sponsor must decide within 10 business days of escalation), and communication protocol (monthly reporting, ad-hoc escalation alerts). (b) Delegation Below Committee Level: The framework grants authority to committee chairs (Editorial Board Chair, Psychometrician as Metrics & Validation Committee Chair, Compliance & Risk Management Committee Chair, Project Lead) but does not specify whether these chairs can make routine operational decisions (e.g., can the Psychometrician hire a research assistant without Steering Committee approval? Can the Project Lead approve a $20K curriculum-design invoice without Finance Lead sign-off?) Define delegation authority thresholds (e.g., <$25K spending, <2-week timeline impact, routine operational decisions delegated to committee chairs; >$50K or strategic decisions require Steering Committee approval). (c) Standards Stewardship Committee Transition: The frame work specifies that a Standards Stewardship Committee will be established by Month 30 (2029-04-13) post-Phase-3, but the relationship between the Phase 1-3 Editorial Board and the post-Phase-3 Stewardship Committee is unclear. Will Editorial Board members serve on the Stewardship Committee? Will there be a formal transition meeting and knowledge-transfer protocol? Will the same decision-logging and conflict-resolution procedures apply post-Phase-3? Specify a Stewardship Committee Charter (to be finalized by Month 30 = 2029-04-13) that documents governance continuity and transition procedures.

Tough Questions

  1. Gate Metrics Credibility: By Month 11 (2027-09-13), can the Psychometrician and Metrics & Validation Committee certify that the four gate metrics (ordinal error rate ≥25% reduction, comprehension speed ≤10% slower, pronunciation consistency ≥15% above control, 30-day retention ≥70%) are grounded in a defensible power analysis (≥80% power at α=0.05), that the sample size target (≥80 completers per arm) is justified and achievable by data lock (Month 22 = 2028-08-13), and that inter-rater reliability is calibrated to kappa ≥0.70 floor? What assumptions underlie the ≥25% ordinal-error-reduction threshold—is it based on benchmarking against other language-learning interventions, or is it a consensus judgment of the Editorial Board, and if the latter, what is the evidentiary basis?
  2. Rule Finalization and Ambiguity: By Month 11 (2027-09-13), will the Editorial Board publish a complete, non-ambiguous Clear English Standard v0.1 that specifies the ordinal marker symbol, its spoken pronunciation, the morphology retention cutoff with a published list of retained vs. regularized forms, the homograph-pair list with enforcement policy per pair, and the core-lexicon specification with coverage audit showing ≥85% coverage of pilot running text? If the Editorial Board cannot finalize all core rules without escalation to the external Arbiter, what is the timeline for Arbiter resolution, and does it still permit the 30-day public comment window before Month 12 (2027-10-13) v0.1 publication?
  3. Construct Validity of Gate Metrics: What explicit control conditions and manipulation checks will be embedded in the Phase 2 pilots to isolate Clear English effects from alternative explanations (repeated exposure to ordinals, learner motivation to participate in a 'novel standard' study, accent proximity to learners' first language, baseline literacy differences)? By Month 5 (2027-03-13), will the Psychometrician publish a detailed construct-validity section of the pre-analysis plan that documents how each confound is measured and how the primary analysis will control for it (e.g., via regression, matching, or stratified analysis)?
  4. Pilot Recruitment and Retention Evidence: By Month 3 (2027-01-13), what are the signed, written enrollment commitments from 3-4 adult ESL programs and 2-3 technical/safety-training organizations, and what does each commitment document (per-learner guarantee, payment terms, educator training, retention incentives, dropout tolerance)? By Month 13 (2027-11-13), what is the actual enrollment vs. the ≥115 per arm target, and if shortfall is >15%, what is the contingency plan (additional recruitment sites, extended enrollment period, Phase 2 timeline extension) and associated cost within the $175K pre-gate contingency cap?
  5. Budget and Timeline Discipline: At the Month 9 (2027-07-13) Phase 1 spending review, what is the actual cumulative spend vs. the $1.1M Phase 1 budget allocation, and what is the 6-month forecast for Phase 2 spending (Month 9-14 = 2027-07-13 to 2027-12-13)? If Phase 1 spend is >10% over or <10% under budget, what is the root cause and what reallocation is recommended to maintain the $175K pre-gate contingency cap intact? If Phase 2 forecast indicates a $300K overrun (8.6% of total budget), what scope reduction is proposed—fewer pilot cohorts, smaller assessment battery, or Phase 1 extension deferral?
  6. Measurement Inter-Rater Reliability Assurance: By Month 11 (2027-09-13), after rater training and the calibration study (Months 10-11 = 2027-08-13 to 2027-09-13), will Cohen's kappa for pronunciation-consistency scoring and ordinal-error scoring meet the ≥0.75 (proposed) target and exceed the 0.70 floor across all rater pairs? If any rater pair falls below 0.70 after the initial 2-week retraining window (Month 10-11 = 2027-08-13 to 2027-09-13), what is the evidence that a 4-week Phase 1 extension (~$85K cost) will remediate the reliability gap, and by what date must kappa be confirmed ≥0.70 (proposed: Month 12 = 2027-10-13) to permit Phase 2 green light?
  7. Educator Engagement and Pushback Signals: By Month 6 (2027-04-13), what baseline metrics establish educator and standards-body sentiment on Clear English (e.g., survey of TESOL members, social-media sentiment analysis, direct interviews with 10-15 curriculum directors)? By Month 18 (2028-04-13), what is the change in sentiment, and what threshold of increase in critical feedback (>20% negative mentions, loss of a major partner commitment, a published TESOL or IATEFL position statement expressing concern) would trigger the 'educator pushback' escalation procedure to the Steering Committee and corrective outreach?

Summary

The Clear English program is a moderately ambitious, evidence-gated, 36-month language-standardization initiative ($3.5M user constraint) spanning rule specification, pilot validation and public release. The governance framework—comprising a practitioner-leaning Editorial Board, an independent Metrics & Validation Committee, a Steering Committee with escalation authority, and a Compliance & Risk Management Committee—is comprehensive and well-structured to manage critical dependencies: rule clarity (Month 12 = 2027-10-13 lock), measurement credibility (pre-registered metrics by Month 11 = 2027-09-13), pilot recruitment and retention (460 learners across 4 arms), and post-launch stewardship (commitment sought by Month 33 = 2029-07-13). The framework prioritizes adoption-first, evidence-based decision-making, with clear escalation paths for rule deadlock, budget overruns, measurement threats and stakeholder pushback. Key strengths include pre-registration discipline, independent validity oversight, and explicit governance charters. Critical remaining gaps are quantitative gate thresholds (must be finalized and pre-registered by Month 11 = 2027-09-13), construct-validity control procedures, stewardship funding security (currently unfunded), and clear contingency procedures if critical path items slip or validity falls short of standards.

1. Gate Metrics Pre-Registration and Psychometric Validation

The go/no-go decision at Month 24 (2028-10-13) is the project's only gate. Weak, un-justified, or post-hoc thresholds render the gate scientifically disputable and risk adopter rejection (20-50% adoption loss). Pre-registration by Month 11 (2027-09-13) locks thresholds before data collection begins, foreclose post-hoc critique and establish external credibility with standards bodies, educators and regulators.

Data to Collect

Simulation Steps

Expert Validation Steps

Responsible Parties

Assumptions

SMART Validation Objective

By Month 11 (2027-09-13), deliver a pre-analysis plan with numeric, empirically justified thresholds for all four gate metrics, registered on Open Science Framework with board sign-off and third-party reviewer attestation. Measurable: plan specifies exact threshold values (e.g., ordinal error ≥25%), sample size with power analysis, and decision rules. Achievable: validity study (N=30) and inter-rater calibration (N=3-4 raters) completed by Month 10 (2027-08-13). Relevant: ensures Month 24 (2028-10-13) gate is defensible and not disputable. Time-bound: registration deadline Month 11 (2027-09-13), 5 weeks before Phase 2 start (Month 13 = 2027-11-13).

Notes

2. Pilot Partner Commitments and Recruitment Feasibility

Pilot recruitment failure (missing 115 per arm by Month 13 = 2027-11-13 or dropout >30%) reduces final sample to <80 per arm, cutting statistical power by 10-25% and risking false-negative gate outcomes that waste $1.2M Phase 2 spend. Signed partner commitments, baseline-study data, and early cohort-manager engagement reduce recruitment risk and provide early warning signals for course correction (by Month 10 = 2027-08-13, not Month 22 = 2028-08-13 when recovery is impossible).

Data to Collect

Simulation Steps

Expert Validation Steps

Responsible Parties

Assumptions

SMART Validation Objective

By Month 3 (2027-01-13), secure signed Memoranda of Understanding from ≥3 ESL programs and ≥2 technical-training organizations guaranteeing ≥50 learners per partner (≥300 total estimate) with explicit penalty clauses and enrollment deadlines. By Month 13 (2027-11-13), confirm ≥115 per arm (460 total) enrolled across all partners. Measurable: enrollment tracking dashboard shows cumulative enrollments and dropout-to-date by site and cohort. Achievable: recruitment baseline study (Months 1-2 = 2026-11-13 to 2026-12-13) validates feasibility of 30% dropout tolerance with incentives. Relevant: ensures pilot sample size meets ≥80-per-arm power requirements. Time-bound: baseline study and MOU signing by Month 3 (2027-01-13); interim milestones Month 8, 10 (2027-06-13, 2027-08-13); enrollment completion Month 13 (2027-11-13).

Notes

3. Editorial Board Governance and Rule Specification Consensus

Rule ambiguity, deadlock or mid-pilot changes invalidate pilot assessment results (learners trained on conflicting rule versions, inter-rater scoring of pronunciation is inconsistent). Explicit governance (voting procedures, arbiter mechanism, decision logging) enables rapid dispute resolution (target <4 weeks per dispute) and locks rules by Month 12 (2027-10-13) so pilots begin with stable, published rules. Public comment and transparent rule rationale build educator and standards-body confidence in legitimacy.

Data to Collect

Simulation Steps

Expert Validation Steps

Responsible Parties

Assumptions

SMART Validation Objective

By Month 1 (2026-11-13), publish Editorial Board Charter. By Month 2 (2026-12-13), hold first board meeting with all 7-9 members; assign rule-specification workstreams. By Month 10 (2027-08-13), finalize all five rule specifications (ordinal, G2P, morphology, homograph, accent) and publish a decision log documenting voting outcomes and minority positions. By Month 11 (2027-09-13), publish draft standard for 30-day public comment. By Month 12 (2027-10-13), lock all rules, close comment window, and issue rule-freeze notice. Measurable: decision log shows <4-week dispute resolution (voting or arbiter), 100% rule clarity score ≥3.5 from independent linguists. Achievable: board members meet monthly, arbiter available by Month 5 (2027-03-13). Relevant: stable rules by Month 12 (2027-10-13) enable consistent pilot protocol application. Time-bound: rule-freeze Month 12 (2027-10-13), 30 days before Phase 2 start (Month 13 = 2027-11-13).

Notes

4. Audio Production, Inter-Rater Calibration, and Pronunciation Consistency Measurement

Pronunciation consistency is a primary gate metric (kappa ≥0.70 floor, ≥0.75 target proposed). Weak inter-rater reliability (kappa <0.70) inflates measurement error by 20-30%, reducing statistical power to detect Clear English effects and risking false-negative gate outcomes that waste Phase 2 investment and kill the project. Audio production bottleneck: if recording is delayed or rater calibration fails, the Phase 1 exit gate (Month 12 = 2027-10-13) is missed and Phase 2 is compressed. Pronunciation guidance (the overlay on print) is a core deliverable: without usable audio, the overlay cannot be taught or assessed.

Data to Collect

Simulation Steps

Expert Validation Steps

Responsible Parties

Assumptions

SMART Validation Objective

By Month 3 (2027-01-13), finalize reference-accent anchor specification with exemplar recordings. By Month 4 (2027-02-13), recruit and begin training 4-6 candidate raters. By Month 10 (2027-08-13), measure inter-rater Cohen's kappa on a 100-200 word pilot sample and confirm kappa ≥0.70 across all raters. By Month 11 (2027-09-13), complete full 5,000-word audio production (either human-recorded or synthetic baseline + verification). Measurable: kappa ≥0.70 documented for each rater pair; all 5,000 lexicon entries have 2+ usable pronunciation audio files; encrypted storage deployed and audit-passed. Achievable: studio capacity confirmed by Month 2 (2026-12-13); rater training timeline 2-3 months (Months 8-10 = 2027-06-13 to 2027-08-13). Relevant: pronunciation guidance is a core project deliverable; audio reliability (kappa) determines gate-metric credibility. Time-bound: kappa confirmed by Month 10 (2027-08-13), 2 months before Phase 2 start (Month 13 = 2027-11-13), allowing 1-month remediation window if kappa <0.70.

Notes

5. Licensing, Name Stewardship, and Post-v1.0 Governance Sustainability

Post-Month-36 (2029-10-13) stewardship is unfunded ($150K-$250K/year estimate) and no permanent steward is committed yet. Without stewardship, the standard will atrophy: change requests accumulate unanswered, errata go unfixed, adopter confidence erodes, and Phase 3 adoption collapses by 30-50% within 24 months (by Month 60 = 2031-10-13). Licensing terms (permissive vs. certification-mark) determine whether third-party materials are clearly flagged as conforming or non-conforming, affecting fragmentation risk. Early steward search (by Month 18 = 2028-04-13) and binding commitment (by Month 33 = 2029-07-13) ensure v1.0 is not released without a sustainable governance plan. Public clarity on licensing and stewardship builds adopter confidence that the standard will be maintained long-term.

Data to Collect

Simulation Steps

Expert Validation Steps

Responsible Parties

Assumptions

SMART Validation Objective

By Month 6 (2027-04-13), publish Licensing and Name Stewardship Policy and hold a board vote to select the final model. By Month 12 (2027-10-13), publish conformance checklist (if certification-mark model) on project website. By Month 18 (2028-04-13), approach 2-3 steward candidates with RFI and request letters of interest by Month 24 (2028-10-13). By Month 33 (2029-07-13), secure a signed MOU with a committed steward specifying funding source, annual budget ($150K-$250K), governance structure, and 10+ year commitment. By Month 30 (2029-04-13), publish v1.0 only with stewardship MOU in hand and published Stewardship Roadmap. Measurable: licensing policy and conformance checklist published; steward identity and MOU commitments published with v1.0. Achievable: 3-month legal analysis (Months 1-3 = 2026-11-13 to 2027-01-13); 6-month steward identification and RFI (Months 12-18 = 2027-10-13 to 2028-04-13); 6-month MOU negotiation (Months 27-33 = 2029-01-13 to 2029-07-13). Relevant: stewardship is a prerequisite for v1.0 credibility; permanent funding ensures long-term standards maintenance and adopter confidence. Time-bound: stewardship MOU signed before v1.0 release (Month 33 = 2029-07-13 before Month 30 = 2029-04-13 is impossible, so MOU must be negotiated and signed by Month 30 = 2029-04-13, shifting RFI/interest solicitation earlier to Months 12-15 = 2027-10-13 to 2028-01-13).

Notes

Summary

Clear English is a 36-month, $3.5M language-standardization initiative (three gated phases) aimed at adult ESL, technical writing and safety-critical documentation. This data-collection and validation plan identifies the five most critical data domains: (1) Gate Metrics Pre-Registration (highest risk: weak thresholds render the Month 24 = 2028-10-13 go/no-go disputable; mitigation: hire independent psychometrician by Month 2 = 2026-12-13, deliver power analysis by Month 5 = 2027-03-13, pre-register by Month 11 = 2027-09-13); (2) Pilot Partner Commitments and Recruitment (highest risk: sample-size shortfall <80 per arm invalidates statistical power; mitigation: conduct recruitment baseline study Months 1-2 = 2026-11-13 to 2026-12-13, secure signed MOUs by Month 3 = 2027-01-13, hire cohort manager by Month 4 = 2027-02-13); (3) Editorial Board Governance and Rule Specification (highest risk: rule deadlock or ambiguity delays Phase 2 or invalidates pilots; mitigation: publish charter by Month 1 = 2026-11-13, hold first meeting Month 2 = 2026-12-13, resolve disputes via external arbiter by Month 10 = 2027-08-13, freeze rules by Month 12 = 2027-10-13); (4) Audio Production and Inter-Rater Calibration (highest risk: kappa <0.70 at Month 10 = 2027-08-13 forces 4-week extension or scope reduction; mitigation: lock studio contract by Month 2 = 2026-12-13, recruit raters by Month 4 = 2027-02-13, conduct kappa calibration by Month 10 = 2027-08-13, pivot to hybrid synthesis if needed); (5) Licensing and Post-v1.0 Stewardship (highest risk: unfunded stewardship post-Month-36 causes standard atrophy within 24 months, reducing Phase 3 adoption by 30-50%; mitigation: publish licensing policy by Month 6 = 2027-04-13, identify steward candidates by Month 18 = 2028-04-13, secure signed MOU by Month 33 = 2029-07-13, make stewardship a v1.0 release prerequisite). Each domain specifies simulation steps (tools, pilot testing, cost modeling), expert-validation steps (independent review, pre-registration, board approval), SMART objectives (measurable, time-bound deliverables), and critical assumptions with sensitivity scores. The validation plan ensures the project meets its 'adoption-first, evidence-gated' positioning by locking gate thresholds early (pre-registered by Month 11 = 2027-09-13), recruiting defensible pilot samples on schedule, resolving governance ambiguity before rule-locking, and securing stewardship before v1.0 release. Key uncertainties flagged: pronunciation consistency kappa achievability in a constructed-language context (no published benchmark), steward-organization availability at $150K-$250K/year (unfunded gap post-project), and educator/standards-body acceptance of the adopted licensing and governance model. Immediate actionable tasks: (1) hire independent psychometrician by Month 2 (2026-12-13); (2) identify and approach 4-5 ESL programs and 2-3 technical organizations by Month 1 (2026-11-13); (3) publish Editorial Board Charter and hold first meeting by Month 2 (2026-12-13); (4) lock studio contract and recruit 4-6 raters by Month 4 (2027-02-13); (5) identify steward candidates and begin preliminary outreach by Month 12 (2027-10-13).

Documents to Create

Create Document 1: Project Charter

ID: 45622232-b1ca-478f-84a7-9d0c7b8650af

Description: Foundational project governance document specifying the Clear English Standard program scope (36-month, 3-phase, $3.5M fixed budget), go/no-go gate at Month 24 (2028-10-13), primary deliverables (v1.0 standard, dictionary, style guide, pilot curriculum), stakeholder roles, success criteria, and approval authorities. Intended audience: editorial board, funding bodies, institutional partners.

Responsible Role Type: Project Manager / Program Director

Primary Template: PMI Project Charter Template

Secondary Template: PRINCE2 Project Initiation Document

Steps to Create:

Approval Authorities: Program Sponsor, Editorial Board Chair, Project Lead

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: The Project Charter fails to specify binding gate thresholds, authority rules or contingency procedures. During Phase 1, rule disputes on ordinal design and morphology retention deadlock the editorial board for 8 weeks, compressing Phase 2 pilots by 67% and triggering a 4-week Phase 1 extension ($85K estimate draw). Psychometric validation is incomplete; inter-rater reliability falls to kappa 0.60 instead of target 0.75, and no construct-validity framework is in place, leaving confounds uncontrolled. Pilot recruitment falls short: only 60 completers per arm (below the 80-completer power target estimate) due to missed partner commitments and unclear adoption messaging. By Month 24 (2028-10-13), data are inconclusive; ordinal error reduction is 18% (below the 25% proposed threshold), and pronunciation consistency metric is noisy (kappa 0.60). The board cannot decide: the charter does not specify how to resolve a borderline gate outcome, and stakeholders dispute whether the metrics were adequate. An extension is declared, pushing Phase 2 to Month 30 (2029-04-13) at $300K cost (estimate), exhausting the reserve and consuming unallocated Phase 3 funds. By Month 30 (2029-04-13), stewardship funding is still unfunded, educator pushback has mounted and competing standards have emerged. The program releases a v1.0 with no committed steward, limited third-party adoption, and reputation damage. By Month 48 (2030-10-13), the standard has atrophied and adoption has stalled at ~5,000 learners instead of the 100,000+ feasible under a credible, timely gate and steward commitment.

Best Case Scenario: The Project Charter clearly specifies scope, phase gates, metrics thresholds and decision authority, adopted by Month 1 (2026-11-13) and signed by the Program Sponsor and Editorial Board Chair. The charter guides tight Phase 1 execution: rules are finalized by Month 10 (2027-08-13), metrics are pre-registered with explicit thresholds by Month 11 (2027-09-13), and audio production completes on time and budget ($80K–$120K estimate). Pilot recruitment hits targets: ≥115 per arm enrolled by Month 13 (2027-11-13), with ≥80 completers per arm retained through follow-up (70%+ retention estimate). Purpose-built assessments with kappa ≥0.75 inter-rater reliability and clear construct-validity frameworks generate clean, defensible data. By Month 24 (2028-10-13), the gate decision is unambiguous: all four metrics meet pre-registered thresholds; ordinal error reduction is 28% (above the 25% proposed threshold), comprehension speed is 8% slower (within the 10% proposed limit), pronunciation consistency is 18% above control with kappa 0.77, and 30-day retention is 73% (above the 70% proposed threshold). The board issues a clear GO decision, releasing the full $0.35M reserve. By Month 30 (2029-04-13), v1.0 is released with a committed steward organization and clear post-project governance roadmap. Phase 3 adoption accelerates: ≥5 licensed third-party adopters (target ≥3 proposed) are in place by Month 36 (2029-10-13), including 2 major ESL publishers, 1 technical standards body, and 2 safety-training organizations. Learner reach reaches ~30,000–50,000 by Month 36 (2029-10-13), with strong evidence and positioning for future expansion. The standard achieves credibility and stability, supporting 10–15 year sustainability under funded stewardship.

Fallback Alternative Approaches:

Create Document 2: Editorial Board Charter and Governance Framework

ID: 46f4c8a2-aedf-4c93-bdfd-f4efff63255c

Description: Formal document establishing editorial board composition, voting rules, conflict-of-interest disclosure, tiebreak-arbiter selection process, decision-logging requirements, and rule-finalization timeline. Specifies how disputed rule decisions (ordinal, morphology, homographs, accent) are escalated and resolved. Audience: editorial board members, project team, external stakeholders seeking legitimacy.

Responsible Role Type: Project Manager / Governance Administrator

Primary Template: ISO/TC 37 Language and Terminology Committee governance templates

Secondary Template: ASD-STE100 Maintenance Group procedures

Steps to Create:

Approval Authorities: Editorial Board Chair, Program Sponsor

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: Editorial board disputes over rule design (ordinal marker form, morphology regularization scope, homograph markers) remain unresolved through Month 10–12 (2027-08-13 to 2027-10-13) due to ambiguous voting rules and no tiebreak mechanism. As a result, rules are either locked in ambiguous form or withheld pending further discussion, compressing Phase 2 pilots from 12 to 8–10 months. Compressed pilots shrink to fewer cohorts or shorter follow-up periods, reducing statistical power and measurement reliability (kappa drops below the 0.70 floor). The Month 24 (2028-10-13) go/no-go decision rests on inconclusive or noisy data, forcing either an extension (Phase 2 stretches to Month 30–36 = 2029-04-13 to 2029-10-13, consuming up to $600K (estimate) and stranding Phase 3 funding) or a disputed gate outcome that educators and standards bodies reject. Long-term credibility is damaged, and adoption stalls at 5,000–10,000 learners instead of the target 50,000+.

Best Case Scenario: Editorial board charter with clear voting (simple majority, quorum 6 of 9), linguist veto limited to ambiguity findings, and a pre-agreed external arbiter is published by Month 1 (2026-11-13). Rule disputes are documented transparently: majority and minority positions appear in the published rationale, so contested rules are defensible and stakeholders understand the trade-offs. Workstream owners meet deadlines (Month 10 = 2027-08-13); arbiter is consulted for one or two technical questions, making a binding recommendation by Month 10 (2027-08-13). Rules are locked on schedule by Month 12 (2027-10-13), and the draft standard withstands the 30-day public-comment window without major rewrites. Phase 2 pilots proceed at full strength (460 enrolled, 80%+ completion rate), measurement is robust (kappa ≥0.75), and the Month 24 (2028-10-13) go/no-go decision is scientifically defensible. Educators and standards bodies perceive the charter as legitimate, reducing resistance and enabling Phase 3 partnerships and adoption.

Fallback Alternative Approaches:

Create Document 3: Outcome Metric Battery Design and Pre-Analysis Plan

ID: 95578caa-10a4-450b-8ef1-0fc637c2d8fc

Description: Detailed specification of four go/no-go metrics (ordinal error rate, comprehension speed, pronunciation consistency, 30-day retention) including measurement instruments, scoring procedures, control-group design, inter-rater reliability targets (kappa ≥0.70 floor, ≥0.75 target), sample-size justification via power analysis, pre-registered pass/fail thresholds, and intention-to-treat analysis rules. Independently reviewed by a psychometrician. Registered on Open Science Framework by Month 11 (2027-09-13). Intended for editorial board, external reviewers, and regulatory bodies.

Responsible Role Type: Psychometrician / Assessment Specialist

Primary Template: Open Science Framework pre-registration template (aspredicted.org or equivalent)

Secondary Template: APA Standards for Educational and Psychological Testing

Steps to Create:

Approval Authorities: Independent Psychometrician (lead author), Editorial Board (vote on thresholds), External Expert Reviewer

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: An underdeveloped pre-analysis plan with vague thresholds, weak instruments, and uncontrolled confounds leads to a disputed gate outcome at Month 24 (2028-10-13). If the gate passes but external reviewers later find the instruments were insensitive to Clear English effects or the thresholds were arbitrary, a false-positive outcome launches a standard that fails to deliver promised benefits, destroying adopter confidence and reducing Phase 3 adoption by 30–50%, capping learner reach at 15,000–35,000. If the gate fails but was driven by weak measurement rather than Clear English insufficiency, an equally damaging false-negative kills a viable initiative, stranding $1.2M–$1.4M (Phase 2–3 budget estimate) and requiring either a costly 6-month Phase 2 extension (~$300K, estimate) or a withdrawn standard. Either outcome triggers regulatory pushback, litigation risk if safety-critical pilots were conducted, and reputational damage that forecloses future language standardization initiatives in the field.

Best Case Scenario: A rigorous, pre-registered pre-analysis plan with quantitative, justified thresholds; validated instruments; inter-rater reliability kappa ≥0.75; explicit confound controls; and a validity study (Months 10–11 = 2027-08-13 to 2027-09-13) published by Month 11 (2027-09-13) enables a transparent, defensible Month 24 (2028-10-13) go/no-go decision. If the gate passes, the clear evidence base gives educators, publishers and standards bodies confidence to adopt Clear English, enabling Phase 3 launch with ≥3 licensed third-party adopters by Month 36 (2029-10-13) and a 10,000–50,000 learner reach. If the gate fails, the rigorous metrics and published thresholds allow stakeholders to trust the outcome, preventing fragmentation into unofficial variants and permitting an informed decision about revision or sunset. Either way, the credible evidence base becomes a model for other language-standardization initiatives and strengthens the case for evidence-gated linguistic innovation.

Fallback Alternative Approaches:

Create Document 4: Clear English Standard Specification v0.9 (Draft for Comment)

ID: 514a9a21-d20b-4eae-8c79-48f9e0170564

Description: Comprehensive draft rule set covering ordinal representation (prefix-marker notation + invariant spoken form), grapheme-to-phoneme mapping for core lexicon (pronunciation overlay guidance), morphology retention rules (irregular verbs/plurals threshold), homograph disambiguation policy (marker list + application rules), and accent-anchor specification (phonemic inventory + mapping to other varieties). Includes rationale, worked examples, exceptions, and change-control procedures. Published for 30-day public comment by Month 11 (2027-09-13). Intended for educators, publishers, standards bodies, and ESL professionals.

Responsible Role Type: Linguistic Specialist / Computational Linguist

Primary Template: ISO 639-5 Language Code standard template

Secondary Template: ASD-STE100 specification document format

Steps to Create:

Approval Authorities: Editorial Board (majority vote + tiebreak if needed), Public Comment Review Committee

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: A poorly specified draft (ambiguous rule triggers, missing thresholds, no worked examples, weak accent justification) is published at Month 11 (2027-09-13) for public comment. During the 30-day comment window, educators, publishers and standards bodies raise 15–30 substantive critiques (unclear morphology exceptions, homograph marker inconsistency, accent bias); the editorial board cannot resolve these disputes before Month 12 (2027-10-13) rule freeze, forcing either a publication of visibly flawed rules (damaging credibility) or a 4–8 week extension that compresses Phase 2 pilots by 33–67%, reducing statistical power and rendering the Month 24 (2028-10-13) go/no-go gate inconclusive. A failed or disputed gate decision strands $1.2M–$1.4M (Phase 2–3 budget estimate) and delays market entry to Month 36 (2029-10-13) or beyond, during which competing standards or initiatives may emerge and educator skepticism hardens, cutting Phase 3 adoption by 30–50%.

Best Case Scenario: A comprehensive, well-justified specification published by Month 11 (2027-09-13) with 30–50 worked examples per rule, explicit quantitative pass/fail thresholds for all four gate metrics, documented accent mappings, and published responses to all public comments. Educators, publishers and standards bodies receive a clear, defensible rule set that they can teach, audit and implement consistently. Pilot curricula closely follow the published rules, measurement noise is minimized, and the Month 24 (2028-10-13) go/no-go decision rests on unambiguous, pre-registered evidence. A positive gate outcome is accepted by educational partners, publishers secure early licensing commitments, and Phase 3 public release proceeds on schedule, enabling adoption by ≥3 third-party organizations by Month 36 (2029-10-13) and building the foundation for post-project stewardship and long-term standard stability.

Fallback Alternative Approaches:

Create Document 5: 5,000-Word Core Lexicon with Pronunciation Guidance

ID: 9cf52d63-45ad-4552-a0de-77bff7411467

Description: Ranked list of 5,000 English word types (4,500 frequency-led general vocabulary + 500 technical/safety block) with: frequency band and corpus source, part-of-speech and word sense (polysemy markers), pronunciation guidance (IPA-based or minimal respelling overlay notation), mapping to standard English equivalent, and notes on rule exceptions (e.g., irregular verbs retained). Coverage audit confirms ≥85% of pilot running text. Delivered with a companion Pronunciation Key (single reference-accent anchor specification + notation guide). Intended as input for dictionary, curriculum, and pilot materials.

Responsible Role Type: Linguistic Specialist / Lexical Semanticist

Primary Template: ISO 1087 Terminology Databases standard

Secondary Template: Merriam-Webster or Cambridge Dictionary lexicographic entry template

Steps to Create:

Approval Authorities: Linguistic Specialist (lead), Editorial Board (sign-off on coverage and exceptions)

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: Lexicon is delivered late (Month 15–18 = 2028-01-13 to 2028-04-13) with incomplete pronunciation guidance and <80% coverage. Pilot materials are designed using an out-of-date, partial lexicon. Pronunciation consistency scoring is delayed or unreliable (kappa 0.65), rendering the pronunciation metric non-credible at the Month 24 (2028-10-13) go/no-go gate. Editorial board disputes lexicon selection methodology as unrepresentative, calling the go/no-go outcome into question. Simultaneously, partners discover that key high-frequency words are missing, forcing curriculum designers to rework materials. The gate decision is delayed 6–12 months while the lexicon is revised, stranding $1.2M–$1.4M in Phase 3 funding and damaging stakeholder confidence in the standard's viability. Post-launch, third parties publish competing 'Clear English' lexicons with divergent word selections, fragmenting the standard.

Best Case Scenario: Lexicon is finalized by Month 10 (2027-08-13) with ≥85% coverage, full pronunciation guidance in IPA and overlay notation, and transparent, audited selection methodology published. Pronunciation recordings are complete, inter-rater reliability achieves kappa 0.77 (target ≥0.75 proposed), and pronunciation key is usable for pilot scoring and learner reference. Database is clean, sortable and integrated into curriculum-design tools and pilot assessment platforms, enabling educators and publishers to adopt it immediately. Coverage audit identifies 3–5 missing high-frequency words; targeted additions by Month 10 (2027-08-13) bring coverage to ≥87%, exceeding the ≥85% threshold (proposed). Editorial board approves the lexicon at Month 11 (2027-09-13), and it feeds directly into pilot materials, reducing curriculum-design rework by 40%. The lexicon's transparent methodology and public provenance support regulatory approval and publisher confidence. At Month 24 (2028-10-13), the pronunciation consistency metric is valid and credible, enabling a defensible go/no-go decision and Phase 3 adoption by ≥3 third-party organizations.

Fallback Alternative Approaches:

Create Document 6: Pronunciation Guidance System and Rater-Calibration Protocol

ID: 5915ff9b-fbd8-495b-a118-cbffa5cf01d4

Description: Complete specification of the single reference-accent anchor (chosen phoneme inventory, vowel quality conventions, exemplar recordings, mapping to other major English varieties). Includes pronunciation-notation system (IPA-based, minimal respelling, or hybrid) with rater-training manual and inter-rater reliability scoring rubric for the pronunciation-consistency metric. Specifies Cohen's kappa target (≥0.75) and floor (≥0.70), calibration procedure (100–200 word pilot sample), and retraining trigger. Designed so raters can achieve reliable pronunciation-consistency scoring by Month 10 (2027-08-13).

Responsible Role Type: Orthography & Phonetics Designer / Audio Production Manager

Primary Template: IPA Handbook or Pullum & Ladusaw Phonetic Symbol Unicode chart

Secondary Template: ESL pronunciation-teaching manual (e.g., Celce-Murcia, Brinton & Goodwin)

Steps to Create:

Approval Authorities: Audio Production Manager, Independent Psychometrician (kappa validation), Editorial Board

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: The Pronunciation Guidance System remains incomplete or ambiguous through Month 11 (2027-09-13): inter-rater kappa is 0.65 (below the 0.70 floor), the notation system is unclear, exemplars are missing, or the anchor-accent choice is challenged by stakeholders demanding multi-accent coverage. The editorial board cannot pre-register the pronunciation-consistency metric with confidence, forgoing the pre-analysis plan deadline. Phase 2 pilots proceed without reliable pronunciation scoring, inflating measurement noise by 20–30% (estimate) and making the pronunciation-consistency gate metric inconclusive at Month 24 (2028-10-13). The go/no-go decision becomes disputable; stakeholders claim the gate failed due to weak measurement rather than Clear English inadequacy, forcing a costly 3–6 month Phase 2 extension ($300K–$600K estimate) to re-collect and re-analyze pronunciation data. If the extension is rejected, a contested no-go outcome strands Phase 3 adoption and damages credibility among ESL publishers and standards bodies.

Best Case Scenario: The Pronunciation Guidance System is finalized by Month 11 (2027-09-13) with clear, documented specifications: a defensible reference-accent anchor (e.g., General American with explicit IPA mappings to other varieties), a hybrid notation system (IPA for raters, simplified overlay for learners), comprehensive rater training and a well-tested scoring rubric. Inter-rater kappa reaches 0.76 (target achieved) by Month 10 (2027-08-13), enabling confident pre-registration of the pronunciation-consistency metric with explicit pass/fail thresholds. Phase 2 pilots proceed with reliable pronunciation scoring, yielding clean, statistically powered results on the pronunciation-consistency gate metric by Month 22 (2028-08-13). The Month 24 (2028-10-13) go/no-go decision is defensible and not disputed; standards bodies and publishers accept the evidence, enabling Phase 3 public release and adoption by educational partners. The documented accent anchor and notation system become a reusable reference for future dialect or language extensions, multiplying the standard's value.

Fallback Alternative Approaches:

Create Document 7: Pilot Partner Memoranda of Understanding (MOUs)

ID: 7d530971-4d91-4e4d-8132-fc1488329beb

Description: Legally binding agreements with each pilot partner organization (ESL programs and technical/safety-training sites) specifying: minimum learner enrollment (≥50 per partner by Month 13 = 2027-11-13), assessment schedule (4 in-person/virtual sessions across Months 13–24 = 2027-11-13 to 2028-10-13), data-collection protocols (informed consent, audio recording, test administration), learner incentives ($50–$150 per learner estimate, breakdown by partner), partner payment terms ($30–$50 per session per learner estimate, or lump-sum), and penalty clauses (liquidated damages if recruitment shortfalls, make-up recruitment window by Month 15 = 2028-01-13, escalation contacts). Signed by Month 3 (2027-01-13).

Responsible Role Type: Project Manager / Regulatory Affairs Manager

Primary Template: University-Nonprofit Research Partnership Agreement template

Secondary Template: TESOL Program Partnership MOU template

Steps to Create:

Approval Authorities: Project Manager (legal review), Partner Organization Authorized Representative, Program Sponsor (budget commitment)

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: A partner organization signs an MOU without clear enrollment commitments or liability disclaimers, then either enrolls only 25 learners (33% below target) and claims force majeure, or uses Clear English materials in a safety-critical operational procedure without approval, causing a participant injury or near-miss. The project faces simultaneous crises: insufficient pilot data (fewer than 80 completers per arm, invalidating the go/no-go gate), a liability claim or regulatory investigation, partner withdrawal from the study, and reputational damage from the safety incident. The Month 24 (2028-10-13) gate decision is postponed 6+ months while the project remediates and re-recruits, Phase 2 extends into Month 30–36 (2029-04-13 to 2029-10-13), and Phase 3 launch is delayed to Month 42 (2030-04-13) or cancelled, stranding $1.2M–$1.5M in unspent Phase 3 and reserve funds.

Best Case Scenario: All MOUs are signed by Month 3 (2027-01-13) with unambiguous enrollment targets (≥50 per partner, 4–5 partners total = 200–250 learners across ESL and technical cohorts), clear assessment schedules integrated into partner-institution course calendars, and signed liability disclaimers that prevent unauthorized use. Partners and learners comply fully with protocols; dropout stays at or below the 30% proposed threshold; inter-rater reliability and data quality exceed targets (kappa 0.80+). All 4 assessment sessions complete on schedule by Month 24 (2028-10-13), 30-day follow-up data is complete, and all gate metrics meet or exceed thresholds. The Month 24 (2028-10-13) go/no-go decision is unambiguous and fully defended; Phase 3 launch occurs by Month 30 (2029-04-13) as planned; partner organizations become early adopters and testimonials, credibility with educators and standards bodies is established, and steward organizations express serious interest.

Fallback Alternative Approaches:

Create Document 8: Data Protection and Privacy Policy

ID: b3a58520-c73f-4e3b-90b2-ac9c14faa57d

Description: Comprehensive GDPR and US state law-compliant document specifying: data types collected (pronunciation audio, test scores, demographics), collection purpose (pilot measurement for gate metrics), lawful processing grounds (participant consent + research exemption), retention periods (audio 3 years post-analysis; scores 5 years for replication; consent forms 3 years minimum), access controls (authorized team members only, signed data-use agreements), encryption standards (AES-256 or equivalent, FIPS 140-2 validated), backup and disaster-recovery procedures, participant rights (access, correction, deletion within 30 days), breach-notification protocol, and Data Protection Impact Assessment summary (GDPR Article 35). Published alongside informed-consent forms. Audience: research participants, ethics committees, data-protection authorities.

Responsible Role Type: Data Protection Officer / Legal Counsel

Primary Template: GDPR Data Protection Policy template (ICO or national equivalents)

Secondary Template: US University IRB research-participant privacy policy template

Steps to Create:

Approval Authorities: Data Protection Officer (lead author), Institutional Review Board (ethics approval), Legal Counsel (GDPR/state law compliance), Project Lead (finalization)

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: A privacy breach of pronunciation audio (e.g., server misconfiguration exposing unencrypted files or unauthorized access via compromised credentials) is discovered at Month 16 (2028-02-13) mid-pilot. Notification and investigation delays trigger GDPR Article 33 violations; regulators (ICO, US state AG) launch enforcement action; participants and data-protection advocates publicize the breach; the project's credibility is damaged; ethics boards halt Phase 2 pilots pending remediation (3–6 month delay); liability litigation from affected participants ensues. Concurrently, inadequate informed consent (discovered during ethics-board audit) invalidates pilot data, forcing a Phase 2 restart or no-go at the Month 24 (2028-10-13) gate. Combined impact: pilot data unusable, gate decision delayed or failed, Phase 2–3 timeline and budget (estimated $2M–$2.05M) at risk, and public trust in Clear English permanently damaged. Scenario likelihood: low (security and consent breaches are preventable with diligent early planning); impact: extremely high (existential to project credibility).

Best Case Scenario: By Month 1 (2026-11-13), a comprehensive DPIA and ethics-compliant protocols are drafted and approved by the relevant ethics board and data-protection authority by Month 6 (2027-04-13). Encryption, access controls, and breach-notification procedures are implemented and audited by Month 8 (2027-06-13). Clear, multilingual informed-consent forms are published on the project website by Month 8 (2027-06-13) and provided to all 460+ pilot participants at enrolment. Participant deletion requests and withdrawal are processed within 30 days with written confirmation. Phase 2 pilots proceed without ethics or privacy delays, all 460 participants are recruited and retained (70%+ follow-up), and the gate decision at Month 24 (2028-10-13) rests on uncontested, legally defensible data. The Privacy Policy and DPIA become model documentation for ESL and language-education research; regulatory authorities and ethics boards treat Clear English pilots as a benchmark for ethical data handling in education research. Phase 3 adoption is accelerated by demonstrated compliance and participant trust. Public credibility is enhanced; third-party educators and standards bodies view the project as trustworthy stewards of sensitive learner data.

Fallback Alternative Approaches:

Create Document 9: Pilot Recruitment and Retention Plan

ID: a448d45e-112a-47b5-aea4-39df5b421c54

Description: Operational plan specifying recruitment targets (≥115 enrolled per arm = 460 total by Month 13 = 2027-11-13), recruitment strategy per partner (marketing channels, eligibility criteria, enrollment milestones), learner incentive structure ($50–$150 per learner estimate, breakdown), partner payment terms ($30–$50 per session estimate or lump-sum), dropout-risk mitigation (incentives, flexible scheduling, peer cohorts, make-up sessions within ±1 week), and monthly retention tracking (dashboard showing % enrolled, dropout-to-date, projected completers). Probabilistic enrollment model with 50th/75th/90th percentile scenarios based on pilot baseline study (Months 1–2 = 2026-11-13 to 2026-12-13). Includes escalation protocol: if enrollment misses interim milestones by >2 weeks, activate acceleration tactics (increased incentives, evening sessions, $20K–$30K budget).

Responsible Role Type: Phase 2 Cohort Manager / Recruitment Specialist

Primary Template: TESOL Adult ESL Program recruitment and retention toolkit

Secondary Template: National Institutes of Health (NIH) recruitment and retention guidance

Steps to Create:

Approval Authorities: Cohort Manager (lead), Project Manager (budget and contingency authority), Pilot Partners (enrollment commitment)

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: Enrollment stalls at 60–70% of target by Month 11 (2027-09-13), dropout exceeds 40% across sites despite mitigation efforts, and pilot completion falls to 50–60 learners per arm (200–240 total, below the 320 minimum). The gate metrics become statistically unreliable and inconclusive. The board faces a forced choice at Month 24 (2028-10-13): declare a no-go outcome and strand $1.2M (Phase 3 + reserve), or extend Phase 2 by 3–6 months at a cost of $300K–$600K (estimate), pushing v1.0 release to Month 33–39 (2029-07-13 to 2030-01-13) and killing near-term adoption momentum. If extension is chosen but recruitment barriers persist, a second extension becomes politically and financially unviable, resulting in project termination and reputational damage to the program and partner organizations.

Best Case Scenario: The Pilot Baseline Study identifies high recruitment conversion (60–70%) and baseline dropout (20–25%), enabling confident enrollment by Month 13 (2027-11-13). Partner enrollment and retention tracking proceeds on schedule; incentives and support protocols keep dropout at 25–28%, yielding 115–120 completers per arm (460–480 total, 440–500+ enrolled). The four gate metrics are measured reliably (inter-rater kappa ≥0.75, follow-up completion ≥70%), ordinal error reduction meets the ≥25% threshold, pronunciation consistency exceeds the 15% target, and comprehension speed stays within the 10% tolerance. The Month 24 (2028-10-13) go/no-go outcome is unambiguous, partners and educators accept the gate decision with confidence, Phase 3 public release proceeds on schedule by Month 30 (2029-04-13), and early adopters point to robust pilot evidence when justifying adoption investment.

Fallback Alternative Approaches:

Create Document 10: Project Risk Register

ID: 937ec994-723f-4b4e-97cc-afbcd609d58f

Description: Living document identifying 20+ project risks (regulatory rejection, pilot recruitment failure, assessment validity, audio-production bottleneck, editorial board deadlock, safety-critical liability, etc.) with: risk description, likelihood (high/medium/low), severity (high/medium/low), risk owner, mitigation strategy, mitigation timeline, and escalation trigger. Updated monthly, with critical-path risks flagged to the editorial board at Months 3, 6, 9, 12, 18, 24 (2027-01-13, 2027-04-13, 2027-07-13, 2027-10-13, 2028-04-13, 2028-10-13). Guides contingency reserve allocation and Phase-1 exit-gate readiness assessment.

Responsible Role Type: Project Manager / Risk Officer

Primary Template: PMI Risk Management Plan template

Secondary Template: ISO 31000:2018 Risk Management standard

Steps to Create:

Approval Authorities: Project Manager (owner and primary analyst), Risk Officer (if separate), Editorial Board (escalation and contingency release decisions)

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: At Month 18 (2028-04-13), a combination of unmitigated risks converges: (1) regulatory authorities have not responded to outreach, delaying partner approvals by 6 weeks, pushing pilot enrolment into Month 15 (2028-01-13); (2) inter-rater reliability testing at Month 10 (2027-08-13) revealed kappa 0.62 (below the 0.70 floor), but retraining and a second round of calibration were deferred to "resolve later"; (3) an educator focus group (Month 6 = 2027-04-13) flagged resistance to the prefix-ordinal marker, but no mitigation action was documented or board-escalated, leading to 25% non-compliance in pilot materials by Month 18 (2028-04-13); (4) audio production ran 8 weeks over budget and consumed $185K (exceeding the pre-gate draw cap), straining Phase 2 recruitment incentives. By Month 22 (2028-08-13), the data lock reveals: pilot sample is 68 completers per arm (below the 80 minimum), 30-day follow-up completion is 58% (below the 70% gate threshold), ordinal-rule-compliance variance is high, and inter-rater kappa on pronunciation is still 0.68. The editorial board must choose: extend Phase 2 by 3 months (cost ~$300K, exceeding available reserve and forcing Phase 3 cuts) or invoke a no-go decision based on inconclusive data (stranding $1.2M in Phase 2–3 budget and delaying market entry to Month 36 = 2029-10-13 or beyond). Either outcome undermines credibility: an extension signals poor project planning; a no-go on weak data suggests the gate was too ambitious or the measurement was flawed. Post-hoc stakeholder criticism ("the register didn't flag these risks early" and "no one was accountable for mitigation") compounds damage to the editorial board's governance legitimacy and the standard's perceived rigor.

Best Case Scenario: By Month 3 (2027-01-13), the risk register is fully operationalized with 20 documented risks, clear ownership, escalation triggers and monthly review discipline. Regulatory outreach (Risk #1 owner: regulatory liaison) identifies approval pathways and secures non-binding advisory letters by Month 4 (2027-02-13), allowing pilot partner recruitment to proceed without delay. Assessment-validity risk (Risk #3 owner: psychometrician) is proactively managed: construct-validity analysis and confound controls are built into the pre-analysis plan draft (Month 5 = 2027-03-13), a small validity study (N=20–30) is completed by Month 11 (2027-09-13) confirming kappa ≥0.75, and metrics are pre-registered on schedule. Editorial-board deadlock (Risk #4) is prevented by an explicit charter (Month 1 = 2026-11-13) and an agreed external arbiter (Month 5 = 2027-03-13), allowing disputed rules to be resolved by Month 10 (2027-08-13) without cascading delays. Audio production (Risk #6 owner: audio production manager) secures a firm studio contract by Month 2 (2026-12-13) and completes all 5,000 entries on schedule by Month 11 (2027-09-13) within budget; rater training is completed by Month 9 (2027-07-13) with kappa validation documented. By Month 12 (2027-10-13), Phase 1 exits cleanly with rules locked, audio complete, metrics pre-registered, lexicon coverage audited at 87%, and ethics approval in hand. Phase 2 enrolment achieves 125 per arm by Month 13 (2027-11-13), providing 10% attrition headroom. A Month 18 (2028-04-13) midpoint check reveals on-track progress with only minor variance (educator compliance at 94%, audio quality spot-checks passing, follow-up completion on target). The Month 24 (2028-10-13) go/no-go decision is clean: all four metrics meet pre-registered thresholds, sample sizes exceed minimums, inter-rater reliability is robust, and validity conditions hold. The board votes GO with confidence, public release proceeds by Month 30 (2029-04-13) with a written steward commitment in place, and Phase 3 outreach achieves 4+ third-party adopters by Month 36 (2029-10-13). The register becomes a model for other language-standardization initiatives, demonstrating that disciplined risk management enables credible, evidence-gated program decisions.

Fallback Alternative Approaches:

Create Document 11: Project Budget and Cash-Flow Forecast

ID: 5cd6b401-d03a-4db9-ab35-ad056a110faf

Description: Detailed financial baseline (itemized Phase 1 and Phase 2 costs by workstream: staff, audio, lexicon, assessment, incentives, partner payments, travel, legal), monthly burn rates, cumulative earned-value curves, and rolling 6-month cash-flow forecast. Establishes variance triggers (>10% overrun flagged within 5 days), contingency-reserve allocation, and draw-authorization procedures (up to $25K without board vote, $25K–$175K with 5-day approval). Updated monthly with actual vs. plan variance analysis and spending forecast revision. Audience: project lead, finance office, editorial board.

Responsible Role Type: Budget Officer / Financial Manager

Primary Template: PMI Budget Template and Project Financial Plan

Secondary Template: US Federal Grants Management Handbook (if government-funded)

Steps to Create:

Approval Authorities: Budget Officer (lead analyst), Finance Office (baseline approval), Program Sponsor (contingency draw >$50K)

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: A combination of undetected cost overruns, poor contingency-draw discipline and absent variance reporting leaves the project insolvent mid-Phase 2. Specifically: (1) Phase 1 audio production and psychometric validation overrun by $200K (estimate) by Month 10 (2027-08-13), undetected because no monthly variance reports are issued; (2) the project lead and finance office each assume the other is monitoring, so the overrun is not escalated; (3) by Month 12 (2027-10-13), Phase 2 begins with only $900K remaining in the combined Phase 2 and reserve budget, insufficient to fund 12 months of pilots, assessments and partner payments estimated at $1.2M; (4) contingency draws of $150K–$200K (estimate) are requested ad-hoc in Months 14–18 (2027-12-13 to 2028-04-13) for pilot recruitment shortfalls and rater retraining, exhausting the pre-gate draw cap and the full $350K reserve by Month 18 (2028-04-13); (5) a 3-month Phase 2 extension to complete data collection costs $300K (estimate), but no funds remain, forcing either unauthorized draw requests or cancellation of Phase 2 pilots; (6) the Month 24 (2028-10-13) go/no-go gate is postponed indefinitely, stranding the project and damaging credibility with ESL programs, publishers and standards bodies; (7) a no-go outcome at Month 30–36 (2029-04-13 to 2029-10-13) leaves no unspent Phase 3 or reserve funds to return, negating the cost-containment principle and leaving funders and stakeholders uncertain whether the project was abandoned due to evidence failure or financial mismanagement.

Best Case Scenario: A detailed, disciplined Project Budget and Cash-Flow Forecast document establishes clear financial governance from Month 1 (2026-11-13) forward. Monthly variance reports show spending aligned with plan (±5% actual vs. budget), triggering corrective action promptly when overruns approach 10%. Quarterly earned-value analysis (SPI ≥0.95, CPI ≥1.0) confirms the project stays on schedule and within cost targets. A rolling 6-month cash-flow forecast identifies the peak liquidity need (≈$1.3M cumulative by Month 18 = 2028-04-13, estimate) and confirms adequate reserves to cover Phase 2 extension scenarios up to 3 months. Contingency draws are authorized efficiently: a $50K psychometric re-validation request at Month 10 (2027-08-13) is approved within 2 days, rater training is completed by Month 11 (2027-09-13), and inter-rater kappa reaches 0.75 target, enabling Phase 2 to begin on schedule. By Month 24 (2028-10-13), the go/no-go gate decision is supported by reliable cost and schedule data; if the outcome is GO, Phase 3 launches with full $1.2M ($0.85M Phase 3 + $0.35M released reserve) and no financial distraction; if NO-GO, $1.2M–$1.4M in unspent Phase 3 and contingency funds are returned, demonstrating fiscal responsibility and preserving stakeholder trust for future initiatives. The project is perceived as well-managed, delivers evidence on time and at budget, and achieves credibility with educators, publishers and standards bodies that adopt Clear English in Phase 3.

Fallback Alternative Approaches:

Documents to Find

Find Document 1: ESL Learner Corpus and Frequency Data

ID: c7580490-a507-489a-b615-884e736dbb1a

Description: Large corpus of English text produced by or targeted at adult ESL learners (e.g., Cambridge English Learner Corpus, TOEFL corpus, COCA General Academic subsection, JACET list of academic words). Required to derive the 5,000-word core lexicon by frequency ranking and to identify the highest-frequency irregular verbs and morphologically complex words that must be retained for learnability. Intended audience for analysis: lexicon designer.

Recency Requirement: Most recent available version (corpus data is cumulative; updates are beneficial but not time-critical for word-frequency ranking).

Responsible Role Type: Linguistic Specialist / Corpus Analyst

Steps to Find:

Access Difficulty: Easy to Medium. COCA is freely available online; Cambridge Corpus requires institutional subscription (typically free via university library access); TOEFL lists are public. Compile into a ranked lexicon by Month 3 (2027-01-13).

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: Lexicon selection is performed on an undated, limited or unrepresentative corpus (e.g., a small learner sample of N=100–500) discovered too late (Month 10 = 2027-08-13 or later) to correct. Pilots reveal that Core Lexicon Selection Basis coverage is only 75–80% instead of >=85% (proposed threshold), leaving 15–20% of running text outside the lexicon. Confounding is severe: learners' comprehension difficulty derives partly from unknown vocabulary, not Clear English rule effects, inflating measurement noise by 20–30% and reducing statistical power to detect ordinal and pronunciation effects by 25–40%. At the Month 24 (2028-10-13) go/no-go gate, the ordinal error rate or pronunciation consistency metric fails to meet its pre-registered threshold, but the board cannot rule out that poor lexicon coverage caused a false-negative outcome. The gate decision becomes disputable: educators and standards bodies reject the no-go as invalid, claiming the pilot was poorly designed. The project is forced into a 6–12 month Phase 2 extension ($300K–$600K, estimate) to re-run pilots with an expanded, verified lexicon, stranding $300K–$600K (estimate) and delaying public release to Month 36–42 (2029-10-13 to 2030-04-13). Adoption momentum is lost; publishers and standards bodies defer commitments. Final adoption reaches 5,000–10,000 learners instead of 50,000–100,000 (estimate), and the standard's credibility is permanently damaged.

Best Case Scenario: Lexicon is derived from a large, recent, multi-source ESL corpus (Cambridge, COCA, TOEFL, academic-vocabulary sources) representing 500,000+ tokens (estimate) across diverse learner populations and proficiency levels. Frequency ranks are published openly with methodological transparency, enabling third-party verification and adoption-partner confidence. Audit at Month 8 (2027-06-13) confirms >=85% coverage of running text in existing ESL curricula and safety-critical glossaries, with no remediation needed. Irregular-verb and morphologically complex-word rankings directly inform the Irregular Morphology Retention Threshold, locking in go/went and other high-frequency irregulars while regularizing only low-frequency, low-learning-burden forms. Homograph and homophone ranking informs a concise, high-impact list of <=50 pairs for mandatory markers in safety-critical documents. Pilots proceed with clean, transparent measurement: comprehension confounds are minimal, and ordinal error rate and pronunciation consistency metrics cleanly reflect Clear English effects. At Month 24 (2028-10-13), the go/no-go gate is decided on defensible evidence, with no dispute over lexicon adequacy. Early adopters (ESL publishers, standards bodies, safety-training organizations) cite the transparent lexicon methodology in justifying adoption, accelerating Phase 3 uptake. By Month 36 (2029-10-13), >=3 third-party adopters are licensed, reaching 50,000–100,000 learners, and the standard's credibility is established in the ESL and technical-writing communities.

Fallback Alternative Approaches:

Find Document 2: Existing English Irregular Verb and Morphology Error Databases

ID: 3dc2b5a3-8804-4046-8846-c003e51081b0

Description: Published research databases and learner-error corpora (e.g., ELEC corpus from Chujo & Hasegawa, learner error corpora compiled by ESL-assessment organizations) documenting which irregular verbs and plural forms are most frequently misused or cause learning difficulty for adult ESL learners. Required to rank the morphology retention threshold (which irregulars to keep, which to regularize) and to identify the highest-friction patterns. Intended audience: morphology-rule workstream lead.

Recency Requirement: Prefer studies published within the last 10 years (2016–2026 estimate); morphology acquisition patterns are stable over time, so older research is acceptable if recent is unavailable.

Responsible Role Type: Linguistic Specialist / Applied Linguist

Steps to Find:

Access Difficulty: Medium. Published studies are freely available via academic databases (Google Scholar, ResearchGate); access to corpus data may require emailing authors or institutional subscription. Compile by Month 5 (2027-03-13).

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: The morphology-rule workstream team proceeds without accessing current learner-error corpora and relies on linguistic intuition or outdated handbooks to decide the morphology retention threshold. By Month 8 (2027-06-13), pilot curriculum development begins with an arbitrary rule—e.g., 'regularize all verbs with fewer than 10 million Google hits'—that does not reflect actual ESL learner friction. During Phase 2 pilots (starting Month 12 = 2027-10-13), teachers and learners report that the retained irregulars (e.g., go/went) are confusing and error-prone, contradicting the assumption that frequent irregulars are already learned. The morphology error rate in pilots fails to improve as expected, or the pronunciation consistency score is confounded by unexpected morphology-error variance. At Month 18 (2028-04-13) midpoint review, the editorial board realizes the retention threshold was misaligned with learner data, forcing either mid-pilot rule changes (invalidating earlier assessments) or a no-go recommendation at Month 24 (2028-10-13) due to weak morphology effectiveness. Cost: 3–4 week rework ($50K–$100K estimate) or loss of credibility on the morphology rule, reducing Phase 3 adoption by 20–30%.

Best Case Scenario: The morphology-rule workstream team obtains and analyzes the ELEC corpus, recent ESL-assessment rubrics and 2–3 peer-reviewed studies on irregular-verb and plural-form acquisition (published 2016–2025 estimate) by Month 5 (2027-03-13). The analysis reveals that learners struggle most with verbs like go/went (high frequency but highly irregular) and with irregular plurals (child/children, ox/oxen). However, the team also finds that most learners internalize the top 20–30 irregular verbs through repeated exposure, even when regularized forms are introduced. The workstream proposes a data-driven retention threshold: retain all irregulars in the top 500-word band (covering >85% of text), regularize only the 50–100 lowest-frequency irregulars with clear recognition parallels (e.g., build/builded parallel to jump/jumped). This threshold is published, auditable and defensible. Pilot teachers report the rule is clear and learnable; morphology error rates improve by 30–40% (exceeding the >=25% proposed threshold). The rule's evidence-based grounding strengthens the editorial board's confidence, accelerates Phase 2 progress and raises Phase 3 adoption interest by 15–25% (estimate) among publishers who perceive the standard as rigorous and empirically grounded.

Fallback Alternative Approaches:

Find Document 3: Homograph and Homophone Lists for English (Including Specialized Domains)

ID: b0d2d465-7f48-4c9a-949a-e22839d65ed0

Description: Comprehensive list of English homographs (same spelling, different pronunciation/meaning; e.g., lead/lead, read/read) and homophones (same pronunciation, different meaning; e.g., to/two/too) with frequency rankings and domain relevance (common in technical, medical, legal, or general English). Required for Homograph Disambiguation Policy (Decision 7) to define which pairs must be marked, which are low-priority, and which are domain-specific. Intended audience: homograph-policy workstream lead and safety-critical curriculum designer.

Recency Requirement: Existing lists of homographs are stable (no recent updates expected); use any authoritative source published in the last 15 years.

Responsible Role Type: Linguistic Specialist / Semanticist

Steps to Find:

Access Difficulty: Easy. Homograph lists are published in linguistics textbooks and online dictionaries; many are freely available. Compile a prioritized list by Month 4 (2027-02-13).

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: A weak or incomplete homograph list, delivered late (Month 6–8 = 2027-04-13 to 2027-06-13 instead of Month 4 = 2027-02-13 to 2027-06-13), delays the Homograph Disambiguation Policy finalization and forces the editorial board to adopt either a loose, non-evidence-backed policy or a conservative one that burdens safety-critical writers without proven risk reduction. During Phase 2 pilots, critical homographs omitted from the list cause misreading incidents in safety-critical test passages, inflating the ordinal-error metric or confounding comprehension-speed measurements. At Month 18 (2028-04-13) midpoint review, pilot data reveals that unmarked homophones (e.g., 'to/two' in numbered procedures) account for 15–20% of miscommunications, forcing a mid-pilot policy revision that invalidates earlier assessment data. The editorial board must either rerun a cohort (3–6 month delay, ~$150K–$300K cost estimate) or report to stakeholders at Month 24 (2028-10-13) that the homograph evidence is inconclusive, triggering a disputed or conditional go/no-go gate, loss of partner confidence and potential Phase 3 delay to Month 36 (2029-10-13) or beyond.

Best Case Scenario: A comprehensive, frequency-ranked and domain-validated homograph list is delivered by Month 4 (2027-02-13), compiled from academic corpus data, safety-critical incident reports and controlled-language standards (ASD-STE100, plain-language guides). The list identifies 40–50 highest-impact pairs, 70% of which fall within the 5,000-word core lexicon, with clear justification for inclusion and a method for handling borderline cases. Safety organizations and ESL publishers review the list by Month 5 (2027-03-13) and endorse its domain relevance in their advisory roles. The Homograph Disambiguation Policy is finalized and published by Month 6 (2027-04-13), mandating markers in safety-critical documents for the high-impact list and leaving markers optional elsewhere. Pilot curriculum designers integrate the policy seamlessly by Month 12 (2027-10-13), and pilot data shows that marked homographs have ≤5% misreading rates (compared to unmarked control pairs), demonstrating clear safety benefit. The policy becomes a concrete, credible success story in Phase 3 outreach, attracting safety-critical and technical-writing adopters and contributing to the ≥3 licensed-adopter target by Month 36 (2029-10-13).

Fallback Alternative Approaches:

Find Document 4: Existing ESL and Technical-Writing Textbooks and Curricula (Sample Materials)

ID: 2e43572b-b45d-4cec-b987-d41dae20b19e

Description: Representative ESL textbooks (e.g., Cambridge English series, Oxford English series), ESL course syllabi, and technical-writing training materials from pilot partner organizations to use as a corpus for the lexicon-coverage audit (confirming that the 5,000-word core lexicon covers ≥85% of running text in actual pilot curricula). Intended audience: lexicon designer and curriculum analyst.

Recency Requirement: Textbooks and curricula in current use (published within the last 5 years, 2021–2026 estimate). Historical or outdated materials are not suitable for coverage audit.

Responsible Role Type: Curriculum Designer / Lexicon Analyst

Steps to Find:

Access Difficulty: Medium to Easy. ESL textbooks are widely available; pilot partner materials require signed agreements and may be confidential. Obtain sample materials by Month 4 (2027-02-13); complete coverage audit by Month 8 (2027-06-13).

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: At Month 8 (2027-06-13), a lexicon-coverage audit reveals that the core 5,000-word list covers only 75–80% of running text in the ESL and technical-writing samples, particularly missing high-frequency safety and procedural vocabulary. The shortfall cannot be absorbed by Month 12 (2027-10-13) without either delaying audio production (pushing pronunciation recording into Phase 2) or abandoning the full 5,000-word target and proceeding with a smaller, less credible lexicon. A lexicon-expansion decision delays v1.0 rule finalization and audio completion to Month 14–15 (2027-12-13 to 2028-01-13), compressing Phase 2 pilots to a 10-month window and reducing effective sample retention by 5–10 percentage points (estimate). The four gate metrics are weakened by confound effects, and the editorial board cannot defensibly say at Month 24 (2028-10-13) whether Clear English effects are true or measurement artefact, forcing a disputed no-go outcome and stranding $1.2M–$1.4M (Phase 2–3 budget).

Best Case Scenario: By Month 8 (2027-06-13), the audit confirms that the 5,000-word core lexicon covers 87–92% of running text in current ESL and technical-writing curricula, with a defensible 4,500 general / 500 technical split that aligns with pilot partner materials. Identified gaps (5–10 words, estimate) are minor and non-critical, and can be optionally added by Month 10 (2027-08-13) without increasing audio recording scope. Audio production proceeds on schedule (Months 6–11 = 2027-04-13 to 2027-09-13) with confirmed pronunciation entries per curriculum type. Phase 2 pilots begin with a lexicon that participants recognize as representative of their own study materials, eliminating confounds and strengthening the validity of comprehension speed and retention assessments. The four gate metrics rest on clean data, and the Month 24 (2028-10-13) go/no-go decision is defensible to educators, publishers and standards bodies.

Fallback Alternative Approaches:

Find Document 5: Corpus of English Spelling Irregularities and Grapheme-to-Phoneme Mapping Rules

ID: 310887a3-943c-472d-bbe9-9c832956e4df

Description: Linguistic research or curated corpus documenting the patterns of English spelling-to-sound irregularities (grapheme-to-phoneme mismatches), such as the 'ough' patterns (rough, through, though, thorough, dough), vowel digraphs (ea, ei, ie), and silent letters. Required to design the Grapheme-to-Phoneme Intervention rules (Decision 2) and to prioritize which words in the core lexicon need the most pronunciation guidance. Intended audience: linguistic specialist and pronunciation specialist.

Recency Requirement: Existing linguistic descriptions of English phonology are stable; use any authoritative source published in the last 30 years.

Responsible Role Type: Linguistic Specialist / Phonetics Specialist

Steps to Find:

Access Difficulty: Easy. Phonology and linguistics textbooks are widely available in university libraries. Compile by Month 3 (2027-01-13).

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: An incomplete or inaccurate corpus of irregularities leaves the G2P intervention rules targeting the wrong patterns—perhaps omitting 'ough' or mischaracterizing vowel digraphs—so pilot learners do not receive pronunciation guidance on their actual pain points. The pronunciation-consistency gate metric shows no significant improvement over control, the gate fails at Month 24 (2028-10-13), and the initiative is abandoned, forfeiting $1.2M–$1.4M in Phase 2–3 spending (estimate). Alternatively, conflicting source materials on accent realization cause pronunciation guidance to be inconsistent across the 5,000-word lexicon, inter-rater reliability (kappa) drops below the 0.70 floor, forcing a 4-week Phase 1 extension and triggering a draw on the $175K pre-gate contingency reserve, leaving insufficient headroom for other Phase 1 overruns.

Best Case Scenario: A thorough, frequency-ranked corpus of English irregularities aligned with the reference accent anchor is completed by Month 3 (2027-01-13), allowing the linguistic specialist to design precise, high-impact G2P rules targeting the top 10–15 spelling patterns causing the most learner confusion. The 5,000-word lexicon is systematically mapped and validated against the corpus by Month 8 (2027-06-13), ensuring 85%+ running-text coverage in pilot materials. Pronunciation-guidance consistency is high (inter-rater kappa ≥0.75), assessment items are exemplary, and pilot learners show ≥25% reduction in ordinal and pronunciation errors relative to control. The pronunciation-consistency gate metric passes decisively at Month 24 (2028-10-13), supporting a GO decision and Phase 3 release, with >3 third-party adopters committed by Month 36 (2029-10-13).

Fallback Alternative Approaches:

Strengths

Weaknesses

Opportunities

Threats

Recommendations

Strategic Objectives

Assumptions

Missing Information

Questions

Roles Needed & Example People

Roles

1. Project Lead / Program Director

Contract Type: full_time_employee

Contract Type Justification: Program Lead / Director must own end-to-end delivery across 36 months, manage governance, maintain stakeholder confidence and ensure budget discipline. This is a continuous, core accountability role requiring full control and availability from Month 0 (2026-10-13) onward. No procurement-outside-expertise model applies; the role is integral to project success and requires deep institutional knowledge of decisions, timelines and partner relationships.

Explanation: Owns the end-to-end delivery of the standard across three gated phases, manages the core team, editorial board governance, critical-path tracking, and stakeholder escalation. Ensures budget discipline, timeline adherence, and go/no-go decision readiness. This role is essential from Month 0 (2026-10-13) onward to establish governance, secure partnerships and maintain credibility with educators, standards bodies and regulators.

Consequences: Without a dedicated program lead, governance and decision-making becomes diffuse, critical deadlines slip (e.g., board charter delayed, partner commitments unsigned, psychometric validation postponed), budget tracking lapses, stakeholder communication becomes inconsistent, and the Month 24 (2028-10-13) go/no-go gate collapses under competing priorities and unclear authority. Project risk of failure increases by an estimated 30–50%.

People Count: 1

Typical Activities: Sarah owns end-to-end delivery across three phases: establishing the editorial board charter and voting procedures by Month 1 (2026-11-13), securing signed partner commitments by Month 3 (2027-01-13), managing monthly critical-path reviews and escalating any slip over 2 weeks, maintaining the project budget tracker and forecasting Phase 2–3 spending, chairing editorial board meetings and logging contested rule decisions, reporting go/no-go readiness to the board at Month 24 (2028-10-13), and transitioning stewardship governance by Month 30 (2029-04-13). She spends roughly 30% of time on governance and decision authority, 30% on timeline and budget discipline, 25% on stakeholder communication and partner relationship maintenance, and 15% on risk escalation.

Background Story: Sarah Chen, based in Austin, Texas, is a program director with 12 years of experience managing large-scale education and standards initiatives. She holds an MBA from UT Austin and a background in public health program management. Sarah led a successful three-year health literacy curriculum rollout across 15 school districts and has deep relationships with education authorities and non-profit partners. She is fluent in Mandarin and English, with experience managing cross-cultural teams. Sarah joined the Clear English project in October 2026 specifically for its evidence-gated approach and adoption-first philosophy, values aligned with her belief that standards succeed through stakeholder buy-in, not mandate.

Equipment Needs: Laptop and project-management software (Microsoft Project, Asana, or Jira) for critical-path tracking and budget forecasting. Video conferencing platform (Zoom, Teams) with recording capability for distributed editorial board and stakeholder meetings. Document version-control system (GitHub, SharePoint) for decision logging and rule drafts. Secure file storage and backup. High-speed internet connection.

Facility Needs: Office space with meeting rooms suitable for monthly editorial board gatherings and stakeholder calls. Private workspace for sensitive governance documents and budget forecasts. Meeting space capacity for 8–12 people (editorial board + project lead + secretary). Virtual-meeting infrastructure for board members in distributed locations. Proximity to pilot partner institutions and stakeholder organizations beneficial but not mandatory given virtual engagement capability.

2. Psychometrician / Assessment Specialist

Contract Type: full_time_employee

Contract Type Justification: Psychometrician / Assessment Specialist is essential to design and validate gate metrics, ensure pre-registration by Month 11 (2027-09-13), and lead inter-rater calibration. While assessment is often contractor work, the 14-month engagement (Month 2 = 2026-12-13 to Month 15+ post-gate analysis) and requirement for continuous involvement in validation cycles, pre-analysis plan development and kappa calibration makes a full-time role more cost-effective and ensures continuity. Alternatively, independent_contractor if an established assessment firm is engaged for the full Phase 1–2 scope under a fixed deliverable contract.

Explanation: Designs and validates the four gate metrics (ordinal error rate, comprehension speed, pronunciation consistency, 30-day retention), ensures they are statistically sound and pre-registered by Month 11 (2027-09-13), and leads inter-rater training and kappa calibration. Critical for gate credibility: weak or disputable metrics render the Month 24 (2028-10-13) decision non-defensible and undermine partner confidence.

Consequences: Absent psychometric expertise leads to weak, unmeasurable gate criteria; inter-rater reliability falls below kappa 0.70, inflating measurement noise by 20% and reducing statistical power by 10–15%; the Month 24 (2028-10-13) gate decision becomes scientifically disputable, triggering stakeholder rejection and forcing expensive ($200K–$300K) rework or a failed gate that strands Phase 3 funding ($1.2M–$1.4M).

People Count: 1

Typical Activities: Marcus designs and validates four gate metrics: commissioning a validity study (N=20–30) in Months 10–11 (2027-08-13 to 2027-09-13), drafting the pre-analysis plan by Month 5 (2027-03-13) with quantitative thresholds (e.g., ordinal error reduction ≥25%), registering the plan on Open Science Framework by Month 11 (2027-09-13), and leading inter-rater training and kappa calibration for pronunciation consistency (target kappa ≥0.75). He advises the editorial board on construct validity concerns, identifies potential confounds (e.g., repeated exposure to ordinals), and designs control conditions to isolate Clear English effects. He conducts a dry-run validity check at Month 10 (2027-08-13) and retrains raters if kappa falls below 0.70, extending Phase 1 by 4 weeks if necessary.

Background Story: Dr. Marcus Okafor, a psychometrician and educational measurement specialist, holds a PhD in Educational Research Methodology from the University of Michigan and has published 18 peer-reviewed papers on validity and reliability in language assessment. He spent 8 years as an assessment director at a major ESL testing organization and has designed inter-rater training protocols for oral-proficiency exams used by over 100,000 test-takers annually. Marcus brings deep expertise in pre-registration, confound control and measurement validity. He was hired by Month 2 (2026-12-13) specifically because the Clear English go/no-go gate depends entirely on defensible, pre-registered metrics; his reputation in applied measurement lends credibility to the gate decision.

Equipment Needs: Statistical software (R, SPSS, SAS, or equivalent) for designing validity studies, calculating inter-rater reliability (Cohen's kappa), and conducting power analysis. Online survey platform (Qualtrics, REDCap) for collecting assessment data if piloting digitally. Reading-assessment instruments (commercial or custom) compatible with Clear English and standard English conditions. Data-analysis and visualization tools (e.g., ggplot2, Excel). Laptop and secure data storage for participant datasets.

Facility Needs: Office space with private work area for confidential psychometric analysis and instrument validation. Access to a quiet testing environment for the small validity study (N=20–30) at Month 10–11 (2027-08-13 to 2027-09-13); could be a university partner's lab or a rented quiet room. Secure server or encrypted cloud storage for pre-analysis plan and sensitive research data. Video conferencing for consultation with the editorial board and external reviewers.

3. Linguistic Specialist / Computational Linguist

Contract Type: full_time_employee

Contract Type Justification: Linguistic Specialist / Computational Linguist (min 2, max 3 per canonical facts) requires continuous development of rule specification, lexicon and editorial board guidance Months 0–12 (2026-10-13 to 2027-10-13) and ongoing support through Phase 2. This is a core technical role with no clear exit point until rules are finalized and pilots are analyzed. Multiple linguists create redundancy and depth. Full-time employment ensures consistency and availability, particularly during contested rule decisions where external linguistic review cannot substitute for core team expertise.

Explanation: Develops the rule specification (ordinals, morphology retention, homograph disambiguation, grapheme-to-phoneme mapping) and owns the 5,000-word core lexicon. Chairs or advises the editorial board on linguistic consistency and ambiguity resolution. Essential during Phase 1 to finalize rules by Month 12 (2027-10-13) and ensure they are unambiguous before pilots begin.

Consequences: Insufficient linguistic expertise leads to rule ambiguity, internal contradiction, and inconsistent application; editorial board disputes remain unresolved, delaying rule finalization by 4–12 weeks; mid-pilot rule changes invalidate earlier assessments and inflate measurement error; adopters perceive the standard as linguistically incoherent, reducing Phase 3 adoption by 20–40%.

People Count: min 2, max 3, depending on rule complexity and lexicon scope

Typical Activities: Keiko and James lead three rule-specification workstreams: ordinal-marker design, morphology retention threshold, and homograph disambiguation. They draft rule specifications with written rationale by Month 10 (2027-08-13), chair editorial board subcommittees on contested rules, facilitate consensus between linguists and practitioners, and prepare documentation for the 30-day public comment window (Month 11 = 2027-09-13). Keiko leads morphology and homograph work, compiling a ranked list of irregular forms and high-impact homograph pairs from learner-error corpora. James leads ordinal-marker design, proposing the invariant prefix notation and fixed spoken form. Both contribute to the pre-comment rule document (Month 11 = 2027-09-13) and manage rule finalizations by Month 12 (2027-10-13), freezing the rule set before pilots begin.

Background Story: Dr. Keiko Sato and Dr. James O'Brien are two senior linguists co-leading rule specification. Keiko, trained at Cambridge in English phonology and morphology, spent 10 years at Oxford University Press developing English-learning curricula and has published on regularizing irregular verbs in ESL contexts. James, a computational linguist from MIT, specializes in grapheme-to-phoneme systems and has built speech-synthesis lexicons for three Asian languages. Together they bring complementary expertise: Keiko's pedagogical and morphological depth, James's technical and phonetic precision. Both understand the tension between linguistic consistency and learnability and are committed to evidence-based rule choices over pure elegance.

Equipment Needs: Linguistics reference tools (Oxford English Dictionary, major ESL learner corpora, morphological databases). Corpus-analysis software (AntConc, SketchEngine) for mining irregular verbs and high-frequency words. Text-annotation and markup tools (BRAT, Prodigy) for managing lexicon and rule examples. Pronunciation/phonetics software (Praat) for designing phoneme-based rule specifications. Document collaboration tools (Google Docs, Overleaf) for co-authoring rule specifications with the second linguist. Laptop with large monitor for extended writing and analysis.

Facility Needs: Office space shared with curriculum and development team for close coordination on rule clarity and pedagogical fit. Access to university linguistics library or database subscriptions (e.g., Linguistics and Language Behavior Abstracts, Project MUSE) for research on morphology and phonology. Meeting space for editorial board subcommittee discussions on contentious rules (ordinals, homographs). Ideally proximity to or affiliation with a university linguistics department for access to applied-linguistics expertise and student assistants for corpus work.

4. Phase 2 Cohort Manager / Pilot Administrator

Contract Type: full_time_employee

Contract Type Justification: Phase 2 Cohort Manager / Pilot Administrator is hired by Month 6 (2027-04-13) and runs continuously through Month 24 (2028-10-13) and 30-day follow-up (Month 22–26 = 2028-08-13 to 2028-12-13). This is a single, continuous role requiring hands-on management of 460 pilot participants, coordination with 5–7 institutional partners, weekly tracking and real-time problem-solving. The role is non-negotiable for achieving the pilot's 70%+ retention rate and defensible sample sizes. Full-time is essential; part-time or contractor models lack the availability to respond to recruitment bottlenecks and participant dropouts.

Explanation: Manages recruitment, enrollment and retention of pilot learners (target 460 across 4 arms, >=80 completers per arm). Coordinates with ESL programs and technical-training partners, tracks attendance, manages incentive payments and 30-day follow-up. Essential from Month 6 (2027-04-13) onward to ensure dropout stays below 30% and minimum sample sizes are achieved for gate credibility.

Consequences: Without dedicated cohort management, enrollment lags, dropout exceeds 30% (potentially reaching 40–50%), effective sample size drops below 80 per arm, statistical power degrades by 15–25%, and the gate metrics become inconclusive or invalid; pilot data is unusable, forcing a 3–6 month Phase 2 extension ($300K–$600K additional) or a false-negative no-go that kills a viable standard.

People Count: 1

Typical Activities: Rosa manages all aspects of pilot participant recruitment and retention: coordinating with 5–7 partner institutions (ESL programs and technical-training organizations), tracking enrollment toward a target of 115 per arm (460 total), scheduling four in-person assessment sessions per participant across Months 13–24 (2027-11-13 to 2028-10-13), managing participant incentives ($50–$150 per learner, totaling $23K–$69K), conducting 30-day follow-up contact (no later than 60 days post-test), and responding immediately to any participant who misses a session. She maintains a master spreadsheet of all 460 participants and their progress, sends attendance reminders 2 weeks and 1 day before each session, arranges make-up sessions within ±1 week, and flags at-risk participants to the project lead weekly.

Background Story: Rosa Mendoza, the Phase 2 Cohort Manager, is a former ESL instructor with 7 years of classroom experience and 4 years managing student success programs at a large community college in the San Antonio area. She speaks fluent Spanish and English and has strong relationships with ESL teachers and program coordinators across Texas. Rosa has personal experience with the frustration of irregular English morphology and spelling inconsistencies in her own teaching and sees the Clear English project as an opportunity to test evidence-based solutions. She was hired by Month 6 (2027-04-13) specifically to ensure the 460 pilot participants stay engaged and dropout remains below 30%.

Equipment Needs: Participant-management database (custom or off-the-shelf, e.g., REDCap, Qualtrics) for tracking 460 learners across 4 cohorts, attendance, contact information, incentive status and 30-day follow-up. Email and SMS reminders/scheduling system. Spreadsheet software (Excel, Google Sheets) for master participant list and dropout monitoring. Videoconference platform for virtual assessments if any sessions are conducted remotely. Secure encrypted storage for participant contact and incentive data (GDPR/HIPAA-level security).

Facility Needs: Office space (preferably shared with project lead or nearby) for daily participant coordination and rapid response to recruitment/retention issues. Phone line and internet for outreach calls to at-risk participants. Meeting space or videoconference capability for weekly status check-ins with the project lead. Ideally located in one of the pilot hubs (e.g., Austin, Washington DC, Cambridge area) to enable in-person relationship-building with ESL programs and technical-training partners. Travel budget for quarterly on-site visits to pilot institutions (already budgeted in project travel allocation).

5. Curriculum Designer / Materials Developer

Contract Type: full_time_employee

Contract Type Justification: Curriculum Designer / Materials Developer (1–2 per canonical facts) must produce pilot-ready learning materials by Month 13 (2027-11-13) and ensure fidelity throughout Phase 2 pilots. This is a continuous design-and-iteration role, not a discrete deliverable (print a curriculum, hand off). Materials must be revised if rules change, adapted to partner settings, and debugged during pilots. One FTE for core ESL module, potentially one for technical-glossary and safety exercises. Full-time employment ensures pedagogical consistency and rapid response to rule clarifications or pilot findings.

Explanation: Designs pilot learning materials (print and digital), assessments, and the pilot curriculum that embeds the Clear English rules and tests comprehension, ordinal accuracy and pronunciation consistency. Ensures materials are pedagogically sound, free from rule errors, and aligned with pilot protocols. Active during Phases 1–2 to produce pilot-ready curriculum by Month 13 (2027-11-13).

Consequences: Absent curriculum design results in pilot materials that are poorly aligned to rules, contain rule errors or pedagogical gaps, and fail to engage learners; assessment instruments become misaligned to the intended Clear English constructs; pilot fidelity is low, confounding results; assessment data is unreliable for the gate decision, reducing credibility by an estimated 20–30%.

People Count: min 1, max 2, depending on breadth of materials (ESL module, technical glossary, safety-labeling exercises)

Typical Activities: David and Elena jointly design pilot learning materials (print booklet and digital module) by Month 13 (2027-11-13), with David leading ESL-module pedagogy and Elena leading technical-glossary design. They embed Clear English rules into scaffolded exercises: ordinal practice (using prefix-marker forms in dates, lists and procedures), pronunciation guidance (optional overlay accessible on digital, printed key for print), and morphology and homograph examples. They conduct dry runs at pilot sites in Month 10 (2027-08-13), identify rule ambiguities or pedagogical misfits, relay findings to the linguistic team for Month 11 (2027-09-13) clarifications, and revise materials to match the final frozen rules by Month 12 (2027-10-13). They support both ESL and technical pilot cohorts with fidelity checks and learner-engagement monitoring Months 13–24 (2027-11-13 to 2028-10-13).

Background Story: David Liu and Elena Rodriguez are two curriculum designers with complementary expertise. David has 6 years of experience designing print and digital ESL materials for a major textbook publisher and knows how to translate linguistic rules into engaging, scaffold learning activities. Elena, a former safety-compliance trainer in the oil and gas industry, has written technical glossaries and procedure guides and understands how clarity, consistency and minimal ambiguity reduce accident risk. Together they design both the ESL pilot module (for adult learners) and the technical/safety-glossary exercises (for the native-speaker cohort). Both are deeply familiar with the tension between pedagogical appeal and rule fidelity.

Equipment Needs: Learning-management system (LMS) or digital content-creation platform (Canvas, Moodle, or proprietary) for delivering pilot materials and embedded assessments. Authoring tools for print and digital materials (Adobe InDesign or equivalent for layout; Articulate Storyline or similar for digital interactivity). Access to Clear English rule specifications and pronunciation guidance (frozen by Month 12 = 2027-10-13). Proofreading and editing software (Grammarly, Microsoft Editor) adapted for Clear English rule-checking. Laptop with dual monitors for design and assessment integration.

Facility Needs: Office space shared with the linguistic team and project lead for rapid iteration and rule alignment. Access to quiet design space for focused curriculum writing and layout work (Months 6–13 = 2027-04-13 to 2027-11-13 are peak production months). Meeting space for dry-run testing with a small pilot group (N=5–10) at Month 10 (2027-08-13); quiet classroom or training room at a partner ESL program or technical-training site. Ideally co-located or virtual-adjacent to pilot partner institutions to enable hands-on material piloting and fidelity checks Months 13–24 (2027-11-13 to 2028-10-13).

6. Educator Liaison / Teacher Engagement Specialist

Contract Type: full_time_employee

Contract Type Justification: Educator Liaison / Teacher Engagement Specialist (0.5–1.0 FTE) must engage TESOL, IATEFL and pilot teachers from Month 1 (2026-11-13) through Phase 3 adoption planning. This is a sustained relationship-building and communication role, not event-based consulting. One FTE ensures continuous teacher training delivery, buffer between the project team and educators, and early warning of educator pushback. Part-time or contractor models create discontinuity and miss the relational trust-building essential to mitigating educator resistance.

Explanation: Builds and maintains relationships with ESL professional organizations (TESOL, IATEFL), pilot partner teachers, and educators; communicates the rationale for Clear English and delivers teacher training and support during pilots. Surfaces educator concerns early (Months 1–3 = 2026-11-13 to 2027-01-13) and ensures buy-in and compliance. Essential to mitigate educator pushback and foster adoption readiness.

Consequences: Without educator engagement, teachers view Clear English as imposed from outside; non-compliance in pilots is high, rule application is inconsistent, and engagement and retention suffer; public criticism from respected educators damages credibility before and after the gate; Phase 3 adoption declines by an estimated 30–50% even with a positive gate outcome.

People Count: 1 FTE or 0.5 FTE part-time, depending on engagement breadth

Typical Activities: Anna engages ESL professional organizations (TESOL, IATEFL and regional chapters) from Month 1 (2026-11-13) onward, co-designs pilot protocols with practicing teachers to increase buy-in, delivers teacher-training workshops on Clear English rules and pilot administration (starting Month 10 = 2027-08-13), and facilitates quarterly advisory panels where pilot teachers surface concerns and offer feedback. She communicates the project's rationale and pilot findings to educators, mitigates teacher resistance by emphasizing that Clear English is supplementary and optional, and gathers early warning signals of educator skepticism. She manages a small pool of teacher stipends ($20K–$40K across Phase 2) to incentivize active participation and co-design engagement.

Background Story: Professor Anna Kowalski, the Educator Liaison, is a 20-year veteran of ESL teacher training and professional development, currently affiliated with a regional TESOL chapter in the Southwest US. She holds a master's degree in TESOL from the University of Arizona and has trained over 500 ESL teachers in curriculum design and assessment. Anna was skeptical of the Clear English project initially—fearing another top-down standard that teachers would resist—but came to champion it after reviewing the evidence-based pilot design and the plan's commitment to supplementary positioning (not replacement) and educator co-design. She brings credibility and trust with the ESL teacher community.

Equipment Needs: Email and video conferencing (Zoom, Teams) for outreach to teacher professional organizations (TESOL, IATEFL) and pilot teachers. Presentation software (PowerPoint, Keynote) for teacher-training workshops. Learning-management system (LMS) or webinar platform (Zoom, GoToWebinar) for delivering asynchronous and synchronous teacher training. Document library or wiki for publishing rationale, FAQs and training materials. Optionally, a survey tool (Qualtrics, SurveyMonkey) for teacher feedback collection during pilots.

Facility Needs: Office space for maintaining relationships, writing training materials and managing educator communications. Access to video-production or presentation space for recording teacher-training modules (Months 10–12 = 2027-08-13 to 2027-10-13) and during Phase 2 for live workshops. Ability to travel (or host virtually) quarterly advisory-panel meetings with ESL teachers; travel budget for 3–4 in-person conferences or regional teacher meetings annually (already budgeted in project outreach). Co-location with major ESL programs or conference venues beneficial but not mandatory if primary mode is virtual.

7. Editorial Board Coordinator / Governance Administrator

Contract Type: part_time_employee

Contract Type Justification: Editorial Board Coordinator / Governance Administrator (0.5 FTE estimated) manages recurring meetings, decision logging and conflict escalation, not a full continuous role. Board meetings occur monthly or bi-monthly, decision documentation is episodic, and tiebreaker arbiter engagement is triggered only on disputes. The role is essential but not full-time; 0.5 FTE (20 hours/week) accommodates meeting administration, documentation and follow-up. Could be hybrid with part-time employment + part-time administrative support from the program lead's office.

Explanation: Manages editorial board meetings, records decisions and rationales, tracks rule disputes and escalation to the tiebreaker arbiter, and publishes decision documentation. Ensures the board charter is enforced (voting rules, conflict-of-interest disclosure, timely decisions). Essential from Month 1 (2026-11-13) to establish governance and keep rule finalization on track.

Consequences: Without governance administration, board meetings lack structure, decisions are poorly documented, conflicts go unresolved, and the tiebreaker arbiter is not engaged; rule finalization delays by 4–12 weeks, compressing Phase 2 by 33–100%; stakeholders perceive the board as disorganized and politically divided, undermining credibility and adoption confidence.

People Count: 1

Typical Activities: Michael schedules and facilitates all editorial board meetings (monthly or bi-monthly, Months 1–36 = 2026-11-13 to 2029-10-13), documents all voting outcomes and rationales for contested rules, tracks rule disputes and escalates to the external tiebreak arbiter when consensus fails, publishes decision summaries on the project website, and maintains a master decision log. He prepares board packets 1 week before each meeting, records minutes and action items, follows up on assigned workstreams (ordinal marker, morphology, homographs), and ensures the board charter's voting rules and conflict-of-interest procedures are followed. He publishes the draft standard with rationale by Month 11 (2027-09-13) and manages the public 30-day comment window.

Background Story: Michael Torres is a project coordinator with 8 years of experience managing meeting logistics, decision documentation and governance workflows in a non-profit standards-development setting. He previously worked for a consortium managing international education standards and is expert at translating complex technical decisions into clear, accessible decision records. Michael is detail-oriented, unflappable under deadline pressure, and skilled at surfacing consensus and disagreeing-respectfully documenting minority positions. He was brought on to ensure the editorial board's decision-making is transparent, traceable and defensible to external stakeholders.

Equipment Needs: Meeting-scheduling and minute-taking tools (e.g., Doodle, When2Meet for scheduling; professional note-taking software). Decision-logging and tracking system: a shared spreadsheet or simple wiki/Confluence instance for recording all board votes, rationale and escalations. Version-control repository (GitHub, GitLab) for managing drafts of rule specifications and published standards. Email and calendar management. Laptop for administrative support.

Facility Needs: Shared office space with the project lead and editorial board for close coordination on governance. Access to a secure meeting room for recording sensitive board decisions (e.g., conflicts of interest, tie-breaking outcomes). High-speed internet and video conferencing for distributed board members. Document storage and backup system for maintaining decision archives. Could be co-located with program offices or centralized in the project headquarters location.

8. Regulatory and Stakeholder Affairs Manager

Contract Type: full_time_employee

Contract Type Justification: Regulatory and Stakeholder Affairs Manager (0.5–1.0 FTE) must engage multiple regulatory bodies, ESL programs, publishers and steward-organization candidates from Month 1 (2026-11-13) through Phase 3 (Month 36 = 2029-10-13). This role involves relationship continuity, regulatory tracking, written submissions to authorities (months of back-and-forth), and steward negotiations that require trust and institutional memory. A 1.0 FTE in Year 1–2 (Phase 1–2) and 0.5 FTE in Year 3 (Phase 3) balances front-loaded engagement with sustained stewardship search. Full-time (or phased) is essential; a contractor engagement for 'regulatory review' misses the relationship work and tracking continuity.

Explanation: Engages regulatory bodies (education authorities, standards bodies, TESOL, IATEFL), technical-training organizations and ESL publishers from Month 1 (2026-11-13) onward; surfaces regulatory risks and approval pathways; secures written partner commitments and steward-organization engagement post-gate. Essential to prevent adoption blocking and ensure institutional partnerships.

Consequences: Absent stakeholder engagement leads to rejection by key adopter groups (educators, standards bodies, regulators) without warning; regulatory approval delays are discovered late (Month 18–24 = 2028-04-13 to 2028-10-13), compressing pilots or blocking deployment; publisher commitments are weak or nonexistent; Phase 3 adoption is near zero; steward funding remains unsecured at Month 33 (2029-07-13), making the standard indefensible as public by Month 36 (2029-10-13).

People Count: 1 (0.5–1.0 FTE), depending on number of jurisdictions and stakeholder relationships

Typical Activities: Patricia identifies regulatory bodies whose approval could enable or block adoption (state education departments, Ofqual in the UK, TESOL, IATEFL and CEFR steerage committees) by Month 1 (2026-11-13) and secures written advisory input from at least one US and one UK standards body by Month 2 (2026-12-13). She documents the regulatory landscape and approval pathways by Month 4 (2027-02-13), prepares formal regulatory submissions (e.g., to state boards) by Month 15 (2028-01-13), manages regulatory timelines and escalates approval delays to the program lead. She cultivates non-binding letters of interest from ESL publishers and technical-training organizations by Month 3 (2027-01-13), monitors competitive or aligned standards initiatives (plain-language guidelines, ASD-STE100 updates) quarterly, and identifies steward-organization candidates and approaches them with a formal proposal by Month 24 (2028-10-13).

Background Story: Dr. Patricia Greenfield, the Regulatory and Stakeholder Affairs Manager, is a former education-policy analyst who spent 10 years at a state department of education and now consults on standards adoption with school districts and ESL organizations. She understands the regulatory landscape for education standards in the US and UK, has relationships with accreditation bodies and standards organizations, and knows how to craft regulatory submissions and navigate approval processes. Patricia joined the Clear English project because she believes evidence-based language standards are desperately needed, yet sees the real risk that regulatory inertia or educator resistance could kill the initiative before it gains traction.

Equipment Needs: Secure database or CRM (Salesforce, HubSpot) for tracking stakeholder relationships, regulatory contacts and partner commitments. Email and telephone for outreach to education authorities, standards bodies and publishers. Document-drafting tools for formal regulatory submissions and partnership proposals. Calendar and scheduling systems for managing regulatory timelines and follow-ups. Secure file storage for sensitive regulatory communications and partnership MOUs.

Facility Needs: Office space with private work area for confidential stakeholder negotiations and regulatory filings. Internet and phone infrastructure for managing international relationships with UK (Ofqual), US (state education departments, TESOL) and international (ISO, CEFR) standards bodies. Meeting space for periodic in-person stakeholder convenings or regional travel to attend standards-body meetings and conferences. Travel budget for engagement with regulatory bodies and steward-organization candidates (Months 1–36 = 2026-11-13 to 2029-10-13), with heavier travel in Months 24–36 (2028-10-13 to 2029-10-13) for stewardship search and Phase 3 partnership building.

9. Audio Production & Technical Infrastructure Manager

Contract Type: independent_contractor

Contract Type Justification: Audio Production & Technical Infrastructure Manager (Months 2–11 = 2026-12-13 to 2027-09-13) is a time-bounded, specialist role: secure studio capacity, coordinate 5,000-entry recording, run inter-rater training, and deliver encrypted storage infrastructure. While critical, this is a front-loaded, deliverable-based engagement with a clear exit point at Month 12 (2027-10-13) when audio is complete. The role benefits from external vendor relationships (audio studios, hosting/storage providers) that a contractor brings; internal FTE overhead is not justified for an 10-month, specialist task. Alternatively, a full-time employee if internal IT infrastructure and in-house recording are priorities; trade-off: cost and hiring delay vs. control.

Explanation: Secures audio recording studio capacity, manages pronunciation recording of the 5,000-word lexicon, coordinates inter-rater training and kappa calibration for pronunciation consistency scoring, oversees encrypted audio storage, and ensures backup and data-integrity protocols. Essential Months 2–11 (2026-12-13 to 2027-09-13) to deliver pronunciation guidance and meet the Month 12 (2027-10-13) lexicon freeze.

Consequences: Without audio-production oversight, studio scheduling and delivery slip, inter-rater training is inadequate, recording quality is inconsistent, and files are lost or unplayable; inter-rater kappa falls below 0.70, invalidating pronunciation consistency scoring; pronunciation guidance is unusable, weakening the ordinal and G2P fix; Phase 1 extends 4–8 weeks, compressing Phase 2 pilots and reducing data quality for the gate.

People Count: 1

Typical Activities: James secures studio capacity and contracts a recording partner by Month 2 (2026-12-13), with firm capacity guarantees for 5,000 entries and 2+ takes each. He budgets and tracks audio-production costs ($80K–$120K, estimate) and pivots to speech-synthesis baseline plus human verification if per-entry costs exceed $20. He designs inter-rater training materials and conducts calibration sessions with 3–4 raters on a 100–200 word pilot sample (Months 9–10 = 2027-07-13 to 2027-08-13), measuring Cohen's kappa and retraining raters if kappa falls below 0.70. He manages encrypted audio-file storage, backup protocols, and GDPR-compliant access controls by Month 6 (2027-04-13), conducts a data-protection audit by Month 8 (2027-06-13), and delivers all 5,000 entries with passing inter-rater checks by Month 11 (2027-09-13).

Background Story: James Okonkwo is a senior audio engineer and digital-infrastructure specialist with 6 years of experience managing large-scale audio-recording projects for language and speech-research programs. He has set up inter-rater training workflows, managed encrypted storage systems for sensitive audio biometric data, and coordinated international recording sessions across multiple time zones. James was contracted specifically because the 5,000-word pronunciation-guidance recording (Months 6–11 = 2027-04-13 to 2027-09-13) is a technically complex, time-bounded deliverable with high quality and reliability requirements: 10,000+ audio files, inter-rater calibration to kappa ≥0.75, secure backup and GDPR-compliant storage.

Equipment Needs: Professional audio recording and editing software (Audacity, Adobe Audition, or studio-grade equivalent). Secure file-transfer and backup systems (encrypted FTP, rsync, or cloud-based backup, e.g., AWS S3 with encryption). Inter-rater reliability assessment tools (spreadsheet or custom database for tracking rater agreement and kappa calculations). Encrypted storage infrastructure (hardware security modules, encrypted cloud servers, or on-premises secure servers) for hosting 10,000+ audio files with access controls and audit logs. Laptop with high-speed storage and processing for managing large audio datasets.

Facility Needs: Coordination and contract management for professional audio studio or language-recording partner (Months 2–11 = 2026-12-13 to 2027-09-13). Quiet studio or recording facility with professional audio equipment for inter-rater training calibration sessions and dry runs (Months 9–10 = 2027-07-13 to 2027-08-13; could be outsourced to a partner studio). Office space for managing studio contracts, tracking delivery timelines and coordinating inter-rater training. Secure on-premises or cloud-hosted server infrastructure for encrypted audio storage, backup and GDPR-compliant access control (location-agnostic; cloud or dedicated server).


Omissions

1. Absence of Quantitative Gate Thresholds and Pre-Registration Plan

The plan names four go/no-go metrics (ordinal error rate, comprehension speed, pronunciation consistency, 30-day retention) but does not specify quantitative pass/fail criteria (e.g., 'ordinal error must drop by ≥25%') or sample-size targets. Without pre-registered thresholds fixed before Month 11 (2027-09-13), the Month 24 (2028-10-13) go/no-go decision becomes subjective and disputable, undermining partner confidence and gate credibility.

Recommendation: By Month 5 (2027-03-13), commission the psychometrician to draft a pre-analysis plan specifying: (1) quantitative thresholds for each metric with explicit justification (e.g., ordinal error reduction ≥25% proposed, comprehension speed ≤10% slower than control proposed, pronunciation consistency kappa ≥0.75 proposed, 30-day retention ≥70% proposed); (2) minimum sample sizes per arm (≥80 completers proposed for 80% statistical power); (3) primary outcomes and intention-to-treat rules. Register this plan on Open Science Framework by Month 11 (2027-09-13) and publish publicly 30 days before Phase 2 begins. If pre-registration is not complete by Month 11 (2027-09-13), delay Phase 2 start and gate decision by 6–12 weeks to ensure thresholds are defensible.

2. Missing Construct Validity and Confound-Control Framework for Gate Metrics

The plan does not specify how to control for alternative explanations of measured effects. Repeated exposure to ordinals (even in standard form) might improve accuracy independent of Clear English; learner motivation to participate in a novel standard could inflate performance; accent proximity to learners' first language might make pronunciation scores high in both conditions. Without explicit control conditions and confound analyses, the gate metrics become scientifically disputable.

Recommendation: By Month 5 (2027-03-13), build a construct-validity section into the Outcome Metric Battery Design decision: (1) identify plausible alternative explanations for each metric (e.g., repeated exposure, motivation, accent proximity); (2) design explicit control conditions (e.g., standard-English ordinals with rule instruction vs. implicit exposure) to isolate Clear English effects; (3) measure manipulation checks (ask learners post-test which rule system they learned); (4) pre-register confound-analysis plan (e.g., regress ordinal error on baseline literacy, first-language phonology, study motivation). Publish this framework in the Month 11 (2027-09-13) pre-analysis plan. If effect sizes or inter-rater reliability at Month 18 (2028-04-13) reveal confounds larger than expected, conduct additional validity work by Month 21 (2028-07-13) rather than proceeding to the gate with weak data.

3. Unspecified Fallback if Inter-Rater Reliability Falls Below Target Kappa

The plan targets Cohen's kappa ≥0.75 (proposed) for pronunciation-consistency scoring, with a floor of 0.70 (proposed). However, no explicit action plan specifies what happens if rater calibration achieves only kappa 0.65–0.70. A weak inter-rater reliability inflates measurement noise by 20%, reducing statistical power to detect Clear English effects by 10–15%, risking a false-negative gate outcome that kills a viable standard or forces expensive rework.

Recommendation: Include in the Phase 1 schedule (by Month 8 = 2027-06-13): design inter-rater training and calibration protocol; recruit ≥3–4 raters with ESL/phonetics background; conduct training on the anchor accent (chosen by Month 3 = 2027-01-13) on a pilot sample of 100–200 words by Month 9 (2027-07-13); measure Cohen's kappa by Month 10 (2027-08-13) and require kappa ≥0.70 (floor) to proceed to full production. If kappa falls below 0.70 at Month 10 (2027-08-13), halt full production, conduct additional rater retraining and calibration (2–4 weeks, extending to Month 10.5 = 2027-08-28 = ~2027-08-28), and retest kappa by Month 11 (2027-09-13). If kappa remains below 0.70, flag to the editorial board for either a 4-week Phase 1 extension (new deadline Month 15 = 2028-01-13) or scope reduction (record only 3,000–4,000 highest-impact words). This ensures pronunciation-consistency scoring meets measurement-reliability standards before pilots begin.

4. Undefined Post-Project Stewardship Funding Model and Governance

The plan extends only to Month 36 (2029-10-13), when external funding and formal project governance end. However, the standard will require ongoing maintenance: responding to adoption feedback, managing version/change requests, updating the lexicon, and handling disputes over rule interpretation. Without a clear stewardship funding model and organizational home identified by Month 33 (2029-07-13), the standard could atrophy within 12–24 months (by Month 48–60 = 2030-10-13 to 2031-10-13). Adopter organizations will lose confidence in stability, reducing Phase 3 adoption by 30–50%.

Recommendation: By Month 24 (2028-10-13) (coinciding with the Phase 2 go/no-go decision), identify ≥2–3 potential permanent steward organizations (language-education non-profits, university consortiums, standards bodies such as ISO or TESOL) and document their capacity and mission alignment. By Month 27 (2029-01-13), approach the top candidates with a formal Stewardship Proposal specifying annual budget ($150K–$250K estimate), key responsibilities (responding to change requests, managing conformance claims, issuing errata, leading full review every 3–5 years) and decision authority. By Month 30 (2029-04-13), negotiate a formal Memorandum of Understanding (MOU) with at least one steward organization committing to assume stewardship for ≥10 years; have it signed and published by Month 33 (2029-07-13). Publish a public 5-year Stewardship Roadmap by Month 36 (2029-10-13) documenting review cycles, change-request prioritization, governance-committee composition and dispute-resolution procedures. If no steward commitment is secured by Month 33 (2029-07-13), flag to the editorial board that v1.0 public release is contingent on stewardship being in place, preventing a launch without long-term maintenance capacity.

5. Audio Production Bottleneck and Multi-Accent Scope Creep Risk

The plan commits to 5,000-word core lexicon with single-accent pronunciation guidance by Month 12 (2027-10-13). Audio production at scale (5,000 entries × ≥2 takes estimate = 10,000+ files) is bottlenecked by studio availability, rater training and inter-rater reliability calibration (target kappa ≥0.75 proposed). The plan does not estimate studio costs, scheduling lead times or contingency for technical failures. Additionally, pressure to add accents (British, American, Australian, Indian) could emerge at Month 9–12 (2027-07-13 to 2027-10-13), inflating audio budget by $50K–$100K (estimate) and straining Phase 1 contingency.

Recommendation: By Month 2 (2026-12-13), conduct detailed audio-production scoping: (1) reserve a professional recording studio or language-recording service with firm capacity guarantees for Months 6–11 (2027-04-13 to 2027-09-13); document lead times, file specifications and backup protocols in a signed contract; identify a contingency provider by Month 3 (2027-01-13); (2) estimate all-in cost per entry (speaker fees, editing, inter-rater scoring): if cost exceeds $20 per entry (estimate), pivot to hybrid approach—speech-synthesis baseline for all 5,000 words by Month 7 (2027-05-13), then human rater verification on the highest-friction 1,000–1,500 words by Month 11 (2027-09-13); (3) by Month 3 (2027-01-13), publish a board-approved policy deferring accent additions to post-v1.0, with a documented process for future requests; cap scope-creep risk by specifying that accent additions require a formal scope-change proposal with budget impact. (4) By Month 9 (2027-07-13), assess production progress and kappa-reliability status; if kappa falls below 0.70 (floor proposed) or costs exceed budget, halt and conduct 2–4 weeks targeted remediation by Month 10 (2027-08-13); if not resolved, flag to board for Phase 1 extension or scope reduction (record 3,000–4,000 words only, violating the 5,000-word constraint and requiring board waiver).

6. Insufficient Contingency Reserve and Pre-Gate Draw Procedure

The plan allocates a $0.35M reserve (10% of budget), with only $175K (5% of budget) available for pre-gate draws. A $300K overrun (8.6% of budget estimate) would exhaust the pre-gate draw cap by $125K, leaving no further contingency before the Month 24 (2028-10-13) go/no-go decision. If Phase 1 extends 4 weeks (~$85K estimate) and Phase 2 encounters unexpected psychometric validation costs or recruitment delays, the remaining headroom ($90K estimate) is inadequate for typical project contingencies.

Recommendation: Establish a clear pre-gate draw procedure by Month 1 (2026-11-13): (1) cap pre-gate draws at $175K (5% of budget, half the reserve), available only for pre-approved, evidence-backed gate-protection needs (e.g., psychometric re-validation, rater retraining, recruitment incentive increases); (2) require the project lead to request draws with written justification to the editorial board, specifying why the expense protects gate credibility and why it could not be anticipated; (3) maintain a running forecast of spending by Month 9 (2027-07-13) and assess whether Phase 2 can proceed on schedule; if remaining pre-gate headroom falls below $90K (estimate) or cumulative overrun exceeds $100K, convene the editorial board at Month 9 (2027-07-13) to decide whether to extend Phase 1 (costing ~$85K per month estimate), reduce Phase 2 scope (fewer cohorts, shorter follow-up) or release additional reserve funds with a board-documented decision. (4) Implement monthly project-status reviews and rolling 6-month spending forecasts from Month 1 (2026-11-13) onward, with escalation to the program lead if any line item tracks >10% over budget.


Potential Improvements

1. Clarify Editorial Board Tiebreaker Mechanism and Timeline

The plan specifies an external tiebreaker arbiter for rule disputes but does not detail how to engage the arbiter, timeline for tiebreaker decisions, cost ceiling or how minority-position documentation will be handled. Vague escalation procedures could delay rule finalization, compressing Phase 2 pilots by 4–12 weeks. A formal, pre-negotiated tiebreaker process with clear decision timelines (e.g., arbiter must rule within 2 weeks) ensures rule disputes do not stall the project.

Recommendation: By Month 3 (2027-01-13), the editorial board must identify and secure a written agreement with an external neutral arbiter (e.g., a senior linguist or standards-development expert from an external institution such as a university or ISO body). Document in the Editorial Board Charter: (1) arbiter's decision authority (e.g., 'arbiter is called if voting deadlocks 4–5 after two discussion rounds'); (2) decision timeline (e.g., 'arbiter must render a written ruling within 2 weeks of referral'); (3) arbiter cost (cap at $10K–$20K estimate per project, or $5K per decision estimate); (4) publication protocol ('both majority and arbiter-preferred positions published in rule rationale'). By Month 5 (2027-03-13), have the arbiter's signed agreement on file and publish a one-page summary on the project website explaining the tiebreaker process. If a rule dispute is referred to the arbiter, the project lead tracks the timeline and escalates if the arbiter's decision takes >2 weeks.

2. Establish Clear Partner Enrollment Guarantees and Make-Up Protocols

The plan requires ≥3–4 ESL programs and ≥2–3 technical-training organizations to provide ≥115 learners per arm (460 total estimate) and achieve a dropout rate ≤30% (estimate). However, the team-members document does not specify what happens if a partner fails to meet enrollment targets or if a learner misses a session. Vague make-up and escalation procedures could lead to unplanned sample-size reductions and statistical power loss.

Recommendation: By Month 3 (2027-01-13), finalize written partner Memoranda of Understanding (MOUs) that specify: (1) minimum guaranteed enrollment (e.g., 'Partner A commits to enroll ≥75 ESL learners by Month 13 = 2027-11-13'); (2) assessment schedule (e.g., 'four in-person sessions of 60–90 minutes each across Months 13–24 = 2027-11-13 to 2028-10-13'); (3) make-up session protocol ('any learner missing a scheduled session has the option for a make-up within ±1 week'); (4) escalation ('if enrollment falls >10% short of guarantee by Month 14 = 2027-12-13, partner notifies project lead within 2 days and project lead activates backup recruitment'); (5) incentive and payment terms (e.g., '$75 per learner for completion incentive; partner receives $40 per learner-session to cover costs'). By Month 13 (2027-11-13), the Cohort Manager confirms that enrollment meets targets and begins tracking attendance. Document all make-up sessions and attendance deviations in the master participant log to assess dropout trends early.

3. Specify Pronunciation Consistency Scoring Procedure and Rater Independence

The plan designates pronunciation consistency as a gate metric requiring Cohen's kappa ≥0.75 (proposed target) inter-rater reliability. However, it does not detail: (1) how raters will be selected and trained; (2) whether raters must be independent of the project team; (3) how audio files will be presented to raters (randomized, blinded to condition); (4) how disagreements will be resolved. Without these procedural details, pronunciation scoring could be biased or inconsistently applied, inflating kappa or introducing rater drift.

Recommendation: By Month 4 (2027-02-13), the psychometrician and audio-production manager must draft a detailed Pronunciation Scoring Protocol specifying: (1) rater recruitment and training (e.g., 'at least 3–4 raters with ESL teaching or speech-pathology background; independent of Clear English development team; trained on reference-accent anchor by Month 9 = 2027-07-13 using a 100–200 word calibration sample'); (2) scoring procedure ('raters score audio files in randomized order, blinded to condition and learner identity; each file scored by ≥2 independent raters; scoring on a validated scale, e.g., 1–5 rating or binary match/mismatch'); (3) inter-rater reliability check (Cohen's kappa calculated on calibration sample by Month 10 = 2027-08-13; target ≥0.75 proposed, floor 0.70 proposed); (4) disagreement resolution ('if raters disagree, a third independent rater breaks the tie; if tie-breaker also disagrees, entry marked as 'unclear' and excluded from scoring'); (5) rater-training documentation ('all raters sign confidentiality agreements and a statement confirming they received training on the scoring protocol'). Publish this protocol in the pre-analysis plan (Month 11 = 2027-09-13) to ensure scoring is transparent and auditable.

4. Define Lexicon Coverage Audit Procedure and Expansion Trigger

The plan specifies that the 5,000-word core lexicon must cover ≥85% of pilot running text (proposed threshold) and commits to a coverage audit by Month 8 (2027-06-13), with fixes by Month 10 (2027-08-13). However, it does not specify: (1) which text corpus will be analyzed (pilot ESL curriculum? technical glossaries? both?); (2) how coverage will be calculated (types vs. tokens?); (3) what constitutes an 'expansion' (adding words to the core 5,000, or creating a secondary 500-word block?); (4) cost and timeline if expansion is needed.

Recommendation: By Month 3 (2027-01-13), specify the lexicon-audit scope: (1) coverage will be calculated on the actual pilot curriculum and technical-glossary documents planned for use in Phase 2, plus running text from at least 2–3 existing ESL textbooks; (2) coverage metric is word type coverage ('how many distinct word forms in pilot text are in the 5,000-word list') calculated on the first 10,000 running words (or entire curriculum if <10,000 words) to approximate early-learning engagement; (3) coverage target ≥85% (proposed); (4) if coverage falls short, the 5,000-word list may be expanded by drawing from a pre-compiled secondary candidate list (e.g., the next 500 highest-frequency words from the same corpus used to build the base 5,000). By Month 8 (2027-06-13), conduct the audit and identify any shortfalls. If expansion is needed, allocate $20K–$50K (estimate) for pronunciation recording of new entries and revise recording timeline: record new entries by Month 11 (2027-09-13) (compressing other work or extending Phase 1 by 1–2 weeks). Document the final lexicon and its coverage in the published v1.0 standard.

5. Clarify Data Privacy and Participant Consent Workflow

The plan notes that ethics/IRB approval and GDPR compliance are required by Month 6 (2027-04-13) but does not specify the consent workflow or data-retention schedule. Ambiguity could delay ethics approval or create compliance gaps, jeopardizing pilot recruitment or exposing the project to regulatory investigation.

Recommendation: By Month 2 (2026-12-13), the project lead and regulatory affairs manager must engage an ethics review committee (IRB, research ethics committee) and draft a study protocol specifying: (1) research classification (is the pilot human-subjects research requiring IRB review? Likely yes; confirm with the IRB); (2) informed-consent process (in writing, in multiple languages if ESL learners speak different home languages, using plain language; electronic or paper consent; right to withdraw and data deletion); (3) data types collected and retention schedule ('audio recordings: 3 years post-analysis or until learner requests deletion; test scores and demographics: 5 years for replication studies; consent forms: 3 years minimum for compliance audit'); (4) access controls ('authorized research team members only; all team members sign data-use agreements'); (5) storage and security ('encrypted on-premises or cloud server, GDPR-compliant, with backup and audit logs'). Obtain written ethics approval by Month 6 (2027-04-13). By Month 10 (2027-08-13), publish standard informed-consent forms and a Data Protection and Privacy Policy on the project website, clearly stating how long data is retained and participants' rights. Provide all participants a copy of the consent form and privacy policy at enrollment.

6. Document Phase 2 Pilot Timeline and Contingency Windows

The plan specifies Phase 2 occurs Months 12–24 (2027-10-13 to 2028-10-13) with enrollment complete by Month 13 (2027-11-13) and data lock by Month 22 (2028-08-13), leaving only 2 months for analysis and gate-decision dossier preparation (Months 22–24 = 2028-08-13 to 2028-10-13). This timeline is compressed and leaves little room for data-quality issues or analysis surprises. Clarifying the pilot schedule with explicit checkpoints and contingency windows improves timeline discipline and reduces gate-decision risk.

Recommendation: Establish a formal Phase 2 schedule and contingency plan by Month 9 (2027-07-13): (1) Enrollment Phase: all recruitment complete by Month 13 (2027-11-13); 1-week buffer for stragglers (to Month 14 = 2027-12-13); (2) Assessment Phase: four sessions per participant across Months 13–24 (2027-11-13 to 2028-10-13); Session 1 by Month 14 (2027-12-13); Session 2 by Month 17 (2028-03-13); Session 3 by Month 20 (2028-06-13); Session 4 by Month 23 (2028-09-13); (3) 30-day follow-up: completed by Month 22 (2028-08-13) (last session Month 23 = 2028-09-13 + 30 days ~Month 24 = 2028-10-13 or slightly later; data collection extended 1–2 weeks if needed); (4) Data lock and quality check: Month 22 (2028-08-13); (5) Analysis and dossier preparation: Months 22–24 (2028-08-13 to 2028-10-13); gate decision Months 24 (2028-10-13). If data quality issues are identified (e.g., >10 files corrupted, dropout exceeds 35%, inter-rater kappa <0.70 in preliminary checks), flag to the editorial board by Month 21 (2028-07-13) with options: (a) extend Phase 2 by 3–6 months for remediation or additional data collection; (b) proceed with inconclusive data and conditional gate decision; (c) conduct targeted re-assessment on a subset of participants. Document all contingency triggers and board-decision authority in the Phase 2 Project Plan by Month 12 (2027-10-13).

7. Specify Licensing Model Decision Criteria and Timeline

The plan states that a Licensing and Name Stewardship decision will be made by Month 6 (2027-04-13), choosing between three options: (a) permissive open license with no name restrictions; (b) name-as-certification-mark with a published conformance checklist; (c) share-alike license requiring divergent works to adopt a distinct name. However, it does not specify which decision criteria (ease of adoption, protection against fragmentation, governance overhead) will weigh most heavily or who decides in case the editorial board is divided.

Recommendation: By Month 3 (2027-01-13), the regulatory affairs manager must commission a legal analysis (estimated $10K–$20K) comparing the three licensing scenarios on: (1) adoption friction (ease for publishers to adopt); (2) fragmentation risk (likelihood of non-conforming variants); (3) governance overhead ($cost and staff time for certification/dispute resolution); (4) perceived fairness/openness (stakeholder perception of gatekeeping). By Month 4 (2027-02-13), present the analysis to the editorial board with a recommendation. Establish a board vote by Month 5 (2027-03-13) with clear voting rules (e.g., simple majority; if tied, program lead + external arbiter decide). The chosen model must be published with explicit rationale by Month 6 (2027-04-13). If the board selects certification mark (option b), publish a free, light conformance checklist by Month 12 (2027-10-13) specifying exactly what materials must do to qualify as Clear English, with a goal of reducing gatekeeping perception and enabling fast approval for most straightforward adaptations.

8. Establish Monthly Budget Tracking and Spending Forecast Protocol

The plan mentions budget controls and a Month 9 (2027-07-13) spending review but does not specify: (1) who tracks spending monthly (project lead? dedicated finance person?); (2) what spending forecast tool is used; (3) what variance thresholds trigger escalation (e.g., >10% over budget on a line item?); (4) escalation procedure. Without clear financial discipline, budget overruns can accumulate silently, consuming contingency reserves without board awareness.

Recommendation: By Month 1 (2026-11-13), establish a monthly budget-tracking system: (1) project lead or a part-time finance administrator maintains a detailed spending log in a shared spreadsheet or accounting system, tracking actual spend vs. budget for each major line item (staff, psychometrics, audio production, pilot incentives, travel, etc.) monthly; (2) by the 5th business day of each month, produce a summary dashboard showing year-to-date actuals, forecast-to-completion, and variance (actual spend % of monthly budget allocation); (3) variance threshold: escalate to the editorial board if any line item is >10% over budget or if cumulative overrun exceeds $50K in a single month (estimate); (4) at Month 9 (2027-07-13), conduct a formal Phase 1 spending review: assess whether Phase 1 is on budget; if overrun >$100K, convene the board to decide whether to extend Phase 1, reduce Phase 2 scope or release additional reserve funds; (5) establish rolling 6-month spending forecasts at Months 9 (2027-07-13), 15 (2028-01-13), 21 (2028-07-13) and 27 (2029-01-13) to identify future budget gaps early and allow mid-course corrections. Document all budget decisions and board actions in the decision log maintained by the governance administrator.

9. Define Pilot Fidelity Monitoring and Rule-Compliance Checkpoints

The plan specifies that curriculum designers will conduct dry runs and support fidelity checks during pilots (Months 13–24 = 2027-11-13 to 2028-10-13), but does not detail: (1) what 'fidelity' means (consistent rule application? all rules taught? rules taught in the specified order?); (2) how fidelity will be measured (classroom observations? curriculum deliverable reviews? learner quiz on rule accuracy?); (3) how rule violations will be corrected. Poor fidelity could introduce confounds (learners in one site receive incomplete rule instruction), inflating measurement noise and weakening gate evidence.

Recommendation: By Month 12 (2027-10-13), the curriculum design team must document a Fidelity Monitoring Protocol specifying: (1) definition of fidelity: ('Clear English' cohorts are taught all core rules (ordinals, morphology, homographs, pronunciation guidance) in the prescribed order and frequency; control cohorts receive standard-English instruction); (2) fidelity measures: (a) instructor compliance checklist (curriculum designers or an independent observer confirm that each of the 4–6 core rules was taught in the prescribed sessions); (b) learner comprehension check (brief 5–10 minute quiz after each rule unit, scored to confirm learners understood the rule); (c) delivery logs (instructors record which rules were taught each session and any deviations); (3) fidelity monitoring schedule: Month 14 (2027-12-13) initial site visit to all partners; Month 17 (2028-03-13) midpoint fidelity audit (review delivery logs and conduct random classroom observations); Month 23 (2028-09-13) final audit; (4) corrective action: if fidelity is <80% (estimated) at any site by Month 17 (2028-03-13), the curriculum team contacts the instructor, reviews the lesson materials, and provides coaching; if fidelity remains <80% by Month 20 (2028-06-13), flag to the project lead for consideration of excluding that site's data or requiring re-teaching. Document all fidelity findings in the gate-decision dossier (Months 22–24 = 2028-08-13 to 2028-10-13) to contextualize any low ordinal-accuracy or pronunciation-consistency scores.

Critique and recommended actions from domain experts.

1 Expert: Applied Psychometrician & Assessment Design Specialist

Knowledge: Educational measurement, validity and reliability analysis, pre-analysis plan design, inter-rater agreement (Cohen's kappa), statistical power analysis, ESL assessment instruments

Why: The pre-registration of four gate metrics (ordinal error, comprehension speed, pronunciation consistency, 30-day retention) by Month 11 (2027-09-13) is critical to project credibility. Current thresholds are proposals; expert will lock defensible, empirically justified numeric targets and ensure the Phase 2 go/no-go decision is not disputable. Weak or absent thresholds directly threaten gate validity and Phase 3 adoption (20–50% loss noted in risk register).

What: Design and pre-register a quantitative assessment battery: specify minimum sample size per arm (justifying the ≥80 completers proposal), primary and secondary outcomes, intention-to-treat rules, rater reliability targets (kappa ≥0.70 floor), and pass/fail thresholds for each metric. Deliver a pre-analysis plan draft by Month 5 (2027-03-13) for board review and formal registration by Month 11 (2027-09-13).

Skills: Instrument validation, experimental design, effect-size estimation, power analysis, inter-rater calibration, preregistration workflow (OSF, similar platforms), ESL assessment literacy

Search: psychometrician language testing ESL assessment design, applied measurement specialist educational validity, Cohen's kappa inter-rater reliability training

1.1 Primary Actions

1.2 Secondary Actions

1.3 Follow Up Consultation

At the next consultation, discuss: (1) Psychometrist hiring timeline and pre-analysis plan schedule—confirm whether a validity study by Month 5 (2027-03-13) is feasible with current budget and staffing. (2) Mini-pilot design and site selection—identify specific ESL programs and technical-training organizations to approach for the Month 2–4 (2026-12-13 to 2027-02-13) mini-pilot. (3) Audio production and rater fallbacks—confirm whether hybrid synthetic + verification model is acceptable if human inter-rater kappa is <0.70. (4) Steward candidates and funding models—identify organizations with sufficient financial stability and mission alignment to sustain $150K–$250K annual stewardship post-Month 36 (2029-10-13). (5) Regulatory and standards-body engagement strategy—clarify which jurisdictions require formal approval before pilots can operate and whether research-study framing can bypass some delays.

1.4.A Issue - Pre-Registration and Psychometric Validation Are Dangerously Underspecified

The project plan specifies four gate metrics (ordinal error ≥25% reduction, comprehension speed ≤10% slower, pronunciation consistency ≥15% above control, 30-day retention ≥70%) as 'proposed thresholds,' not pre-registered. The psychometrician hire is scheduled for Month 2 (2026-12-13), but the pre-analysis plan (PAP) is not due until Month 9 (2027-07-13), with pre-registration by Month 11 (2027-09-13)—only 30 days before Phase 2 pilots begin. This compressed timeline creates three failures: (1) no pilot validity study (N=20–30) to calibrate thresholds before they are locked; (2) no time to correct instrument ambiguity if the dry run at Month 10 (2027-08-13) exposes flawed items; (3) post-hoc claims by educators and regulators that thresholds were rigged or arbitrary, undermining the gate decision credibility that is the entire epistemic foundation of the project.

1.4.B Tags

1.4.C Mitigation

Hire the psychometrician by Month 1 (2026-11-13) (not Month 2 = 2026-12-13) and commission a phased deliverable: (1) By Month 3 (2027-01-13), submit a draft instrument specification, item pool and effect-size justification. (2) By Month 5 (2027-03-13), conduct and complete a small pilot validity study (N=20–30 adult ESL learners and native speakers, 2–3 assessment sessions) to estimate effect sizes and refine items. (3) By Month 8 (2027-06-13), deliver the final pre-analysis plan with numeric thresholds backed by observed effect sizes, not proposals. (4) Pre-register by Month 10 (2027-08-13) (not Month 11 = 2027-09-13), allowing 6 weeks for editorial board review and early third-party comment. If a validity study is not feasible by Month 5 (2027-03-13), defer Phase 2 pilots and extend Phase 1 by 8–12 weeks (cost ~$170K–$255K, estimate) to establish credible baselines.

1.4.D Consequence

Without pre-registered, empirically justified thresholds, the Month 24 (2028-10-13) go/no-go decision will be scientifically disputable. Educators and standards bodies will claim the thresholds were set to produce a predetermined outcome, reducing Phase 3 adoption by 20–50% and triggering public criticism. A false-positive gate (passing weak evidence) could launch a flawed standard; a false-negative (rejecting real effects) wastes $1.2M on inconclusive pilots and forfeits 12 months' credibility building.

1.4.E Root Cause

The project plan prioritizes timeline compression over epistemic rigor. Hiring the psychometrician 1 month after project start, then compressing the validity study, instrument refinement and pre-registration into 9 months, reflects an assumption that thresholds can be proposals until Month 11 (2027-09-13). This assumption is false: standards bodies, funders and educators demand empirically grounded thresholds locked before evidence collection begins. The root cause is insufficient allocation of Phase 1 time and budget to psychometrics.

1.5.A Issue - Pilot Recruitment and Retention Strategy Lacks Contingency Depth and Early Verification

The plan specifies signed commitments from ≥3 ESL programs and ≥2 technical organizations by Month 3 (2027-01-13), with enrolment beginning Month 12 (2027-10-13) (9 months later) and completion by Month 13 (2027-11-13). This 9-month lag creates three risks: (1) signed letters are non-binding or evaporate if institutional circumstances change; (2) no early verification of learner eligibility, willingness or capacity until Month 12 (2027-10-13), when reversal costs are maximal; (3) no pilot recruitment trial run (mini-pilot, N=20–30) to test assessment logistics, dropout drivers and incentive adequacy before full-scale enrolment. The plan budgets for a 30% dropout tolerance but provides no data-driven dropout prediction, contingency learner pools, or escalation triggers (e.g., 'if dropout exceeds 20% by Month 15 = 2028-01-13, recruit an additional cohort of 40–50').

1.5.B Tags

1.5.C Mitigation

(1) By Month 2 (2026-12-13), recruit and run a mini-pilot (N=20–30 adult learners and native-speaker technical trainees, at 1–2 partner sites) through at least 2 full assessment cycles (Months 2–4 = 2026-12-13 to 2027-02-13). Document actual dropout, reasons for attrition, dropout timing, incentive sufficiency and assessment burden. (2) By Month 4 (2027-02-13), use mini-pilot data to calibrate a dropout-prediction model and revise enrolment and retention protocols. (3) By Month 3 (2027-01-13), obtain signed Memoranda of Understanding (not just letters) with explicit clauses: guaranteed learner supply with liquidated damages ($500–$1K per missing learner, estimate) if recruitment targets are missed; institution's escalation contact and 30-day notification of shortfalls. (4) By Month 6 (2027-04-13), conduct a recruitment triage: identify learners at high dropout risk (e.g., attendance history, work instability) and apply differentiated retention tactics (higher incentives, flexible scheduling, peer cohorts). (5) Establish an escalation trigger: if dropout exceeds 20% by Month 15 (2028-01-13), immediately recruit a standby cohort of 40–50 learners (cost ~$30K–$50K, estimate) to reach the minimum 80 per-arm threshold.

1.5.D Consequence

If pilot recruitment falls short or dropout exceeds 30%, effective sample size drops below 80 per condition, reducing statistical power to ~60% (estimate). This inflates the Type II error (false-negative) risk: real Clear English effects are not detected, triggering a false-negative gate outcome and a no-go decision despite potential efficacy. Alternatively, retention shortfalls compress the data-collection window and force rushed, incomplete 30-day follow-up assessments, invalidating the retention metric. Either path wastes Phase 2 budget (~$1.2M) and forces a 6-month extension (cost ~$300K–$600K, estimate) or project termination.

1.5.E Root Cause

The recruitment strategy treats pilot partners as static commitments rather than active collaborators with changing capacity. The 9-month lag between signed commitments and actual enrolment reflects an assumption that letters of intent guarantee delivery without ongoing relationship management. The plan lacks early verification (mini-pilot) and contingency learner pools, indicating insufficient budgeting for recruitment risk and retention management. The cohort manager is hired at Month 6 (2027-04-13), after recruitment design should be finalized, creating a downstream, reactive posture.

1.6.A Issue - Inter-Rater Reliability and Audio Production Timeline Creates a Critical Single-Point Failure

The plan specifies audio recording of 5,000 lexicon entries (≈10,000 files at 2 takes) during Months 6–11 (2027-04-13 to 2027-09-13), with inter-rater training and calibration during Months 8–10 (2027-06-13 to 2027-08-13). If inter-rater Cohen's kappa falls below 0.70 at Month 10 (2027-08-13), the fallback is '2–4 weeks additional retraining.' This assumes retraining succeeds, but provides no contingency if kappa remains ≤0.70 after retraining. The plan proposes a 4-week Phase 1 extension (~$85K cost, estimate) as the only fallback, but this single extension does not address the core failure modes: (1) selected raters may be unsuitable for pronunciation judgement (accent, ear training, language background); (2) audio quality or speaker training may be poor, inflating noise; (3) the reference accent anchor may not be sufficiently defined for consistent scoring. Without alternative rater sources, pre-screening, or a synthetic-audio fallback, any kappa failure at Month 10 (2027-08-13) blocks full Phase 2 launch.

1.6.B Tags

1.6.C Mitigation

(1) By Month 2 (2026-12-13), establish rater pre-screening criteria: phonetics or applied-linguistics background (MA or equivalent), native or native-like proficiency in the reference accent, and prior rater-training experience. Pre-screen at least 6–8 candidate raters by Month 4 (2027-02-13), testing each on a 50-word calibration sample to identify the 3–4 most reliable. (2) By Month 3 (2027-01-13), finalize and document the reference accent anchor in a 2–3 page specification: vowel inventory, key consonant contrasts, stress and intonation patterns, and recordings of example words. Provide raters with this spec and 20–30 anchor exemplars by Month 7 (2027-05-13). (3) By Month 5 (2027-03-13), conduct a micro-pilot recording session (100–200 entries) with the top rater candidates; measure inter-rater kappa on this sample by Month 6 (2027-04-13). If kappa ≥0.75, proceed to full production by Month 7 (2027-05-13). If 0.70–0.74, implement targeted retraining (focused on misaligned phoneme categories) and retest by Month 7.5 (2027-05-28). If <0.70, pivot immediately to a hybrid model: (a) Synthetic speech (TTS) baseline for all 5,000 entries by Month 8.5 (2027-06-28) (cost $15K–$25K, estimate); (b) human rater verification only on the top 1,500–2,000 highest-friction words (irregular, diphthongs, schwa words) by Month 11 (2027-09-13). (4) By Month 9 (2027-07-13), if human recording is still in progress, secure a backup studio and a secondary rater by Month 8 (2027-06-13) to parallelise sessions and reduce single-vendor risk.

1.6.D Consequence

If inter-rater kappa falls below 0.70 and retraining fails, the project faces a hard stop at Month 10.5 (2027-08-28). Proceeding to Phase 2 with kappa <0.70 inflates the pronunciation-consistency metric's measurement error by 20–30%, reducing statistical power to detect true Clear English effects by 10–15% (estimate). The gate outcome becomes unreliable: pronunciation consistency could falsely pass (Type I error, false positive) or falsely fail (Type II error), invalidating the go/no-go decision. A 4-week Phase 1 extension addresses timeline slippage but not the underlying validity crisis. Without a pre-planned hybrid (synthetic + verification) fallback, kappa failure forces a 12-week extension (~$170K–$255K cost, estimate) or scope reduction (recording only 3,000 words, violating the 5,000-word user constraint).

1.6.E Root Cause

The audio production timeline is on the critical path, compressed into 6 months (Months 6–11 = 2027-04-13 to 2027-09-13) with only a 4-week contingency buffer. The project assumes raters can be trained to kappa ≥0.70 by Month 10 (2027-08-13), but provides no pre-screening, no rater-selection validation and no synthetic-audio fallback plan. The reference accent anchor is not finalized until Month 3 (2027-01-13) (or later), leaving only 3–4 months for raters to internalize the standard before calibration testing. The single-point failure is the absence of a hybrid recording strategy (synthetic baseline + verification subset) that would allow Phase 2 launch even if human rater kappa is delayed or subthreshold.


2 Expert: ESL Curriculum & Adoption Lead

Knowledge: Adult ESL pedagogy and program management, publisher partnerships, TESOL/IATEFL networks, supplementary-module design and integration, learner retention and engagement strategies

Why: Pilot recruitment, retention and partner engagement are high-risk; the plan requires ≥115 enrolled per arm by Month 13 (2027-11-13), ≤30% dropout, and signed commitments from ≥3 ESL programs and ≥2 technical-training orgs by Month 3 (2027-01-13). The expert will secure and manage these partnerships, design the supplementary-module positioning to maximize teacher buy-in, and lead the educator liaison function to prevent the 'external imposition' perception flagged in threats.

What: By Month 1 (2026-11-13), identify and formally pitch 4–5 ESL programs and 2–3 technical orgs; by Month 3 (2027-01-13), obtain signed letters of understanding guaranteeing cohort size, assessment scheduling and per-learner payment terms. Co-design pilot protocols with teacher advisory panels; hire and direct the 1.0 FTE Cohort Manager (by Month 6 = 2027-04-13); establish quarterly practitioner check-ins to maintain retention and collect early adoption signals.

Skills: Program management, stakeholder engagement and negotiation, ESL syllabus design, teacher professional development, retention-focused course design, TESOL/IATEFL credibility and networks

Search: ESL curriculum director adult language programs, TESOL practitioner liaison educator engagement, ESL publisher partnerships supplementary materials

2.1 Primary Actions

2.2 Secondary Actions

2.3 Follow Up Consultation

At the next meeting, we must address: (1) Power analysis and sample-size justification—what effect sizes do you expect for ordinal error reduction and pronunciation consistency, and do 80 completers per arm provide adequate statistical power? (2) Which ESL programs and technical-training sites have been informally approached, and what is their likelihood of commitment by Month 3 (2027-01-13)? (3) Steward candidates—have you identified any universities, language non-profits, or standards bodies willing to house the standard for $150K–$250K per year? (4) Audio cost and rater availability—what quotes have you obtained from professional studios, and do you have 3–4 qualified raters (ESL or phonetics background) available by Month 8 (2027-06-13)? (5) Regulatory landscape—which education and safety authorities (Ofqual, state education departments, OSHA, HSE) must approve or endorse adoption in your target jurisdictions, and what are their timelines?

2.4.A Issue - Gate Metrics Are Still Proposals, Not Pre-Registered. This Is a Critical Credibility Risk.

The plan lists four gate thresholds (ordinal error ≥25% reduction, comprehension ≤10% slower, pronunciation consistency ≥15% above control, 30-day retention ≥70%) as 'proposed' figures. None are pre-registered on an open repository, no power analysis justifies the sample size (80 per arm), and no independent psychometrician has signed a contract specifying deliverables. Without pre-registration by Month 11 (2027-09-13), the Month 24 (2028-10-13) go/no-go decision will be scientifically indefensible. Regulators, standards bodies and publishers will claim the thresholds were set post-hoc to justify a desired outcome.

2.4.B Tags

2.4.C Mitigation

Execute immediately: (1) By Month 2 (2026-12-13), hire an independent psychometrician (signed contract, $150K–$200K budget). (2) By Month 5 (2027-03-13), deliver a pre-analysis plan with numeric thresholds, sample-size power analysis, and intention-to-treat rules. (3) By Month 11 (2027-09-13), register the complete plan on Open Science Framework or Aspredicted.org, with board sign-off in writing. (4) Publish thresholds on the project website immediately for third-party review. This is non-negotiable for Phase 2 credibility.

2.4.D Consequence

A disputed or undefended gate decision will fracture stakeholder confidence: standards bodies may refuse to cite the standard, ESL publishers will hesitate to adopt, and a false-positive outcome (weak evidence supporting a GO) will damage adoption by 20–50% in Phase 3. The project will be perceived as academically dishonest, not rigorous.

2.4.E Root Cause

Empty

2.5.A Issue - Pilot Partner Commitments Are Not Yet Signed. Recruitment Failure Will Invalidate Phase 2.

The plan calls for 'signed commitments by Month 3 (2027-01-13)' from ≥3 ESL programs and ≥2 technical-training organizations. No evidence is presented that these partners have been approached, that they have provisionally agreed, or that they understand the commitment (≥50 learners per partner, 4 in-person sessions, 30-day follow-up, demographic data collection). If recruitment stalls or dropout exceeds 30%, the effective sample size falls below 80 per arm, invalidating statistical power and forcing a 3–6 month Phase 2 extension ($300K–$600K). No contingency plan specifies how to recover if a partner withdraws.

2.5.B Tags

2.5.C Mitigation

Action required by Month 1 (2026-11-13): (1) Identify and formally approach 4–5 ESL programs and 3 technical-training sites with a one-page partnership proposal specifying cohort size, assessment schedule, incentives ($50–$150 per learner), and partner payment ($30–$50 per session). (2) By Month 3 (2027-01-13), secure signed letters of understanding with binding enrollment guarantees. (3) Hire a dedicated Phase 2 Cohort Manager (1.0 FTE, $60K–$80K/year) by Month 6 (2027-04-13) to manage retention, track attendance, and conduct mid-phase check-ins. (4) Over-recruit to ≥115 per arm (460 total) to buffer for a 30% dropout rate. If recruitment fails by Month 6 (2027-04-13), escalate to the editorial board immediately.

2.5.D Consequence

Without signed commitments, Phase 2 begins with no enrolled learners. Recruitment delays compress the pilot window, forcing a 3–6 month Phase 2 extension that consumes the $175K pre-gate reserve and leaves a $35K shortfall. A no-go outcome becomes more likely, returning $1.2M unspent and delaying publication to Month 39 (2030-01-13) or later, breaking the 36-month timeline.

2.5.E Root Cause

Empty

2.6.A Issue - Post-Project Stewardship Is Unfunded. Version 1.0 Release Depends on a Commitment That Does Not Yet Exist.

The plan specifies that v1.0 must be released by Month 30 (2029-04-13) 'conditional on a written steward commitment.' No steward organization has been approached, no letters of interest have been collected, and no funding source for the $150K–$250K per year stewardship cost has been identified. The plan cannot credibly promise a v1.0 release without a signed commitment in hand. After Month 36 (2029-10-13), the standard will atrophy: corrections will accumulate unanswered, adopter confidence will degrade, and Phase 3 adoption will fall by 30–50% within 24–36 months.

2.6.B Tags

2.6.C Mitigation

By Month 12 (2027-10-13), launch a Standing Stewardship Committee (2–3 board members, 4–6 hours/month). By Month 18 (2028-04-13), identify 2–3 candidate steward organizations (language non-profits, university consortiums, ISO committees) and audit their 3+ years of financials, governance, and standards-maintenance experience. By Month 24 (2028-10-13), present a formal Stewardship Proposal to the top 2 candidates specifying annual budget ($150K–$250K), responsibilities (change requests, conformance claims, errata), and decision authority. Request a written letter of interest by Month 27 (2029-01-13) and a signed MOU by Month 30 (2029-04-13). Freeze v1.0 release until the MOU is signed.

2.6.D Consequence

Without a funded steward, the standard becomes orphaned post-Month-36. Fragmentation accelerates: unofficial forks emerge, conformance claims go unanswered, and third-party adoption stalls. By Month 60 (2031-10-13), the standard is perceived as abandoned, reducing Phase 3 uptake by 30–50% and eroding the credibility the project invested 3 years to build.

2.6.E Root Cause

Empty


3 Expert: Language Standardization & Governance Expert

Knowledge: Language standards bodies (ISO, ICAO, ASD-STE100), editorial board governance and decision-making, change-control and versioning frameworks, standards adoption and third-party conformance

Why: The project's editorial board charter, voting rules, tiebreak arbiter and post-v1.0 stewardship model are underspecified and risk deadlock (flagged in weaknesses). This expert will codify governance (Decision 13: Editorial Board Seat Allocation), lock the release cadence and licensing framework (Decision 10 & 11), and secure a permanent steward by Month 24 (2028-10-13)—directly preventing the 'unfunded stewardship after Month 36 (2029-10-13)' threat that could degrade Phase 3 adoption by 30–50% within 24–36 months.

What: By Month 1 (2026-11-13), draft and publish a 2–3 page Editorial Board Charter specifying voting rules, tiebreak arbiter selection and cost cap ($5K–$20K estimate), conflict-of-interest rules and term limits. By Month 5 (2027-03-13), retain and brief the external arbiter. By Month 6 (2027-04-13), finalize and publish the Licensing and Name Stewardship Policy (certification-mark approach) and Change-Control & Release Cadence framework. By Month 24 (2028-10-13), identify and secure a written commitment from a steward organization ($150K–$250K annually, 10+ years).

Skills: Language standards governance (ISO, ICAO precedent), editorial decision architecture, third-party conformance auditing, intellectual property and certification-mark strategy, post-project stewardship and funding models

Search: language standards governance expert ASD-STE100 ISO liaison, editorial board structure decision-making framework, standards stewardship funding sustainability

3.1 Primary Actions

3.2 Secondary Actions

3.3 Follow Up Consultation

At the next consultation (suggest Month 1 = 2026-11-13), present: (1) a signed contract with the independent psychometrician and a draft statement of work for the pre-analysis plan, power analysis, and pre-registration; (2) a published Editorial Board Charter with voting rules, arbiter selection, and conflict-of-interest rules; (3) a 3-4 page Regulatory Landscape Summary identifying key standards bodies and their approval pathways; (4) initial outreach letters to at least 4-5 ESL programs and 2-3 technical-training organizations with a partnership proposal. By Month 3 (2027-01-13), present signed pilot partner commitments and confirmation of the Cohort Manager hire. By Month 6 (2027-04-13), present the finalized Licensing and Name Stewardship Policy, audio studio capacity confirmation with cost audit, ethics-board approval, and data-protection policies. By Month 11 (2027-09-13), present the pre-registered gate metrics on Open Science Framework with independent psychometrician sign-off, final rule set with published rationale, and rater inter-rater reliability dry-run results (target kappa ≥0.70). These milestones directly address the three critical gaps: gate credibility, governance legitimacy, and pilot feasibility.

3.4.A Issue - Pre-Registration and Gate Thresholds Remain Proposals, Not Locked Commitments

The gate metrics (ordinal error ≥25% reduction, comprehension within 10%, pronunciation consistency ≥15% above control, 30-day retention ≥70%) are labelled 'proposed thresholds' throughout. They are not yet pre-registered on an open repository, do not have a psychometrician-led power analysis confirming sample-size adequacy (at least 80 per arm), and lack published decision rules for borderline outcomes (e.g., if ordinal error is reduced 24% vs. 25%). This is critical because the Month 24 (2028-10-13) go/no-go decision is the only gate; a weak or disputable threshold invalidates the entire evidence strategy and invites stakeholders to claim the outcome is rigged.

3.4.B Tags

3.4.C Mitigation

Immediately (Month 0 = 2026-10-13): Draft a statement of work for the independent psychometrician specifying: (1) deliver a pre-analysis plan by Month 9 (2027-07-13) with explicit numeric thresholds, sample-size justification, power calculations (target 80% power, two-sided α=0.05), and intention-to-treat rules; (2) register the plan on Open Science Framework or equivalent by Month 11 (2027-09-13), 30 days before Phase 2 begins; (3) publish thresholds and rationale on the project website by Month 11 (2027-09-13) for third-party review. Secure a signed contract by Month 2 (2026-12-13). Commission a 20-30 participant validity study in Months 10-11 (2027-08-13 to 2027-09-13) to confirm that the proposed thresholds are defensible and that the instruments detect ordinal and pronunciation effects. Escalate to the editorial board for written sign-off of the final thresholds by Month 12 (2027-10-13).

3.4.D Consequence

Without pre-registered, defended thresholds, the Month 24 (2028-10-13) go/no-go decision will be scientifically disputable. Educators, standards bodies, and publishers can claim the gate was rigged or that borderline results were manipulated. A false-positive outcome (a GO on weak evidence) launches a standard that fails in Phase 3 adoption; a false-negative (a NO-GO on borderline data) squanders $1.2M in Phase 2 spending and delays steward commitment. Dispute risk alone reduces third-party adoption confidence by 20-50% and invites regulatory challenge. ICAO, ISO, and ASD-STE100 precedent shows that credible standards require pre-registered metrics and independent validation; a weak gate risks relegating Clear English to a minority variant or relegating it to a footnote in education literature.

3.4.E Root Cause

The plan names four metrics and proposes numeric values, but the psychometrician role was listed as 'hired by Month 2 (2026-12-13)' without specifying that the pre-analysis plan (PAP) drafting, validity study, and formal pre-registration must occur by Month 11 (2027-09-13). No contract exists yet with the psychometrician, no power analysis has been run, and no open-science registration is scheduled. The strategic decisions document identifies Outcome Metric Battery Design as a critical lever, yet the plan treats thresholds as negotiable rather than as non-negotiable pre-commitments before Phase 2 begins.

3.5.A Issue - Editorial Board Governance Structure Lacks Explicit Decision Authority and Dispute Resolution

The plan specifies a 'practitioner-leaning editorial board of 7-9 members with linguist review-and-veto limited to ambiguity/contradiction findings' and names a 'tiebreak arbiter.' However, the charter itself is not drafted, voting procedures are not documented, the arbiter's scope and fee cap ($10K-$20K estimated) are not locked, and no escalation path is published for contested rule decisions. The strategic_decisions document flags Editorial Board Seat Allocation as a high-impact lever affecting the usability-versus-consistency trade-off in morphology and homograph decisions. The plan requires rules to be locked by Month 12 (2027-10-13), but without a formal, published charter with clear decision rules, disputes can stretch into Phase 2, invalidating early pilot comparisons.

3.5.B Tags

3.5.C Mitigation

By Month 1 (2026-11-13 at 09:00): Draft and publish a 2-3 page Editorial Board Charter specifying: (1) voting rule (simple majority, quorum 6 of 9); (2) linguist veto scope (only ambiguity, logical contradiction, or factual error; not subjective preference); (3) veto override path (if linguists veto a rule, present both positions to the board and allow override by 2/3 majority); (4) conflict-of-interest disclosure (members must recuse if they profit from a rule); (5) tiebreak arbiter (externally appointed, e.g., from a university or standards body, with written fee schedule capped at $10K per decision). By Month 5 (2027-03-13): Secure the arbiter's written commitment and fee schedule in advance. By Month 10 (2027-08-13): publish a 1-page decision log of all disputed rules, including majority/minority positions and the rationale for the chosen path. Lock all rules by Month 12 (2027-10-13) and conduct a 30-day public-comment window (Month 11 = 2027-09-13 to Month 11.5 = 2027-09-28 to 2027-09-28) with a published response to comments. This echoes ICAO and ISO precedent, where explicit governance structures and published reasoning builds credibility.

3.5.D Consequence

Without a published, formal charter and clear dispute resolution, the board can deadlock indefinitely. Contested decisions (e.g., whether to regularize go/went, or how to mark homophones) can stretch from Month 5 (2027-03-13) to Month 12 (2027-10-13) or later, compressing the Phase 1 exit gate and forcing a 4-12 week extension ($85K-$250K estimated). Mid-pilot rule changes invalidate prior assessments, weakening the go/no-go evidence. Standards bodies, publishers, and educators perceive the process as opaque or rigged, reducing adoption by 20-30%. Past precedent (ASD-STE100 governance debates 2000-2005) shows that weak governance invites external challenges that can paralyze a standard for years. Stronger governance signals institutional legitimacy and third-party confidence.

3.5.E Root Cause

The plan names decisions (practitioner-leaning board, linguist veto, tiebreak arbiter) but does not publish governance documents. The charter is mentioned as due by Month 1 (2026-11-13), but no template, voting threshold, conflict-of-interest rules, or arbiter-selection criteria are specified. The SWOT analysis flags 'Editorial board deadlock or rule ambiguity delaying the Month 12 (2027-10-13) rules lock' as a key risk, yet mitigation only says 'publish board charter by Month 1 (2026-11-13)' without operationalizing how disputes are actually resolved. This mirrors past standards failures (e.g., Simplified Spelling Board disputes in the 1960s, which paralyzed rule decisions).

3.6.A Issue - Pilot Recruitment, Retention, and Audio Production Are Under-Resourced and Lack Explicit Fallback Plans

The plan targets at least 80 completers per arm (320 total across 4 arms, implying enrollment of ≥115 per arm at a 70% retention rate estimate), with signed partner commitments by Month 3 (2027-01-13). However: (1) no psychometric power analysis yet exists to confirm that 80 per arm is sufficient; (2) the Cohort Manager (1.0 FTE, $60K-$80K/yr) is not hired until Month 6 (2027-04-13), leaving 5 months of recruitment with no dedicated staff; (3) audio production is budgeted $80K-$120K (estimate) with a $20 per-entry cost floor, but if cost exceeds this, the fallback (synthetic baseline plus human verification of highest-friction words) is not funded in Phase 1; (4) inter-rater reliability (kappa ≥0.70 floor, target 0.75) is critical for the pronunciation consistency gate metric, yet rater training and a dry run are scheduled only by Month 10 (2027-08-13), giving a 2-month window to retrain or reduce scope before the rules lock. This concentrates risk in Months 8-12 (2027-06-13 to 2027-10-13).

3.6.B Tags

3.6.C Mitigation

Immediate actions (Month 0-2 = 2026-10-13 to 2026-12-13): (1) Confirm the psychometric power analysis target (80 per arm) or adjust enrollment targets and Phase 2 budget based on effect-size assumptions (this is the psychometrician's job by Month 5 = 2027-03-13). (2) Hire the Cohort Manager by Month 6 (2027-04-13), but onboard and plan recruitment by Month 2 (2026-12-13) in a 0.5 FTE advisory capacity; have them draft partner commitments, incentive structures, and a retention protocol before Month 3 (2027-01-13). (3) By Month 2 (2026-12-13): Secure studio capacity with firm pricing and delivery timelines; trigger a cost audit by Month 4 (2027-02-13); if per-entry cost exceeds $20 (estimate), pivot immediately to a hybrid approach (synthetic baseline for all 5,000 by Month 7 = 2027-05-13, human verification of highest-friction 1,000-1,500 by Month 11 = 2027-09-13). (4) Schedule a rater training and kappa dry run for Month 9 (2027-07-13) (not Month 10 = 2027-08-13), with a go/no-go decision by Month 9.5 (2027-07-28); if kappa <0.70, conduct intensive retraining for Weeks 1-4 of Month 10 (2027-08-13) with retest by Month 10.5 (2027-08-28). If retest kappa is still <0.70, escalate to the board by Month 11 (2027-09-13 at 09:00) with two options: (a) reduce lexicon scope to 3,000 highest-impact words (violates user constraint, not recommended), or (b) extend Phase 1 by 6 weeks (not 4) to allow rater retraining and a third kappa check, shifting Phase 2 start to Month 13 (2027-11-13) (cost ~$125K estimated). Publish these decision rules and timelines on the project website by Month 1 (2026-11-13) to signal credibility and give partners visibility into fallback scenarios.

3.6.D Consequence

Weak pilot recruitment and retention (dropout >30%) reduces effective sample size below 80 per arm, inflating measurement error by 20-30% and reducing statistical power to detect true ordinal and pronunciation effects by 10-20%. An underpowered gate metric is inconclusive and forces either a false-negative (NO-GO on weak evidence, wasting $1.2M) or a false-positive (GO on borderline data, launching a weak standard). Unreliable pronunciation scoring (kappa <0.70) adds 10-15% measurement noise to the pronunciation consistency gate, making it impossible to distinguish true Clear English effects from rater variance. Audio cost overruns or late rater-training discovery compress the Phase 1 rules-lock deadline, forcing either a 6-week extension (cost $125K-$150K estimated) or a scope reduction that violates the 5,000-word user constraint. Past precedent (ICAO aviation-English pilot studies 2010-2015) shows that under-resourced recruitment and late assessment readiness are the top reasons pilots fail to generate defensible evidence; the cost of remediation is typically 2-3 months and $200K-$400K, not the projected 4 weeks and $85K.

3.6.E Root Cause

The plan names recruitment targets and a retention goal but does not sequence hiring or budget fallbacks tightly. The Cohort Manager is a critical role for retention, yet is not hired until Month 6 (2027-04-13), after the first 5 months of partner engagement and recruitment logistics should have begun. Audio production cost is volatile (per-entry cost unknown; potential $50K+ overrun), yet is not subject to a go/no-go decision at Month 8 (2027-06-13) with clear fallback triggers. Inter-rater reliability is a gate-metric prerequisite, yet the dry run is scheduled for Month 10 (2027-08-13) with only 2 months to remediate if kappa falls below 0.70 (the floor). This mirrors the risk register's flag: 'Weak or disputable assessment validity and rater reliability (kappa below 0.70)' is a key risk, yet mitigation says only 'extend Phase 1 by 4 weeks if kappa stays below 0.70,' implying a reactive, not proactive, approach.


4 Expert: Data Protection & Research Ethics Advisor

Knowledge: GDPR and US state data-privacy law, Institutional Review Board (IRB) and Research Ethics Committee (REC) processes, informed consent and learner safeguarding, product liability in language/safety-critical contexts

Why: Audio recordings of 460 learners, pronunciation scoring, and potential safety-critical pilot materials expose the project to GDPR/privacy breach, ethics-approval delay, and liability litigation if misreading occurs. These must be locked by Month 6 (2027-04-13) to avoid Month 18–24 (2028-04-13 to 2028-10-13) discovery of unresolved exposure. The expert will secure IRB/REC approval, establish encrypted storage and audit protocols, and define safety-critical liability thresholds that keep pilots within 'glossary and labeling' bounds (not live procedures).

What: By Month 2 (2026-12-13), engage an IRB/REC and draft a study protocol (learner population, intervention, data types, retention). By Month 4 (2027-02-13), commission a product-liability analysis covering safety-critical misreading scenarios and insurance requirements. By Month 6 (2027-04-13), obtain written ethics approval and secure liability insurance (≥$1M–$5M per incident, estimate). By Month 8 (2027-06-13), finalize Data Protection and Privacy Policy and audit encrypted storage. By Month 10 (2027-08-13), publish plain-language consent forms and data-use agreements in multiple languages.

Skills: GDPR compliance, IRB/REC navigation, informed-consent design in plain language, data encryption and audit, product liability assessment, safety-critical documentation standards (IEC 62304, DO-178C or equivalent)

Search: GDPR data protection officer language research, IRB ethics committee human-subjects protocol, product liability insurance safety documentation

4.1 Primary Actions

4.2 Secondary Actions

4.3 Follow Up Consultation

"In the next consultation, we should address: (1) the final IRB/REC approval status and any conditions imposed on audio recording or data retention; (2) the results of the Data Protection Impact Assessment and which data-minimization optimizations are feasible (e.g., can inter-rater reliability be calibrated on a 300-word subset instead of 5,000 words?); (3) confirmation of insurance coverage and liability strategy, including whether the safety-critical wedge will remain operational-procedures-only (non-live) or scale to glossary-only (safest); (4) the cloud-vendor DPA status and whether data residency or sub-processor controls require changes; (5) incident-reporting procedures and whether the pilot partners' signed agreements have been finalized; (6) a draft Learner Privacy Compliance Report for Month 12 (2027-10-13) documenting all regulatory approvals, data-protection measures, and insurance status. If any IRB objections or insurance-availability issues have emerged, we should discuss contingency plans (e.g., switching to synthetic audio, narrowing the safety-critical scope, or extending Phase 1 to allow additional risk assessment)."

4.4.A Issue - IRB/REC Approval Timeline Is Dangerously Compressed and May Block Phase 2 Start

The project targets IRB/REC approval by Month 6 (2027-04-13) but requests expedited review by Month 4 (2027-02-13). Expedited review typically handles minimal-risk studies; if the audio-recording component or learner-identification protocols raise concerns about privacy, data sensitivity, or long-term retention, the board may require full review (4–8 weeks instead of 2–3 weeks). Additionally, no consent template, privacy statement, or data-retention schedule is drafted before Month 2 (2026-12-13), yet these are required by most IRBs before submission. A Month 4 (2027-02-13) submission with incomplete consent language will be returned for revision, delaying approval to Month 7–8 (2027-05-13 to 2027-06-13), compressing the Month 13 (2027-11-13) enrolment deadline by 4–6 weeks and forcing either rushed recruitment or scaled-back cohort targets.

4.4.B Tags

4.4.C Mitigation

By Month 1 (2026-11-13), draft a plain-language Informed Consent Template (1–2 pages) specifying: what data will be collected (pronunciation audio, test responses, reading times, name and email), how long each data type is retained (audio 3 years post-analysis then deleted unless learner consents to archival; scores and demographics 5 years for verification), who may access it (core research team with signed data-use agreements; no sharing with third parties without consent), encryption and backup procedures, and the learner's right to withdraw and request deletion at any time. Include translations into the home languages of ESL cohorts if feasible. By Month 1 (2026-11-13), also draft a Data Protection and Privacy Policy (2–3 pages) documenting GDPR/state-law compliance, data-minimization principles, and breach-notification procedures. Submit both to the IRB along with the study protocol by Month 2 (2026-12-13) for a 2-week pre-screening and feedback cycle; revise based on IRB queries by Month 3 (2027-01-13); resubmit for formal review by Month 3.5 (2027-01-28); target approval by Month 5 (2027-03-13). If full review is mandated, negotiate for a phased approval (audio recording and scores first, follow-up contact second) to allow recruitment to begin by Month 6 (2027-04-13) under provisional ethics clearance for core data collection. Engage a data-protection officer or legal counsel specializing in research compliance (separate from the product-liability counsel) by Month 1 (2026-11-13) to guide compliance.

4.4.D Consequence

Without accelerated IRB action and complete submission by Month 2 (2026-12-13), approval will slip to Month 7–8 (2027-05-13 to 2027-06-13), shortening the recruitment window to 5–6 months (vs. 8 months planned). This forces over-recruitment pressure on partner organizations, raising dropout risk above the tolerated 30% and reducing effective sample size below the 80-per-arm minimum, invalidating the gate metrics and triggering a Phase 2 extension costing $300K–$600K (estimate). Alternatively, a scaled-back cohort (60–70 per arm) proceeds but loses statistical power, raising Type II error risk (false-negative gate) and requiring higher effect-size thresholds that may be unachievable.

4.4.E Root Cause

The plan assumes expedited review will clear by Month 6 (2027-04-13) without accounting for (a) the likelihood that audio recording of pronunciation triggers full review; (b) the absence of a written, detailed consent template and data-use agreement in plain language; (c) the lack of a formal data-retention and deletion schedule specifying which data (audio, scores, demographics) are retained for how long and under what conditions. IRB turnaround depends critically on submission completeness: missing consent templates, data-protection statements, or privacy notices routinely trigger rejection-for-revision cycles adding 3–6 weeks.

4.5.A Issue - Audio Recording, Biometric Data and GDPR Compliance Are Underestimated; Learner Privacy Exposure Is Substantial

The project plans to record pronunciation audio from 460 learners (>115 per arm) across 4 sessions, plus demographic data and test scores, retaining audio for 3 years post-analysis. Under GDPR (applicable to UK pilots and EU participants), voice recordings are biometric data requiring explicit lawful-processing grounds (consent, legitimate interest, or legal obligation). The plan documents 'consent' but does not address: (1) scope of consent—are learners consenting only to research use or also to storage in an encrypted archive for 3 years? (2) right to be forgotten—learners can demand audio deletion at any time, but can the psychometric validity study be re-run without re-recording a sample, or does deletion invalidate inter-rater reliability claims? (3) cross-border transfer—if the US-based hub stores encrypted audio on cloud servers (AWS, Azure), GDPR requires data-processing agreements (DPAs) with the cloud vendor, which add 2–4 weeks of legal negotiation. (4) data-minimization principle—can inter-rater reliability be assessed on a 200-word subset instead of 5,000 entries, or is the full-corpus recording non-negotiable? The plan mentions 'encrypted storage by Month 6 (2027-04-13) and audit by Month 8 (2027-06-13)' but does not specify which encryption standard (AES-256?), key-management protocol (who holds the decryption key?), or cloud-vendor DPA status.

4.5.B Tags

4.5.C Mitigation

By Month 1 (2026-11-13), commission a Data Protection Impact Assessment (DPIA) under GDPR Article 35 (or equivalent UK/US framework) to: (1) document the lawful processing ground for audio recording (proposed: explicit consent + research exemption under Schedule 1, Part 2 (academic research) of the UK DPA 2018, if applicable); (2) map retention periods for each data type (audio 3 years post-analysis, but specify when 'analysis' is complete—at Month 24 = 2028-10-13 gate or Month 30 = 2029-04-13 v1.0 release?); (3) implement data minimization: run an inter-rater calibration on a 200–300 word pilot subset (Months 8–9 = 2027-06-13 to 2027-07-13) to establish kappa, then record only the full 5,000-word corpus if kappa is confirmed >=0.70, or switch to a synthetic baseline if training does not achieve kappa; (4) detail encryption standard (AES-256, FIPS 140-2 validated, or equivalent) and key-management protocol (keys held in split custody, escrow with a third party, or on-premises only); (5) pre-negotiate a Data Processing Agreement with the selected cloud vendor (AWS, Azure, or alternative) by Month 3 (2027-01-13), specifying data location, sub-processor controls, and DPA renewal every 12 months; (6) draft a Right-to-Be-Forgotten Protocol specifying that a learner's request to delete audio is honored within 30 days, but the learner's outcome data (test scores, reading time) may be retained for analysis if anonymized post-deletion; (7) document residual risk: if more than 5% of learners (>23 per arm) request deletion during Months 13–24 (2027-11-13 to 2028-10-13), the inter-rater reliability sample may fall below N=15 per rater, triggering a re-training cycle or Cohen's kappa downgrade (target 0.75 becomes 0.70 floor). By Month 4 (2027-02-13), publish the DPIA and the draft DPA on the project website (redacting cloud-vendor confidential terms) to signal regulatory compliance to the IRB and pilot partners.

4.5.D Consequence

Without a DPIA and explicit data-processing grounds documented before Month 2 (2026-12-13), the IRB may classify the project as high-risk, escalating from expedited to full review (adding 4–6 weeks, approval slips to Month 7–8 = 2027-05-13 to 2027-06-13). Additionally, a UK data-protection authority (ICO) or GDPR-compliant institution could challenge the consent scope and retention schedule at any time Months 6–24 (2027-04-13 to 2028-10-13), triggering a compliance investigation and a requirement to delete audio from all participants, invalidating the inter-rater reliability score and forcing the pronunciation consistency metric to revert to a non-audio proxy (e.g., written transcripts), which is weaker and may not meet the gate threshold. In the worst case, a breach notification requirement (if audio is exposed) could trigger regulatory fines of 10–20 million EUR or up to 4% of global revenue (GDPR Article 83) and reputational damage that blocks Phase 3 adoption.

4.5.E Root Cause

The plan treats audio recording as a low-risk, standard-research activity and assumes standard consent is sufficient, but does not account for GDPR Article 9 (special categories of personal data, including biometrics) or the UK Data Protection Act 2018 Schedule 1 exemptions for research. The root causes are: (a) no explicit biometric-data processing-ground documented (consent alone is often insufficient; 'legitimate interest' for standards development may be arguable but requires impact assessment); (b) no data-minimization analysis—the plan records 5,000 words × 2 takes × 460 learners = 4.6M audio files without exploring whether inter-rater reliability can be established on a 500–1,000 word pilot sample, not the full corpus; (c) no vendor due-diligence or DPA pre-negotiated with cloud-storage providers; (d) a 'right to be forgotten' request mid-pilot could delete a learner's audio, invalidating that learner's data from the validity study and triggering a re-analysis that may weaken kappa estimates.

4.6.A Issue - Safety-Critical Liability Exposure Is Bounded but Not Eliminated; Insurance, Disclaimers and Regulatory Strategy Are Incomplete

The plan scopes safety-critical pilots to 'glossary and labeling exercises, no live operational procedures' and budgets legal/liability spend at $150K–$200K (estimate), but does not document: (1) which jurisdictions' product-liability frameworks apply (OSHA in the US, HSE in the UK, ISO 26262 or IEC 62304 for medical devices, FAA or EASA for aviation)? (2) whether the 'glossary and labeling' scope is sufficient to avoid product-liability claims if a misreading of Clear English ordinals or homophones in a label causes injury (e.g., a pharmaceutical concentration label reading '11th dose' misread as '1st' under the prefix-marker rule, resulting in overdose); (3) what insurance is available, at what cost, and whether it covers 'pilot' or 'research' use or only commercial release; (4) what disclaimers are legally sufficient to limit liability if a pilot partner uses Clear English materials in a live context without explicit authorization? The plan mentions 'retain legal counsel by Month 2 (2026-12-13)' and 'liability strategy by Month 4 (2027-02-13)', but these are not detailed: no specific scenarios, no regulatory-body notification strategy, no insurance specifications, no template disclaimers.

4.6.B Tags

4.6.C Mitigation

By Month 1 (2026-11-13), engage a lawyer specializing in product liability and regulatory compliance in both the US and UK jurisdictions (not the same counsel as the data-protection advisor, to ensure independent review). Commission a written Liability and Regulatory Landscape Analysis (3–5 pages) addressing: (1) which product-liability regimes apply to safety-critical documentation standards (US Restatement Third of Torts § 2, UK Product Liability Directive 85/374/EEC, industry-specific standards like ISO 26262 for automotive, IEC 62304 for medical devices); (2) whether a research exemption is available (e.g., FDA Good Laboratory Practice exemptions, UK Research Ethics Committee approval providing qualified immunity); (3) liability scenarios for each pilot cohort (e.g., ESL learner misreading of ordinals in a classroom glossary vs. a technical trainer introducing labeled procedures into a factory floor); (4) estimated exposure for a 'worst-case' incident (injury or property damage from misreading) and comparable verdicts or settlements in education or language-standard cases; (5) available insurance products (professional liability, errors & omissions, product liability for 'pilot' or 'developmental' standards) and rough premium estimates ($20K–$50K annually, estimate, vs. the $150K–$200K budget allocated to all legal/liability). By Month 2 (2026-12-13), also commission an Underwriting Proposal from at least two insurance brokers specializing in education or standards liability, requesting a quote for coverage of the pilot activities and conditions (coverage limit $1M–$5M per incident, estimate). By Month 4 (2027-02-13), publish a Liability Strategy Document (2 pages) on the project website specifying: (a) the chosen liability-mitigation approach (e.g., 'research exemption + institutional indemnity, combined with site-specific disclaimers and partner agreements'); (b) a Disclaimer and Consent Template for pilot partners confirming that the standard is developmental and not intended for life-critical use; (c) mandatory Human-Review Protocol specifying that all safety-critical materials must be reviewed by a native speaker and a domain expert (pharmacist, nurse, engineer) before use in any operational context; (d) incident-reporting requirements (pilot partners must report any ambiguity, misreading, or near-miss within 24 hours to the project team); (e) the regulatory notification strategy (e.g., if a serious incident occurs, notify relevant regulators—OSHA, HSE, state medical board—within 10 days as part of the project's own incident-investigation process, not to shift liability but to build transparency). Secure signed Pilot Partner Agreements by Month 6 (2027-04-13) that explicitly state the standard is experimental, that partners may not use it in live operational procedures without explicit written approval, and that partners indemnify the project from claims arising from unauthorized use. If insurance cannot be secured at a cost <$50K/year (estimate), or if the underwriter classifies safety-critical materials as 'uninsurable pilot' due to unknown risks, scale the safety-critical wedge to non-life-critical glossaries (e.g., labeling of office supplies or library materials, not pharmaceuticals or operating procedures) until post-Phase-2 evidence demonstrates that the ordinal and homograph rules are sufficiently reliable.

4.6.D Consequence

Without a detailed Liability Strategy and confirmed insurance by Month 4 (2027-02-13), the project risks uninsured exposure: if a pilot partner uses Clear English materials in a live setting and an injury or near-miss occurs, the project team could face product-liability claims (estimated $100K–$1M+ defense costs, settlement or judgment), regulatory investigation (OSHA recordkeeping, HSE prosecution, state board review), and reputational damage that blocks Phase 3 adoption by all technical and safety-critical partners (estimated 30–50% of adoption target). Additionally, if the IRB discovers that liability exposure has not been quantified or mitigated, it may withdraw ethics approval or downgrade the pilot to 'non-operational use only,' narrowing the scope and reducing the credibility of the safety-critical evidence at the Month 24 (2028-10-13) gate. Conversely, over-conservative disclaimers that position the standard as 'not suitable for any operational use' will deter safety-critical partners from participation, eliminating the technical-glossary cohort from pilots and reducing the overall adoption case.

4.6.E Root Cause

The plan treats safety-critical liability as a secondary concern ('limit pilots to glossary and labeling') and assigns it a single line item ('legal strategy by Month 4 = 2027-02-13'), without distinguishing between research liability (covered by IRB approval and institutional indemnity) and product liability (exposure to third-party injury claims, regulatory prosecution, and reputational harm). The root causes are: (a) no clarity on what 'glossary and labeling exercises' means operationally—are learners labeling pharmaceutical bottles with Clear English ordinals in a supervised classroom, or are pilot partners introducing labeled materials into actual workplace settings?; (b) no differentiation between US and UK liability frameworks (US relies on product-liability tort law; UK relies on Consumer Protection from Unfair Trading Regulations and Health & Safety at Work etc. Act 1974); (c) no assessment of whether a 'research study' exemption applies if the materials are not released commercially; (d) no insurance-market research to confirm whether liability coverage is available or affordable at $150K–$200K (estimate) for a novel, unproven standard.


5 Expert: Lexical Semantics & Controlled Vocabulary Specialist

Knowledge: Corpus linguistics, frequency analysis, semantic field mapping, controlled-language vocabulary design (ASD-STE100, ISO 1087), ESL core vocabulary selection, word sense disambiguation

Why: The 5,000-word core lexicon (4,500 frequency-led + 500 technical/safety block) is the foundation of all downstream work: the dictionary, pronunciation guidance, pilot curriculum, and homograph identification. Current selection basis (frequency-led with incident-driven optional seeding) lacks a formal ranking, gap-analysis, and collision-detection protocol. The expert will audit the lexicon against pilot running text, ensure >=85% coverage by Month 8 (2027-06-13), and surface high-friction homographs and ambiguous near-synonyms that feed Decision 7 (Homograph Disambiguation Policy) and the pronunciation-consistency metric scoring. Weak lexicon coverage or missed ambiguities reduce pilot utility by 15-30% and force Month 10-11 (2027-08-13 to 2027-09-13) rework.

What: By Month 4 (2027-02-13), deliver a ranked, justified 5,000-word core list with frequency bands, semantic domains, and provenance (corpus source, incident records, or syllabus). By Month 6 (2027-04-13), conduct a coverage audit against all pilot materials (ESL texts, technical manuals, safety glossaries); flag gaps and high-friction polysemes. By Month 8 (2027-06-13), finalize the list with documented exceptions and expansion justification; deliver a semantic-field map linking related terms (e.g., ordinal markers, safety procedures) to homograph-policy designers.

Skills: Corpus analysis and frequency profiling, semantic field and word-sense mapping, vocabulary auditing and gap analysis, controlled-vocabulary design and ISO 1087 standards, homograph and polysemy identification

Search: corpus linguist vocabulary selection ESL core lexicon, controlled language terminology ASD-STE100 semantic fields, word frequency analysis polysemy disambiguation

5.1 Primary Actions

5.2 Secondary Actions

5.3 Follow Up Consultation

At the next review (Month 3 = 2027-01-13), confirm: (1) psychometrician hired and power analysis commissioned; (2) signed pilot partner commitments (≥3 ESL programs, ≥2 technical-training organizations); (3) Editorial Board Charter published with tiebreak arbiter named; (4) legal counsel retained and safety-liability strategy finalized; (5) audio vendor identified and cost-per-entry estimate confirmed; (6) IRB/ethics approval pathway clarified; (7) steward-search workstream assigned and first candidate list drafted. Critical dependency: if any of these is missing or delayed, Phase 1 will compress and pilot evidence will degrade. Discuss fallbacks and contingency triggers (e.g., if steward commitment is unlikely by Month 18 = 2028-04-13, consider extending Phase 3 or pivoting to a lighter post-v1.0 governance model).

5.4.A Issue - Gate Metrics Are Proposed, Not Pre-Registered; Thresholds Lack Psychometric Justification

All four gate thresholds (ordinal error ≥25% reduction, comprehension ≤10% slower, pronunciation consistency ≥15% above control, 30-day retention ≥70%) are marked 'proposed' and remain unvalidated estimates. No power analysis confirms that ≥80 completers per arm achieves 80% statistical power to detect these effects. The pre-analysis plan is not yet commissioned, and the psychometrician hire is not scheduled until Month 2 (2026-12-13). Without pre-registered, psychometrically justified thresholds by Month 11 (2027-09-13), the Month 24 (2028-10-13) go/no-go gate will be disputable and credibility-damaging.

5.4.B Tags

5.4.C Mitigation

Hire the psychometrician by Month 2 (2026-12-13) with explicit deliverables: power analysis confirming sample size by Month 5 (2027-03-13), draft pre-analysis plan with numeric thresholds by Month 9 (2027-07-13), and independent validity review by Month 10 (2027-08-13). Pre-register the complete plan on Open Science Framework by Month 11 (2027-09-13) with board sign-off. Publish thresholds and justification publicly to forestall post-hoc disputes.

5.4.D Consequence

Without pre-registration, the Month 24 (2028-10-13) go/no-go becomes scientifically disputable. A false-positive gate (launching a weak standard) reduces Phase 3 adoption credibility by 30–50%. A false-negative gate (rejecting a viable standard) wastes Phase 2 investment. Stakeholders and standards bodies will demand external review, delaying adoption by 6–12 months and eroding partner confidence.

5.4.E Root Cause

Plan treats thresholds as illustrative examples rather than pre-locked commitments. Psychometric vendor selection and power-analysis budget are deferred, leaving no time buffer before Month 12 (2027-10-13) when rules lock and pilots must begin.

5.5.A Issue - Pilot Recruitment and Retention Strategy Lacks Concrete Partner Commitments and Risk Mitigation

The plan proposes signing pilot partner commitments by Month 3 (2027-01-13) but provides no current list of target ESL programs, safety-training organizations, or publisher letters of interest. No Cohort Manager is hired until Month 6 (2027-04-13), leaving a 3-month gap when recruitment logistics are unmanaged. Dropout tolerance is 30%, but with ≥115 enrollments per arm, a 30% loss leaves only 80–81 completers per arm—the bare minimum for power. No contingency plan names recruitment fallbacks or re-engagement tactics.

5.5.B Tags

5.5.C Mitigation

Immediately identify and formally approach ≥4–5 ESL programs and ≥2–3 technical-training organizations (by Month 1 = 2026-11-13) with written pilot proposals. Obtain signed letters of understanding guaranteeing ≥50 learners per partner by Month 3 (2027-01-13). Hire Cohort Manager by Month 3 (2027-01-13) (not Month 6 = 2027-04-13), allocate ≥$50K–$80K for incentives and partner payments, and establish a dropout-response protocol (outreach within 24 hours, one-time make-up sessions).

5.5.D Consequence

Failure to recruit ≥460 learners by Month 13 (2027-11-13) or dropout >30% reduces effective sample size below the ≥80-per-arm floor. This invalidates power for all four gate metrics, forcing a 3–6 month Phase 2 extension (≥$300K cost, straining budget) or a false-negative gate outcome that rejects a viable standard.

5.5.E Root Cause

Recruitment risk is identified in the SWOT but no concrete partner list or hiring schedule exists. The plan assumes ESL programs and technical-training organizations will commit without pre-existing relationships or co-designed protocols.

5.6.A Issue - Post-Month-36 Stewardship Is Unfunded and No Permanent Steward Is Identified; Standard Risks Atrophy

The plan correctly identifies that post-v1.0 stewardship costs $150K–$250K per year (estimate) but does not specify a funding source or named steward organization. The project currently has no revenue stream, no endowment, and no explicit commitment from a non-profit, university, or standards body to assume stewardship. Without a funded steward by Month 36 (2029-10-13), the standard will receive no corrections, no version updates, and no active governance after Phase 3 ends. Publishers and educators will lose confidence in stability within 12–24 months, degrading adoption by 30–50%.

5.6.B Tags

5.6.C Mitigation

By Month 12 (2027-10-13), identify ≥2–3 potential steward candidates (university consortium, language non-profit, or standards body with 3+ years of audited financials). By Month 24 (2028-10-13), solicit written letters of interest. By Month 30 (2029-04-13), negotiate a formal MOU committing the steward to ≥10 years of funding ($150K–$250K per year) from endowment, member fees, or organizational budget. Publish the stewardship roadmap and steward identity with v1.0 release (Month 30 = 2029-04-13).

5.6.D Consequence

Without a committed, funded steward by Month 30 (2029-04-13), the v1.0 release is incomplete and non-credible. Errata and change requests accumulate unanswered. Publishers withdraw support within 12–24 months (by Month 48–60 = 2030-10-13 to 2031-10-13). Adoption fails to reach the ≥3 third-party adopters target, and the project ends as an academic exercise with negligible real-world impact.

5.6.E Root Cause

Plan prioritizes Phase 1–3 delivery but defers long-term sustainability to the end. No steward-search workstream is budgeted or scheduled, and the $0.35M reserve cannot cover post-36-month operational costs. The project risks becoming a 'publish and abandon' exercise.


6 Expert: Orthography & Phonetics Design Engineer

Knowledge: Phonemic transcription, grapheme-to-phoneme rule design, phonetic pedagogy, pronunciation guidance systems, diacritical marking conventions, IPA and practical orthographies

Why: Decision 2 (Grapheme-to-Phoneme Intervention Depth) and Decision 8 (Reference Accent Anchor) require a mapping from 5,000 English words to a consistent sound system, with inter-rater reliability (kappa >=0.70, target 0.75) and a fixed spoken reading for the ordinal prefix. The expert will design the pronunciation-guidance overlay (printed key for print, ruby-style for digital), anchor it to one reference accent with documented phonemic inventory, and produce a rater-calibration protocol for scoring the pronunciation-consistency metric. Without expert orthographic and phonetic grounding, the overlay will be ambiguous, raters will diverge, and the pronunciation-consistency gate score will become noisy (kappa <0.70, raising the risk of false-negative or false-positive gate outcomes).

What: By Month 3 (2027-01-13), select and justify one reference accent (US, RP, or equivalent); document its phonemic inventory and vowel-quality conventions. By Month 5 (2027-03-13), design a minimal pronunciation-guidance notation (IPA, respelling key, or hybrid) for the 5,000-word lexicon, tested on a pilot sample (100-200 words) for rater learnability. By Month 8 (2027-06-13), produce a rater-training manual and a pronunciation-consistency scoring rubric with worked examples. By Month 10 (2027-08-13), conduct inter-rater calibration (Cohen's kappa on 100-200 words); if kappa <0.70, iterate training and notation by Month 11 (2027-09-13).

Skills: Phonemic transcription and IPA, grapheme-to-phoneme algorithm design, phonetic notation and teaching, accent variation mapping, rater-calibration and inter-rater reliability, pronunciation-pedagogy best practice

Search: phonetics pronunciation guide orthography design, ESL pronunciation teaching IPA transcription, rater calibration inter-rater reliability phonetic scoring

6.1 Primary Actions

6.2 Secondary Actions

6.3 Follow Up Consultation

At the Month 3 (2027-01-13) consultation, review: (1) Accent Selection Rationale: is the chosen accent justified and accepted by the board? Has the proof-of-concept audio been recorded and pilot-tested with 5–10 ESL learners for comprehensibility? (2) Ordinal Spoken-Form Specification: is the chosen form teachable in 1–2 exposures? Have 5–10 learners been able to learn and produce it consistently? (3) Instrument Specification: are the effect-size estimates from the validity study feasible for the ordinal-error and pronunciation tasks, or do they require sample-size increases or threshold adjustments? (4) Pilot Partner Confirmations: are signed commitments in hand from at least 3 ESL programs and 2 technical/safety organizations? If not, what recruitment contingencies are being activated? (5) Psychometrician Contracting: is the pre-analysis plan on track for Month 9 (2027-07-13) delivery and Month 11 (2027-09-13) pre-registration?

6.4.A Issue - Anchor Accent Choice Deferred; Pronunciation Consistency Scoring Will Fail Without It

The plan states 'One reference accent chosen and justified by Month 3 (2027-01-13)' but provides no accent selected. Pronunciation consistency kappa >=0.75 (target) cannot be reliably scored without a fixed anchor. If raters are asked to score naturalness or regional fit instead of adherence to a published anchor, inter-rater reliability drops 15–25% (typical). Pilot audio and all rater training depend on this choice. The pre-analysis plan at Month 5 (2027-03-13) cannot specify scoring procedures without it. A deferred accent choice compresses the window between accent lock (Month 3 = 2027-01-13) and rater calibration (Month 9, 2027-07-13), leaving only 6 months to train raters and achieve kappa >=0.70 floor by Month 10 (2027-08-13).

6.4.B Tags

6.4.C Mitigation

By Month 1 (2026-11-13), commission a 2–3 page Accent Selection Rationale Document specifying: (a) candidate accents (RP, GenAm, Irish, etc.) ranked by teachability, learner demand in ESL contexts, and distinctiveness of phonemic contrasts; (b) phonological mapping tables showing which vowel mergers or consonant distinctions each accent encodes; (c) rater-population fit (will raters be native speakers of the anchor or trained non-natives?); (d) fallback: if no consensus by Month 3 (2027-01-13), use a 'core-contrast' approach (shared distinctions only, other realizations unspecified). Finalize accent by Month 2 (2026-12-13). Commission a 50–100 word proof-of-concept audio sample in the chosen accent by Month 4 (2027-02-13) and play it at the first board meeting to validate listener acceptance before scaling to 5,000 entries.

6.4.D Consequence

Without a locked anchor by Month 3 (2027-01-13), rater training slips to Month 10 (2027-08-13) or later. If inter-rater kappa falls below 0.70 at Month 10 (2027-08-13), the 4-week Phase 1 extension ($85K estimate) is triggered automatically. If the anchor is changed after rater training begins (Month 9, 2027-07-13), all trained raters must retrain, adding 4–6 weeks and $40K–$60K (estimate). Weak accent guidance also invites multiple interpretations of 'naturalness,' fragmenting pronunciation guidance across early adopters and reducing the pronunciation consistency score by 10–20%, potentially failing the Month 24 (2028-10-13) gate.

6.4.E Root Cause

The accent anchor (Decision 8: Reference Accent Anchor) was identified as strategically important but its selection was delegated to Month 3 (2027-01-13) without explicit criteria, justification framework, or a fallback if consensus fails. No phonological contrasts (shared vowels vs. distinctiveness) or pedagogical fit (learner populations served by each accent) have been documented. The board charter does not specify who decides accents or how tied votes are broken.

6.5.A Issue - Pre-Analysis Plan and Psychometric Instrument Validity Not Defended; Gate Thresholds Are Still Proposals

The plan states 'Develop a purpose-built assessment set for each of the four metrics, calibrated against a standard-English control group, and have an independent psychometrician review item validity before the pilots begin' (Decision 4: Outcome Metric Battery Design). However, no validity study design is specified, no expected effect sizes are documented, and no power analysis justifies the claimed minimum sample size of 80 completers per arm. The gate thresholds (ordinal error >=25% reduction, comprehension no more than 10% slower, pronunciation consistency >=15% above control, 30-day retention >=70%) remain proposals until pre-registered Month 11 (2027-09-13). A validity study is budgeted at $150K–$200K (estimate), with a dry run Month 10 (2027-08-13), leaving only 4 weeks to address validity failures before pre-registration lock. If the validity study reveals low discriminative power for the ordinal-error task or pronunciation task, the thresholds cannot be justified, and the gate dossier at Month 24 (2028-10-13) becomes disputable.

6.5.B Tags

6.5.C Mitigation

By Month 3 (2027-01-13), commission the psychometrician to deliver a 5–8 page Instrument Specification and Feasibility Report detailing: (a) ordinal-error measurement: propose 2–3 candidate task formats (e.g., reading-to-matching, ordinal-in-context comprehension, error-spotting in a procedure), justify which is most sensitive to ordinal-marker effects, and cite prior evidence or pilot data if available; (b) pronunciation consistency: specify the anchor-dependent scoring rubric (phonemic accuracy vs. native-like naturalness), define kappa calculation method (pairwise inter-rater agreement vs. multi-rater consensus), and justify the kappa >=0.75 target; (c) comprehension speed: define which text type (narrative, procedural, technical) best isolates spelling-to-sound effects; (d) 30-day retention: specify whether retention is measured by re-test accuracy, self-report, or engagement metrics. By Month 5 (2027-03-13), initiate the validity study with N=30–50 (increased from proposed 20–30 estimate) to estimate effect sizes for ordinal error, pronunciation, and reading speed under the Clear English variant. By Month 9 (2027-07-13), deliver final pre-analysis plan with power calculations and threshold justification; if any threshold falls below the 80% statistical-power bar, flag to the board by Month 10 (2027-08-13) for adjustment or sample-size increase. Pre-register by Month 11 (2027-09-13) with published power calculations so the gate cannot be disputed.

6.5.D Consequence

If the validity study is skipped or compressed (Month 10 = 2027-08-13 only), validity problems (e.g., ceiling effects in ordinal accuracy, kappa <0.60 for pronunciation) are discovered at Month 18–20 (2028-04-13 to 2028-06-13) after 6+ weeks of pilot data have been collected. Re-scoring or re-designing assessments compresses analysis, delays the gate dossier by 6–8 weeks, and introduces post-hoc methodological choices that invite stakeholder challenge. A no-go or inconclusive outcome at Month 24 (2028-10-13) triggers a 3-month Phase 2 extension ($300K estimate), consuming 25% of the project reserve. Weak or unpublished thresholds also invite educators and standards bodies to dismiss the gate outcome as arbitrary, reducing Phase 3 adoption by 20–30%.

6.5.E Root Cause

The decision to commission purpose-built assessments (rather than adapt off-the-shelf instruments) was driven by the need to measure ordinal and pronunciation effects specific to Clear English. However, no ordinal-error measurement task has been piloted, no item pool for pronunciation consistency has been validated, and no effect-size estimates from comparable interventions have been documented. The pre-analysis plan is due Month 9 (2027-07-13), but the validity study (N=20–30, estimate) must run Months 10–11 (2027-08-13 to 2027-09-13) in parallel, compressing the timeline. If the validity study uncovers that the ordinal marker requires 3–5 exposures to reach 90% accuracy (instead of the assumed 1–2), the effect-size estimate changes, and sample-size calculations must be redone.

6.6.A Issue - Ordinal Marker Spoken Form Unspecified; Pilot Learners Will Not Know How to Read It Aloud

Decision 1 (Ordinal Marker Architecture) selects 'numeric ordinals with an invariant prefix marker placed before the digits,' with 'fixed spoken reading published.' However, the spoken form is not specified. What is the spoken form: 'prefix-ONE' (e.g., 'prefix one' for 1), 'clear-one,' a single phoneme /ə/, or a silent marker? How does a learner know whether '○1' (hypothetical example) is read aloud as a word, an abbreviation, or silently skipped? If the spoken form is ambiguous, learners produce inconsistent speech, raters score inconsistently, and the pronunciation consistency score at the Month 24 (2028-10-13) gate inflates measurement noise by 15–30%. Pilot participants cannot be trained on a marker whose spoken reading is not finalized. A marker symbol and spoken form are both part of the ordinal rule, not downstream implementation choices.

6.6.B Tags

6.6.C Mitigation

By Month 2 (2026-12-13), the ordinal-marker workstream (workstream owner assigned by Month 2 = 2026-12-13 per the Editorial Board Charter) must deliver a 2–3 page Ordinal Spoken-Form Specification documenting: (a) candidate spoken forms (single morpheme, e.g., 'ord' or /ɔɹd/, vs. a phrase like 'ordinal', vs. silent or letter-spelling); (b) learnability evidence or examples from other constructed orthographies (e.g., how Japanese furigana annotations are read; how acronyms like 'URL' are handled in ESL); (c) pilotability: how will learners be trained in 1–2 exposures to produce it consistently? (d) alternative: if no consensus on a spoken form emerges, defer marker speech to an optional-annotation approach where learners may read the digit aloud (e.g., '1' as 'one') and the marker silent, accepting lower pronunciation consistency but avoiding ambiguity. Finalize the spoken form by Month 10 (2027-08-13) and record a 20–50 word proof-of-concept sample by Month 11 (2027-09-13) to validate rater and learner comprehension before the pilots begin at Month 13 (2027-11-13).

6.6.D Consequence

If the ordinal marker's spoken form is not finalized by Month 10 (2027-08-13), rater training is delayed 4–6 weeks, and inter-rater calibration slips to Month 11 (2027-09-13) or beyond, compressing the Phase 1 buffer to zero. If the form is ambiguous during pilots (Months 13–24 = 2027-11-13 to 2028-10-13), learners produce inconsistent pronunciations, kappa for pronunciation scoring drops below 0.70, and the Phase 1 extension is triggered or the pronunciation gate metric is lost. Learners cannot be effectively trained in reading ordinals if they do not know whether the marker produces a word, silence, or a letter-name. This ambiguity is a direct cause of failure to meet the Month 12 (2027-10-13) exit gate (kappa >=0.70 floor) and forces a 4–8 week extension and rework at a cost of $85K–$150K (estimate).

6.6.E Root Cause

The ordinal-marker design has been treated as a symbol-and-mechanics choice ('prefix placement,' 'invariant,' 'mechanical conversion') without specifying the phonological commitment. The plan assumes a 'fixed spoken reading for that suffix' (Decision 1) or 'published' reading (canonical facts) but does not specify what that reading is. This is a phonological design gap: deciding that the marker is 'a prefix' does not decide whether it is read, silent, or abbreviated. Without that decision, the first rater-training session at Month 9 (2027-07-13) cannot proceed because raters have no model of what learners should produce.


7 Expert: Technical Writing & Safety-Critical Documentation Advisor

Knowledge: Simplified technical English, safety-critical documentation standards (IEC 62304, DO-178C, ISO/IEC 80601), procedure design, risk-informed writing, industry-specific glossaries (aviation, medical, industrial)

Why: The safety-critical adoption wedge (technical glossary and labeling cohort) is the project's highest-value, highest-liability scenario, but governance and content oversight are underspecified. This expert will co-design the technical-glossary content (500-word reserved block of the core lexicon), ensure alignment or documented divergence from ASD-STE100 and plain-language standards (Decision 12: Controlled-Language Alignment Posture), and advise on liability containment (glossary and labeling only, no live procedures before Month 24 = 2028-10-13). The expert will also help interpret the homograph-disambiguation policy (Decision 7) for safety contexts, where a misread 'lead/lead' could cause incident-level harm. Without safety-critical expertise, the glossary will omit domain-critical terms, liability exposure will be unquantified, and adopters will perceive the standard as outside safety governance, blocking the technical wedge's credibility.

What: By Month 2 (2026-12-13), audit existing safety-critical documentation standards and glossaries (industrial, medical, aviation) to identify the 500-word technical-safety block and gaps. By Month 5 (2027-03-13), co-design a safety-critical style guide (procedure layout, homograph warnings, disclaimer language) and advise legal counsel on liability thresholds (what document types are safe for pilot use before Month 24 = 2028-10-13). By Month 8 (2027-06-13), deliver a technical-glossary pilot sample (100-200 words, real procedure excerpts) for readability and error-rate testing. By Month 12 (2027-10-13), produce a technical-adoption roadmap post-Phase-2, positioning Clear English as an optional best-practice overlay on existing safety systems, not a replacement.

Skills: Safety-critical documentation standards (IEC, DO-178C, ISO), simplified technical writing and ASD-STE100 practice, risk assessment and incident-level harm analysis, procedure design and user-interface language, regulatory compliance (OSHA, HSE, industry-specific authorities)

Search: safety-critical documentation technical writing IEC 62304 DO-178C, simplified technical English procedure design, risk management documentation standards aviation medical industrial

7.1 Primary Actions

7.2 Secondary Actions

7.3 Follow Up Consultation

["At Month 3 (2027-01-13), review signed pilot partner commitments, recruitment pilot data, and initial psychometrician scope. Confirm the Reference Accent Anchor choice and justification, and validate that the external board arbiter has agreed to their role and fee. Assess cohort-manager hiring progress and the audiorecording RFP timeline. Address any slippage in board charter publication or rule-specification workstream kickoff.", "At Month 6 (2027-04-13), conduct a mid-Phase-1 critical-path review: confirm ethics approval status, audit pilot studio capacity and cost-per-entry estimates, review the draft pre-analysis plan from the psychometrician, and assess rule-drafting progress in the board subcommittees. Confirm the Regulatory Affairs workstream is engaged with advisors and obtaining written input on the glossary-and-labeling scope. Address insurance quotes and liability strategy decisions.", "At Month 10 (2027-08-13), conduct a Phase 1 exit-readiness review: validate inter-rater kappa ≥0.70 on the training sample, confirm all four gate thresholds are finalized and ready for pre-registration, review the draft standard and prepare for the 30-day public comment window. Ensure board rule disputes are resolved and the arbiter (if needed) has issued tie-breaking decisions. Confirm pilot partner enrollment is tracking toward 115 per arm by Month 13 (2027-11-13).", "At Month 18 (2028-04-13), conduct a Phase 2 midpoint check: verify that enrollment reached ≥115 per arm by Month 13 (2027-11-13), assess dropout rates and conduct a mid-phase retention check. Review preliminary comprehension-speed and pronunciation-consistency results (if available from the first cohort). Flag any site below 65% completion for re-engagement. Begin early steward-organization outreach and assess interest in a formal proposal."]

7.4.A Issue - Pre-Registration Thresholds Remain Proposals, Not Locked Commitments; Gate Credibility Is at Risk

The pre-analysis plan and gate thresholds (ordinal error ≥25%, comprehension speed ≤10% slower, pronunciation consistency ≥15% above control, 30-day retention ≥70%) are labelled 'proposed' throughout the canonical facts and risk assessments. No signed commitment from the independent psychometrician exists; no power analysis confirming that 80 completers per arm achieves 80% statistical power for these effect sizes; no threshold for inter-rater kappa reliability is pre-locked. At Month 11 (2027-09-13), three documents require simultaneous publication: a pre-analysis plan, thresholds and a 30-day public comment window. Without locked thresholds by Month 9 (2027-07-13), stakeholders can dispute the gate outcome as post-hoc tuning, and educators/standards bodies will reject the result as scientifically undefensible. This is a critical path item with zero schedule buffer.

7.4.B Tags

7.4.C Mitigation

By Month 1.5 (2026-11-28), publish a Request for Proposals (RFP) for the independent psychometrician specifying: deliverables (pre-analysis plan, power analysis for ≥80 per arm with published effect-size assumptions, validity study design, rater-training protocol, inter-rater kappa calibration by Month 10 = 2027-08-13). By Month 2 (2026-12-13), have a signed contract. By Month 5 (2027-03-13), receive the draft pre-analysis plan including justification for each threshold. By Month 9 (2027-07-13), finalize thresholds and deposit on Open Science Framework. Month 11 (2027-09-13) comment window then proceeds with a defensible, auditable baseline. Allocate $200K (within the $150K-$200K psychometrics budget) for this work and bump the critical path.

7.4.D Consequence

Without locked, pre-registered thresholds, the Month 24 (2028-10-13) go/no-go decision is disputable. Educators, standards bodies (TESOL, Ofqual) and publishers will claim the gate was tuned to produce a GO. A false-positive GO launches a weak standard with low Phase 3 adoption (risk: 20-50% uptake reduction). A false-negative NO-GO on inconclusive data triggers a $300K-$600K Phase 2 extension that exhausts the $175K pre-gate reserve and produces a shortfall. Either outcome erodes stakeholder confidence and undermines the 'adoption-first, evidence-gated' positioning that is the project's core legitimacy claim.

7.4.E Root Cause

No psychometrician hired; thresholds chosen by example rather than pre-registered; power analysis deferred. The pre-project assessment identifies this as the top priority action, but the canonical facts do not confirm a hire or a signed contract. Threshold proposals derive from the initial plan document, not from validated research design.

7.5.A Issue - Pilot Recruitment and Retention Risks Are Underestimated; Fallback Capacity Is Weak

The plan requires ≥80 completers per arm (320 total across 4 arms) by Month 22 (2028-08-13), with enrolment ≥115 per arm (460 total) by Month 13 (2027-11-13) and dropout ≤30%. Pilot partner commitments are due Month 3 (2027-01-13), and a cohort manager is not hired until Month 6 (2027-04-13)—a 3-month gap where recruitment momentum is lost. The 30% dropout tolerance (80 / 0.70 ≈ 114) is high for adult learners in month-long assessments; typical ESL pilot dropout is 30-50%. No fallback is budgeted if enrolment misses 115 per arm; the partner commitments specify 'minimum guaranteed cohort size' but no penalty or recovery plan if they miss. Safety-critical cohort is secondary and unproven in terms of recruitment speed or incentive effectiveness. A single cohort manager with no assistant creates a bottleneck for 460 participants across 5-7 sites.

7.5.B Tags

7.5.C Mitigation

By Month 1.5 (2026-11-28), identify 6-8 candidate ESL programs and 3-4 technical/safety-training organizations; send RFPs with a clear enrollment guarantee (≥50 per partner by Month 13 = 2027-11-13) and a penalty clause (e.g., $5K per learner shortfall, or a make-up recruitment window by Month 15 = 2028-01-13). By Month 3 (2027-01-13), secure signed agreements. Hire the cohort manager by Month 3 (2027-01-13) (not Month 6 = 2027-04-13) as a 1.5 FTE role with an assistant (0.5 FTE) to manage enrollment, retention and incentive logistics. Run a small pilot recruitment test (20-30 learners) at one site during Months 3-5 (2027-01-13 to 2027-03-13) to validate dropout assumptions and refine incentive design. Budget an additional $30K-$50K for recruitment shortfall contingency (bonus payments, gift cards, course credits if dropout exceeds 25%). Document dropout and completion rates weekly and flag any site below 65% completion at Month 18 (2028-04-13) for immediate re-engagement or replacement.

7.5.D Consequence

Pilot sample size below 80 per arm reduces statistical power by 10-15% and increases the probability of a false-negative gate outcome (missing a real effect) or an inconclusive result that triggers a $300K-$600K extension. Dropout above 40% effectively reduces the sample to <60 per arm, invalidating the power analysis entirely and making the gate result scientifically indefensible. This directly threatens the Month 24 (2028-10-13) GO/NO-GO credibility and extends Phase 2 by 3-6 months, consuming $300K-$600K of the $175K pre-gate reserve and forcing either a budget overrun or a scaled retreat to 2,000-word lexicon or fewer pilot sites.

7.5.E Root Cause

ESL and technical training partnerships are 'proposed' (not signed); recruitment timelines and dropout rates are estimates from standard ESL studies, not validated for this pilot design. Cohort manager hire is scheduled after commitments are signed, creating a 3-month gap. No contingency budget for recruitment shortfall or dropout above 30%.

7.6.A Issue - Safety-Critical Liability and Regulatory Approval Pathways Are Identified but Not Actively Managed; Delayed Approvals Will Compress Pilots

The plan includes a safety-critical adoption wedge (technical glossary cohort) but defers detailed liability and regulatory analysis to Month 2 (2026-12-13) and Month 4 (2027-02-13). The pre-project assessment flags that rejection by educational authorities (Ofqual, state education departments) is a 'high-likelihood, high-severity risk' with 30-50% adoption impact, yet the Regulatory Affairs workstream is not established until Month 3 (2027-01-13) at 0.5 FTE. Legal counsel is retained by Month 2 (2026-12-13) but the liability strategy is not set until Month 4 (2027-02-13)—two months into the project. If a formal regulatory submission is required (e.g., to Ofqual for accreditation of pilot curriculum), the plan acknowledges a 4-8 month review window, with no contingency path if approval is delayed. The risk register notes that regulatory delays could compress Phase 2 by 4-8 months, yet no pilot-as-research-study fallback is budgeted or pre-negotiated with ethics committees or regulators. Insurance availability and cost for safety-critical materials is not confirmed.

7.6.B Tags

7.6.C Mitigation

By Month 1 (2026-11-13), commission a regulatory and liability landscape analysis (by the legal counsel or a specialized consultant, 40 hours, $5K-$10K estimate) identifying: (a) whether pilot materials require formal regulatory approval in target jurisdictions (US, UK); (b) approval timeline if required (4-8 months, estimate); (c) whether a 'research study' classification can avoid approval or accelerate it; (d) insurance requirements and preliminary quotes for $1M-$5M product liability coverage. By Month 2 (2026-12-13), have legal counsel retain a product-liability specialist and secure written insurance quotes. Establish a Standing Regulatory Affairs workstream (1.0 FTE, not 0.5) by Month 1 (2026-11-13) to proactively engage regulators (Ofqual, OSHA, HSE) in March-April 2027 (Months 5-6 = 2027-03-13 to 2027-04-13) for non-binding advisory input on the 'glossary and labeling' scope—obtain written responses confirming this scope does not trigger mandatory approval by Month 8 (2027-06-13). If approval is required and takes 4+ months, shift safety-critical pilots to a post-Month-24 (2028-10-13) Phase 2.5 (Months 24-30 = 2028-10-13 to 2029-04-13) research track, funded from Phase 3 reserve, so main ESL pilots are not compressed. Pre-negotiate with ethics committees that pilot data can be used for both educational and safety-efficacy analysis.

7.6.D Consequence

If regulatory approval is required but not anticipated, a 4-8 month delay compresses Phase 2 pilots by 33-67%, reducing assessment window from 12 months to 4-8 months. This inflates measurement noise, reduces time for recruitment, and forces a shortened follow-up window (<30 days instead of the target 30-day retention assessment). The gate metrics become inconclusive and trigger a $300K-$600K Phase 2 extension or a NO-GO outcome that wastes the $1.2M Phase 2 spend. Insurance unavailability or cost exceeding $50K annually forces a retreat to non-procedural glossary-only pilots, eliminating the high-impact homograph-disambiguation evidence and reducing adoption value for safety-critical organizations. This directly threatens the safety-critical wedge credibility and the 'adoption-first, evidence-gated' positioning.

7.6.E Root Cause

Safety-critical adoption is attractive for high-impact evidence (e.g., homograph disambiguation reduces misreading in procedures) but is not treated as a distinct risk stream with its own approval and insurance pathway. Regulatory landscape assessment is deferred; approval contingencies are not pre-negotiated; insurance quotes are not obtained. The project assumes a 'glossary and labeling' scope for safety pilots (low-risk) but has not obtained written approval from regulators or safety bodies that this scope avoids mandatory approval delays.


8 Expert: Project Budget & Risk Officer

Knowledge: Project financial management, earned-value tracking, budget-contingency reserves, scenario-cost modeling, critical-path scheduling, risk-quantification frameworks (RACI, risk-register integration)

Why: The $3.5M budget is fixed and granular: Phase 1 $1.1M, Phase 2 $1.2M, Phase 3 $0.85M, reserve $0.35M. Current risk mitigation assumes a 4-week Phase 1 extension ($85K) and a 3-month Phase 2 extension ($300K), leaving only $35K headroom (estimate). The budget officer will establish monthly earned-value tracking, a rolling cash-flow forecast, and decision rules for reserve draws (current cap: $175K pre-gate). Without rigorous tracking, slippage in audio production ($80K-$120K, Month 6-11 = 2027-04-13 to 2027-09-13), assessment design ($150K-$200K), or partner incentives ($78K-$161K) will exceed the pre-gate cap unnoticed, forcing mid-phase scope cuts or timeline compression that invalidate pilots. The officer will also quantify the cost of each risk scenario (e.g., 6-month Phase 2 extension = $600K, exceeding all reserves), tie them to the go/no-go gate and post-stewardship funding gap ($150K-$250K/yr, $1.5M-$2.5M over 10 years, unfunded).

What: By Month 1 (2026-11-13), establish a financial baseline: itemize all Phase 1 and Phase 2 costs by workstream (rules, lexicon, audio, assessment, recruitment, staffing, travel, legal), set monthly burn rates, and publish a rolling cash-flow forecast. By Month 3 (2027-01-13), institute monthly earned-value reviews: track spend-to-date against plan, flag any category exceeding plan by >10%, and model the cost of the two identified fallback scenarios (Phase 1 extension $85K, Phase 2 extension $300K). By Month 12 (2027-10-13), conduct the Phase 1 exit-gate financial review: confirm all pre-gate expenses, validate the reserve balance, and present the reserve-release decision to the board (how much of the $350K reserve is released post-NO-GO or retained post-GO for Phase 3). By Month 24 (2028-10-13), quantify the post-Phase-3 stewardship funding gap and present three scenarios: (a) secured steward organization with committed funding, (b) fundraising/endowment plan requiring $X by Month 36 (2029-10-13), or (c) scaled stewardship (e.g., annual review only, no continuous maintenance).

Skills: Project financial management and earned-value analysis, cash-flow forecasting and variance analysis, budget-contingency reserve rules and decision gates, cost-scenario modeling and Monte-Carlo simulation, critical-path and schedule-risk integration, RACI assignment and spending authority

Search: project budget manager earned-value analysis reserves, financial planning contingency risk quantification, critical-path schedule cost integration Monte Carlo

8.1 Primary Actions

8.2 Secondary Actions

8.3 Follow Up Consultation

At the next consultation (recommend Month 3 = 2027-01-13, or immediately if budget concerns emerge earlier), review: (1) actual Phase 1 spend vs. budget baseline and revised cash-flow forecast for Months 2-12 (2026-12-13 to 2027-10-13); (2) enrollment baseline study findings and the probabilistic recruitment model (75th percentile dropout rate); (3) the psychometrician's power analysis memo and effect-size justifications; (4) signed partner commitments and recruitment plans (names, contact info, enrollment milestones); (5) candidate steward organizations and preliminary letters of interest; (6) audio production RFQs and locked vendor pricing by Month 4 (2027-02-13); (7) monthly variance and earned-value dashboards showing Schedule Performance Index and Cost Performance Index trending. Discuss whether Phase 1 is on track to deliver rules lock, 5,000-word lexicon with usable audio, and pre-analysis plan by Month 12 (2027-10-13) without contingency draws >$50K. If Phase 1 is trending red on schedule or cost by Month 6 (2027-04-13), discuss scope-cut options (e.g., 4,000-word lexicon, audio of highest-friction 1,000 words only) and timeline options (e.g., 2-week Phase 1 extension). By Month 12 (2027-10-13), confirm Phase 2 is ready to launch on schedule and on budget, with all pilot recruitment and retention logistics in place, ethics approval finalized, and gate metrics pre-registered and defended.

8.4.A Issue - Critical Pre-Gate Budget Headroom Exhausted; Overrun Exposure Unmanaged

The $175K pre-gate draw cap (5% of budget, half the $350K reserve) is inadequate against the identified fallback costs. A Phase 1 4-week extension ($85K) plus rater retraining and pre-registration work leaves only $90K headroom. Any psychometric redesign, audio re-production, or recruitment shortfall acceleration could trigger a $125K+ shortfall before the Month 24 (2028-10-13) gate. The plan acknowledges this but does not establish earned-value checkpoints or burn-rate thresholds that would trigger board escalation early. Without monthly cash-flow tracking and a trigger for reserve deployment, the project will discover budget stress at Month 8-9 (2027-06-13 to 2027-07-13), compressing Phase 2 and invalidating the gate.

8.4.B Tags

8.4.C Mitigation

Establish a monthly burn-rate baseline by Month 1 (2026-11-13): allocate the $1.1M Phase 1 budget across 12 line items (staff, audio, lexicon, assessment design, admin) with specific monthly targets and cumulative earned-value curves. By Month 2 (2026-12-13), set hard triggers: if cumulative actual spend exceeds budget baseline by >10% ($33K at Month 2 = 2026-12-13), trigger a board variance review within 5 days and a recovery plan within 10 days (e.g., defer discretionary travel, reduce audio takes from 2 to 1.5, compress rater training timeline). At Months 3, 6 and 9 (2027-01-13, 2027-04-13, 2027-07-13), conduct earned-value analysis (planned vs. actual cumulative spend, schedule performance index) and publish a revised cash-flow forecast for the remaining phase. If forecast predicts Phase 1 overrun >$50K, convene an emergency board meeting to approve either a Phase 1 scope cut (e.g., 4,000-word lexicon, single-accent audio only) or a phased release of the pre-gate reserve tranche (up to $50K additional with specific justification). Establish a monthly reconciliation with the finance function and a single, named Budget Owner accountable for weekly variance tracking.

8.4.D Consequence

Without immediate action: Phase 1 cost overrun discovered at Month 9-10 (2027-07-13 to 2027-08-13) leaves 2 months to absorb it, forcing either a $175K+ draw that consumes the reserve, or a 1-2 month Phase 2 delay that compresses pilot recruitment and data collection. A delayed Phase 2 start by 4-8 weeks erodes the pilot window from 12 to 8-10 months, reducing assessment sessions from 4 to 3 and cutting effective sample size by 15-25% after attrition, invalidating statistical power for the go/no-go gate. False-negative or inconclusive gate outcome forces a 3-6 month extension ($300K-$600K), fully exhausting the reserve and delaying v1.0 release by 6-12 months.

8.4.E Root Cause

The reserve design assumes independent fallbacks (one 4-week Phase 1 extension OR rater retraining, not both), but real execution risk cascades (weak audio delivery → delayed recording → rater calibration compressed). The $175K cap was set as a static policy without earned-value triggers or monthly burn-rate limits. No Phase 1 stage gates or cost baselines exist to detect overspend early enough to adjust scope or schedule.

8.5.A Issue - Pilot Recruitment and Retention Risks Underestimated; Sample-Size Loss Unmitigated

The plan targets at least 80 completers per arm (320 total across 4 arms), requiring at least 115 enrolments per arm (460 total) at a 30% dropout tolerance. However, this depends on signed pilot partner commitments by Month 3 (2027-01-13)—9 months away—with no interim recruitment checkpoints. The plan assumes dropout <=30%, but typical adult-education and technical-training pilot dropout is 35-45% without active incentive management. No cohort manager is hired until Month 6 (2027-04-13), leaving 3 months of recruitment unmanaged. If recruitment lags (only 70-80 enrolments per arm by Month 10 = 2027-08-13) and dropout reaches 40% (realistic without manager), only 48-60 completers per arm survive, dropping below the 80-per-arm minimum by >25%, invalidating statistical power for the four gate metrics.

8.5.B Tags

8.5.C Mitigation

Establish a Pilot Recruitment and Retention Plan (2-3 pages) by Month 2 (2026-12-13): conduct a pilot baseline study with 2-3 candidate ESL programs and 1 technical-training organization (Months 1-2 = 2026-11-13 to 2026-12-13, budget $15K-$20K, estimate) to measure realistic recruitment (% of eligible population converting to enrolment), baseline dropout (% completing all 4 sessions without intensive management), and demographic retention patterns (age, language background, motivation). From this, generate a probabilistic recruitment model with 50th, 75th and 90th percentile scenarios, and a retention curve month-by-month. Use the 75th percentile dropout rate (not 30%) as your planning baseline. By Month 3 (2027-01-13), require each partner to submit a written recruitment plan specifying: list of all eligible learners (N), weekly recruitment calls/emails, in-person enrollment sessions (dates, venues), and partner staff time allocated. Establish interim enrollment milestones (40% enrolled by Month 8 = 2027-06-13, 70% by Month 10 = 2027-08-13, 100% by Month 13 = 2027-11-13) with automatic escalation if missed by >2 weeks: if a partner falls behind, the cohort manager (hired early, by Month 4 = 2027-02-13, not Month 6 = 2027-04-13) activates acceleration tactics (increased incentives, evening/weekend sessions, partner marketing campaign, $20K-$30K budget, estimate). Hire the cohort manager by Month 4 (2027-02-13) (not Month 6 = 2027-04-13) and allocate 30% of their time Months 4-12 (2027-02-13 to 2027-10-13) to pre-Phase-2 recruitment support and contingency planning. Establish a monthly retention-tracking dashboard visible to the board: enrollments to date, dropout-to-date (with reasons), projected completers, and a 95% confidence interval on final sample size; flag to the board if the lower confidence bound falls below 70 per arm, triggering an automatic Phase 2 delay decision by Month 15 (2028-01-13) (before data collection starts) rather than Month 22 (2028-08-13) when it is too late to recover.

8.5.D Consequence

If recruitment achieves only 350-400 enrolments by Month 12 (2027-10-13) (a 20-25% miss, within historical range for voluntary adult pilots) and dropout averages 35% (not 30%), only 227-260 completers survive across 4 arms, leaving 57-65 per arm, cutting sample size by 30-40% below the 80-per-arm target. Statistical power drops from 80% to ~60%, raising the Type II error (false-negative) rate from 20% to 40% and making it 40% likely the gate will fail to detect a true, clinically meaningful effect on ordinal error or pronunciation consistency. A weakened gate forces either an inconclusive outcome and a 3-month Phase 2 extension ($300K, estimate), or a false-negative gate that kills the project despite potentially real effects masked by sample-size underpowering.

8.5.E Root Cause

The plan separates recruitment (signed by Month 3 = 2027-01-13) from retention management (cohort manager hired Month 6 = 2027-04-13), creating a 3-month gap where enrolment ramps without active support. Dropout tolerance (30%) is policy-level rather than based on external benchmarking or partner experience. No intermediate enrollment targets (e.g., 50% enrolled by Month 9 = 2027-07-13) trigger early course correction. The 460-enrolment target is treated as a firm commitment risk rather than a probabilistic forecast with sensitivity analysis.

8.6.A Issue - Gate Metrics Pre-Registration and Threshold Justification Incomplete; Defensibility at Risk

The plan proposes four gate thresholds (ordinal error ≥25% reduction, comprehension ≤10% slower, pronunciation consistency ≥15% above control, 30-day retention ≥70%), but none are pre-registered. Pre-registration is scheduled for Month 11 (2027-09-13), just 5 weeks before pilots begin. No power analysis has been conducted to justify why 80 completers per arm is sufficient to detect these effect sizes with 80% power, and no published benchmarks exist for 'pronunciation consistency' kappa targets in a novel constructed-language context. The plan lacks justification for why ≥15% above control is meaningful, or whether ordinal-only error reduction (the single rule tested most) is likely to yield ≥25% improvement when pilot participants see only 4-8 hours of Clear English exposure across 12 months. Without pre-registered, justified thresholds, the board faces pressure post-hoc to adjust thresholds to match observed data (goalpost-moving), inviting stakeholder claims that the gate was rigged.

8.6.B Tags

8.6.C Mitigation

Immediately commission a Power Analysis Memo (2-3 pages) from the independent psychometrician by Month 2 (2026-12-13), with delivery by Month 5 (2027-03-13). The memo must: (1) specify the assumed effect sizes for each of the four gate metrics (ordinal error reduction, comprehension speed, pronunciation consistency, 30-day retention), justified by reference to analogous interventions (e.g., citation to adult ESL learning studies for retention benchmarks, dyslexia or speech-therapy research for pronunciation consistency effect sizes); (2) conduct a power analysis for each metric, showing the sample size (per arm) required to achieve 80% power at α=0.05 (two-tailed) for each effect size; (3) justify why 80 per arm (or the revised number) is feasible and cost-effective given the partner commitment and dropout assumptions; (4) propose a decision rule for the four metrics (e.g., GO if ≥3 of 4 metrics meet thresholds and all are valid, INCONCLUSIVE if 1-2 metrics fail but data quality is high, NO-GO if ≥2 metrics fail or data quality is compromised). Circulate this memo to the board by Month 6 (2027-04-13) for approval and comment. By Month 10 (2027-08-13), the psychometrician must deliver the finalized pre-analysis plan (5-7 pages) specifying: exact thresholds for each metric (with effect sizes and sample sizes cited), minimum sample size per arm (with sensitivity analysis: power under 70, 80, 100 per arm scenarios), primary outcomes (ordinal error and comprehension speed) and secondary outcomes (pronunciation consistency, retention), the justification for any thresholds that differ from Month 5 (2027-03-13) proposals, and the specific decision rule for the board gate vote. Register this plan on Open Science Framework or equivalent by Month 11 (2027-09-13 at 14:00) with board sign-off, and publish it on the project website immediately. By Month 12 (2027-10-13), commission an independent external expert (not the project's psychometrician) to review the pre-analysis plan for statistical rigor and boundary conditions (e.g., 'what happens if comprehension time is highly skewed or outlier-laden?'), and publish their review summary on the website. This sequence ensures thresholds are justified, pre-committed and defensible by Month 11 (2027-09-13), 5 weeks before pilots begin, and establishes external credibility for the gate.

8.6.D Consequence

At Month 11 (2027-09-13), when the board convenes to pre-register thresholds, if the psychometrician's power analysis reveals that 80 per arm is underpowered (true power 65-70%) to detect a 25% ordinal error reduction, the board faces three bad choices: (1) freeze thresholds at pre-registered but underpowered levels, risking inconclusive gate findings; (2) adjust thresholds downward post-hoc (e.g., 20% reduction instead of 25%), inviting the appearance of goalpost-moving and stakeholder skepticism ('the bar was lowered to get a GO'); (3) delay pilots by 4-6 weeks to recruit additional participants, compressing the assessment window and reducing data quality. Any of these outcomes weakens the gate's credibility as a defensible, pre-committed decision rule. If a NO-GO is reached on the ordinal-error metric (e.g., 18% reduction, below the 25% threshold), stakeholders can claim the threshold was arbitrary because it was never justified against external evidence or similar standards.

8.6.E Root Cause

The plan treats pre-registration as a procedural checklist item (Month 11 = 2027-09-13) rather than as foundational evidence work that must precede protocol sign-off. No power analysis or effect-size literature review has been conducted to anchor the 80-per-arm sample-size estimate or the proposed thresholds. The pronunciation consistency metric is novel (no published kappa benchmarks in this domain) and its meaningfulness is asserted rather than validated. The plan assumes a psychometrician will be hired by Month 2 (2026-12-13) but does not require them to deliver a power-analysis memo by Month 5 (2027-03-13) before rule-locking, so threshold design is decoupled from the rule-specification timeline.

Level 1 Level 2 Level 3 Level 4 Task ID
Clear English Standard v1.0 922abd2a-72ff-4b45-bf76-f1abce051224
Project Initiation and Governance Setup 44c9a9d2-5967-4900-8de8-767722fa72dc
Establish editorial board charter, governance structure and decision authority 84023ef2-6a25-421a-ab7e-4312f1728e4c
Draft editorial board charter with governance framework e3e87dac-9e11-47aa-939e-54bec40cfd21
Recruit and formally appoint 7-9 board members 12de375e-4c54-4362-b8cc-e9a5174a4011
Identify and secure external tiebreak arbiter 2af850d6-fefb-4da1-b47b-83e73f35cf7f
Convene inaugural board meeting and confirm governance procedures a9f7a562-961d-4bea-9e45-0ee072ffafcc
Publish charter and governance framework on project website 11ff692c-f971-4422-ba27-0af1d01abe6b
Recruit core project team including psychometrician, linguists and administrative staff 889964ac-9023-4e6c-978b-e35cba133873
Identify and pre-qualify 15-20 candidate professionals a0de85b1-4885-4019-bde5-270b4a88c5de
Draft job descriptions and offer-letter template 7076cb45-8fe4-4967-9e4f-99be7e02c910
Conduct recruitment outreach and secure written commitments 535e2662-b85f-4277-8f6c-22ef7edb9df5
Plan and execute onboarding and team integration 4998ff46-35a1-425d-a8df-dae8d50fecaf
Confirm key-hire availability and mitigate recruitment risks 945cf99c-f2df-4f10-8080-8433b40eb8e9
Secure ethics approval and establish legal/liability framework with counsel 1000a2fd-d19f-45d6-be98-9fd47e0f9548
Engage ethics review committee and legal counsel by Month 1 (2026-11-13) 901cc1e3-d36d-4a34-a94d-0678777a2986
Develop compliant consent forms and data agreements aeadb695-6dae-4857-bab4-6d8024b0a2bd
Submit ethics protocol and obtain approval by Month 6 (2027-04-13) ad26838f-e260-4919-8200-7cba258bf208
Establish liability strategy and safety-critical material disclaimers c280341e-aeed-4804-9b81-4bb2f698b4c1
Secure encrypted audio storage with compliance audit by Month 8 (2027-06-13) b5a621ca-6ed2-4bb2-b429-e386c331e011
Identify and approach potential pilot partner organizations and steward candidates 042bc5e1-a57c-4b26-a5e2-cbaff9139acf
Compile prospect database of ESL programs and technical organizations 95548fc5-0646-49d6-9066-099cd4034b51
Draft and refine partnership value proposition and MoU template 828fa7b0-c561-4132-bbe6-acf189f33af9
Execute outreach and secure signed commitments by Month 3 (2027-01-13) 317174d1-d9d2-4d89-af2d-994c92ecca57
Establish early steward-candidate identification and engagement c08dfef0-c25e-4ff0-b135-ba5d0c5c2934
Monitor partner commitments and conduct mid-recruitment confirmation by Month 9 (2027-07-13) 7c48b34b-58d6-4eb1-83ee-0f57bb071528
Design and conduct recruitment baseline study with 2-3 pilot sites (Months 1-2 = 2026-11-13 to 2026-12-13) b8b08a8b-1f57-4de2-b802-693ed8fc2cde
Identify and approach 2-3 candidate pilot sites for baseline study c549257d-a160-4e96-9314-ae43ce41661b
Develop recruitment and retention assessment protocol aligned to Phase 2 design f3359245-fc68-4552-8175-59ef77d756b7
Recruit and enroll 30-50 learners across pilot sites and administer two assessment sessions 5347d2ad-4237-4b4a-bb1b-51685143e79e
Analyze baseline data to estimate recruitment conversion and dropout rates for Phase 2 planning e8eeb426-158f-4384-b008-4103c809f6cb
Finalize Phase 2 recruitment plan and partner MoU schedules based on baseline evidence ceb8ec75-33ef-4c37-8540-9dce25709ffb
Rule Specification and Standard Development a3298be4-f0b4-47fc-a62f-f997be0e3a3a
Define and justify five core rule specifications: ordinal markers, grapheme-to-phoneme depth, morphology threshold, homograph policy and accent anchor 3c709290-3843-4eea-ad3f-cf870ce8b761
Design ordinal marker architecture with spoken form 2eee5117-ea99-4090-8858-bc5d5028a16f
Specify grapheme-to-phoneme intervention depth and overlay delivery 3e029f13-f823-4421-9221-2ad663bd71de
Establish irregular morphology retention threshold with frequency cutoff d56524dc-94fb-4069-8f17-a29252e0a4b7
Define homograph disambiguation policy and mandatory marker list 053a75ea-ed0f-4215-9581-bb814e510568
Choose reference accent and document phonemic mapping 7c119e2b-d0e6-4474-9e7e-a2222eb8292c
Compile and curate the 5,000-word core lexicon with frequency validation and coverage audit 415580c3-3fb6-4c55-b49a-acb472df11e0
Secure frequency corpus and licensing agreements 5cec71b0-760f-4d2e-b367-02e4118b0387
Define and document word-selection criteria 791b9f04-cf49-4ba3-8e73-115fada8af77
Compile candidate lexicon and conduct initial curation 9a7c05d8-d9d3-4e6b-aa80-835e6362159b
Conduct coverage audit on pilot running text and remediate gaps 379f5116-6107-4d6e-8506-02bf50dc350b
Finalize lexicon metadata and quality-assurance review eed86f14-27d3-437f-82c4-cced6e2b6587
Establish reference accent anchor with phonemic inventory, key contrasts and exemplar recordings 106c3144-2946-4daa-86bb-bb6cd5f48a8e
Select and justify reference accent choice 50cc1bd2-71cb-45ec-9ab8-f8cbef32b5a2
Define phonemic inventory and key contrasts 4d5e1888-9eea-4757-95d0-e3801b5dfe8e
Produce exemplar recordings (20–50 words per contrast) 4c4d3828-8f4b-4e78-82d2-f6b89788dafa
Develop pronunciation-marking system and rater-training manual 78746b3e-e5fd-4143-b3d9-50e63231c975
Publish accent anchor and exemplar access on project website 9c944443-8162-4f52-9ae9-8e1a3ab826ba
Publish draft standard for 30-day public comment window and address stakeholder feedback (Month 11 = 2027-09-13) 75a184bc-faa9-42e0-b395-965a43ff2ba2
Prepare draft standard with rule rationale and examples fd21dce7-868f-40d5-83a4-e45d812c5cd3
Establish comment-management platform and triage rubric fabc050f-cac5-425a-96f7-a0d4012d03cb
Execute 30-day public comment window with targeted stakeholder outreach 4b10317a-2b31-47b1-8009-f5b2ed14754a
Analyze comments, draft project responses and rule clarifications 8cb0ac94-da94-46f9-89ca-538963d92a74
Convene editorial board review and approve published comment responses 40810fc2-ebb9-4d81-b2d0-cff0964b1981
Publish comment summary, responses and rule-freeze notice by Month 12 (2027-10-13) eb4cb09a-5940-4c1c-83ec-b737d4a08bd4
Lock all rules at Phase 1 exit gate and issue rule-freeze notice by Month 12 (2027-10-13) e9d68819-e218-40ab-9ac4-8b93f048558b
Resolve all outstanding rule disputes via voting or external arbiter 33c07bda-f69d-440c-baa6-7185db318eff
Finalize rule-freeze template and legal notice with counsel review 9727554b-e2b3-4952-b325-b2562a04bff9
Schedule and execute board vote on rule finalization at Month 12 (2027-10-13) start 01517962-4bee-4f26-bc14-da369dfe724e
Issue rule-freeze notice to all stakeholders within 2 business days of board vote 7b0d4820-6e79-4565-a84a-1cc101e89b19
Publish rules-locked decision log and rule-freeze confirmation on project website d3c51fe8-c5bb-43ae-a54a-fb2b17915fcf
Reference Corpus and Audio Production 2f0aba62-5e16-43e5-8724-fc684c3865d6
Contract with professional recording studio and confirm capacity for 5,000-word audio production d53410d3-362f-4cc7-b8cf-3ec6b7c85d1e
Prepare RFP and studio selection criteria 3bb09819-839e-4696-af89-acaac3eacf5c
Issue RFP and negotiate fixed pricing contracts 2780a132-727b-4784-a8bb-92889b2b1a81
Establish fallback vendor relationship and contingency plan c7938ae0-461f-4d16-87f9-8e1c17f2c3f1
Conduct technical dry-run and validate studio workflow 52d04d1d-2d53-4087-bcf3-78491008af26
Monitor studio performance and manage payment/schedule milestones c3ce1e2e-a56b-4bb0-9688-a7fd10c898f9
Recruit, train and calibrate 4-6 pronunciation raters on reference accent and scoring rubric (Months 4-9 = 2027-02-13 to 2027-07-13) 53d00aab-8e06-47ed-b50f-13264b33098f
Recruit 4-6 pronunciation rater candidates c4e2a638-092f-414c-932b-1897d45cda9e
Design rater training protocol and manual 6abdd8ce-09ff-427e-bc6d-b2ec2ec5b8f0
Conduct rater training sessions (6-8 hours total) 82f5a0ac-f55e-4f16-8cdc-cf7b9004ef4a
Execute inter-rater calibration on 100-200 word pilot sample 10dc8123-07c2-4e0a-8436-b4a47646c84d
Monitor rater consistency and maintain backup team 40701236-605d-438a-a9a0-ce9aba0a8a9d
Conduct inter-rater reliability calibration on 100-200 word pilot sample and confirm Cohen's kappa ≥0.70 by Month 10 (2027-08-13) 8bbd5510-dad5-4196-913d-ccea64658f6a
Assemble 100-200 word pilot sample with pronunciation scoring rubric 43000e61-b680-4115-af56-2822cd6fac92
Schedule and conduct independent blind scoring by 3+ raters 649ea8f1-86b0-4d72-bd47-d58e5358b31e
Calculate Cohen's kappa pairwise and document rater-pair breakdowns e98e90c1-bbfd-425d-85d2-11c76218df86
Escalate findings and execute remediation or approval decision 326f8451-2a5f-49e0-9777-1c37c44094d6
Complete 5,000-word audio production with 2+ takes per entry by Month 11 (2027-09-13) c79a07fa-140b-4541-9732-b2f73f8531dc
Finalize lexicon entries and lock accent anchor by Month 8 (2027-06-13) 863712bb-5a71-492b-bdc3-839ffd25a2ab
Coordinate studio recording schedule and manage production workflow 2e117db1-131b-4fd8-928b-8663525e5039
Onboard and retain pronunciation raters through full audio production 860a798f-bee4-4dd0-ba57-979832a5db97
Conduct dry run of assessment and recording workflow at Month 10 (2027-08-13) e4d3f20e-6375-4d0f-bc4e-8fb0615048c9
Deliver encrypted audio files and validation documentation to storage by Month 11 (2027-09-13) end a1b892f3-54a7-4898-9ce7-f4b5e50ef454
Deploy encrypted audio storage infrastructure with GDPR compliance audit and backup protocols 805cfe17-8827-4090-a778-0ae0f965ca1a
Select and contract encrypted storage vendor with GDPR compliance ac144bc0-b8b1-4bac-981b-218a5504610b
Deploy staging environment and conduct technical validation f41d2d4f-6a15-411b-a23b-266b0b1d0727
Execute GDPR and data-protection compliance audit 0b682141-46f7-477d-a79e-43503de794a6
Establish access controls, logging and data-retention procedures 622faca2-8c18-4f88-9adc-216362d777c5
Validate backup integrity and conduct disaster-recovery dry run 21584389-20d1-4b8d-b57d-2b3afcd00a66
Assessment and Metrics Design and Pre-Registration d10d7b3a-c0d0-47b2-bd7e-f58e02449c40
Commission independent psychometrician to design purpose-built assessment instruments for ordinal error, comprehension speed, pronunciation consistency and 30-day retention 7748ea6d-662e-400c-94a8-8ef877228c07
Onboard psychometrician and define assessment scope bc9e4990-0de3-4de2-8a88-9ec4aca221c0
Design ordinal-error, comprehension-speed and pronunciation-consistency instruments 3dbc143b-982d-4889-b7bf-050d8f6819a2
Design 30-day retention follow-up protocol and delayed-posttest format 3e9e4044-19fd-426d-961a-6f9f6643f37e
Pilot-test instruments with 2–3 candidate educators and gather usability feedback c1b52996-f0e1-4ec5-b246-1b534d9a4498
Finalize assessment protocols and obtain board and ethics approval by Month 6 (2027-04-13) 5d838828-f644-43f0-b749-a0a50fcbb35f
Conduct validity study with 20-30 adult ESL and technical learners and estimate effect sizes for power analysis (Months 10-11 = 2027-08-13 to 2027-09-13) 31838d15-c818-4104-be38-7ef98fd3b94f
Recruit and enroll validity-study cohort 34fcb56e-2ffd-45c3-b45b-e5eed76195f4
Administer all four assessment tasks 5cdae0c5-73b4-46a7-ac50-ad4e12277394
Score pronunciation audio and calculate inter-rater kappa 4e01c352-581b-43eb-b801-440dfd0f4336
Compile and clean validity-study data 747eb3f9-97ea-46d1-92be-ade569b44496
Estimate effect sizes and conduct preliminary power analysis bd6362de-77fa-4eaf-aa27-60170566240e
Perform statistical power analysis and confirm minimum sample size of ≥80 per arm achieves 80% power at α=0.05 3b50f4de-d6e9-42f2-a5d5-0c1b1b73d28a
Estimate effect sizes from validity study data 5c802131-10ff-4b7a-a982-45c0076bed8f
Model statistical power across assumed dropout scenarios 9108e23d-40df-4fa3-97c9-72f2ec700f1c
Conduct sensitivity analysis on effect-size assumptions 0aa39b55-8a0f-4f43-9a19-dfb9d7770b72
Convene power-analysis working group and obtain board approval 8140bb7d-3a51-4f48-9f35-c9ea0befbcdd
Finalize sample-size recommendation and document for pre-analysis plan dde222a0-802b-47a3-bdbc-ad9478ee2da3
Develop comprehensive pre-analysis plan with numeric thresholds, decision rules and sensitivity analyses 2e7a70f0-4aba-4c19-be16-5107dfea42bb
Establish pre-analysis-plan taskforce and finalize numeric thresholds 4b76aeb8-0dc6-4982-baf9-66a8a7d07e57
Draft decision rules and inconclusive-outcome boundaries 67a00710-8dbc-4962-b21f-99f00af21f85
Conduct sensitivity analyses across effect-size and dropout scenarios ee4dc3c6-ecb0-4530-8a3e-168d38aac177
Publish draft pre-analysis plan template and circulate for board approval 6d3be1a9-f2df-4e91-89fd-ba40af18f274
Register final pre-analysis plan on Open Science Framework with attestation 0fecf6de-1447-4c2f-8af8-0e0a70dfbfa8
Register pre-analysis plan on Open Science Framework by Month 11 (2027-09-13) with independent reviewer attestation 8196b2b3-1556-4b73-8a79-45454953b89f
Identify and contract independent pre-analysis plan reviewer 36e01c1c-4a0f-4b69-889e-ab938747f6b1
Submit pre-analysis plan to OSF with technical validation 8714ef2a-0487-48df-a023-46b3700bcb56
Publish OSF registration link on project website and issue public notice 0564432a-15ae-47d8-81e4-5cbcb6b46eec
Conduct board sign-off on final registered plan by Month 12 (2027-10-13) a44a8e64-a7e1-42ac-9158-a7d4bea1c8f3
Pilot Partnership and Recruitment 4eed3649-cfc5-45de-b078-69c3b0f3707c
Negotiate and secure signed Memoranda of Understanding with ≥3 ESL programs and ≥2 technical/safety-training organizations by Month 3 (2027-01-13) 69ec9d75-11c8-4f7a-bb9e-1402459c7c38
Prepare template Memorandum of Understanding with standard terms 9181b44f-59b5-40b8-9500-3a7f1c66237d
Conduct 1:1 compliance and legal briefing with each partner site 92e5f76c-6db3-41dc-9217-b90bc7d863ab
Negotiate and finalize signed MoUs with ≥3 ESL programs and ≥2 technical organizations be3409cc-31b9-4c02-a65f-285d042a0070
Secure non-binding letters of interest from ≥3 ESL publishers 86f07ace-4e63-40bc-8a3b-cb6e4421471f
Escalate and resolve any unresolved negotiations by Month 3.5 (2027-01-28) a624c1b9-b094-4cd6-bd12-07db3b1bff45
Hire dedicated Phase 2 cohort manager by Month 4 (2027-02-13) with enrollment and retention accountability 62c395a7-76a3-48c6-a29c-43fa010cbe12
Define cohort manager role scope and accountability metrics 133d6a60-7216-44d8-89b3-0ede4b467b0c
Identify and source cohort manager candidates 10951bc3-cc01-49e8-8a1a-b74869fd45c1
Conduct interviews and salary negotiation with finalists 8cb34995-2397-4452-9526-992998a5501c
Onboard and train cohort manager on enrollment/retention protocols da8c5927-1409-4766-92d5-dcd4715081db
Establish enrollment tracking dashboard and weekly reporting cadence 9681a1c6-a9e5-482b-993a-69fc5962c2fe
Design recruitment and retention protocols with contingency incentive strategies ($50-$150 stipends) 5355a0eb-7b83-4d75-b427-f91390444a68
Co-design recruitment and retention protocols with pilot partners ca4d0418-3866-472e-88d9-ee1203a9b29b
Design and validate incentive strategies ($50–$150 stipends) 544b8bae-44f2-4b5c-a604-cb6104cadb98
Establish legal agreements for data sharing and consent across partner sites ce2213bf-d416-42f3-8793-e2d6827350d4
Create participant recruitment and tracking tools and playbooks e0e40ad4-6378-411b-86dc-3e806d89ef3d
Integrate recruitment protocols with partner curricula and institutional schedules 03228dca-4da5-46a8-be00-2efd09e6195c
Establish monthly enrollment tracking dashboard and conduct mid-recruitment audit at Month 10 (2027-08-13) ab5016fc-2f7f-4804-bd28-a4fc096eaf81
Design and prototype enrollment tracking dashboard 82a10d01-06fd-4591-a637-933b759e6606
Establish weekly enrollment sync calls and monitor metrics 02ba872f-1506-4879-a4ae-2dd898829f34
Conduct mid-recruitment audit at Month 10 (2027-08-13) f3f926e7-c7f7-4da8-9ec4-8624a4ba35ae
Prepare contingency activation protocols if audit reveals shortfall b4b34986-36e5-4210-964a-80bdb2822d15
Flag sample-size risk and escalate to editorial board if needed 0d6b2537-4fcd-4e92-a793-ed0dd799383c
Achieve ≥115 enrollees per arm (460 total) across 4 study arms by Month 13 (2027-11-13) with ≤30% tolerated dropout f43a5b9c-dcf9-4507-b3ff-40b78e1f74fd
Design recruitment and retention protocols 6508c2a6-4c37-4e09-8049-062e664a9d3a
Establish enrollment tracking dashboard 603bacf0-e82d-403f-ab43-3f81a2ea4eea
Activate contingency incentives and outreach 70e94de8-604d-4c18-a27d-9a331df36102
Execute retention monitoring and dropout follow-up 3f858330-04c1-4f1f-bb5a-f274f4f88188
Verify sample-size adequacy for statistical power c4d55cda-eef9-4088-b647-5e555204345e
Pilot Execution and Data Collection (Phase 2) fb8a9bd5-a316-4520-ba02-85771f2864bd
Deliver pilot curriculum and teaching materials aligned to locked rules and 5,000-word lexicon 3697380a-c575-4942-b46c-2642044efcbc
Co-design curriculum framework with pilot partner educators a21c0ac1-addf-416f-be1c-2b8347be22fd
Draft instructional materials for all four study arms 6fb3a47e-baa3-4f60-95be-28122092c9ba
Create pronunciation-guidance overlays and audio-linked reference materials 414fcaa2-e03d-4e3d-ad53-7a9579fe18d3
Validate curriculum fidelity and pilot readiness with partner checklist f4e951b3-a09c-4d11-adac-43cb80e311cd
Produce instructor implementation guide and FAQ for troubleshooting ce8c928b-3494-4551-8f7e-af23cd2285b0
Conduct 4 assessment sessions (approx. 60-90 minutes each) across all arms, recording ordinal error, comprehension speed and pronunciation audio a7449f2b-a8cb-425c-a1ec-d5a4609a7ce0
Pre-schedule assessment sessions with 4-week advance notice and backup time slots 83d4003d-a9f1-48a4-b8b8-0991d12b5f0b
Deploy and test assessment platform across 3-4 pilot sites (Month 10 = 2027-08-13 dry run) ab9d268e-773b-46bc-bc19-40c71dd04af7
Maintain trained rater team with cross-training and backup continuity 63d9e35e-6f8c-4ffb-a00c-1a088483f60d
Execute 4-session assessment protocol with redundant audio capture and data backup c7a18002-52a6-4c08-b7b9-14478dc29d3d
Administer 30-day retention follow-up and compile locked data set by Month 22 (2028-08-13) 8872c22d-e03f-41dd-8d4e-92ffefe0aa0f
Administer 30-day retention follow-up and compile all learner response data by Month 22 (2028-08-13) 7c36c478-d0e9-4633-abb8-89b5d63fa430
Schedule and coordinate 30-day retention follow-up sessions e9e20718-ebb5-42ec-9320-d648bc8417e6
Administer retention assessment and record audio 7ea96c24-ad16-4a4f-99cd-b7d76923aa82
Process and validate retention data for completeness 25637bef-a94f-4952-8950-1548b91b035c
Transfer retention audio files to encrypted storage with metadata 34eb4a75-1d78-44c9-879b-7255d3e47518
Compile final learner response dataset and lock data by Month 22 (2028-08-13) 95b7f44e-a93e-4661-8d03-ffcd2b39ba53
Score pronunciation audio using calibrated inter-rater protocol and compute pronunciation-consistency metric with kappa documentation 28010f4d-a4ef-413b-9090-c44d005592e3
Maintain rater team continuity and calibration 1c1e9417-4e83-4196-b805-389d8c67d579
Prepare and validate audio data for scoring 22dda8a6-e1fb-4f1b-9313-ef65937289cf
Execute inter-rater scoring and manage close-call disputes 1656fdf9-20be-41b1-b589-079e34cd13b9
Calculate and document pronunciation-consistency metric and final kappa a24ae4b6-56d3-44ad-b919-2a589838b23a
Archive scoring data and prepare steward handoff documentation 1438cde9-5241-47b0-81d0-54a669ed48d9
Analyze pilot data against pre-registered thresholds and prepare go/no-go gate decision dossier by Month 24 (2028-10-13) 386069ba-0587-45db-a013-341c1488694b
Lock pilot data and conduct preliminary statistical analysis 62a120d0-f546-4907-bba1-0342f53526bf
Validate effect sizes against pre-analysis plan and power assumptions 8479c067-6303-45d3-a93d-67d6eb992d6d
Evaluate metric outcomes against pre-registered thresholds and decision rules 04b7e00d-3347-4a52-a5d3-37a29296b770
Conduct sensitivity analyses and document assumption violations 2af7a2ac-deff-41e2-8d90-83e583e477af
Prepare comprehensive go/no-go decision dossier for editorial board review 2119a5d1-92f8-41ff-b881-e48b4d8f8a15
Licensing, Governance and Stewardship Planning 03a24926-12d0-4593-915f-c2bf5548b3f2
Commission legal analysis of three licensing models (permissive, certification-mark, share-alike) and obtain board vote by Month 6 (2027-04-13) 8d4f0ba6-9d40-4b4d-b02b-436118467f8b
Retain IP-specialized legal counsel and define scope 1b02d142-6059-484d-9dee-525be878abf3
Draft comparison matrix for three licensing models aadaae75-a79a-4f7f-94c4-ae9a5b6c84b8
Prepare board decision materials and staff recommendation 6eca6ba6-b766-490f-80c9-f9704e2cc16c
Convene editorial board decision meeting and document vote a16553c6-6764-4dc5-a62e-76a968fcacca
Publish licensing decision and rationale on project website d192b47b-3043-49ef-9675-acc0dae3b96a
Publish conformance checklist and licensing policy on project website by Month 12 (2027-10-13) 4ab931b1-e9dd-420a-b0d2-d19a4e1c5f47
Finalize licensing model decision and board approval a4cfb65b-918e-4568-9738-4bfc1e62ba9c
Draft conformance checklist and policy document 9a37718a-75e2-494e-9754-fdb20e1212f2
Conduct stakeholder usability review and iterate f15b742a-cb41-4515-82cb-d6c4ac544203
Prepare website infrastructure and publish materials 9f665a12-4a11-492d-ac82-b5244ef639bb
Publish decision rationale and stakeholder guidance 74f47e27-302c-4c26-98fb-003f8b7d3de2
Identify 2-3 potential steward organizations and solicit non-binding letters of interest by Month 24 (2028-10-13) e4dfbada-a020-47f7-905d-c68c48e73714
Compile steward prospect database with verification 4e304bf1-9dfd-4268-bd70-a1af3961e083
Draft stewardship proposal and governance framework a1a4d95e-6a2a-427d-a703-53c68ea6ed52
Develop outreach strategy and engagement timeline a3a29213-95f5-456d-907e-da96061f2108
Execute prospect outreach and collect letters of interest 425d388d-06c8-4096-b366-f612c7979e30
Negotiate and secure signed Memorandum of Understanding with committed steward by Month 33 (2029-07-13) specifying annual budget ($150K-$250K estimate), governance and 10+ year commitment df93cd84-0aed-4a78-bf4e-abe9d313692d
Identify and engage top steward candidates with formal capability review ab948ebe-aa85-4edf-949f-20b2fcbf466f
Draft stewardship MoU template with flexible governance and budget clauses a2822996-5290-4ca2-bef1-9d227c595f2a
Conduct steward negotiation and align on governance handoff expectations db829c8d-fa55-4ca2-85b8-53c39f8836a0
Secure signed MoU with binding steward commitment by Month 33 (2029-07-13) 678a35fc-ffe8-4e62-87b8-6c2f01feece9
Prepare steward onboarding checklist and transition materials for Month 36 (2029-10-13) handoff 4fb01494-a980-4976-9c2f-e6725fbfff51
Establish standing Stewardship Committee (3-5 members) and publish 5-year Stewardship Roadmap with maintenance calendar and change-request procedures 95d04aa9-56a4-408d-ad87-0a7d1a4a374e
Draft Stewardship Committee charter and role descriptions 8830a77a-8b94-498e-8b1a-52b43e230ce9
Solicit and recruit 3-5 stewardship committee members from steward organization f8b969f1-a7d5-4b0d-9b40-dc065a95f505
Create and publish 5-year Stewardship Roadmap with maintenance calendar 58330b58-c1d3-42d9-b348-b5b155d02199
Establish change-request and conformance-dispute resolution procedures b58cde20-22ef-4834-90bb-96ad7b5e2ff8
Hold inaugural Stewardship Committee meeting and publish meeting minutes and action plan 61ce51ce-a533-4ad2-bd31-d3609b3296ad
Standard Release and Limited Adoption (Phase 3) bd569886-53b4-4b17-b889-29469fcb318f
Finalize style guide, reference dictionary and curriculum package as v1.0 deliverables 20f0b93f-3380-43d0-b2e3-4a889311330a
Draft style guide, reference dictionary, and curriculum v1.0 copy 79dd1655-36a0-4443-8a73-f1004f3fe286
Conduct editorial review, legal liability review, and final formatting 2ee46eaa-df3a-4e7b-b5a2-1ff495da72af
Prepare publication infrastructure and public-website deployment plan 16e23922-ac2a-4419-a3be-7f4b8fd51446
Coordinate announcement, media outreach, and stakeholder briefing bdfb8642-ad90-4b85-aab7-d88dbf7112fc
Execute publication sign-off and go-live f7a9a450-3f14-4dad-a107-cd624e19a8e7
Publish Clear English Standard v1.0 on project website with full rule rationale, decision log and conformance checklist by Month 30 (2029-04-13) 976bd78c-4ac1-4e76-bc53-f94170dee2b8
Finalize style guide, reference dictionary and curriculum package 2bd94673-a912-4ded-afa7-c3b56e0be75e
Conduct legal and accessibility compliance review 11f7475c-4860-4199-b6ed-d04737e5c06d
Provision and test website infrastructure for v1.0 hosting 084f4e44-78b8-4593-ac34-b426335d04fc
Prepare and publish announcement and marketing materials 3ab5b789-6a32-47ac-971d-c5251091a697
Execute v1.0 publication and stakeholder notification 21375e30-0c7c-45ef-9171-abdcbe3b123f
Conduct stakeholder outreach to ESL publishers and technical-writing organizations with non-binding adoption partnerships and marketing materials 1281eadb-2c38-4a37-aaf3-3acef8f60934
Compile verified stakeholder contact database cefc79ae-dfdf-4199-94c6-193cf5423dc2
Develop tailored outreach materials and case studies ab6c5613-764e-411f-a83e-eb60ae2999e2
Schedule and conduct warm-introduction outreach in tranches 99f67ceb-fde0-4ab1-9f26-26c71c6015ed
Execute two-week follow-up and adoption-interest assessment e4a182d5-1853-4299-8dcb-92a12b3cd00a
Negotiate adoption agreements and confirm ≥3 adopters by Month 36 (2029-10-13) 2c154ff8-daaa-488b-8ea5-056fdfc399d5
Support ≥3 licensed third-party adopters (at least 1 ESL publisher) through conformance guidance and minimal technical assistance 584c7e9f-f1b4-4318-99cf-bd0b289309c0
Publish light conformance checklist and adoption-support documentation f4d43903-3451-48ba-8fbe-c2ca2a3b8761
Compile and verify contact list of target adopters and decision-makers 842b043f-0026-4b48-80d8-2883679f3bd3
Design and execute targeted outreach campaign with adoption pitch and case-study materials f03729ac-cf0b-4344-b33e-533c58611a7b
Negotiate adoption agreements and define technical-support scope and limits 42673a17-f9d0-4a61-9c9b-8b240b280ee9
Establish and operate adopter support workflow and escalation procedure 106b5bf0-f801-4aa7-9d01-752571377191
Execute formal handoff to steward organization with archive of all project records, decision logs and maintenance tools by Month 36 (2029-10-13) a4e36b3f-0050-4d12-a61d-ffd17f50eb24
Prepare steward onboarding materials and training checklist 88150500-0d06-4b67-b4ec-7035e2c82fb2
Audit and archive all decision logs, rule rationale and project records e4c7d17d-2d89-4c9d-ac6d-2a450eb8625b
Migrate data, tools and maintenance systems to steward platform 852efc43-c844-4f87-8b0a-ce91e258f5c8
Conduct joint handoff meeting with steward and project team sign-off d2a18bd7-18a8-47ff-acba-b6f9bb195af9
Establish post-handoff support escalation protocol and wind down project 1d7bb301-1cc7-4047-b725-69ddae83a31b

Review 1: Critical Issues

  1. Pre-registration and gate-threshold justification incomplete by Month 11 (2027-09-13). The four gate metrics (ordinal error ≥25%, comprehension ≤10% slower, pronunciation consistency ≥15% above control, 30-day retention ≥70%) remain proposals without a power analysis confirming that 80 completers per arm achieves 80% statistical power. The psychometrician is not hired until Month 2 (2026-12-13), leaving only 9 months to conduct a validity study (N=20–30, Months 10–11 = 2027-08-13 to 2027-09-13), finalize thresholds, and pre-register by Month 11 (2027-09-13)—about 4 weeks before Phase 2 starts at Month 12 (2027-10-13). If thresholds are not empirically justified or pre-committed, the Month 24 (2028-10-13) go/no-go decision becomes scientifically disputable, inviting stakeholder claims of goalpost-moving and reducing Phase 3 adoption credibility by 20–30%.

  2. Pilot recruitment and retention carry 30–40% attrition risk with inadequate contingency. The plan targets 460 enrollments (≥115 per arm) by Month 13 (2027-11-13) but assumes a 30% dropout tolerance that is optimistic for adult voluntary pilots (typical range 35–45%). The cohort manager is not hired until Month 6 (2027-04-13), leaving 3 months of unmanaged pre-Phase-2 recruitment. If dropout reaches 35–45%, effective completers drop to 63–75 per arm (6–21% below the 80-per-arm minimum), reducing statistical power from 80% to ~60% and raising Type II error risk (false-negative gate) to 40%. This directly invalidates the gate evidence and may force a 3–6 month Phase 2 extension costing $300K–$600K, consuming the entire pre-gate reserve.

  3. Post-Month-36 stewardship is unfunded and no steward organization is committed. Annual stewardship costs are $150K–$250K (estimate), totaling $1.5M–$2.5M over 10 years, but no funding source or named steward exists. The plan defers steward identification to Month 12 (2027-10-13) and stewardship negotiation to Months 24–33 (2028-10-13 to 2029-07-13), risking that v1.0 is released at Month 30 (2029-04-13) without a committed steward in place. Without funded post-v1.0 governance, the standard will atrophy within 12–24 months (by Month 48–60 = 2030-10-13 to 2031-10-13), eroding adopter confidence and reducing Phase 3 adoption by 30–50%. This cascades from poor early steward engagement and no pre-committed organizational home for the standard's future maintenance.

Review 2: Implementation Consequences

  1. Successful pre-registration and defensible go/no-go gate (Month 24 = 2028-10-13) deliver evidence-based credibility worth $1.2M–$1.4M in retained Phase 3 adoption value. If gate metrics are pre-registered by Month 11 (2027-09-13) with empirically justified thresholds and a psychometrician-led validity study (N=20–30, Months 10–11 = 2027-08-13 to 2027-09-13), the Month 24 (2028-10-13) go/no-go decision is defensible and accepted by educators, standards bodies and publishers. This credibility preserves Phase 3 funding ($0.85M nominal, up to $1.2M if reserve is released post-GO) and enables ≥3 third-party adopters by Month 36 (2029-10-13), avoiding the 20–50% adoption-loss risk flagged if thresholds are disputed. Conversely, delayed or weak pre-registration invites post-hoc stakeholder challenges, reducing Phase 3 adoption by 20–30% and stranding up to $300K–$400K of the $0.85M Phase 3 budget as undeployable.

  2. Dropout >30% against the 460-enrollment target cascade to force a 3–6 month Phase 2 extension costing $300K–$600K, consuming the entire $350K reserve and creating a budget shortfall of $35K–$250K. If recruitment and retention targets are missed (baseline dropout is 35–45% for voluntary adult pilots, not the planned 30%), effective completers drop to 253–299 across 4 arms (63–75 per arm), reducing statistical power from 80% to ~60% and raising false-negative gate risk from 20% to 40%. Invalid or inconclusive data forces a board-decided Phase 2 extension (3–6 months, Months 24–30 = 2028-10-13 to 2029-04-13, cost $300K–$600K estimate); valid data with a failing metric is a NO-GO, returning up to $1.2M (less draws and wind-down) to funders. This shortfall directly violates the fixed $3.5M budget constraint and cascades through stewardship planning (no v1.0 release by Month 30 = 2029-04-13 triggers steward-commitment uncertainty).

  3. Unfunded post-Month-36 stewardship ($150K–$250K/year, estimate) causes standard atrophy within 12–24 months (by Month 48–60 = 2030-10-13 to 2031-10-13), reducing Phase 3 adoption gains by 30–50% and negating the $0.85M–$1.2M Phase 3 investment. If a steward organization with committed funding is not identified by Month 18 (2028-04-13) and an MoU is not signed by Month 30 (2029-04-13), v1.0 is released at Month 30 (2029-04-13) without a maintenance plan. Within 12–24 months, unanswered change requests, missing errata, and perceived abandonment erode adopter confidence; Phase 3 adopters withdraw or cease marketing by Month 48–60 (2030-10-13 to 2031-10-13), reducing the planned ≥3 adopters to 1–2 and capping learner reach at 10,000–20,000 (vs. the unvalidated 10,000–50,000 estimate). This interaction with Phase 2 extension risk (Consequence 2) is critical: if Phase 2 extends 6 months, steward negotiation slips to Months 30–33 (2029-04-13 to 2029-07-13), leaving minimal time to secure commitment before v1.0 release.

Review 3: Recommended Actions

  1. Hire independent psychometrician by Month 2 (2026-12-13) and commission power analysis by Month 5 (2027-03-13); reduces gate-credibility risk by $300K–$400K in Phase 3 adoption value. Securing a signed psychometrician contract immediately (not deferred) enables a draft pre-analysis plan by Month 5 (2027-03-13)—26 weeks before Month 11 (2027-09-13) pre-registration deadline. This front-loaded schedule provides buffer time: if validity findings require sample-size adjustment (e.g., 80 per arm is underpowered), the board can revise thresholds by Month 10 (2027-08-13) without compressing Phase 2 start. Priority: Critical. Implementation: Issue RFP for psychometrician by Month 0.5 (2026-10-28); secure signed contract specifying power-analysis deliverables by Month 1.5 (2026-11-28); hold kickoff meeting Month 2 (2026-12-13).

  2. Conduct 2–3 site recruitment baseline study (Months 1–2 = 2026-11-13 to 2026-12-13) with N=20–30 learners; reduces enrollment-shortfall risk by validating dropout assumptions and saving $300K–$600K in Phase 2 extension costs. A small pilot recruitment and retention test (budget $15K–$20K, estimate) at 1–2 candidate ESL programs and 1 technical-training site generates realistic dropout-rate data (typical 35–45% for adult voluntary pilots, vs. the planned 30%) and recruitment-conversion rates. Using empirical baseline data to model 75th percentile dropout (not 30%) enables the board to set realistic enrollment targets (about 492–582 enrolments, 123–146 per arm, if dropout is 35–45%, rather than 460, unless a power analysis justifies fewer completers) and activate contingency incentives ($20K–$30K, estimate) early if enrollment tracking lags. Priority: Critical. Implementation: Identify 2–3 pilot sites by Month 1 (2026-11-13); enroll 20–30 learners and run 2 assessment sessions Months 1–2 (2026-11-13 to 2026-12-13); analyze dropout and retention patterns by Month 3 (2027-01-13); finalize revised Phase 2 recruitment plan by Month 3 (2027-01-13).

  3. Begin steward identification by Month 12 (2027-10-13) and secure non-binding letters of interest by Month 24 (2028-10-13); reduces post-v1.0 atrophy risk by $1.5M–$2.5M over 10 years. Early steward search (not deferred to Month 18 = 2028-04-13) ensures a written stewardship commitment is in hand before v1.0 release at Month 30 (2029-04-13), eliminating the unfunded-stewardship gap that causes standard decay by Month 48–60 (2030-10-13 to 2031-10-13). Identifying stewards alongside the Phase 2 go/no-go decision (Month 24 = 2028-10-13) ensures adequate negotiation time (6–9 months) to finalize an MoU by Month 30 (2029-04-13) before release; Month 33 (2029-07-13) is only the latest point at which a delayed release can still be triggered. Priority: High. Implementation: Identify steward candidates by Month 12 (2027-10-13); approach top 2–3 by Month 18 (2028-04-13) with capability assessment; solicit letters of interest by Month 24 (2028-10-13); negotiate MOU Months 27–30 (2029-01-13 to 2029-04-13).

Review 4: Showstopper Risks

  1. Regulatory approval delays (4–8 month timelines) compress Phase 2 pilots and invalidate gate evidence; Likelihood: Medium; impact $300K–$600K extension cost or false-negative gate. The plan assumes a 'glossary and labeling' scope avoids formal regulatory review, but Ofqual (UK), OSHA (US), and state education authorities may require compliance submissions before safety-critical pilots launch at Month 13 (2027-11-13). A 4–8 month approval window (documented risk 2 forecast) pushes pilot start to Month 17–21 (2028-03-13 to 2028-07-13), compressing the 12-month pilot window to 8 months or fewer and reducing 30-day follow-up completion from Month 22 (2028-08-13) to Month 18–20 (2028-04-13 to 2028-06-13), cutting effective assessment time by 20–40%. Mitigation: Pre-negotiate 'research study' classification with ethics committees and regulators by Month 4 (2027-02-13) and secure written advisory input confirming glossary/labeling scope by Month 8 (2027-06-13). Contingency: If approval is required and takes >6 months, defer safety-critical cohort to a post-Month-24 (2028-10-13) Phase 2.5 extension ($150K–$300K, estimate), funded from Phase 3 reserve, protecting the main ESL pilot window.

  2. Audio production cost overrun (per-entry cost exceeds $20 budget; total $120K–$150K+) or inter-rater kappa failure (<0.70) at Month 10 (2027-08-13) triggers a 4-week Phase 1 extension ($85K) that exhausts the pre-gate $175K draw cap, leaving zero contingency for downstream psychometric rework or recruitment activation. Likelihood: Medium; impact $85K–$175K pre-gate draw, stranding only $90K headroom for unforeseen Phase 1 costs. Audio production is on critical path (Months 6–11 = 2027-04-13 to 2027-09-13); if studio cost-per-entry exceeds $20 (estimate), hybrid approach (synthetic baseline + verification, Months 7–11 = 2027-05-13 to 2027-09-13) adds 2–4 weeks. If raters fail to achieve kappa ≥0.70 by Month 10 (2027-08-13) and retraining is required, Phase 1 extends automatically 4 weeks (~$85K, estimate), consuming half the pre-gate reserve and leaving $90K for any other gate-protection draw (psychometric re-validation, recruitment contingency). Mitigation: Lock studio pricing and confirm per-entry cost ≤$20 by Month 4 (2027-02-13); pre-screen raters by Month 4 (2027-02-13) and conduct micro-calibration by Month 6 (2027-04-13) to detect kappa risk early. Contingency: If kappa <0.70 is confirmed at Month 9 (2027-07-13) dry run, activate hybrid model immediately (synthetic + verification) and reallocate the 4-week extension budget to rater retraining compression (2 weeks, $42.5K, estimate), reducing Phase 1 impact to $42.5K and preserving $132.5K pre-gate headroom.

  3. Pilot cohort manager not hired until Month 6 (2027-04-13), but enrollment must reach ≥115 per arm by Month 13 (2027-11-13), leaving only 7 months of managed recruitment when baseline pilot data (Months 1–2 = 2026-11-13 to 2026-12-13) shows adult voluntary dropout is 35–45% (not the assumed 30%); effective completers drop to 63–75 per arm, invalidating statistical power and forcing a 3–6 month Phase 2 extension ($300K–$600K). Likelihood: High; impact $300K–$600K cost overrun or false-negative gate outcome. If baseline study confirms 40% attrition, 460 enrollments yield only 276 completers across 4 arms (69 per arm, below the 80-per-arm minimum)—reducing power from 80% to ~60%, raising Type II error (false-negative) to 50%. This cascades to stewardship planning: invalid data triggers a board-decided extension that can push v1.0 from Month 30 (2029-04-13) to Month 33–36 (2029-07-13 to 2029-10-13) or later, eliminating steward-negotiation time; a valid failing metric is a NO-GO returning up to $1.2M less draws and wind-down. Mitigation: Conduct baseline recruitment pilot (Months 1–2 = 2026-11-13 to 2026-12-13, $15K–$20K, estimate) to validate 35–45% dropout assumption; hire cohort manager by Month 4 (2027-02-13) (not Month 6 = 2027-04-13) with 30% pre-Phase-2 capacity (Months 4–12 = 2027-02-13 to 2027-10-13) for recruitment design and contingency planning. Contingency: If the enrollment audit at Month 12 (2027-10-13) shows forecast completers below 320 or enrolment below the power-analysis target, immediately activate recruitment acceleration (increased incentives $20K–$30K, weekend sessions, partner co-marketing) and review the sample-size target against a power analysis, adjusting gate-threshold sensitivity analyses at Month 11 (2027-09-13) pre-registration to match realistic power assumptions.

Review 5: Critical Assumptions

  1. Assumption: Adult voluntary ESL and technical-training learners will enrol at >=115 per arm and achieve <=30% dropout across 12-month pilots. If actual dropout is 35–45% (documented baseline from adult education literature), effective completers drop to 63–75 per arm (6–21% below the 80-per-arm minimum), reducing statistical power from 80% to 50–65% and inflating Type II error (false-negative gate risk) to 35–50%. A false-negative outcome cascades to: (1) invalid data triggers a board-decided extension, while a valid failing metric is a NO-GO returning up to $1.2M less draws and wind-down; (2) Phase 2 extension ($300K–$600K) consumes the entire $350K reserve and creates a $35K–$250K shortfall; (3) stewardship negotiation slips to Months 30–33 (2029-04-13 to 2029-07-13), leaving zero time to secure commitment before potential v1.0 delay. Validate: Conduct recruitment baseline study (Months 1–2 = 2026-11-13 to 2026-12-13) with N=20–30 learners; document actual weekly dropout and demographic retention patterns; revise enrollment targets to about 492–582 (75th percentile dropout assumption, $15K–$20K, estimate) by Month 3 (2027-01-13).

  2. Assumption: Pronunciation-consistency inter-rater reliability (Cohen's kappa) will reach >=0.70 by Month 10 (2027-08-13) after 2–3 rater-training sessions. If raters fail to achieve kappa >=0.70 (no published benchmark exists for constructed-language contexts), the pronunciation-consistency gate metric becomes uninterpretable, forcing either a 4-week Phase 1 extension ($85K, consuming half the pre-gate $175K draw cap) or metric downgrade to secondary status, weakening gate evidence by 15–20%. This compounds with recruitment shortfall (Assumption 1): if both recruitment and kappa fail, Phase 1 exhausts contingency ($85K + recruitment acceleration $20K–$30K = $105K–$115K), eliminating headroom for psychometric rework ($50K–$100K if instrument redesign is needed), forcing either Phase 1 extension by 8–12 weeks ($170K–$255K, estimate, exceeding the $175K cap) or a compromised gate decision. Validate: Pre-screen rater candidates by Month 4 (2027-02-13) using a 50-word calibration sample (kappa >=0.75 threshold); conduct micro-calibration on 100–200 words by Month 6 (2027-04-13); confirm kappa >=0.70 by Month 10 (2027-08-13) dry run; if kappa <0.70, activate 2–4 week retraining by Month 11 (2027-09-13), or pivot to hybrid synthetic-plus-verification model.

  3. Assumption: A permanent steward organization with committed $150K–$250K annual funding will be available and willing to sign a Memorandum of Understanding by Month 30 (2029-04-13) to assume post-v1.0 governance. If no steward commitment is obtained by Month 30 (2029-04-13), v1.0 release at Month 30 (2029-04-13) occurs without funded maintenance, and the standard atrophies within 12–24 months (by Month 48–60 = 2030-10-13 to 2031-10-13). Phase 3 adopters withdraw or cease marketing by Month 48–60 (2030-10-13 to 2031-10-13), reducing adoption from the >=3 target to 1–2, capping learner reach at 10,000–20,000 (vs. the unvalidated 10,000–50,000 estimate), and negating the $0.85M–$1.2M Phase 3 investment (net loss of $600K–$1M in adoption value, estimate). This compounds with Phase 2 extension risk: if Phase 2 extends 6 months, steward negotiations slip to Months 30–33 (2029-04-13 to 2029-07-13), leaving minimal time before release. Validate: Identify 2–3 steward candidates by Month 12 (2027-10-13); approach top 2 by Month 18 (2028-04-13) with formal capability review; solicit letters of interest by Month 24 (2028-10-13); begin MOU negotiation by Month 27 (2029-01-13); secure signed MOU by Month 30 (2029-04-13) (before release) or delay v1.0 to Month 36 (2029-10-13) or later.

Review 6: Key Performance Indicators

  1. KPI 1: Pilot Statistical Power and Gate Evidence Quality — Target: ≥80 completers per arm (320 total) achieved by Month 22 (2028-08-13) with all four pre-registered metrics meeting thresholds at Month 24 (2028-10-13). Success metric: ordinal error reduction ≥25% (proposed threshold), comprehension speed ≤10% slower (proposed threshold), pronunciation consistency ≥15% above control with statistically significant difference (proposed threshold; kappa ≥0.70 floor, target 0.75, as a separate validity condition), 30-day retention ≥70% of post-test and not below control (proposed threshold). If sample size falls below 80 per arm (power drops to ~60%), or any metric fails (valid data with any failure is NO-GO; invalid data leads to a board-decided extension), underpowered (invalid) data forces a 3–6 month Phase 2 extension ($300K–$600K estimate), consuming the entire $350K reserve. This KPI directly reflects the recruitment-and-retention assumption (Assumption 1): if baseline dropout is 35–45% (vs. planned 30%), enrolment must reach about 492–582 (123–146 per arm) to yield 80 completers. Monitor: monthly enrollment dashboard (target 115 per arm by Month 13 = 2027-11-13) and dropout-by-session tracking; flag if lower confidence bound on final completers falls below 70 per arm at Month 18 (2028-04-13).

  2. KPI 2: Pre-Registration Credibility and Stakeholder Confidence — Target: Pre-analysis plan registered on Open Science Framework by Month 11 (2027-09-13) with independent psychometrician sign-off and published numeric thresholds; zero post-hoc threshold adjustments at Month 24 (2028-10-13) go/no-go decision. Success metric: thresholds justified by power analysis (≥80% power confirmed for 80 per arm), no board vote to lower/raise thresholds after pre-registration. If pre-registration is incomplete, delayed (Month 12 = 2027-10-13 or later), or thresholds are adjusted post-hoc, stakeholder trust declines by 20–30% (educators, standards bodies, publishers claim gatekeeping), reducing Phase 3 adoption by 20–50% and stranding up to $300K–$400K of the $0.85M–$1.2M Phase 3 budget. This KPI reinforces the pre-registration assumption (Assumption 2): early psychometrician engagement (Month 2 = 2026-12-13) and validity study (Months 10–11 = 2027-08-13 to 2027-09-13) are essential. Monitor: track psychometrician contract signature (by Month 2 = 2026-12-13), power-analysis draft (Month 5 = 2027-03-13), and OSF pre-registration (Month 11 = 2027-09-13); escalate if any milestone slips >2 weeks.

  3. KPI 3: Post-v1.0 Stewardship Funding Secured — Target: Signed Memorandum of Understanding with at least one steward organization by Month 30 (2029-04-13) committing ≥$150K–$250K annually for 10+ years, signed by Month 30 (2029-04-13) as the condition for v1.0 release (Month 33 = 2029-07-13 is only the latest point at which a delayed release can still be triggered). Success metric: named steward with 3+ years audited financials, mission alignment, and written governance commitment; zero unfunded stewardship at Month 36 (2029-10-13). If no steward commitment is in hand by Month 30 (2029-04-13), v1.0 would be released without maintenance capacity, and the standard atrophies within 12–24 months (by Month 48–60 = 2030-10-13 to 2031-10-13), reducing Phase 3 adopters from ≥3 target to 1–2, capping learner reach at 10,000–20,000, and negating the $0.85M–$1.2M Phase 3 investment ($600K–$1M net loss in adoption value, estimate). This KPI directly reflects the stewardship assumption (Assumption 3) and compounds with Phase 2 extension risk: if Phase 2 extends 6 months, steward negotiations slip to Months 30–33 (2029-04-13 to 2029-07-13), eliminating negotiation buffer. Monitor: identify steward candidates by Month 12 (2027-10-13), approach top 2 by Month 18 (2028-04-13), collect letters of interest by Month 24 (2028-10-13), and track MOU negotiation progress monthly Months 27–33 (2029-01-13 to 2029-07-13); if signed MOU is not in hand by Month 30 (2029-04-13), defer v1.0 release to Month 36 (2029-10-13) or later.

Review 7: Report Objectives

  1. Primary Objective: Provide a comprehensive, evidence-based strategic and operational review of a 36-month, $3.5M language-standardization initiative (Clear English Standard v1.0) designed to validate pilot efficacy through pre-registered metrics and inform a defensible Month 24 (2028-10-13) go/no-go gate decision. The report identifies five critical levers (ordinal architecture, G2P depth, adoption wedge, metrics design, budget weighting) and thirteen secondary decisions; documents 20 tracked risks with quantified impact (e.g., recruitment shortfall reduces sample size by 30–40%, forcing a $300K–$600K Phase 2 extension); and recommends immediate, time-bound actions (hire psychometrician by Month 2 = 2026-12-13, conduct baseline recruitment study Months 1–2 = 2026-11-13 to 2026-12-13, secure pilot partner commitments by Month 3 = 2027-01-13).

  2. Intended Audience and Key Decisions: This report is written for the editorial board, project leadership, and funders/stakeholders deciding whether to proceed with the planned three-phase delivery ($1.1M Phase 1, $1.2M Phase 2, $0.85M Phase 3 + $0.35M reserve). It informs: (1) go/no-go authority on rule-specification rigor (Decision 1–5 levers); (2) pilot design adequacy (sample size ≥80 per arm, ≤30% dropout assumption, four pre-registered metrics with thresholds ordinal error ≥25%, comprehension ≤10% slower, pronunciation consistency ≥15% above control and statistically significant with kappa ≥0.70 as a separate validity condition, 30-day retention ≥70% of post-test and not below control); (3) governance legitimacy (editorial board charter, tiebreak arbiter, licensing model by Month 6 = 2027-04-13); (4) post-v1.0 sustainability risk (stewardship $150K–$250K/year unfunded, signed commitment required by Month 30 = 2029-04-13; Month 33 = 2029-07-13 is only the latest point at which a delayed release can still be triggered).

  3. Version 2 Differentiation: This report (Version 1) is a post-hoc expert review synthesizing eight input documents; Version 2 should be a living project-management and risk-governance artifact updated monthly at Months 3, 6, 9, 12 (2027-01-13, 2027-04-13, 2027-07-13, 2027-10-13) and quarterly thereafter (Months 15, 18, 21, 24 = 2028-01-13, 2028-04-13, 2028-07-13, 2028-10-13). Version 2 must add: (1) earned-value tracking dashboard (budget variance alerts if >10% over in any line item); (2) critical-path schedule with 2-week slip escalation triggers; (3) monthly enrollment and dropout monitoring dashboard feeding sample-size adequacy forecasts; (4) pre-analysis plan registration evidence (OSF link, board sign-off) by Month 11 (2027-09-13); (5) steward-organization pipeline status (candidate names, letters of interest collected by Month 24 = 2028-10-13, MOU signed by Month 30 = 2029-04-13). Version 2 should consolidate decision logs, risk register updates, and KPI tracking into a single executive briefing for monthly board review.

Review 8: Data Quality Concerns

  1. Power-Analysis Effect-Size Assumptions Lack External Validation. The four gate-metric thresholds (ordinal error ≥25% reduction, comprehension ≤10% slower, pronunciation consistency ≥15% above control, 30-day retention ≥70%) are proposed values without published benchmarks from analogous ESL or constructed-language interventions. If actual effect sizes are smaller (e.g., ordinal error 15–20% reduction, not 25%), the power analysis concludes that 80 completers per arm is underpowered (actual power ~60%, not 80%), forcing either a 3–6 month Phase 2 extension ($300K–$600K, consuming the entire $350K reserve) or a downward threshold adjustment post-hoc (inviting stakeholder claims of goalpost-moving). Recommendation: Commission the psychometrician by Month 2 (2026-12-13) to conduct a targeted literature review by Month 4 (2027-02-13) identifying effect-size benchmarks from adult ESL literacy interventions, speech-therapy studies, and morphology-regularization research; adjust proposed thresholds or sample-size targets by Month 5 (2027-03-13) before the validity study begins.

  2. Pilot Dropout Assumptions (≤30%) Are Not Grounded in Baseline Data. The enrollment and retention plan assumes ≤30% attrition across 12-month in-person assessments, but adult-education literature documents 35–45% typical dropout for voluntary programs. If baseline recruitment study (Months 1–2 = 2026-11-13 to 2026-12-13) confirms 35–45% dropout, the plan's 460-enrollment target yields only 253–299 completers (vs. the 320-minimum goal = 80 per arm × 4 arms), reducing per-arm completers to 63–75 and power to ~50–65%, invalidating the gate. Recommendation: Execute the baseline recruitment study immediately (Months 1–2 = 2026-11-13 to 2026-12-13) with 20–30 learners across 2–3 candidate ESL/technical sites; document weekly dropout and demographic retention patterns by reason; by Month 3 (2027-01-13), revise enrollment targets to about 492–582 (or justify fewer completers by power analysis) and activate contingency incentive budget ($20K–$30K, estimate) if dropout tracking exceeds 25% by Month 10 (2027-08-13).

  3. Inter-Rater Kappa ≥0.70 Achievability Unvalidated in Constructed-Language Context. No published benchmark exists for pronunciation-consistency scoring in a novel ordinal-marker or prefix-governed system. If raters struggle with the reference-accent anchor definition or the ordinal marker's spoken form (not finalized until Month 10 = 2027-08-13), kappa may fall to 0.60–0.65 at the Month 10 (2027-08-13) dry run, triggering a mandatory 4-week Phase 1 extension ($85K estimate) that consumes half the pre-gate $175K draw cap, leaving only $90K for any other gate-protection contingency. Recommendation: Pre-screen 6–8 rater candidates using a 50-word calibration sample by Month 4 (2027-02-13), selecting the top 3–4 (kappa ≥0.75 on pilot); conduct a 100–200 word inter-rater micro-calibration by Month 6 (2027-04-13); if kappa is 0.65–0.70, immediately implement targeted retraining and schedule a retest by Month 9 (2027-07-13); if kappa remains <0.70, activate the hybrid synthetic-baseline-plus-verification model by Month 7 (2027-05-13) to avoid Phase 1 extension.

Review 9: Stakeholder Feedback

  1. Editorial Board and Practitioner Buy-In on Rule Compromises (Ordinal Marker Spoken Form, Morphology Retention Threshold, Homograph Marker Scope). The project locks five core rule decisions by Month 12 (2027-10-13), but the ordinal marker's spoken form (not finalized until Month 10 = 2027-08-13), the morphology retention cutoff (all forms <=1,000-word frequency retained vs. regularizing lower-frequency irregulars), and the homograph-marker scope (mandatory in safety-critical only vs. optional everywhere) remain contentious between linguist purists and practitioner-usability advocates. If the board cannot reach consensus or if educators and publishers reject the chosen rules as linguistically weak or pedagogically burdensome, pilot fidelity degrades (teachers misapply rules, learners receive inconsistent instruction), measurement error inflates by 10–20%, and gate metrics become inconclusive or biased, increasing the risk of a disputed or false-negative NO-GO outcome by 15–25%. Recommendation: By Month 5 (2027-03-13), conduct a small stakeholder advisory panel (5–8 teachers, 2–3 publishers, 2 linguists) to co-review draft rule rationales and surface objections early; document consensus or minority positions; use findings to finalize rules by Month 10 (2027-08-13), allowing 2-month buffer before the Month 12 (2027-10-13) freeze.

  2. Quantified Baseline Evidence for Dropout, Recruitment, and Audio-Production Cost Assumptions. The plan assumes ≤30% dropout, >=115 enrollments per arm by Month 13 (2027-11-13), and $20 per entry audio cost, but no baseline data exists yet. If the baseline recruitment study (Months 1–2 = 2026-11-13 to 2026-12-13, $15K–$20K estimate) reveals 35–45% dropout (typical for adult voluntary programs), effective sample drops to 63–75 per arm (6–21% below the 80-per-arm minimum), reducing statistical power from 80% to 50–65% and forcing a 3–6 month Phase 2 extension ($300K–$600K, consuming the entire $350K reserve). Similarly, if audio costs exceed $20 per entry, the pivot to hybrid synthetic-baseline-plus-verification by Month 7 (2027-05-13) compresses rater training and risks kappa <0.70, triggering the 4-week Phase 1 extension ($85K) fallback. Recommendation: By Month 2 (2026-12-13), board and project lead must explicitly approve the baseline-study scope (N=20–30, 2–3 sites, two assessment sessions Months 1–2 = 2026-11-13 to 2026-12-13) and commit to revising enrollment/dropout targets by Month 3 (2027-01-13) based on observed data, rather than proceeding with optimistic assumptions.

  3. Steward-Organization Identification and Financial Commitment Timeline Clarity. The report flags that stewardship is $150K–$250K per year (estimate), unfunded post-Month 36 (2029-10-13), and that no steward is yet identified. Stakeholders (funders, board, potential adopters) need written clarity on: (1) whether v1.0 release at Month 30 (2029-04-13) is conditional on a signed stewardship MOU in hand, or whether release proceeds and stewardship is sought afterward; (2) which organization types are viable stewards (university consortium, language non-profit, standards body) and what their minimum financial/governance criteria are; (3) the timeline for steward search (identify candidates by Month 12 = 2027-10-13? Month 18 = 2028-04-13? Month 24 = 2028-10-13?), to avoid the risk that v1.0 is released without committed post-launch funding and atrophies within 12–24 months (by Month 48–60 = 2030-10-13 to 2031-10-13), reducing adoption from the >=3 target to 1–2 and negating $600K–$1M in Phase 3 adoption value (estimate). Recommendation: By Month 1 (2026-11-13), editorial board must publish a written Stewardship Policy specifying: v1.0 release is conditional on signed stewardship MOU; steward search begins Month 12 (2027-10-13); board approaches top 2–3 candidates Months 18–24 (2028-04-13 to 2028-10-13) and negotiates MOU by Month 30 (2029-04-13) (before release) or delays release to Month 36 (2029-10-13).

Review 10: Changed Assumptions

  1. ESL Learner Motivation and Engagement in Voluntary Pilots May Have Declined Post-Pandemic. The baseline assumption assumes ≤30% dropout for adult ESL learners in 12-month pilot commitment (Months 13-24 = 2027-11-13 to 2028-10-13), based on pre-2020 adult-education norms. Post-pandemic shifts in learner availability, work-schedule volatility, and reduced institutional classroom capacity may elevate dropout to 35–50% (documented in adult education literature 2022-2025, not cited in current plan). If baseline dropout study (Months 1-2 = 2026-11-13 to 2026-12-13) confirms 40% attrition instead of 30%, effective completers drop to 276 across 4 arms (69 per arm, 13–14% below 80-per-arm minimum), reducing statistical power to 70% (from 80% target) and increasing Type II error risk to 30%. Re-evaluation Action: Conduct baseline study immediately (Months 1-2 = 2026-11-13 to 2026-12-13) with explicit documentation of enrollment and session-attendance barriers; revise dropout contingency incentive budget from $20K–$30K to $40K–$60K (estimate) if baseline confirms >35% attrition by Month 3 (2027-01-13).

  2. Publisher and Standards-Body Appetite for Optional (Non-Mandatory) English Variants Has Shifted Toward Consolidation Risk. The adoption-wedge assumption assumes ESL publishers and technical-writing organizations will adopt Clear English as a supplementary module with non-binding interest letters by Month 3 (2027-01-13). However, consolidation in educational publishing (fewer, larger vendors) and increased regulatory scrutiny of 'non-standard English' may have reduced willingness to invest development time in a variant with no mandated adoption pathway. If publisher interest letters drop below the non-binding target of ≥3 by Month 3 (2027-01-13), or if published feedback signals low commercial viability, Phase 3 adoption projections (≥3 adopters, 10,000–50,000 learner reach, estimate) may be unachievable, stranding $0.85M–$1.2M Phase 3 budget (if reserve is released post-GO). Re-evaluation Action: By Month 2 (2026-12-13), conduct confidential interviews with 5–8 publishers and 3–4 technical-writing organizations to re-assess appetite for v1.0 adoption; if interest signals are lukewarm, escalate to the board by Month 3 (2027-01-13) and reframe Phase 3 as a 'credibility and proof-of-concept' phase (fewer adopters, longer time-to-impact) rather than immediate commercialization.

  3. Regulatory Landscape and Approval Timelines for Safety-Critical Pilots May Have Tightened Post-2023 Due to AI and Automated-Text Governance Changes. The safety-critical assumption assumes a 'glossary and labeling' scope avoids formal regulatory approval and requires only legal disclaimers (Month 4 = 2027-02-13 liability strategy). However, regulatory bodies (OSHA, HSE, FDA where medical context arises) have expanded scrutiny of AI-generated or algorithmically-derived written guidance in safety-critical settings since 2023. If regulator feedback (solicited by Month 8 = 2027-06-13) indicates that pronunciation-overlay or ordinal-marker systems require pre-use approval or formal safety-case review, approval timelines may extend to 6–12 months, compressing Phase 2 pilots from 12 to 6–8 months and reducing assessment window by 33–50%, lowering data quality and statistical power. Re-evaluation Action: By Month 3 (2027-01-13), initiate informal regulatory pre-engagement with OSHA, HSE, or relevant safety bodies in pilot jurisdictions; obtain written advisory feedback on the 'glossary and labeling' scope and any emerging approval requirements by Month 6 (2027-04-13); if approval timelines exceed 4 months, plan a post-Month-24 (2028-10-13) Phase 2.5 safety-critical extension ($150K–$300K, estimate) funded from Phase 3 reserve, protecting the main ESL pilot window from compression.

Review 11: Budget Clarifications

  1. Phase 2 Participant Cost Clarity: Incentive Structure and Partner Payment Terms Undefined. Budget estimate for incentives is $23K–$69K (460 learners × $50–$150 stipend range) and partner payments $55K–$92K (460 × 4 sessions × $30–$50 per session), totaling $78K–$161K (estimate). However, the specific incentive amount ($50, $75, $100, or $150?), payment timing (per-session vs. lump-sum post-completion), and partner cost-share or match requirements are not locked. If incentive levels prove insufficient and dropout reaches 35–40% (vs. the planned 30%), activation of contingency recruitment acceleration ($20K–$30K, estimate) could push participant costs to $98K–$191K, consuming 8.2–15.9% of the $1.2M Phase 2 budget and forcing either budget overrun or a reduction in the number of assessment sessions. Resolution: By Month 1 (2026-11-13), finalize and publish the incentive-structure decision (specify $ amount, payment schedule, partner match); obtain firm partner cost quotes by Month 3 (2027-01-13); if contingency activation is likely (baseline dropout >30%), increase Phase 2 participant budget to $250K–$300K (estimate) by Month 4 (2027-02-13).

  2. Psychometrics and Assessment Instrument Validation Budget ($150K–$200K) May Be Underestimated If Validity Study or Rater Training Requires Redesign. Current allocation assumes a single validity study (N=20–30, Months 10–11 = 2027-08-13 to 2027-09-13) and inter-rater calibration on a 100–200 word sample are sufficient to finalize thresholds by Month 11 (2027-09-13). However, if the validity study reveals low effect sizes or instrument ambiguity, redesign and re-piloting could cost an additional $30K–$50K (estimate). If inter-rater kappa falls to 0.65–0.70 at Month 10 (2027-08-13) and targeted retraining is needed Months 10–11 (2027-08-13 to 2027-09-13), rater costs could overrun by $20K–$40K (estimate), totaling $170K–$240K vs. the budgeted $150K–$200K. A $40K–$50K overrun (2.7–3.5% of Phase 1 budget estimate) would consume 23–29% of the pre-gate $175K draw cap and leave only $125K–$152K for recruitment or other gate-protection contingencies. Resolution: By Month 2 (2026-12-13), obtain a detailed vendor quote from the hired psychometrician including contingency costs for instrument redesign (estimate $30K–$50K) and rater-retraining acceleration (estimate $20K–$40K); establish a $50K psychometrics contingency sub-reserve within the pre-gate $175K cap by Month 3 (2027-01-13).

  3. Audio Production Cost-Per-Entry Threshold ($20 per entry, $100K total) Not Validated; Hybrid Pivot to Synthetic Baseline May Add Hidden Costs. Current budget is $80K–$120K for 5,000-word single-accent recording (Months 6–11 = 2027-04-13 to 2027-09-13). If cost-per-entry exceeds $20 (estimate), the plan pivots to speech-synthesis baseline for all 5,000 entries plus human verification of 1,000–1,500 highest-friction words (estimated $50K–$60K for TTS, $12K–$20K for verification = $62K–$80K total, estimate). However, this hybrid pivot incurs additional rater-training and quality-assurance costs ($10K–$20K, estimate) not explicitly budgeted, and may compress the Phase 1 timeline by 2–4 weeks if rater retraining overlaps with TTS production. A $20K–$40K overrun would consume 11–23% of the pre-gate $175K cap and force either a Phase 1 extension ($85K fallback, totaling $105K–$125K draw, leaving $50K–$70K headroom) or deferral of recruitment-contingency funding. Resolution: By Month 3 (2027-01-13), obtain firm cost quotes from at least two audio studios and one TTS vendor with per-entry pricing; establish a $30K audio-production contingency sub-reserve within the pre-gate $175K cap and a go/no-go decision point at Month 4 (2027-02-13) on whether to lock human production or activate the hybrid model.

Review 12: Role Definitions

  1. Budget Owner and Financial Accountability. Currently, no single named role holds authority over the $3.5M total budget, monthly spend tracking, or variance escalation decisions. If budget authority is diffused across the project lead, phase leads, and board members, cost overruns (estimated $300K–$600K risk scenarios) are discovered too late for corrective action, forcing either mid-phase scope cuts or unauthorized reserve draws that exceed the $175K pre-gate cap by $125K+ (estimate). Resolution: By Month 1 (2026-11-13), formally appoint a single Budget Owner (0.5 FTE) accountable for monthly earned-value analysis, rolling forecasts, and immediate escalation if any line item exceeds budget by >10% ($33K at Month 2 = 2026-12-13); establish clear reserve-draw authorization procedures requiring written justification within 5 days.

  2. Phase 2 Cohort Manager and Retention Accountability. The plan hires this role at Month 6 (2027-04-13), but enrollment begins Month 12 (2027-10-13)—a 6-month gap during which recruitment design, contingency planning, and retention protocols are unowned. If recruitment lags or dropout exceeds 30%, effective completers drop to 63–75 per arm (6–21% below 80-per-arm minimum), reducing power to 50–65% and forcing a $300K–$600K Phase 2 extension (estimate). Resolution: By Month 3 (2027-01-13), assign a temporary 0.5 FTE Recruitment Coordinator to draft partner agreements, incentive structures, and dropout-response playbooks; transition to the 1.0 FTE Cohort Manager at Month 6 (2027-04-13) with explicit retention KPIs (≤30% monthly dropout, ≥115 per arm enrolled by Month 13 = 2027-11-13) and a $20K–$30K contingency-activation authority.

  3. Psychometrician and Pre-Analysis Plan Authority. No assigned role owns the delivery of the pre-analysis plan draft by Month 5 (2027-03-13) or the pre-registration by Month 11 (2027-09-13). If this deliverable slips or lacks rigor, the Month 24 (2028-10-13) gate becomes scientifically disputable, inviting stakeholder claims of goalpost-moving and reducing Phase 3 adoption by 20–30%, stranding up to $300K–$400K (estimate) of the $0.85M–$1.2M Phase 3 budget. Resolution: By Month 2 (2026-12-13), hire an independent Psychometrician with a signed statement of work specifying: power analysis by Month 5 (2027-03-13), validity study in Months 10–11 (2027-08-13 to 2027-09-13), and pre-analysis plan registration on Open Science Framework by Month 11 (2027-09-13); project lead is accountable for weekly milestone tracking and board escalation if the psychometrician misses deadlines >2 weeks.

Review 13: Timeline Dependencies

  1. Rules Lock and Pre-Analysis Plan Registration Sequencing (Month 10-11 = 2027-08-13 to 2027-09-13). Rules must freeze by Month 12 (2027-10-13) to enable stable pilot curriculum design, but the pre-analysis plan (thresholds, power analysis, decision rules) is not pre-registered until Month 11 (2027-09-13)—only 4 weeks before pilots begin at Month 13 (2027-11-13). If rule changes occur after Month 11 (2027-09-13) are discovered during pre-registration (e.g., ordinal marker spoken form ambiguity flagged by independent reviewer), redesign cascades into Phase 2 start delay of 2–4 weeks, compressing the pilot window from 12 to 11–10 months and reducing assessment sessions or follow-up completion. Impact: reduces statistical power by 10–15%, raising false-negative gate risk from 20% to 30–35%. Mitigation: finalize all rule disputes and arbiter rulings by Month 10 (2027-08-13 end); publish draft standard by Month 11 (2027-09-13 start) for comment window only, not rule revision.

  2. Audio Production and Inter-Rater Calibration Dependency (Months 6-10 = 2027-04-13 to 2027-08-13). Recording and rater calibration are on the critical path: studio must deliver 5,000 entries by Month 10 (2027-08-13 for the dry run; Month 11 = 2027-09-13 final). However, rater training and kappa measurement (target Month 10 = 2027-08-13) require the reference accent anchor and ordinal marker spoken form, both not finalized until Month 10 (2027-08-13). If accent or spoken form changes after rater training begins (Month 9 = 2027-07-13), all trained raters must retrain (2–4 weeks, $20K–$40K estimate), delaying kappa confirmation past Month 10 (2027-08-13) and triggering the 4-week Phase 1 extension ($85K, estimate) fallback. Impact: consumes 48% of the $175K pre-gate draw cap, leaving $90K headroom. Mitigation: lock accent and spoken form by Month 8 (2027-06-13) end (not Month 10 = 2027-08-13); begin rater training Month 8 (2027-06-13); confirm kappa >=0.70 by Month 9.5 (2027-07-28) to allow 1-week retraining buffer if needed.

  3. Pilot Enrollment Completion vs. Assessment Session Timing (Month 12-14 = 2027-10-13 to 2027-12-13). All 460 enrollments must be complete by Month 13 (2027-11-13) to begin 4 in-person assessment sessions across Months 13–22 (2027-11-13 to 2028-08-13). However, if recruitment lags and enrollments are still arriving at Month 14 (2027-12-13) or Month 15 (2028-01-13), late-enrolling learners cannot complete all 4 sessions before the Month 22 (2028-08-13) data-lock deadline (only 7–8 months available instead of 9 months), shortening follow-up to <30 days or requiring exclusion of late enrollees. Impact: effective completers drop by 10–20%, reducing per-arm sample from 80 to 64–72, lowering power to 65–70% and raising false-negative risk to 30–35%. Mitigation: establish hard enrollment cutoff at Month 13 (2027-11-13); begin Session 1 by Month 14 (2027-12-13 start) even if enrollment is at 85–90% of target; activate contingency recruitment (bonus incentives $20K–$30K, estimate) immediately if Month 12 (2027-10-13) enrollment audit shows forecast completers <320.

Review 14: Financial Strategy

  1. Post-v1.0 Stewardship Funding Model and Steward Identification Timeline Remain Open. Stewardship costs are $150K–$250K annually (estimate), totaling $1.5M–$2.5M over 10 years, but no funding source or named steward organization exists. If steward search begins at Month 12 (2027-10-13) and negotiations extend to Month 30 (2029-04-13) or beyond, v1.0 is released without committed post-launch governance. The standard atrophies within 12–24 months (by Month 48–60 = 2030-10-13 to 2031-10-13), and Phase 3 adoption declines from ≥3 target to 1–2 adopters, capping learner reach at 10,000–20,000 and negating $600K–$1M in Phase 3 value (estimate). Strategic question: Is v1.0 release conditional on a signed MOU in hand (Month 30 = 2029-04-13), or is stewardship sought post-release at higher risk? Action: By Month 1 (2026-11-13), board must publish a written Stewardship Commitment Policy specifying: v1.0 release contingent on signed MOU, steward search by Month 12 (2027-10-13), and MOU finalization by Month 30 (2029-04-13) or v1.0 delayed to Month 36 (2029-10-13).

  2. Phase 3 Adoption Value and ROI Measurement Unvalidated Against Spending. Phase 3 budget is $0.85M (nominal; up to $1.2M if reserve released post-GO), targeting ≥3 third-party adopters and an unvalidated estimate of 10,000–50,000 learner reach within 5 years. No cost-per-adopter target or cost-per-learner threshold is defined. If ≥3 adopters are not achieved (e.g., only 1–2 commit), Phase 3 ROI drops 33–67%, stranding $255K–$850K (estimate) of the $0.85M–$1.2M Phase 3 budget. Strategic question: What constitutes Phase 3 success? Is adoption of 1–2 high-impact organizations (e.g., major ESL publisher) equivalent to ≥3 smaller adopters? Should cost-per-learner-reached or cost-per-adopter metrics govern Phase 3 spending decisions? Action: By Month 6 (2027-04-13), board must define Phase 3 ROI thresholds: minimum $ per adopter (e.g., $100K–$300K per third-party organization), minimum learner-reach target, and reallocation rules if adoption lags (e.g., shift unspent Phase 3 funds to stewardship reserve by Month 33 = 2029-07-13).

  3. Reserve Release Trigger Ambiguity: No Clear GO Criteria for Releasing the $175K Post-Gate Reserve Balance. The reserve rule caps pre-gate draws at $175K (5% of budget) until Month 24 (2028-10-13), when the remaining $175K is released 'only after the Month 24 (2028-10-13) GO' (decision). However, if the gate outcome is 'inconclusive' (some metrics pass, others unclear), or if a metric passes narrowly (ordinal error 25.1% vs. 25% threshold), the board's discretion to declare a GO and release the reserve is undefined. A delayed or contested gate decision could hold Phase 3 funding at risk for 3–6 months (Months 24–30 = 2028-10-13 to 2029-04-13), cascading into v1.0 release delay and stewardship commitment uncertainty. Strategic question: What is the explicit GO/NO-GO/board-decided-extension decision rule? What triggers a Phase 2 extension instead of release? Action: By Month 11 (2027-09-13) pre-analysis plan, the board must pre-register quantitative pass/fail boundaries for each metric and document a decision tree (GO: all 4 metrics pass and validity holds, i.e. ≥80 completers per arm, follow-up ≥70%, kappa ≥0.70; NO-GO: valid data with any metric failing; invalid or inconclusive data: board-decided extension); publish decision rule on project website immediately.

Review 15: Motivation Factors

  1. Clear Evidence of Progress Against Pre-Registered Metrics (Monthly Validation). Motivation falters if pilot data appears inconclusive or rules prove unworkable after Month 12 (2027-10-13) lock. If monthly enrollment/dropout tracking (Months 13–22 = 2027-11-13 to 2028-08-13) shows trending toward underpowered sample (<80 per arm, reducing power to 50–65%), or if preliminary comprehension/ordinal assessments at Month 18 (2028-04-13) reveal effect sizes below thresholds, team and stakeholder confidence erodes, risking disengagement or calls for Phase 2 extension ($300K–$600K, 26–52% of remaining budget). Mitigation: establish a transparent, monthly KPI dashboard showing enrollment progress, dropout trends, and preliminary effect-size estimates; publish findings at Months 15, 18, 21 (2028-01-13, 2028-04-13, 2028-07-13) to maintain visibility and early-warning signals before the Month 24 (2028-10-13) gate.

  2. Stakeholder Buy-In and Transparent Governance (Board and Partner Alignment). Motivation declines if educators, publishers, or regulators perceive the standard as imposed top-down or rules as linguistically weak/pedagogically burdensome. If consensus on rule compromises (ordinal spoken form, morphology threshold, homograph scope) is not achieved by Month 10 (2027-08-13), or if teachers report rule confusion during pilots, pilot fidelity degrades (measurement error inflates 10–20%), risking a disputed or inconclusive gate outcome and a board-decided extension. Mitigation: conduct quarterly stakeholder advisory panels (Months 6, 12, 18, 24 = 2027-04-13, 2027-10-13, 2028-04-13, 2028-10-13) with teachers, publishers, and safety-training partners; document feedback in published meeting minutes; tie rule finalization and Phase 3 readiness decisions visibly to stakeholder input.

  3. Secured Post-v1.0 Stewardship Commitment as a Credibility Signal (Early Steward Engagement). Motivation erodes if v1.0 release at Month 30 (2029-04-13) occurs without a funded steward, signaling the standard may be abandoned post-launch and atrophy within 12–24 months (by Month 48–60 = 2030-10-13 to 2031-10-13), reducing adoption from ≥3 target to 1–2 and negating $600K–$1M in Phase 3 value (estimate). If steward search does not begin until Month 18 (2028-04-13) and negotiation extends past Month 30 (2029-04-13), release is delayed and adoption momentum lost. Mitigation: identify 2–3 steward candidates by Month 12 (2027-10-13); approach top candidates by Month 18 (2028-04-13) with a formal proposal; secure at least a non-binding letter of interest by Month 24 (2028-10-13) and a signed MOU by Month 30 (2029-04-13) before release; publish steward identity and 5-year roadmap with v1.0 to signal long-term commitment.

Review 16: Automation Opportunities

  1. Automate Monthly Enrollment and Dropout Tracking Dashboard (Months 13–22 = 2027-11-13 to 2028-08-13). Implement a simple enrollment-management tool (REDCap, Qualtrics, or custom spreadsheet with automated alerts) to eliminate manual weekly reconciliation by the cohort manager. Automation reduces administrative overhead by ~10 hours/week (~$5K–$8K annually, estimate) and provides real-time visibility to the board, enabling early detection of recruitment shortfalls and automated escalation triggers (e.g., 'if forecast completers <320 at the Month 12 = 2027-10-13 audit, activate contingency incentive'). This reduces decision latency from 2–4 weeks to 1 week and improves confidence in the sample-size adequacy forecast used for Phase 2 extension decisions.

  2. Streamline Inter-Rater Pronunciation Scoring Workflow with Automated Kappa Calculation and Rater-Disagreement Flagging (Months 6–11 = 2027-04-13 to 2027-09-13). Replace manual Cohen's kappa calculation with a simple Python script or Qualtrics reporting module that ingests rater scores, auto-calculates pairwise and consensus kappa, and flags entries where raters diverge (kappa <0.70 for that entry). Cost: ~$2K–$5K (estimate) for tool development and validation. Savings: ~15 hours/month (~$3.6K–$5.4K annually, estimate) in manual scoring reconciliation, plus earlier detection of rater reliability issues by Month 9 (2027-07-13) instead of Month 10 (2027-08-13), reducing retraining timeline compression risk.

  3. Automate Monthly Budget Variance and Earned-Value Reporting (Months 1–36 = 2026-11-13 to 2029-10-13). Implement a lightweight budget-tracking template (Excel or simple accounting software) with automated monthly summaries of actuals vs. budget, variance flags (>10% threshold), and rolling 6-month cash-flow forecasts. Cost: ~$1K–$3K (estimate). Savings: ~8 hours/month (~$2.4K–$3.6K annually, estimate) of manual reconciliation and reduces budget-discovery delays from Month 8–9 (2027-06-13 to 2027-07-13) to Month 2 (2026-12-13), enabling proactive contingency activation (e.g., hybrid audio pivot) instead of reactive mid-phase crisis decisions.

Q1: What is the 'Pragmatic Foundation' strategic path, and how does it differ from the alternative scenarios presented in the plan?

A1: The Pragmatic Foundation is the recommended scenario: invariant-prefix ordinal markers (coexisting with legacy 1st/2nd/3rd forms), optional pronunciation overlay (leaving printed text standard), ESL-first supplementary wedge, purpose-built validated metrics, and even Phase 1–3 budget split. It prioritizes adoption-first, non-mandate positioning. Alternative: Pioneer's Gambit pursues respelling, spelled ordinals ('oneth'), and consumer-toggle wedge with thin Phase 1 (higher linguistic ambition, fragmentation risk). Prudent Consolidator uses off-the-shelf instruments, guidance-layer-only pronunciation, large held-reserve (lower precision on Clear English effects, credibility risk). The Pragmatic Foundation balances defensible evidence and educator buy-in.

Q2: Why is the 'pronunciation consistency' gate metric considered high-risk, and what happens if inter-rater reliability (Cohen's kappa) falls below the proposed floor of 0.70?

A2: Pronunciation consistency (>=15% above control, kappa >=0.75 target, >=0.70 floor) is high-risk because: (1) no published benchmark exists for inter-rater agreement in constructed-language contexts; (2) rater training depends on a reference accent anchor and ordinal marker spoken form not finalized until Month 10 (2027-08-13); (3) if kappa <0.70 at the Month 10 (2027-08-13) dry run, measurement error inflates by 20–30%, reducing statistical power to detect true effects by 10–15%. Fallback: 4-week Phase 1 extension (~$85K) for retraining, or hybrid model (synthetic baseline + verification subset). This consumes 48% of the pre-gate $175K draw cap, leaving $90K headroom for other contingencies.

Q3: What is the unfunded stewardship gap, and why does it threaten long-term adoption even if the Phase 2 go/no-go gate succeeds?

A3: Post-v1.0 stewardship (change requests, errata, conformance claims, governance) costs $150K–$250K annually (estimate), totaling $1.5M–$2.5M over 10 years. No steward organization is yet identified; steward search is deferred to Month 12 (2027-10-13) or later. If no steward is committed by Month 33 (2029-07-13) before v1.0 release (Month 30 = 2029-04-13), the standard atrophies within 12–24 months (by Month 48–60 = 2030-10-13 to 2031-10-13). Third-party adopters withdraw, leaving 1–2 instead of >=3, and learner reach caps at 10,000–20,000 (vs. 100,000+ unvalidated goal), negating $600K–$1M in Phase 3 adoption value. This compounds Phase 2 extension risk: if pilots extend 6 months, steward negotiation is compressed to 3 months before release.

Q4: What does the 'pre-analysis plan registration' requirement mean, and why is pre-registration by Month 11 (2027-09-13) non-negotiable for gate credibility?

A4: Pre-analysis plan registration means: by Month 11 (2027-09-13), the psychometrician must publish a complete plan on Open Science Framework specifying exact numeric thresholds (e.g., ordinal error >=25% reduction), sample-size power analysis (>=80 per arm for 80% power), primary/secondary outcomes, and decision rules. The plan is then locked before Phase 2 pilots begin at Month 13 (2027-11-13). Non-negotiable because: (1) pre-registration forecloses post-hoc threshold-tuning claims; (2) educators, standards bodies, and publishers will dispute any go/no-go outcome if thresholds were not pre-committed; (3) a delayed or weak pre-registration (Month 12 = 2027-10-13 or later) risks a 4-week Phase 1 extension to allow public comment, compressing Phase 2. The plan currently treats thresholds as 'proposals' without power-analysis justification.

Q5: What are the three highest-consequence risk scenarios, and what budget overruns or timeline extensions would result?

A5: Risk 1: Pilot recruitment/retention shortfall (enrolment <450, dropout >30%) yields effective completers <80 per arm, reducing statistical power from 80% to 50–65% and forcing a 3–6 month Phase 2 extension ($300K–$600K estimate, consuming the entire $350K reserve and creating a $35K–$250K shortfall). Risk 2: Audio production cost overrun (per-entry cost >$20) or inter-rater kappa <0.70 triggers a 4-week Phase 1 extension (~$85K), consuming 48% of the pre-gate $175K draw cap and leaving $90K headroom. Risk 3: Unfunded stewardship post-Month-36 (no committed steward by Month 33 = 2029-07-13) causes standard atrophy by Month 48–60 (2030-10-13 to 2031-10-13), reducing adoption from >=3 to 1–2 and negating $600K–$1M in Phase 3 adoption value (estimate). All three directly threaten the Month 24 (2028-10-13) go/no-go credibility or post-launch viability.

Q6: What are the ethical and fairness concerns raised by anchoring pronunciation guidance to a single reference accent, and how does the plan address regional and cultural bias?

A6: The plan anchors all pronunciation guidance, audio models, and pilot scoring to one reference accent (chosen by Month 3 = 2027-01-13), which simplifies measurement but risks alienating speakers of other major English varieties (British, Australian, Indian, South African). A single anchor implicitly privileges one speaker population and may reduce perceived adoption appeal outside that region. The plan documents this tension in Decision 8 (Reference Accent Anchor) and proposes mitigation: publish mapping tables showing how other accents relate to the anchor by Month 12 (2027-10-13), and defer multi-accent recording to post-v1.0 as an optional, unfunded extension. However, no explicit equity or inclusivity review is documented, and learners from non-anchor regions may experience the standard as regionally biased, potentially suppressing adoption in those populations.

Q7: What liability and safety risks does the project accept by pursuing safety-critical pilots (technical glossary, procedures), and what happens if a misreading of a Clear English ordinal marker or homograph causes an incident?

A7: The plan limits safety-critical pilots to glossary and labeling exercises (no live operational procedures before Month 24 = 2028-10-13), retains legal counsel by Month 2 (2026-12-13), and caps liability spending at $150K–$200K (estimate). However, if a pilot partner uses Clear English materials in an operational setting (despite disclaimers) and a misreading occurs—e.g., an ordinal marker '○1' is misread as '0.1' or a homograph 'lead' (to guide) is misread as 'lead' (the metal)—resulting in injury, regulatory investigation, or litigation, the project faces product-liability exposure, OSHA or HSE investigation, and reputational damage. The plan does not quantify the probability or financial exposure of a serious incident. If insurance is unavailable or cost exceeds $50K annually (estimate), the safety-critical wedge is scaled back to non-life-critical glossaries (office supplies, library materials, not pharmaceuticals or procedures), eliminating the high-impact evidence that makes the technical-glossary cohort credible.

Q8: What does the plan's decision to position Clear English as supplementary (not mandatory or a K-12 replacement) mean for real-world adoption, and is the 'optional module' strategy realistic for achieving the >=3 adopter target?

A8: The plan explicitly rejects mandates and K-12 replacement and positions Clear English as an optional, supplementary module for adult ESL and technical writing. This means: (1) publishers are not required to adopt; (2) learners choose to use it alongside standard English; (3) no governmental mandate or curriculum change is pursued. The advantage is low institutional friction and educator buy-in. The risk is adoption voluntariness: if Clear English is perceived as a niche variant or academic exercise, publishers may deprioritize it against more established curricula. The >=3 third-party adopters target (proposed threshold) depends on publishers and technical organizations perceiving measurable value (cost savings, learner engagement, reduced errors). However, the intelligibility target (>=90% of standard-English control accuracy within 2 weeks exposure, user constraint) suggests learners can switch between Clear English and standard English fluidly, reducing the sense of necessity. If adoption is framed as 'nice-to-have' rather than 'essential,' market uptake may stall at 1–2 small adopters, capping learner reach at 10,000–20,000 instead of the unvalidated 100,000+ estimate.

Q9: What are the 'controversial aspects' of the irregular morphology retention threshold and homograph disambiguation policy, and how might educator resistance to these rules undermine pilot fidelity?

A9: Two core rules raise controversy: (1) Irregular Morphology Retention (Decision 6): Retain all irregular forms in the top 1,000-word frequency band (e.g., go/went, be/was) but regularize lower-frequency irregulars. This trade-off protects learner recognition (most frequent forms unchanged) but creates inconsistency (some irregulars are regular, some are not), violating the stated goal of 'regularized' morphology. Teachers may perceive this as a half-measure that adds rule complexity without fully solving the problem. (2) Homograph Disambiguation (Decision 7): Mandatory markers only in safety-critical documents for <=50 high-impact pairs (e.g., read/read, lead/lead). Optional elsewhere. This creates a two-tier standard: safety-critical glossaries are heavily marked; ESL textbooks are not. Teachers and learners may find the inconsistency confusing—why is homograph marking enforced in one context but not others? If educators resist these rules as linguistically weak or pedagogically burdensome, they may misapply them during pilots (e.g., regularize all irregulars, mark all homophones), invalidating the assessment data. Measurement error could inflate by 10–20%, rendering gate metrics inconclusive and increasing false-negative risk by 15–25%.

Q10: What are the broader implications of the plan's failure to identify and secure a post-v1.0 steward organization before public release, and what happens to the standard if it is abandoned after Month 36 (2029-10-13)?

A10: The unfunded stewardship gap ($150K–$250K per year, $1.5M–$2.5M over 10 years, estimate) means the plan has no committed post-launch governance or maintenance funding. If v1.0 is released at Month 30 (2029-04-13) without a signed stewardship Memorandum of Understanding in hand, the standard becomes an orphaned artifact: change requests accumulate unanswered; errata go unfixed; the lexicon stagnates without updating to emerging vocabulary and cultural shifts. Within 12–24 months (by Month 48–60 = 2030-10-13 to 2031-10-13), adopter confidence erodes. Third-party publishers and educators perceive the standard as abandoned, cease marketing materials, and withdraw from adoption. The plan's >=3 adopter target (proposed threshold) collapses to 1–2, capping learner reach at 10,000–20,000 instead of the unvalidated 100,000+ estimate, negating $600K–$1M in Phase 3 adoption value (estimate). This cascades to stakeholder trust: if funders, educators, and standards bodies perceive stewardship as an afterthought, they lose confidence that Clear English will be maintained long-term and deprioritize adoption relative to more established standards (ASD-STE100, plain-language guidance, ICAO aviation English). The plan compounds this risk by deferring steward identification to Month 12 (2027-10-13) or later; if Phase 2 extends 6 months (due to recruitment shortfall or inconclusive data), steward negotiation slips to Months 30–33 (2029-04-13 to 2029-07-13), leaving minimal time to secure commitment before release.

A premortem assumes the project has failed and works backward to identify the most likely causes.

Assumptions to Kill

These foundational assumptions represent the project's key uncertainties. If proven false, they could lead to failure. Validate them immediately using the specified methods.

ID Assumption Validation Method Failure Trigger
A1 The $3.5M envelope, with a $175K pre-gate draw cap, absorbs foreseeable Phase 1 and Phase 2 cost shocks (audio, psychometrics, retraining) without cutting pilot scope. By Month 2 (2026-12-13), obtain firm quotes from 2-3 studios and the psychometrician, build a bottom-up Phase 1 and Phase 2 cost model, and run stacked fallback scenarios (4-week extension plus audio overrun) against the cap. Stacked plausible scenarios exceed the $175K pre-gate cap, or firm quotes put audio above $20 per entry and psychometrics above $200K (estimate).
A2 Prefix ordinals, the spoken reading and the single-accent overlay can be fixed by Month 10 (2027-08-13) and scored by raters at kappa >=0.70, so the gate hardware (instruments, raters, audio) works as designed. By Month 3 (2027-01-13), record a 50-100 word proof-of-concept sample with candidate marker readings and have 3-4 pre-screened raters score it blind; compute pairwise kappa. Pairwise kappa below 0.70 after one retraining round, or fewer than 3 raters reach 0.75 on the screening sample.
A3 Adult ESL learners, educators and publishers will accept a supplementary Clear English module and enrol and complete the pilot at the planned rate (>=115 per arm, <=30% dropout). By Month 2 (2026-12-13), run the 20-30 learner baseline study at 2-3 sites and interview 5-8 publishers and TESOL/IATEFL contacts about willingness to enrol, co-produce and cite the standard. Observed dropout above 35% in the baseline study, fewer than 3 ESL programs and 2 technical organizations willing to sign by Month 3 (2027-01-13), or fewer than 3 publishers giving written interest.
A4 A steward organization with $150K-$250K per year (estimate) of committed funding will exist and sign before the Month 30 (2029-04-13) v1.0 release, so the standard is maintained after Month 36 (2029-10-13). By Month 12 (2027-10-13), at steward search start, send a 2-page stewardship brief to 5-6 candidate organizations (non-profits, university consortia, standards bodies) and request a written response on interest, budget capacity and conditions. Fewer than 2 candidates give written interest, or none can identify a funding source for $150K-$250K per year (estimate) by Month 24 (2028-10-13).
A5 Safety-critical glossary and labeling pilots can run under legal disclaimers and human review without triggering regulatory approval, insurer refusal or liability exposure that blocks the technical cohort. By Month 4 (2027-02-13), obtain written advice from retained counsel and at least 2 insurance brokers on pilot coverage, and informal written input from one US and one UK safety or education regulator on the glossary-and-labeling scope. Counsel or a regulator indicates formal approval is required, or insurers decline pilot coverage or quote premiums above $50K per year (estimate).
A6 A practitioner-leaning board of 7-9 members can resolve contested rules (ordinal reading, morphology cutoff, homograph list) by vote or arbiter by Month 10 (2027-08-13) without eroding legitimacy or forcing mid-pilot changes. By Month 3 (2027-01-13), run a simulated contested-rule vote with a draft charter and 2-3 external linguists scoring rule clarity, and confirm arbiter availability and conflict-of-interest declarations in writing. The simulated dispute takes longer than 4 weeks to resolve, average clarity score is below 3.5 of 5 (proposed threshold), or no qualified arbiter agrees by Month 5 (2027-03-13).
A7 The ordinal prefix marker and legacy 1st/2nd/3rd forms can coexist in real documents, and a mechanical converter handles dates, lists and procedures without creating new ambiguity or rework for adopters. By Month 4 (2027-02-13), run a conversion test on 200-300 real documents (dates, numbered steps, tables) from ESL and technical sources, and have 2 technical writers review converted output for ambiguity. More than 5% of converted instances (proposed threshold) are ambiguous or misread by reviewers, or reviewers need manual correction on more than 10% of documents (proposed threshold).
A8 ESL publishers and technical-writing organizations see enough practical value in a supplementary, optional Clear English module to license it and use it in courseware, so the >=3 licensed adopter target is reachable. By Month 3 (2027-01-13), hold structured interviews with 5-8 ESL publishers and 3-4 technical-writing organizations and ask each to state conditions for licensing, expected cost and evidence required. Fewer than 3 publishers state they would license at a GO outcome, or most name a requirement (mandate, full curriculum, revenue guarantee) outside the plan's no-mandate scope.
A9 Key specialist roles (psychometrician, cohort manager, 2-3 linguists, audio lead) can be hired on time and retained through Month 24 (2028-10-13) within the budgeted salaries. By Month 1 (2026-11-13), post the psychometrician and cohort manager roles, obtain salary benchmarks and screen at least 5 qualified candidates per role, and confirm availability dates. Fewer than 3 qualified candidates per role, offers declined at budgeted pay, or the psychometrician start date later than Month 2 (2026-12-13).

Failure Scenarios and Mitigation Plans

Each scenario below links to a root-cause assumption and includes a detailed failure story, early warning signs, measurable tripwires, a response playbook, and a stop rule to guide decision-making.

Summary of Failure Modes

ID Title Archetype Root Cause Owner Risk Level
FM1 The Reserve That Vanished Before the Gate Process/Financial A1 Budget Owner (Program Director) CRITICAL (16/25)
FM2 The Marker Nobody Could Say Technical/Logistical A2 Lexicon and Audio Lead CRITICAL (15/25)
FM3 The Standard Nobody Wanted to Join Market/Human A3 Regulatory and Stakeholder Affairs Manager CRITICAL (20/25)
FM4 The Orphaned Standard Process/Financial A4 Regulatory and Stakeholder Affairs Manager CRITICAL (16/25)
FM5 The Label That Cried Wolf Technical/Logistical A5 Legal and Liability Counsel Lead (Project Lead oversight) CRITICAL (15/25)
FM6 The Board That Split the Standard Market/Human A6 Editorial Board Chair HIGH (12/25)
FM7 The Empty Chair at the Gate Process/Financial A9 Project Lead HIGH (12/25)
FM8 The Prefix That Broke the Paperwork Technical/Logistical A7 Lead Linguist (Ordinal Workstream) HIGH (12/25)
FM9 The Free Standard No One Licensed Market/Human A8 Regulatory and Stakeholder Affairs Manager CRITICAL (16/25)

Failure Modes

FM1 - The Reserve That Vanished Before the Gate

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If forecast cumulative pre-gate draws exceed $175K before Month 12 (2027-10-13) with no funded plan to keep >=80 completers per arm, halt Phase 2 launch and return to the board for descoping or cancellation.


FM2 - The Marker Nobody Could Say

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If kappa remains below 0.70 after the retest and a 4-week extension, pronunciation consistency is dropped as a primary gate metric by board decision or the project pivots; no Phase 2 launch on unreliable scoring.


FM3 - The Standard Nobody Wanted to Join

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If signed enrolment guarantees cover fewer than 320 expected completers by Month 6 (2027-04-13) despite standby sites, cancel Phase 2 or pivot the wedge before further spend.


FM4 - The Orphaned Standard

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If no signed steward commitment exists by Month 30 (2029-04-13), v1.0 public release is not triggered; Month 33 (2029-07-13) is only the latest point at which a delayed release can still be triggered, and if no signed commitment exists by then, v1.0 public release is cancelled and the project closes with archived materials.


FM5 - The Label That Cried Wolf

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If insurance cannot be secured and counsel advises uninsured exposure, safety-critical pilots are cancelled and the project proceeds ESL-only.


FM6 - The Board That Split the Standard

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If core rules are not locked by Month 13 (2027-11-13), Phase 2 does not launch and the board decides on extension or cancellation.


FM7 - The Empty Chair at the Gate

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If no qualified psychometrician is contracted by Month 4 (2027-02-13), Phase 2 start is deferred by board vote until pre-registration is credible, or the project is cancelled.


FM8 - The Prefix That Broke the Paperwork

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If ambiguity stays above 5% (proposed threshold) after one redesign cycle by Month 10 (2027-08-13), the ordinal rule is withdrawn from the v1.0 gate and the board decides a pivot.


FM9 - The Free Standard No One Licensed

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If no publisher or standards body has signed a licence commitment by Month 30 (2029-04-13), Phase 3 outreach spending stops and unspent funds are returned.

Reality check: fix before go.

Summary

Level Count Explanation
🛑 High 14 Existential blocker without credible mitigation.
⚠️ Medium 4 Material risk with plausible path.
✅ Low 2 Minor/controlled risk.

Checklist

1. Violates Known Physics

Does the plan's success require breaking a known law of physics (e.g., thermodynamics, conservation of energy, speed-of-light limit, causality)?

Level: ✅ Low

Justification: This is a linguistic standardization, curriculum design, and pilot-testing program. Success depends on documented rule systems, human learning measured via objective test performance, institutional adoption decisions, and pedagogical engineering—all of which are physical processes (cognition, information systems, organizational behavior). The plan makes no claims that non-physical mechanisms produce real-world learning outcomes and does not require breaking any named law of physics.

Mitigation: No physics-related action required — the plan does not invoke physics-incompatible mechanisms.

2. No Real-World Proof

Does success depend on a technology or system that has not been proven in real projects at this scale or in this domain?

Level: 🛑 High

Justification: Rated HIGH because the plan hinges on a novel combination of five elements (prefix ordinal markers, optional pronunciation overlay, supplementary ESL-first wedge, purpose-built validated gate metrics, and non-profit certification-mark governance) without independent evidence at comparable scale. No published precedent demonstrates that this system combination works together; Basic English (1930s) adoption faded; spelling reforms failed; ASD-STE100 and ICAO control languages exist but are distinct models. Effect-size assumptions driving the power analysis are unvalidated. Failure cascades to zero adoptable output—returns $0 and kills the initiative.

Mitigation: Run four parallel validation tracks (Market, Legal, Technical, Evidence) with two NO-GO gates: (1) Empirical/engineering validity by Month 10 (2027-08-13)—if inter-rater kappa <0.70 or power analysis reveals underpowering, stop Phase 2; (2) Legal/compliance by Month 8 (2027-06-13)—if regulatory approval exceeds 4 months or insurers decline, defer safety cohort. Publish pre-analysis plan with effect-size justification by Month 11 (2027-09-13) and conduct validity study (N=20–30, Months 10–11 = 2027-08-13 to 2027-09-13) to confirm assumptions before Phase 2 launch. Each track produces one authoritative source or supervised pilot showing results vs. baseline.

3. Buzzwords

Does the plan use excessive buzzwords without evidence of knowledge?

Level: ⚠️ Medium

Justification: Rated MEDIUM because the plan names five critical strategic levers (ordinal architecture, G2P depth, adoption wedge, outcome metrics, budget weighting) with business-level mechanisms and owners, but gate thresholds remain "proposed" without empirically justified numeric values. Pre-analysis plan and power analysis are not due until Month 11 (2027-09-13), only about 4 weeks before Phase 2 starts at Month 12 (2027-10-13). If effect-size assumptions are wrong or thresholds require mid-project adjustment, the Month 24 (2028-10-13) go/no-go decision becomes disputable, reducing stakeholder confidence by 20-30% and Phase 3 adoption by that margin.

Mitigation: Psychometrician: deliver draft pre-analysis plan with numeric thresholds and power analysis by Month 5 (2027-03-13); conduct validity study (N=20-30, Months 10-11 = 2027-08-13 to 2027-09-13) to confirm effect-size assumptions; pre-register on Open Science Framework by Month 11 (2027-09-13) with board sign-off and public disclosure. Gate thresholds must be locked and defended before Phase 2 starts at Month 12 (2027-10-13).

4. Underestimating Risks

Does this plan grossly underestimate risks?

Level: ⚠️ Medium

Justification: Rated MEDIUM because the plan identifies 20 tracked risks with quantified impacts, but second-order cascade effects—particularly recruitment failure → sample-size loss → false-negative gate → 6-month Phase 2 extension → stewardship negotiation compression → unfunded v1.0 orphaning—lack explicit mitigation sequencing or decision thresholds. The gate metrics (ordinal error ≥25%, pronunciation consistency ≥15% above control and significant, with kappa ≥0.70 as a separate validity condition) depend on adequate sample size and measurement reliability, both jeopardized if recruitment/retention miss targets (high likelihood per baseline assumptions) or rater training fails (medium likelihood). If either failure cascades unchecked, the Phase 2 extension consumes the entire $350K reserve and eliminates funding headroom for stewardship contingency (estimated $150K–$250K/year post-launch). The plan acknowledges these cascades in the premortem but lacks actionable monthly KPI dashboards or automatic escalation triggers (e.g., "if forecast completers are below 320 (or enrolment is below the 460 power-analysis target) at the Month 12-13 = 2027-10-13 to 2027-11-13 audit, activate contingency immediately"). This gap creates a 3-6 month discovery lag before corrective action, reducing effectiveness.

Mitigation: Program Lead: Establish by Month 1 (2026-11-13) a living risk dashboard with monthly KPI triggers (enrollment targets, dropout rates, spend variance >10%, recruitment velocity). Define automatic escalation thresholds: if forecast completers are <320 (or enrolment is below the 460 planned) at the audit one month after enrolment opens (Month 12-13 = 2027-10-13 to 2027-11-13), immediately activate contingency incentive draw ($20K–$30K, estimate) and flag Phase 2 extension risk to the board within 5 days. Create a Cascade Mitigation Playbook documenting: (1) recruitment failure → sample-size shortfall → statistical power loss → inconclusive gate → 3–6 month extension ($300K–$600K cost); (2) kappa <0.70 → pronunciation metric failure → 4-week extension ($85K) → reserve cap breached → stewardship funding gap emerges. Update the playbook monthly and present findings to the board at Months 6, 12, 18, 24 (2027-04-13, 2027-10-13, 2028-04-13, 2028-10-13) to enable proactive contingency activation before total reserve is exhausted.

5. Timeline Issues

Does the plan rely on unrealistic or internally inconsistent schedules?

Level: 🛑 High

Justification: Rated HIGH because the timeline is compressed and contains critical path dependencies that leave minimal buffer for slippage. The Month 24 (2028-10-13) go/no-go gate depends on three prerequisites that must lock by Month 12 (2027-10-13): (1) pre-analysis plan with numeric thresholds pre-registered by Month 11 (2027-09-13)—requiring power analysis from a psychometrician not yet hired; (2) all pilot partner commitments signed by Month 3 (2027-01-13)—with recruitment baseline not yet conducted; (3) inter-rater kappa ≥0.70 confirmed by Month 10 (2027-08-13)—requiring audio production (Months 6–11 = 2027-04-13 to 2027-09-13) on a critical path with no contingency raters pre-screened. If any single item slips 4–6 weeks (audio delivery delay, psychometrician hire delay, kappa retraining), Phase 2 start compresses by 1–2 months, reducing the 12-month pilot window to 10–11 months, cutting effective assessment time by 8–17% and reducing statistical power to detect ordinal error or pronunciation effects by 10–15%. A 6-week slip cascades to either a false-negative gate (no-go on inconclusive data, stranding $1.2M Phase 2 spend) or a 3–6 month extension ($300K–$600K, consuming the entire $350K reserve). The plan acknowledges this (Risk Register entries 6, 12) but lacks explicit critical-path buffers or escalation triggers (e.g., 'if audio studio delivery is >2 weeks late by Month 8 = 2027-06-13, activate the hybrid synthetic-baseline model immediately'). Monthly earned-value tracking and 2-week slip escalation thresholds are missing from the canonical timeline.

Mitigation: Program Lead: Establish by Month 1 (2026-11-13) a detailed critical-path schedule with explicit dependencies and 2-week slip escalation triggers for each gate milestone (psychometrician hired Month 2 = 2026-12-13; power analysis draft Month 5 = 2027-03-13; audio studio contract signed Month 3 = 2027-01-13; rater pre-screening complete Month 4 = 2027-02-13; kappa ≥0.70 confirmed Month 10 = 2027-08-13; pre-analysis plan registered Month 11 = 2027-09-13). If any item slips >2 weeks, escalate to editorial board within 5 days with a recovery plan (e.g., hybrid audio model, extended Phase 1 timeline, scope reduction). Conduct monthly critical-path reviews at Months 3, 6, 9 (2027-01-13, 2027-04-13, 2027-07-13) and publish findings to the board.

6. Money Issues

Are there flaws in the financial model, funding plan, or cost realism?

Level: ⚠️ Medium

Justification: Rated MEDIUM because committed funding sources and draw schedules exist (Phase 1 $1.1M, Phase 2 $1.2M, Phase 3 $0.85M + $0.35M reserve, total $3.5M user constraint), but critical dependencies and contingency exposure are substantial. Pre-gate reserve capped at $175K (5% of budget) with stacked fallback scenarios (4-week Phase 1 extension ~$85K + psychometric re-validation + recruitment contingency) potentially exceeding the cap by $125K, leaving only $90K unallocated headroom. Post-Phase-2 stewardship ($150K–$250K annually) is unfunded and no steward organization is committed, creating a $1.5M–$2.5M ten-year gap post-v1.0 release. Pilot recruitment/retention shortfall (ample likelihood given 35–45% typical adult dropout vs. 30% plan assumption) forcing 3–6 month Phase 2 extension ($300K–$600K, estimate) would consume entire reserve and create $35K–$250K shortfall. Runway is defensible only if recruitment succeeds and primary technical risks (kappa ≥0.70, power analysis validated) are resolved by Month 12 (2027-10-13).

Mitigation: Finance Officer: By Month 1 (2026-11-13), establish monthly earned-value tracking with variance alerts (>10% overrun triggers board review within 5 days); conduct spending audit at Months 3, 6, 9 (2027-01-13, 2027-04-13, 2027-07-13) and document rolling 6-month forecasts. Identify and pre-commit a steward organization with written funding pledge by Month 30 (2029-04-13) before v1.0 release, locking annual stewardship budget ($150K–$250K, estimate) from external sources (endowment, membership, grant). If the steward commitment is not signed by Month 30 (2029-04-13), defer v1.0 release until stewardship is funded; Month 33 (2029-07-13) is the latest point at which a delayed release can still be triggered.

7. Budget Too Low

Is there a significant mismatch between the project's stated goals and the financial resources allocated, suggesting an unrealistic or inadequate budget?

Level: 🛑 High

Justification: Rated HIGH because the stated budget of $3.5M is not substantiated by vendor quotes or scale-appropriate benchmarks. The plan allocates Phase 1 $1.1M for rule specification, lexicon development, and audio production of 5,000 entries, but provides only rough cost estimates (audio "typically $80K–$120K estimate," psychometrics "$150K–$200K estimate") without firm quotes from professional studios, assessment vendors, or comparable language-standardization projects. The plan acknowledges audio production as cost-critical (Months 6–11 = 2027-04-13 to 2027-09-13 budget bottleneck) but defers cost-per-entry validation to Month 4 (2027-02-13), after rule lock and partner commitments are due. A per-entry cost exceeding $20 (the proposed $100K ÷ 5,000 threshold) would trigger a hybrid pivot to speech synthesis, invalidating assumptions and consuming contingency. No normalized cost-per-word benchmarks are cited against comparable lexicon projects (e.g., corpus-based dictionary development, ESL curriculum production). Contingency reserve is capped at 10% ($0.35M), with pre-gate draws limited to $175K (5% of budget)—inadequate against known failure scenarios (Phase 1 extension $85K + recruitment contingency $20K–$30K + psychometric rework $50K+ totals $155K–$165K, leaving near-zero headroom). The plan lacks a detailed cost-realism validation baseline.

Mitigation: Finance Officer and Lexicon Lead: Obtain firm, irrevocable quotes from ≥3 professional audio studios by Month 2 (2026-12-13) specifying per-entry cost, delivery timeline (≤4 weeks), take requirements (2+ takes), and backup/contingency rates. Simultaneously, benchmark 5,000-word lexicon production against ≥3 published ESL dictionary or corpus projects (Cambridge, Oxford, learner corpora) documenting cost per entry, including pronunciation audio. Normalize by per-word cost and validate assumptions against benchmarks. Adjust Phase 1 budget or implement the hybrid synthetic-baseline model by Month 4 (2027-02-13) if per-entry costs exceed $20 (estimate).

8. Overly Optimistic Projections

Does this plan grossly overestimate the likelihood of success, while neglecting potential setbacks, buffers, or contingency plans?

Level: ⚠️ Medium

Justification: Rated MEDIUM because the plan presents four gate-metric thresholds (ordinal error ≥25%, comprehension ≤10% slower, pronunciation consistency ≥15% above control and significant, retention ≥70% of post-test and not below control) and adoption target (≥3 adopters) as single values without confidence intervals, sensitivity analysis, or published benchmarks. Dropout and learner-reach estimates lack worst-case/best-case scenarios. The plan acknowledges uncertainty in risk registers and fallback timelines but does not formalize effect-size sensitivity (e.g., power curves under 20%, 25%, 30% ordinal reduction) or adoption-rate ranges. Canonical facts confirm gates are "proposed thresholds" pending pre-analysis plan finalization by Month 11 (2027-09-13), so contingency analysis is deferred, not absent.

Mitigation: Psychometrician: Deliver sensitivity analysis by Month 9 (2027-07-13) showing statistical power under ordinal-error reduction of 20%, 25%, 30% (vs. ≥25% threshold); model sample-size adequacy under 30%, 35%, 40% dropout scenarios. Regulatory Affairs Lead: Model adoption under 1, 2, 3, ≥5 third-party adopter scenarios and resulting learner reach (5,000–100,000 range). Publish ranges and best/worst/base-case projections in the pre-analysis plan registered by Month 11 (2027-09-13).

9. Lacks Technical Depth

Does the plan omit critical technical details or engineering steps required to overcome foreseeable challenges, especially for complex components of the project?

Level: 🛑 High

Justification: Rated HIGH because core build-critical components lack foundational engineering artifacts. The 5,000-word lexicon, inter-rater pronunciation-scoring system, and four pre-registered gate metrics are specified at policy level but lack formal technical specifications. No interface contracts exist between the ordinal-marker system and learner-facing materials, the pronunciation overlay and digital/print delivery platforms, or the assessment instruments and pilot curriculum. Acceptance tests for ordinal-error measurement, pronunciation-consistency scoring (Cohen's kappa calibration), and comprehension-speed instruments are not documented. Integration plan and non-functional requirements (accuracy thresholds, latency, accessibility, availability of audio files) are absent. The pre-analysis plan (Month 11 = 2027-09-13) is foundational but lacks implementation detail: no technical specification for how ordinal markers are encoded, tagged, or parsed in documents; no acceptance criteria for rater-training completion or kappa floor validation before pilots; no integration roadmap linking assessment platforms, learner data collection, and gate-decision automation. This gap directly threatens gate credibility: if inter-rater kappa is discovered below 0.70 at Month 10 (2027-08-13) dry run, no formal acceptance test exists to govern whether retraining or fallback (hybrid synthetic model) is triggered. Critical components (pronunciation overlay, marker conversion) are architectural decisions without technical implementation specs.

Mitigation: Psychometrician and Engineering Lead: By Month 5 (2027-03-13), deliver a Technical Specification Document (5-7 pages) covering: (1) ordinal-marker encoding (symbol, notation, data format in digital/print); (2) inter-rater kappa measurement procedure (rater selection, training protocol, blind-scoring workflow, dispute resolution, minimum N for statistical validity); (3) acceptance test suite: kappa ≥0.70 on calibration sample (100-200 words, ≥3 raters), pronunciation-error task floor (lowest quartile ≥50% accuracy), comprehension-speed baseline (control ≥85th percentile fluency). (4) Integration map with owners (assessor, linguist, platform lead) and dates (audio delivery Month 11 = 2027-09-13, integration platform testing Month 10 = 2027-08-13, pilot dry-run Month 10 = 2027-08-13). Within 30 days of each gate deadline (Month 10 = 2027-08-13, Month 24 = 2028-10-13), validate acceptance criteria and document pass/fail evidence.

10. Assertions Without Evidence

Does each critical claim (excluding timeline and budget) include at least one verifiable piece of evidence?

Level: 🛑 High

Justification: Rated HIGH because nearly all critical claims—pilot partner commitments (>=3 ESL programs, >=2 technical organizations), pre-analysis plan with numeric thresholds and power analysis, ethics approval, inter-rater kappa >=0.70, steward organization commitment—lack verifiable artifacts (signed contracts, registered plans, approval letters, or formal agreements). The plan specifies when evidence should be obtained (Month 3 = 2027-01-13, Month 11 = 2027-09-13, Month 30 = 2029-04-13) but provides no current documentary proof. Most critically, the Month 24 (2028-10-13) go/no-go gate depends on a pre-analysis plan not yet commissioned; the psychometrician hire (Month 2 = 2026-12-13) is not confirmed. Without evidence of these foundational commitments and contracts in hand before Month 3 (2027-01-13), the plan cannot proceed credibly. Per the rubric, critical control/evidence is missing, creating a likely failure mode.

Mitigation: Finance/Program Lead: By Month 1.5 (2026-11-28), obtain signed RFPs from >=3 ESL programs and >=2 technical-training organizations; execute MOUs with enrollment guarantees by Month 3 (2027-01-13). Simultaneously, issue a signed contract with the independent psychometrician specifying power-analysis deliverables by Month 5 (2027-03-13) and pre-analysis plan registration by Month 11 (2027-09-13). Retain legal counsel and ethics-review board contact by Month 2 (2026-12-13). Start the steward search by Month 12 (2027-10-13) and request written letters of interest by Month 24 (2028-10-13).

11. Unclear Deliverables

Are the project's final outputs or key milestones poorly defined, lacking specific criteria for completion, making success difficult to measure objectively?

Level: 🛑 High

Justification: Rated HIGH because 'Clear English Standard v1.0' final deliverable lacks specific, verifiable acceptance criteria beyond policy intent. 'Public standard,' 'reference dictionary,' and 'compliance' are named but unmeasured: no minimum lexicon coverage KPI, no defined ordinal-error rate improvement target, no documented pronunciation-consistency threshold.

Mitigation: Editorial Board: By Month 11 (2027-09-13), define SMART acceptance criteria for v1.0 deliverables with KPIs: (1) Reference Dictionary completeness: 5,000 core entries with pronunciation audio (target >=99% coverage); (2) Ordinal Rule clarity: >=90% native-reader and educator comprehension of ordinal marker notation (target >=4/5 on clarity rubric); (3) Pilot-validated metrics: ordinal error reduced >=25%, pronunciation consistency >=15% above control and significant (kappa >=0.70 as a separate validity condition). Document in published specification.

12. Gold Plating

Does the plan add unnecessary features, complexity, or cost beyond the core goal?

Level: 🛑 High

Justification: Rated HIGH because the plan explicitly positions Clear English as a parallel (not replacement) English variant offered as an optional, supplementary module alongside standard English curricula. The goal statement says 'without mandates or K-12 replacement,' and Decision 3 (Adoption Wedge and Sequencing) selects 'adult ESL programs and publishers' as the lead market. However, the plan does not identify, isolate, or cost the 'gold-plating' features—non-core rule enhancements, optional multi-accent audio recording, authoring-tool automation, or glossary extensions—that add material scope and budget exposure without being foundational to the 5,000-word lexicon, ordinal marker, G2P overlay, or the gate metrics themselves. Specifically: (1) The pronunciation-consistency gate metric hinges on single-accent audio (proposal approved Decision 8), yet the plan defers multi-accent recording to 'post-v1.0' without pre-committing that the additional cost ($50K–$100K estimate for 2–3 accents) will not creep into Phase 1 or Phase 2 budgets. (2) The homograph-disambiguation policy (Decision 7) proposes optional tool-assisted marking ('an authoring-tool plugin'), but this plugin is not funded in v1.0 and its omission risks governance creep: if early adopters demand it, Phase 3 budget ($0.85M nominal, up to $1.2M with reserve) will be diverted from outreach to engineering. (3) The lexicon-expansion trigger (if coverage audits show <85% by Month 8 = 2027-06-13) can push per-entry recording and rater work beyond the budgeted $80K–$120K, consuming contingency. None of these features (multi-accent, plugin, expanded lexicon) is required to satisfy the core project objectives: deliver a defensible 5,000-word core, ordinal rule, G2P overlay, and pass the four gate metrics by Month 24 (2028-10-13). Gold-plating features risk: (1) compressing the gate timeline (e.g., if multi-accent audio is added, audio production extends beyond Month 11 = 2027-09-13, delaying rater training and kappa confirmation past Month 10 = 2027-08-13, triggering the 4-week Phase 1 extension fallback); (2) consuming the $175K pre-gate draw cap (currently capped at $175K for gate-protection draws; multi-accent and plugin development would consume $50K–$100K+, leaving insufficient headroom for recruitment or psychometric rework); (3) spreading scope across adopters without clarity on whose budget funds the add-on (publisher? project?). The plan does not document a formal gold-plating gate: no month/decision point at which optional features are reviewed against the project objectives and either committed to as in-scope or deferred to Phase 3/post-v1.0.

Mitigation: Editorial Board: Establish by Month 3 (2027-01-13) a Scope Control Charter (1–2 pages) that defines 'in-scope' for v1.0 as: the 5,000-word lexicon with single-anchor pronunciation, ordinal prefix rule with fixed spoken form, G2P optional overlay, homograph list (no tool), and four gate metrics. Any feature outside this list (multi-accent audio, authoring plugin, lexicon expansion beyond 5,000 words unless coverage audit forces it, additional morphology changes, enhanced homograph marking) is marked 'proposed' and requires explicit budget approval by the editorial board before Month 10 (2027-08-13). For each gold-plating proposal, the proposer must submit a one-page Benefit Case (KPI, owner, cost, alternative drop) to the board; the board votes on inclusion by Month 11 (2027-09-13), before pre-analysis plan lock. Any gold-plating approved must not exceed a $30K–$50K (estimate) total spend cap pre-gate; overages are deferred to Phase 3.

13. Staffing Fit & Rationale

Do the roles, capacity, and skills match the work, or is the plan under- or over-staffed?

Level: 🛑 High

Justification: Rated HIGH because the Psychometrician / Assessment Specialist is the single non-delegable expertise required to design defensible gate metrics, conduct power analysis, and pre-register thresholds by Month 11 (2027-09-13). If this rare role is not hired by Month 2 (2026-12-13) or their power analysis reveals underpowering, the Month 24 (2028-10-13) go/no-go decision becomes scientifically disputable, reducing Phase 3 adoption by 20–50% and stranding up to $300K–$400K of the $1.2M Phase 3 budget. Applied measurement expertise in ESL assessment and pre-analysis plan registration is scarce and difficult to replace or fast-track.

Mitigation: Regulatory Affairs Manager: Validate psychometrician availability by issuing an RFP to 5–8 qualified candidates by Month 1 (2026-11-13) and securing a signed contract with the top candidate by Month 2 (2026-12-13), specifying deliverables and a penalty clause if power-analysis draft is not delivered by Month 5 (2027-03-13).

14. Legal Minefield

Does the plan involve activities with high legal, regulatory, or ethical exposure, such as potential lawsuits, corruption, illegal actions, or societal harm?

Level: 🛑 High

Justification: Rated HIGH because legality and required approvals for this language-standardization program are substantially undefined or unclear, creating potential showstopper risks. The plan addresses education, adult ESL, and safety-critical documentation contexts, each subject to distinct regulatory regimes, but the controlling statutes and approval authorities are not mapped. Specifically: (1) Education and ESL Curricula: No evidence that US state education departments, Ofqual (UK regulator of education standards), TESOL professional standards body, or CEFR governance bodies have been formally engaged to clarify whether Clear English adoption in accredited programs requires compliance review, registration, or curriculum-alignment approval. The regulatory landscape assessment is deferred to Month 8 (2027-06-13) as an informal advice-gathering exercise, not a formal pre-filing with authorities. (2) Safety-Critical Documentation: No formal legal determination exists on whether glossaries and procedure labels using ordinal markers, homograph markers, or pronunciation guidance trigger product-liability review, OSHA (Occupational Safety and Health Administration) or HSE (Health and Safety Executive, UK) oversight, or FDA (if medical device contexts arise) premarket review. The plan states 'glossary and labeling only, no live procedures' as a liability containment strategy, but regulators have not confirmed this scope avoids mandatory approval. (3) Intellectual Property and Name Stewardship: The plan reserves 'Clear English' as a potential certification mark but has not registered it with USPTO, UK Intellectual Property Office, or international trademark bodies; no clearance search confirms the name is unencumbered. (4) Data Protection and Ethics: IRB/ethics approval is targeted for Month 6 (2027-04-13), but the study protocol is not yet submitted; GDPR and US state data-protection compliance are assumed but not audited. The plan acknowledges regulatory risks in the risk register but provides no evidence of pre-filing conversations, clearance opinions, or risk-mitigation agreements with authorities. Without documented approval pathways and regulator engagement, a 4-8 month approval delay (documented forecast in the risk register) could compress Phase 2 pilots by 33-67%, invalidating gate evidence.

Mitigation: Regulatory and Stakeholder Affairs Manager: Establish by Month 2 (2026-12-13) a Regulatory Landscape Map identifying all applicable authorities (US: state education departments, OSHA, FDA if applicable, FTC for consumer claims; UK: Ofqual, HSE, ICO for data protection; International: CEFR steerage, ISO language committees). Conduct pre-filing outreach by Month 4 (2027-02-13) with written inquiries to at least one US and one UK education/safety authority requesting non-binding advisory input on the 'glossary and labeling' scope. Obtain written responses by Month 8 (2027-06-13) documenting whether formal approval is required, timelines, and any conditions. If approval is required and timelines exceed 4 months, defer safety-critical pilots to a post-Month-24 (2028-10-13) Phase 2.5 research track ($150K-$300K, estimate, funded from Phase 3 reserve), protecting the main ESL pilot window. Secure IRB/ethics approval by Month 6 (2027-04-13) and publish a Data Protection and Privacy Policy by Month 12 (2027-10-13).

15. Lacks Operational Sustainability

Even if the project is successfully completed, can it be sustained, maintained, and operated effectively over the long term without ongoing issues?

Level: 🛑 High

Justification: Rated HIGH because post-Month-36 (2029-10-13) stewardship is unfunded ($150K–$250K annually estimated) with no committed steward organization identified. The plan releases v1.0 by Month 30 (2029-04-13) conditional on "a written steward commitment," but steward search does not begin until Month 12 (2027-10-13), and no non-binding letters of interest are solicited until Month 24 (2028-10-13). Without funded long-term maintenance post-launch, the standard will atrophy within 12–24 months (by Month 48–60 = 2030-10-13 to 2031-10-13): change requests accumulate unanswered, errata go unfixed, adopters withdraw confidence, and Phase 3 adoption collapses from ≥3 target to 1–2, negating $600K–$1M in adoption value.

Mitigation: Regulatory Affairs Manager: Identify 2–3 steward candidates (university consortiums, language non-profits, standards bodies) by Month 12 (2027-10-13); approach with formal Stewardship Proposal specifying $150K–$250K annually, governance structure, and 10+ year commitment by Month 24 (2028-10-13); secure signed MOU before v1.0 release at Month 30 (2029-04-13) confirming funding source and maintenance responsibilities.

16. Infeasible Constraints

Does the project depend on overcoming constraints that are practically insurmountable, such as obtaining permits that are almost certain to be denied?

Level: ✅ Low

Justification: Rated LOW because the project is a language-standardization and educational-pilot program, not a physical facility or construction project. No zoning, occupancy-code, fire-load, or structural constraints apply. Operational constraints (regulatory approval for pilot use, ethics clearance, data-protection compliance, liability insurance, partner facility access) are the real hard limits; these are documented in the regulatory landscape assessment and risk register, not zoning law. Standard office and audio-capture space exist in all three candidate hubs at budgeted cost.

Mitigation: Hub Selection Lead: Confirm the chosen operational hub (Austin, Cambridge, or D.C. metro) by Month 3 (2027-01-13) and execute a 36-month lease or co-working agreement; verify that space meets audio-capture acoustics, partner accessibility, and board-meeting capacity within 30 days of lease signature.

17. External Dependencies

Does the project depend on critical external factors, third parties, suppliers, or vendors that may fail, delay, or be unavailable when needed?

Level: 🛑 High

Justification: Rated HIGH because external dependencies are substantial and single-point-of-failure risks are inadequately mitigated. The plan depends on: (1) 5,000-word audio production (Months 6–11 = 2027-04-13 to 2027-09-13) from a single primary studio with only a 'backup vendor identified by Month 3 (2027-01-13)'—no firm contract for the backup, no contingency budget if primary studio capacity is exhausted or per-entry cost escalates; (2) inter-rater pronunciation scoring at kappa ≥0.70 (target 0.75 proposed) by Month 10 (2027-08-13), with only 3–4 trained raters and no pre-screened secondary panel if primary raters become unavailable, quit, or fail calibration; (3) ≥3 ESL program and ≥2 technical-organization pilot partners for enrollment by Month 13 (2027-11-13), with written commitments due Month 3 (2027-01-13) but no contingency recruitment sites identified or contacted, and a 9-month gap between commitment and enrollment during which partner circumstances (staffing, budgets, competing initiatives) can change; (4) ethics approval and data-protection clearance by Month 6 (2027-04-13), with IRB submission deferred to Month 2 (2026-12-13) and no contingency regulator or ethics body identified if primary review body escalates or imposes lengthy conditions; (5) steward-organization commitment for $150K–$250K per-year post-v1.0 funding (estimated), with no named steward candidate and search deferred to Month 12 (2027-10-13)—if a steward commitment is not signed by Month 30 (2029-04-13), v1.0 release is conditional (Month 33 = 2029-07-13 is the latest point at which a delayed release can still be triggered) and standard risks orphaning by Month 48–60 (2030-10-13 to 2031-10-13). No failover strategy documents parallel suppliers, rater contingency rosters, backup partner sites, secondary ethics reviewers, or alternative steward pipelines. If any single dependency (studio, rater team, partner site, ethics body, steward) breaks unexpectedly, the critical path (audio completion Month 11 = 2027-09-13, rules lock Month 12 = 2027-10-13, pilot enrolment complete Month 13 = 2027-11-13, gate Month 24 = 2028-10-13) experiences 4–8 week delays that compress subsequent phases and reduce data quality. A 6-week audio-studio delay compresses rater training from 6 weeks to 2 weeks, risking kappa <0.70 and triggering a 4-week Phase 1 extension ($85K estimate) that consumes 48% of the pre-gate $175K draw cap.

Mitigation: Regulatory Affairs Manager: By Month 2 (2026-12-13), execute signed backup-vendor agreements with ≥2 secondary audio studios committing to surge capacity (500–1,000 files within 2 weeks if primary vendor fails) at locked per-entry rates; confirm in writing. Simultaneously, recruit a secondary rater panel of 2–3 additional trained raters by Month 4 (2027-02-13) (in addition to the primary 3–4) and maintain currency with quarterly training refreshes. Identify ≥2 fallback pilot sites (ESL programs or technical-training organizations) by Month 3 (2027-01-13) with signed letters of interest (non-binding but confirming willingness to enroll ≥30 learners if a primary partner withdraws). Engage secondary IRB/ethics reviewers and conduct pre-submission consultation by Month 1 (2026-11-13) so alternate review pathways are known if primary review is delayed. Start the steward search by Month 12 (2027-10-13), solicit steward-candidate letters of interest by Month 24 (2028-10-13) and initiate formal proposal discussions with ≥3 candidates (not 2) by Month 18 (2028-04-13) to provide negotiation cushion.

18. Stakeholder Misalignment

Are there conflicting interests, misaligned incentives, or lack of genuine commitment from key stakeholders that could derail the project?

Level: 🛑 High

Justification: Rated HIGH because two key stakeholders have fundamentally misaligned incentives that are not yet publicly documented or negotiated. The Finance Department is likely incentivized by quarterly budget adherence and ROI per dollar spent within fixed fiscal periods; the R&D/Linguistics Team is incentivized by linguistic comprehensiveness and long-term evidence rigor. A tension emerges: Finance pressures for lean Phase 1 rules (faster to pilot) and deferred costly features (pronunciation audio, multi-rater validation); R&D insists on robust rule specification, multi-accent validation, and rigorous pilot instrumentation before releasing the standard. The project acknowledges this in Decision 5 (Phase Budget Weighting and Reserve) and Decision 4 (Outcome Metric Battery Design), naming the trade-off between 'evidence rigor versus a fixed budget.' However, no shared OKR exists that bridges the tension. Without explicit alignment, Finance may demand early gate closure or budget cuts (e.g., single accent, 3,000-word lexicon, off-the-shelf instruments) that weaken R&D's evidence base, triggering disputes at Month 9-12 (2027-07-13 to 2027-10-13) when trade-offs must be finalized for Phase 2. The misalignment directly threatens gate credibility at Month 24 (2028-10-13): if a budget squeeze forces cheaper measurement instruments or thinner rule validation, stakeholders can later claim the go/no-go decision was under-evidenced.

Mitigation: Editorial Board (Chair, Finance Lead, R&D Lead): Co-author a one-page Shared OKR by Month 3 (2027-01-13) specifying a joint success metric (e.g., 'Deliver defensible gate metrics validated on >=80 per-arm pilots within the $1.2M Phase 2 budget, with no instrument cost exceeding $200K or rule specification cost exceeding $400K'). Establish monthly Steering Meetings (Months 3-12 = 2027-01-13 to 2027-10-13) with Finance Lead and R&D Lead to jointly review actuals, trade-offs and forward forecast. Lock rule specifications and gate metrics jointly by Month 10 (2027-08-13), ensuring Finance sign-off on instrument costs and R&D sign-off on timeline constraints.

19. No Adaptive Framework

Does the plan lack a clear process for monitoring progress and managing changes, treating the initial plan as final?

Level: 🛑 High

Justification: Rated HIGH because critical controls are missing: (1) No unified KPI dashboard with defined review cadence, owners, and escalation thresholds. Monitoring activities ('monthly reviews,' 'quarterly panels') are scattered across documents but lack assigned accountability, formal chartering, or decision authority. (2) No mid-project change-control process specifying who approves scope changes (e.g., multi-accent audio, lexicon expansion), at what cost/schedule thresholds escalation is triggered, or how scope creep is rejected. Decision 10 addresses post-v1.0 versioning, not in-flight control. (3) Vague monitoring language: 'we will monitor trends quarterly' without automatic response protocols or stop rules integrated into active governance. (4) STOP rules exist in the premortem but are contingency plans, not active KPI dashboard feedback triggers. Without a unified, high-cadence feedback loop with owners and escalation authority, cost overruns, recruitment shortfalls, and measurement failures risk discovery only at Months 9-12 (2027-07-13 to 2027-10-13) or later, eliminating corrective action windows.

Mitigation: Program Lead: Establish by Month 1 (2026-11-13) a Monthly KPI Dashboard Charter specifying: (1) KPI universe (enrollment trend, dropout rate, spend variance, rater kappa trend, rule-dispute velocity); (2) Review cadence (monthly executive dashboard review, escalation board meeting if any KPI drifts >10% from baseline); (3) Owners (Budget Owner, Cohort Manager, Psychometrician, Board Chair); (4) Change-control gate (Scope Change Request form with cost/schedule impact; approval authority by Editorial Board if cost >$25K or schedule >2 weeks). Implement dashboard in Month 2 (2026-12-13) with automatic weekly updates and monthly board briefings. Integrate STOP rules as auto-triggered escalations (e.g., if cumulative spend >$175K pre-gate, halt Phase 2 launch within 5 days).

20. Uncategorized Red Flags

Are there any other significant risks or major issues that are not covered by other items in this checklist but still threaten the project's viability?

Level: 🛑 High

Justification: Rated HIGH because the plan contains at least three High-severity risks with strong coupling: (1) Pilot Recruitment/Retention shortfall (Likelihood high: 35–45% adult dropout vs. 30% plan assumption) cascades to sample-size loss <80 per arm, invalidating statistical power for all four gate metrics (ordinal error, comprehension speed, pronunciation consistency, retention); (2) Gate-threshold pre-registration delay or weak psychometric validation (Likelihood medium-high: psychometrician not yet hired, power analysis not due until Month 5 = 2027-03-13, pre-registration Month 11 = 2027-09-13) renders the Month 24 (2028-10-13) go/no-go scientifically disputable, triggering stakeholder rejection and 20–30% Phase 3 adoption loss; (3) Unfunded post-v1.0 stewardship ($150K–$250K/year, estimate, no steward commitment planned until Month 30 = 2029-04-13) causes standard atrophy within 12–24 months, reducing Phase 3 adopters from ≥3 target to 1–2, negating $600K–$1M in adoption value. A single common-mode trigger is the Phase 2 extension: if pilot recruitment/retention shortfall forces a 3–6 month Phase 2 extension ($300K–$600K), it consumes the entire $350K reserve and compresses stewardship negotiation from 6–9 months (Months 24–33 = 2028-10-13 to 2029-07-13) to 3 months (Months 30–33 = 2029-04-13 to 2029-07-13), making steward commitment unachievable before v1.0 release (Month 30 = 2029-04-13). Alternatively, if inter-rater kappa <0.70 at Month 10 (2027-08-13) forces a 4-week Phase 1 extension ($85K), it consumes 48% of the pre-gate $175K draw cap, leaving only $90K headroom for recruitment contingency ($20K–$30K) or psychometric rework ($50K+), forcing either a budget shortfall or scope cut (e.g., 4,000-word lexicon instead of 5,000, violating user constraint). The three risks are tightly coupled: underpowered recruitment threatens gate credibility, which threatens stewardship commitment, which threatens post-v1.0 viability; technical measurement failures (kappa, power analysis) threaten gate defensibility, which threatens adopter confidence, which threatens stewardship funding. No single dependency is documented to separately mitigate all three.

Mitigation: Risk Integration Owner: establish by Month 1 (2026-11-13) a living Cascade Risk Dashboard mapping the three High risks (Recruitment, Gate Defensibility, Stewardship Funding) with explicit dependencies: (1) Forecast completers <320 (or enrolment below 460) at the Month 12-13 (2027-10-13 to 2027-11-13) audit → automatic trigger for Phase 2 extension by Month 15 (2028-01-13) decision → stewardship negotiation compressed to 3 months (Months 30–33 = 2029-04-13 to 2029-07-13) → contingency: defer v1.0 release from Month 30 (2029-04-13) to Month 36 (2029-10-13) to secure MOU; (2) Kappa <0.70 at Month 10 (2027-08-13) → automatic 4-week Phase 1 extension request ($85K draw) → $90K remaining pre-gate headroom insufficient for both recruitment + psychometric rework → contingency: activate hybrid synthetic-baseline model immediately and reduce Phase 1 extension to 2 weeks; (3) Stewardship commitment not secured by Month 30 (2029-04-13) → v1.0 release conditional on signed MOU or deferred to Month 36 (2029-10-13) → automatic board decision rule within 5 days of Month 30 (2029-04-13). Publish dashboard monthly and escalate if any cascade threshold is crossed.

Part 3: Audit trail

What was checked, and how.

Check Method Covers Result
Against sources Web search Sections that searched: Premise Attack (11) 11 searches. Other real-world figures (prices, costs, market sizes, laws, precedents) were not verified.
Canonical facts Reconciled, then the table's own arithmetic re-checked 45 key numbers and dates 3 from your prompt, 19 decisions, 12 proposed thresholds, 11 estimates.
Internal consistency Lint against the canonical facts, then repair and re-lint Executive Summary, Pitch, Premortem, Project Plan, Review Plan, Self Audit and the assumptions (summary version) Before repair: 3 high / 3 medium. After: 0 high / 3 medium, plus 6 needing a decision (see Decisions Required).
Arithmetic Deterministic re-computation Every written calculation ("a x b = c") in 20 sections 28 checked, 1 wrong.
Calendar Deterministic Every "Month N" paired with a date Dates recomputed from the plan start (Month 0).
Schedule Deterministic Gantt and WBS Computed from the estimated durations and dependencies.

By section

Section Checks applied
Decisions Required derived from the consistency check
Canonical Facts reconciled across documents; own arithmetic re-checked; arithmetic (23 calculations, 1 wrong)
Executive Summary consistency lint and repair
Pitch consistency lint and repair
Project Plan consistency lint and repair
Strategic Decisions none
Scenarios none
Assumptions arithmetic (1 calculation, 0 wrong)
Governance arithmetic (1 calculation, 0 wrong)
Related Resources none
Data Collection arithmetic (1 calculation, 0 wrong)
Documents to Create and Find none
SWOT Analysis none
Team none
Expert Criticism arithmetic (2 calculations, 0 wrong)
Review Plan consistency lint and repair
Questions & Answers none
Premortem consistency lint and repair
Self Audit consistency lint and repair
Premise Attack web search (11 searches)

Arithmetic errors

Stated results that do not match their own calculation:

Section Statement Stated Computed
Canonical Facts $85K (1.1M/12 x 0.923 months = 1.1M x 4/52 1.1M 84.61k

Contradictions between the core documents, after repair.

Consistency: first pass found 3 high / 3 medium / 1 low contradictions. Repair: round 1: 42 edits → 1 high / 4 medium; round 2: 42 edits → 0 high / 3 medium. Published: round 2 (fewest high-severity issues). Shown below: the final check of the repaired documents (0 high / 3 medium / 3 low).

1. Reserve cannot fund the extensions and top-ups charged to it (🔴 High) — needs a project decision

2. Steward receives the $0.35M reserve vs stewardship unfunded (🔴 High) — needs a project decision

3. Safety-critical cohort deferral vs 4-arm, 320-completer gate and conflicting triggers (🔴 High) — needs a project decision

4. Steward fallback: cancel v1.0 at Month 33 vs defer to Month 36 or later (🔴 High) — needs a project decision

5. Underpowered/inconclusive pilot treated as NO-GO or 'false-negative gate' (🟡 Medium)

6. Baseline recruitment study precedes ethics, consent and partner commitments (🟡 Medium) — needs a project decision

7. Ordinal spoken form locked in the same month as the kappa check that depends on it (🟡 Medium) — needs a project decision

8. Enrolment audit month, tripwires and dropout units (🟡 Medium)

9. Psychometrics timeline: lead-time arithmetic and what is 'due' when (🟡 Medium)

10. Pre-gate headroom and percentage arithmetic (⚪ Low)

11. Cohort manager timing and ownership gap (⚪ Low)

12. Stewardship roadmap horizon: 5-year vs 10-year (⚪ Low)

Summary

The plan is largely consistent on its core structure: budget split, 4-arm design, gate rule, Month 30 release conditional on a steward commitment, and the 10% morphology/accent/ordinal design choices. Most earlier fixes have held. The remaining problems are concentrated in funding and fallback logic: the $0.35M reserve is claimed by several competing uses, safety-cohort and steward fallbacks are unresolved, and an extension after invalid data has no stated source of funds. Several lower-level timing and arithmetic slips (enrolment audit month, ordinal lock vs kappa check, headroom percentages) are fixable by editing to the canonical values. The user's intelligibility constraint (at least 90% of control accuracy within 2 weeks) is not operationalized as a gate metric in any document.

How the canonical facts were reconciled

The budget split ($1.1M + $1.2M + $0.85M + $0.35M = $3.5M) and the 8.6%, 86%, 115-per-arm and 460-learner figures recompute correctly and were kept. Corrected: participant costs summed only two of five listed lines ($78K-$161K) and now total $208K-$351K; the Phase 1 staff envelope was overstated ($0.7M-$0.8M) and is now about $0.5M-$0.7M after non-staff lines; the Phase 1 exit kappa (0.75) was aligned with the 0.70 floor used by the fallback and Phase 2 validity rule; the pre-gate draw cap leaves at least half (not 'most') of the reserve returnable; a garbled date/text fragment in the stewardship basis was repaired. Added a free-reserve fact because the same $350K reserve was implicitly counted against both the 4-week Phase 1 extension ($85K) and the 3-month Phase 2 extension ($300K), which together exceed it by $35K; the separate lexicon-reduction fallback was merged into the audio fact to stay within the fact limit, and the $20/entry trigger vs. $24/entry upper budget, partner-capacity sizing and the freeze running past Month 36 (2029-10-13) were flagged in basis fields.

Initial Prompt

Plan:
Design and launch a new standardized variant of English (“Clear English”) that fixes high‑friction inconsistencies across ordinals, spelling‑to‑sound, irregular morphology, and ambiguous homographs, while remaining intelligible to current English speakers. The goal is a parallel standard for education, ESL, technical writing, and safety‑critical documentation—not a wholesale replacement of English.

Define a three‑year program with gated phases. Phase 1 (12 months) specifies the rules and produces a reference corpus; Phase 2 (12 months) pilots learning materials and tests usability; Phase 3 (12 months) publishes a public standard and launches limited‑scope adoption.

Scope and constraints:
- Intelligibility: average adult comprehension within 2 weeks of exposure.
- Ordinals: remove special cases (11th/12th/13th; 1st/2nd/3rd; 21st/31st patterns). Choose one approach: (A) numeric + invariant ordinal marker, or (B) fully spelled ordinals with regularized endings; justify.
- Spelling‑to‑sound: define a minimal, consistent grapheme‑to‑phoneme mapping; keep Latin alphabet; diacritics optional but must be minimal and justified.
- Morphology: regularize a defined subset of irregular verbs and plurals (e.g., go/went, mouse/mice), but cap changes to preserve recognizability. Specify a threshold for when irregular forms are retained.
- Homographs and homophones: introduce disambiguation rules or optional markers for a limited list of high‑impact pairs (e.g., lead/lead, read/read), with a clear policy for when disambiguation is required.
- Core lexicon: 5,000 words with regularized pronunciation guidance and a mapping from standard English.
- Avoid aggressive scenarios: no mandates, no immediate K‑12 replacement, no universal adoption claims.
- Pilot cohorts: adult ESL learners and native speakers using a safety‑critical or technical glossary.
- Budget: $3.5M total across three years (propose a realistic split).

Deliverables:
- “Clear English Standard v1.0” with formal rule set and rationale.
- Reference dictionary (word list + pronunciation guidance + mappings).
- Style guide covering ordinals, disambiguation markers, and regularized morphology.
- Pilot curriculum (print + digital) with assessments.
- Public licensing policy enabling third‑party adoption.

Define governance (editorial board + linguistic review), risk register (educator pushback, rule ambiguity, fragmentation), and outreach plan (academic partners, ESL publishers, standards orgs). Include a clear go/no‑go decision point after Phase 2 based on pilot data (comprehension speed, ordinal error rate, pronunciation consistency score, learner retention after 30 days).

Optimize for user adoption. Don't optimize for linguistic purity.
Don't pick the most aggressive scenario.

Today's date:
2026-Oct-13

Project start ASAP

Prompt Screening

Verdict: 🟢 USABLE

Rationale: The prompt describes a concrete, detailed three-year program to design and launch a standardized English variant, with phases, scope constraints, a $3.5M budget, deliverables, governance, and decision gates. It is ambitious but specific and plannable.

Redline Gate

Verdict: 🟢 ALLOW

Rationale: The prompt requests a benign project plan for a standardized, optional English variant for education and technical writing; it carries no harm potential or operational risk.

Violation Details

Detail Value
Capability Uplift No

Premise Attack

Why this fails.

Premise Attack 1 — Integrity

Forensic audit of foundational soundness across axes.

[STRATEGIC] A third, invented English variant that must stay readable to current speakers yet re-spell, re-pronounce and re-inflect 5,000 words has no buyer: the one niche where a controlled English works already has a governed standard, and everywhere else learners need the English that people actually speak.

Bottom Line: REJECT: A parallel 'Clear English' for ESL and safety-critical writing duplicates an established standard in the only niche that needs it and asks learners to master a variant that nobody else uses.

Reasons for Rejection

Second-Order Effects

Evidence

Premise Attack 2 — Accountability

Rights, oversight, jurisdiction-shopping, enforceability.

[STRATEGIC] — Fork In The Cockpit: a new spelling, ordinal and verb-form variant aimed at safety-critical documentation adds a second reading standard to the one place where a reader cannot afford to wonder which standard a page is written in, and it attacks the spelling layer when the controlled-language layer that already serves technical writing is what matters.

Bottom Line: REJECT: Fork In The Cockpit puts a second, unrecognised spelling standard into the documents where only one can be trusted, and past English-reform efforts suggest it would end up as a stranded dialect with a small user base. The need for clearer technical English is real, but this premise does not meet it.

Reasons for Rejection

Second-Order Effects

Evidence

Premise Attack 3 — Spectrum

Enforced breadth: distinct reasons across ethical/feasibility/governance/societal axes.

[STRATEGIC] A voluntary English variant must out-compete both standard English and an incumbent technical-writing standard, yet offers learners a dead-end dialect and safety documents a fresh misreading hazard.

Bottom Line: REJECT: A voluntary, unmandated English variant with $3.5M and three years cannot displace standard English or the established technical-English standard, and its only certain product is one more convention that safety-critical readers must tell apart from the original.

Reasons for Rejection

Second-Order Effects

Evidence

Premise Attack 4 — Cascade

Tracks second/third-order effects and copycat propagation.

This is a strategic flaw: a fourth, privately authored orthography is proposed as a "parallel standard" to a language whose entire value is that everyone else already uses the incumbent form. Every learner and safety-critical reader would have to master Clear English and still be fluent in Standard English, so the product has negative marginal value for exactly the audiences it targets, and the "optimize for adoption" goal is contradicted by the design itself.

Bottom Line: Abandon the premise: do not create a new variant of English with new spellings, because a second system that users must learn on top of the first has negative adoption value regardless of how well the rules are written. If the real aim is clarity in ESL and safety-critical documents, the premise of re-spelling English is the source of the failure, not the governance, budget or phasing.

Reasons for Rejection

Second-Order Effects

Evidence

Premise Attack 5 — Escalation

Narrative of worsening failure from cracks → amplification → reckoning.

[STRATEGIC] — Orphan Dialect Trap: A voluntary, mandate-free English variant that is close enough to standard English to be 'intelligible in two weeks' yet different enough to need teaching is born with no installed base, no regulator, and no employer, so the more it fixes, the less anyone can use it.

Bottom Line: REJECT: A voluntary, near-English variant with no authority, no installed base and no customer demanding it cannot be both easy enough to adopt and different enough to matter, and it would turn learners and safety documentation into the unwilling test population for that contradiction. The gate is closed.

Reasons for Rejection

Second-Order Effects

Evidence

Overall Adherence: 99%

IMPORTANCE_ADHERENCE_SUM = (5×5 + 5×5 + 5×5 + 5×5 + 5×5 + 5×5 + 5×5 + 5×5 + 4×4 + 5×5 + 5×5 + 4×5 + 4×5 + 5×5 + 5×5) = 356
IMPORTANCE_SUM = 5 + 5 + 5 + 5 + 5 + 5 + 5 + 5 + 4 + 5 + 5 + 4 + 4 + 5 + 5 = 72
OVERALL_ADHERENCE = IMPORTANCE_ADHERENCE_SUM / (IMPORTANCE_SUM × 5) = 356 / 360 = 99%

Summary

ID Directive Type Importance Adherence Category
1 Design and launch a new standardized variant of English ('Clear English') fixing high‑friction inconsistencies: ordinals, spelling‑to‑sound, irregular morphology, and ambiguous homographs. Requirement 5/5 5/5 Fully honored
2 Parallel standard for education, ESL, technical writing, safety‑critical documentation—not a wholesale replacement of English. Constraint 5/5 5/5 Fully honored
3 Three‑year program (36 months) with gated phases: Phase 1 (12 months, Months 0–12 = 2026-10-13 to 2027-10-13) rules + corpus; Phase 2 (12 months, Months 12–24 = 2027-10-13 to 2028-10-13) pilots; Phase 3 (12 months, Months 24–36 = 2028-10-13 to 2029-10-13) public standard + limited adoption. Constraint 5/5 5/5 Fully honored
4 Total budget: $3.5M across 36 months (USD). Constraint 5/5 5/5 Fully honored
5 Intelligibility: average adult comprehension of Clear English within 2 weeks of exposure must be >=90% of standard-English control accuracy. Requirement 5/5 5/5 Fully honored
6 Ordinals: remove special cases (11th/12th/13th; 1st/2nd/3rd; 21st/31st). Choose and justify one approach: (A) numeric + invariant marker, or (B) fully spelled with regularized endings. Requirement 5/5 5/5 Fully honored
7 Spelling‑to‑sound: define minimal, consistent grapheme‑to‑phoneme mapping; keep Latin alphabet; diacritics optional but minimal and justified. Requirement 5/5 5/5 Fully honored
8 Morphology: regularize a defined subset of irregular verbs and plurals; cap changes to preserve recognizability; specify threshold for when irregulars are retained. Requirement 5/5 5/5 Fully honored
9 Homographs and homophones: introduce disambiguation rules or optional markers for limited list of high‑impact pairs (e.g., lead/lead, read/read); define policy for when disambiguation is required. Requirement 4/5 4/5 Partially honored
10 Core lexicon: 5,000 words with regularized pronunciation guidance and mapping from standard English. Requirement 5/5 5/5 Fully honored
11 Avoid: no mandates, no immediate K‑12 replacement, no universal adoption claims. Do not optimize for linguistic purity; optimize for user adoption. Banned 5/5 5/5 Fully honored
12 Pilot cohorts: adult ESL learners and native speakers using safety‑critical or technical glossary (Phase 2, Months 12–24 = 2027-10-13 to 2028-10-13). Requirement 4/5 5/5 Fully honored
13 Define governance (editorial board + linguistic review), risk register, and outreach (academic partners, ESL publishers, standards orgs). Requirement 4/5 5/5 Fully honored
14 Clear go/no‑go decision point at Month 24 (2028-10-13) after Phase 2 based on pilot data: comprehension speed, ordinal error rate, pronunciation consistency score, 30‑day learner retention. Requirement 5/5 5/5 Fully honored
15 Deliverables: Clear English Standard v1.0 (formal rule set + rationale), reference dictionary, style guide, pilot curriculum (print + digital), public licensing policy. Requirement 5/5 5/5 Fully honored

Issues

Issue 9 - Homographs and homophones: introduce disambiguation rules or optional markers for limited list of high‑impact pairs (e.g., lead/lead, read/read); define policy for when disambiguation is required.

Which generator version and models produced each part.

Generator

Stages

Stage Generated at Generator Models LLM calls
screen_planning_prompt 2026-10-13T01:23:37 v2.0.6 claude-sonnet-5-5 1
setup 2026-10-13T01:23:33 v2.0.6 - 0
extract_constraints 2026-10-13T01:23:50 v2.0.6 claude-sonnet-5-5 1
identify_purpose 2026-10-13T01:23:39 v2.0.6 claude-sonnet-5-5 1
premise_attack 2026-10-13T01:25:25 v2.0.6 claude-sonnet-5-5 5
redline_gate 2026-10-13T01:23:43 v2.0.6 claude-sonnet-5-5 1
classify_domain 2026-10-13T01:24:55 v2.0.6 claude-sonnet-5-5 4
plan_type 2026-10-13T01:25:03 v2.0.6 claude-sonnet-5-5 1
potential_levers 2026-10-13T01:29:59 v2.0.6 claude-sonnet-5-5 23
potential_levers_constraint 2026-10-13T01:30:44 v2.0.6 claude-sonnet-5-5 1
triage_levers 2026-10-13T01:30:22 v2.0.6 claude-sonnet-5-5 1
enrich_levers 2026-10-13T01:30:48 v2.0.6 claude-sonnet-5-5 3
triaged_levers_constraint 2026-10-13T01:31:09 v2.0.6 claude-sonnet-5-5 1
enriched_levers_constraint 2026-10-13T01:31:33 v2.0.6 claude-sonnet-5-5 1
focus_on_vital_few_levers 2026-10-13T01:31:09 v2.0.6 claude-sonnet-5-5 1
candidate_scenarios 2026-10-13T01:32:15 v2.0.6 claude-sonnet-5-5 1
strategic_decisions_markdown 2026-10-13T01:31:09 v2.0.6 - 0
vital_few_levers_constraint 2026-10-13T01:31:46 v2.0.6 claude-sonnet-5-5 1
candidate_scenarios_constraint 2026-10-13T01:32:57 v2.0.6 claude-sonnet-5-5 1
select_scenario 2026-10-13T01:32:30 v2.0.6 claude-sonnet-5-5 1
scenarios_markdown 2026-10-13T01:32:30 v2.0.6 - 0
selected_scenario_constraint 2026-10-13T01:33:05 v2.0.6 claude-sonnet-5-5 1
physical_locations 2026-10-13T01:32:41 v2.0.6 claude-sonnet-5-5 1
currency_strategy 2026-10-13T01:32:48 v2.0.6 claude-haiku-4-5-20251001 1
identify_risks 2026-10-13T01:34:40 v2.0.6 claude-haiku-4-5-20251001 1
make_assumptions 2026-10-13T01:35:02 v2.0.6 claude-sonnet-5-5 1
distill_assumptions 2026-10-13T01:35:10 v2.0.6 claude-sonnet-5-5 1
review_assumptions 2026-10-13T01:36:02 v2.0.6 claude-haiku-4-5-20251001 1
consolidate_assumptions_markdown 2026-10-13T01:37:58 v2.0.6 claude-haiku-4-5-20251001 9
pre_project_assessment 2026-10-13T01:39:35 v2.0.6 claude-haiku-4-5-20251001 1
canonical_facts 2026-10-13T01:44:54 v2.0.6 claude-sonnet-5-5 2
project_plan 2026-10-13T01:45:33 v2.0.6 claude-sonnet-5-5 1
create_wbs_level1 2026-10-13T01:45:37 v2.0.6 claude-haiku-4-5-20251001 1
governance_phase1_audit 2026-10-13T01:46:09 v2.0.6 claude-haiku-4-5-20251001 1
related_resources 2026-10-13T01:45:59 v2.0.6 claude-sonnet-5-5 1
find_team_members 2026-10-13T01:46:30 v2.0.6 claude-haiku-4-5-20251001 1
governance_phase2_bodies 2026-10-13T01:47:46 v2.0.6 claude-haiku-4-5-20251001 1
swot_analysis 2026-10-13T01:46:21 v2.0.6 claude-sonnet-5-5 1
enrich_team_members_with_contract_type 2026-10-13T01:46:52 v2.0.6 claude-haiku-4-5-20251001 1
expert_review 2026-10-13T01:50:29 v2.0.6 claude-haiku-4-5-20251001 10
governance_phase3_impl_plan 2026-10-13T01:52:51 v2.0.6 claude-haiku-4-5-20251001 1
enrich_team_members_with_background_story 2026-10-13T01:47:33 v2.0.6 claude-haiku-4-5-20251001 1
governance_phase4_decision_escalation_matrix 2026-10-13T01:53:23 v2.0.6 claude-haiku-4-5-20251001 1
enrich_team_members_with_environment_info 2026-10-13T01:50:18 v2.0.6 claude-haiku-4-5-20251001 1
governance_phase5_monitoring_progress 2026-10-13T01:54:52 v2.0.6 claude-haiku-4-5-20251001 1
governance_phase6_extra 2026-10-13T01:55:37 v2.0.6 claude-haiku-4-5-20251001 1
review_team 2026-10-13T01:54:58 v2.0.6 claude-haiku-4-5-20251001 1
consolidate_governance 2026-10-13T01:55:37 v2.0.6 - 0
team_markdown 2026-10-13T01:54:58 v2.0.6 - 0
data_collection 2026-10-13T02:01:18 v2.0.6 claude-haiku-4-5-20251001 1
identify_documents 2026-10-13T02:01:27 v2.0.6 claude-haiku-4-5-20251001 1
create_wbs_level2 2026-10-13T02:01:45 v2.0.6 claude-haiku-4-5-20251001 1
filter_documents_to_create 2026-10-13T02:01:51 v2.0.6 claude-sonnet-5-5 1
filter_documents_to_find 2026-10-13T02:02:08 v2.0.6 claude-haiku-4-5-20251001 1
draft_documents_to_create 2026-10-13T02:06:22 v2.0.6 claude-haiku-4-5-20251001 11
draft_documents_to_find 2026-10-13T02:04:55 v2.0.6 claude-haiku-4-5-20251001 5
identify_task_dependencies 2026-10-13T02:02:15 v2.0.6 claude-haiku-4-5-20251001 1
wbs_project_level1_and_level2 2026-10-13T02:01:45 v2.0.6 - 0
create_pitch 2026-10-13T02:02:20 v2.0.6 claude-haiku-4-5-20251001 1
estimate_task_durations 2026-10-13T02:05:29 v2.0.6 claude-haiku-4-5-20251001 16
markdown_with_documents_to_create_and_find 2026-10-13T02:06:22 v2.0.6 - 0
convert_pitch_to_markdown 2026-10-13T02:05:17 v2.0.6 claude-haiku-4-5-20251001 1
create_wbs_level3 2026-10-13T02:08:52 v2.0.6 claude-haiku-4-5-20251001 40
wbs_project_level1_and_level2_and_level3 2026-10-13T02:08:52 v2.0.6 - 0
create_schedule 2026-10-13T02:08:53 v2.0.6 - 0
review_plan 2026-10-13T02:14:04 v2.0.6 claude-haiku-4-5-20251001 16
executive_summary 2026-10-13T02:14:57 v2.0.6 claude-haiku-4-5-20251001 1
questions_and_answers 2026-10-13T02:17:28 v2.0.6 claude-haiku-4-5-20251001 2
premortem 2026-10-13T02:18:43 v2.0.6 claude-sonnet-5-5 3
prompt_adherence 2026-10-13T02:15:42 v2.0.6 claude-haiku-4-5-20251001 2
self_audit 2026-10-13T02:24:48 v2.0.6 claude-haiku-4-5-20251001 20
consistency_review 2026-10-13T02:29:05 v2.0.6 claude-sonnet-5-5 1
consistency_repair 2026-10-13T02:37:57 v2.0.6 claude-sonnet-5-5 13
decision_register 2026-10-13T02:38:23 v2.0.6 claude-sonnet-5-5 1
arithmetic_check 2026-10-13T02:38:23 v2.0.6 - 0