Solicitation 26RF0010901 · EDC prime · BrightQuery technical subcontractor

The two-year plan

All 181 contracted capabilities - 179 distilled from the RFP and its Environmental Scan, plus two the EDC statement of work added - assigned to a phase of the engagement and sized as a full production build. Nothing here presumes prior work; every line traces back to the solicitation on demand. Following EDC's deliverable calendar: Year 1 specifies, validates with alpha prototypes, and delivers the functional prototype platform; Year 2 runs the classroom beta, produces the lessons, connects the classroom, and launches.

These rows are capabilities, not technical features: one row per promise the solicitation extracts, the unit of traceability and pricing. At build time each decomposes into roughly five to ten technical features, so the sprint-level backlog behind this plan runs past a thousand stories. Capabilities are the language of the contract; stories are the language of the sprint.

01

The engagement at a glance

Contracted capabilities

181

179 from the solicitation + 2 EDC-SOW-added; each unpacks into 5-10 technical features

Timeline

24 mo

four phases, three hard gates

Platform engineering

950 wk

midpoint engineer-weeks (511 - 1,400 range)

Management plan

31

process obligations spanning both years

02

The shape of two years

EDC's calendar, adopted as ours: Year 1 (Oct 2026 - Sep 2027) specifies, validates with teachers through alpha prototypes, and delivers the Functional Prototype Platform - the Year-1 contract deliverable and the renewal point. Year 2 (Oct 2027 - Sep 2028) runs the classroom beta, produces the 24 lessons, proves the connector, completes the testing package, and launches. Three gates keep it honest.

Y1A · Specify + alphaOct 26-Mar 27 · 24 obligationsURS + functionality + tech specscontent audit + selection rubricalpha prototypes with teachersY1B · Prototype buildApr-Sep 27 · 72 obligationsthe Functional Prototype (1.7)modular APIs · discovery · authoringeducator sessions on real dataY2A · Beta + contentOct 27-Mar 28 · 24 obligationsclassroom beta cohort (2.2)24 lessons + templates (2.3)Google Classroom connector (2.4)Y2B · LaunchApr-Sep 28 · 30 obligationsfull test package on SI infraLearning Lab 2.0 launch (2.7)promotion + summative reportsspecs approvedprototype delivered + renewallaunch + acceptanceProcess lane · 31 management-plan obligations · TRB gates, draft/final review windows, teacher validation, comms · M1-M24
PhaseEntry criteriaExit criteria
Y1A · Specify + alpha (Oct 26 - Mar 27)Subcontract executed; content strategy approved (CS-01); Smithsonian access provisioned (EDAN/DAMS, environments)GATE 1 - specifications: User Requirements, Functionality, and Technical/Integration Specifications SI-approved (EDC 1.2/1.4/1.5); content audit + resource-selection rubric delivered (1.3); alpha-prototype findings documented with teachers (1.6); PIAs + privacy notice complete (SP-04)
Y1B · Prototype build (Apr - Sep 27)Gate 1 passed; approved specifications govern the buildGATE 2 - the Year-1 deliverable and renewal point: Functional Prototype Platform delivered (1.7) - modular API architecture, educator-centered discovery and authoring, engagement analytics baseline; interim vulnerability scan passed before educator sessions (SP-01); Year-2 plan agreed (2.1)
Y2A · Beta + content (Oct 27 - Mar 28)Year-2 renewal; beta cohort recruited and onboarded (BETA-01/02)Beta cohort cycles underway in classrooms with iterative releases (2.2); 24 exemplar lessons (12 social studies + 12 science) published through human review (2.3); the Google Classroom connector live end to end (2.4)
Y2B · Launch (Apr - Sep 28)Beta evidence in hand; connector provenGATE 3 - acceptance and launch: full accessibility/security/performance/acceptance package passed on Smithsonian infrastructure (2.5); Learning Lab 2.0 launched (2.7); promotion (2.6) and summative (2.8) reports delivered

M3

URS + functionality specifications drafted; first alpha prototypes in teacher sessions

M6

Gate 1: specifications SI-approved; alpha findings shape the prototype build

M9

Prototype platform feature-complete in staging; interim security scan passed

M12

Gate 2: Functional Prototype Platform delivered; Year-2 go/no-go and plan

M15

Beta cohort live in classrooms; first exemplar lessons through human review

M18

24 lessons published; Google Classroom connector proven end to end

M21

Full accessibility/security/performance package on Smithsonian infrastructure

M24

Gate 3: Learning Lab 2.0 launched; summative report delivered

03

Where the work lands

All fifteen solicitation domains, placed on EDC's calendar. Year 1 carries the specification and prototype weight; content production, the cohort, the connector, and launch land in Year 2. Migration sits beyond the deliverable set entirely - a flagged expansion, tracked in the risk register (R12).

04

The work, broken down

The work breakdown structure: each phase decomposed into its workstreams, with item counts and midpoint engineer-weeks. Every leaf is an obligation in the browsable table at the bottom, so the WBS, the charts, and the traceability register are one dataset.

W1.1Y1A · Specify and validate

Oct 26-Mar 27

W1.1.1Content strategy3 items~15 ew
W1.1.2Discovery & search1 item~12 ew
W1.1.3Authoring & templates3 items~22 ew
W1.1.4Object-based learning1 item~1 ew
W1.1.5Distribution & integration2 items~10 ew
W1.1.6Standards alignment1 item~5 ew
W1.1.8Accessibility & equity1 item~1 ew
W1.1.10Architecture & portability4 items~34 ew
W1.1.11Security & privacy7 items~26 ew
W1.1.12Analytics1 item~5 ew

W1.2Y1B · Prototype Platform Build

Apr-Sep 27

W1.2.1Content strategy6 items~40 ew
W1.2.2Discovery & search6 items~51 ew
W1.2.3Authoring & templates10 items~49 ew
W1.2.4Object-based learning8 items~61 ew
W1.2.5Distribution & integration2 items~24 ew
W1.2.6Standards alignment6 items~25 ew
W1.2.7Teacher & student UX12 items~72 ew
W1.2.8Accessibility & equity4 items~34 ew
W1.2.9Governance & trust5 items~21 ew
W1.2.10Architecture & portability2 items~24 ew
W1.2.11Security & privacy3 items~15 ew
W1.2.12Analytics7 items~42 ew
W1.2.16Beta program1 item~5 ew

W2.1Y2A · Beta, content, connect

Oct 27-Mar 28

W2.1.1Content strategy3 items~15 ew
W2.1.2Discovery & search3 items~15 ew
W2.1.3Authoring & templates1 item~1 ew
W2.1.4Object-based learning1 item~5 ew
W2.1.5Distribution & integration1 item~5 ew
W2.1.6Standards alignment1 item~5 ew
W2.1.7Teacher & student UX2 items~10 ew
W2.1.8Accessibility & equity3 items~15 ew
W2.1.9Governance & trust3 items~15 ew
W2.1.10Architecture & portability2 items~24 ew
W2.1.12Analytics2 items~6 ew
W2.1.14Process & delivery1 item~5 ew
W2.1.16Beta program1 item~5 ew

W2.2Y2B · Test, launch, report

Apr-Sep 28

W2.2.2Discovery & search2 items~10 ew
W2.2.4Object-based learning1 item~12 ew
W2.2.5Distribution & integration6 items~58 ew
W2.2.7Teacher & student UX1 item~12 ew
W2.2.8Accessibility & equity1 item~5 ew
W2.2.9Governance & trust1 item~5 ew
W2.2.10Architecture & portability3 items~11 ew
W2.2.12Analytics2 items~10 ew
W2.2.13Migration11 items~90 ew
W2.2.14Process & delivery1 item~12 ew
W2.2.15Promotion1 item~5 ew

W3PROC · Management plan

M1-M24

W3.1Content strategy2 itemsprocess
W3.4Object-based learning1 itemprocess
W3.6Standards alignment1 itemprocess
W3.8Accessibility & equity2 itemsprocess
W3.9Governance & trust3 itemsprocess
W3.10Architecture & portability1 itemprocess
W3.11Security & privacy4 items~1 ew
W3.13Migration1 itemprocess
W3.14Process & delivery14 itemsprocess
W3.15Promotion2 itemsprocess

05

The application it becomes

The same work, seen as the product: 22 navigational modules in five role-scoped workspaces, decomposed into 495 named features, every feature tracing to capability IDs. Modules appear per role and per subscription toggle, so the module catalog a buyer selects from maps one-to-one onto the navigation teachers, curators, and administrators actually see.

LIBRARY - find

teachers, curators

Home26 features
Discover42 features
Subjects14 features
Museums10 features
Standards16 features
Sets15 features

STUDIO - create

teachers, SI educators

Lesson Studio47 features
My Lessons12 features
Community13 · opens later

CLASSROOM - deliver

teachers, students

Teach10 features
Assignments22 features
Student App19 features

CURATION - steward

Smithsonian editors

Review23 features
Signals15 features
Coverage16 features
Corpus35 features
Policies20 features

OPERATIONS - run

OET, district IT

Insights31 features
People28 features
Connectors33 features
Migration29 · opens later
Settings19 features

How to read this

22 modules, 495 features, every feature tracing to capability IDs; counts are feature totals per module. The prototype year turns on the platform modules; content, cohort, connector, and launch features land in Year 2 per the EDC calendar. Community and Migration deliberately open later.

06

How big each phase is

Full-build engineering, sized per obligation (S under 2 engineer-weeks, M 2-8, L 8-16+) and rolled up with its uncertainty range. The prototype year carries ~594 midpoint engineer-weeks; the 31 process obligations run alongside as the management plan and carry no engineering weeks.

Whiskers span the per-obligation minimum and maximum; the label is the midpoint.

07

What each phase is made of

The same phases by effort class: many medium builds and a disciplined set of large ones, which is what makes each phase parallelizable across a team.

08

The team it takes

Three-point estimates rolled into an implied team size (26 productive weeks per phase, engineering only), and the scope baseline as a burn-up: what is planned complete at each gate. The prototype year builds steadily; the crunch is Y2A, where the beta, the 24 lessons, and the connector land together - carried in the risk register with a staged-pipeline mitigation.

Implied FTE per phase (unleveled)

Scope burn-up at each gate

Engineer-weeks measure engineering scope, not calendar or headcount commitments; the 31 process obligations and all content production ride outside these figures.

09

What sets the pace

The dependent chain that sets the schedule. The content pipeline feeds human review, privacy and security clear in parallel, and the three gates sit on this line - which is why those items get staffing priority from day one.

  1. Strategy approved

    CS-01

  2. Audit + rubric

    EDC 1.3

  3. Specifications

    1.2 / 1.4 / 1.5

  4. Alpha prototypes

    1.6 · with teachers

  5. GATE 1 · specs

    M6

  6. Prototype build

    1.7

  7. GATE 2 · prototype + renewal

    M12

  8. Beta + 24 lessons

    2.2 / 2.3

  9. Connector

    2.4

  10. Test package

    2.5

  11. GATE 3 · launch

    M24

The longest dependent chain. Everything else parallelizes around it; a slip on this chain moves a gate, so these items get staffing priority and weekly visibility.

10

Who does what

Responsibility assignment across the four parties. One accountable owner per workstream; the split mirrors the partnership: EDC leads pedagogy and the cohort, BrightQuery builds and operates the platform, the Smithsonian holds editorial and security authority.

WorkstreamSI OETSI OCIO / PrivacyEDC (prime)RLMGBrightQueryBeta teachers
Content strategy + audit (CS-01, CS-02)ARCI
Platform build: discovery, authoring, review and provenanceCACRI
Curation + publish decisions (GV-01)ACI
Standards alignment confirmation (ST-05)ARC
24 exemplar lessons (production)ARCCC
Integrations: Google Classroom (2.4) + connector menu (DI-01..06)IARI
Privacy: PIAs, COPPA, notices (SP-03..06)CACRI
Security testing (SP-01, SP-02)IACR
Beta cohort recruitment + operations (BETA-01)ARCC
Feedback synthesis + go/no-go evidence (CS-G2)ARCCC
Migration + continuity (MG-*)ACCR
Educator-facing UX design + front-end buildCARCI
PL videos + communities of practice (Y2)ARCCI

R responsible (does the work) · A accountable (one per row) · C consulted · I informed. EDC, as prime, is accountable for SOW deliverables; the Smithsonian holds editorial and security authority; BrightQuery is responsible for the platform; RLMG is responsible for the educator-facing interface design and front-end build. SI OET is the Smithsonian Office of Educational Technology (the program office); SI OCIO is the Office of the Chief Information Officer, paired with the Privacy Office.

11

Year 1 proves the design, Year 2 proves the classroom

The two years have different characters, and budgeting should read them differently.

Year 1 · specify + prototype · ~594 eng-wk

The specifications and alpha prototypes come first, validated with teachers before the build - then the Functional Prototype Platform: the modular API architecture, the educator-centered discovery and authoring experience, and the analytics baseline, on real Smithsonian data. Year 1 ends with working software and a renewal decision.

Year 2 · beta, content, launch · ~356 eng-wk platform

The classroom beta, the 24 exemplar lessons with educator templates, the Google Classroom connector, the full compliance package, and the launch. Year 2 also carries the operations the engineering figures do not price - content production, cohort operations, testing on Smithsonian infrastructure - which is where its budget weight sits.

12

Delivering the statement of work

Two mappings, one accounting: every element of the SOW summary lands on named capabilities, and every deliverable in EDC's 7.9.26 revision (1.1-1.7 in Year 1, 2.1-2.8 in Year 2) carries its share of them - so the deliverable set, the subcontract scope, and the solicitation stay one story.

EDC SOW elementYearCarried by
Curated subset: artifacts, subjects, grade bands, standardsY1CS-02, CS-03, DS-01, DS-02, ST-01
24 exemplar lessons (12 social studies + 12 science) across the four grade bandsY2CS-05, CS-06, AU-01..AU-12, OB-02, OB-08 (authoring platform lands Y1B)
Lesson-plan templatesY1CS-06, AU-03, AU-04, UX-08
Object-based learning supportsY1OB-01..OB-09 (CS-10 validates in the Y2A beta)
Aligned to selected standardsY1DS-04, ST-01..ST-06, UX-11
Integrations: ONE contracted connector (Google Classroom, EDC 2.4); Canvas/Kahoot as groundworkY2DI-02, AR-09 (DI-01 API lands Y1B; DI-03, DI-06 follow)
Teachers apply as beta testers; feedback; refineY2BETA-01, AN-01, AN-04, AX-09, PR-01, PR-02, CS-G2 (BETA-02 accounts land Y1B)
More artifacts, lessons, subjects, educator types, formatsY2CS-12, CS-G1, AU-14, UX-14, DS-09
More platform integrationsY2DI-04, DI-05, DI-06, DI-08
More sophisticated AI-enabled supportsY2AU-14, AX-06, AX-07 (each behind SP-03 privacy review)
PL videos, exemplar lesson videos, communities of practiceY2UX-12, AX-05, PR-G2 + Y2B platform hosting
Guidance: young children, multilingual learners, new to primary sourcesY2AX-06, AX-07, DS-09, UX-14
#EDC deliverableLeadYearWhat BrightQuery contributes
1.1Project Management & Success MetricsEDCY1metrics + telemetry plans, review points; Project Launch Report inputs
1.2User Journeys and Needs (URS, prototype)EDCY1technical assumptions, AI-readiness requirements, integration priorities
1.3Content Audit and Resource SelectionEDCY1audit pipeline, readiness rubric tooling, exclusion gates
1.4Functionality PrioritizationEDC + RLMGY1feasibility input to the Functionality Specifications
1.5Technical Systems & Platform Integration SpecsBQY1the SI-approved technical and integration specifications
1.6Iterative Development and Teacher Feedback (alpha)EDC + RLMGY1working alpha prototypes on real data behind the clickable flows
1.7Prototype Platform BuildBQ + RLMGY1the functional prototype: modular API architecture, discovery, authoring, analytics baseline
2.1Year-2 PM & Success MetricsEDCY2revised metrics + Year 2 timeline inputs
2.2Beta Testing and Iterative DevelopmentEDCY2iteration engineering behind cohort feedback cycles (the release pipeline lands with the Y1B prototype)
2.3Ready-to-Go Content (24 lessons: 12 SS + 12 Sci)EDCY2authoring pipeline + educator templates (both land with the Y1B prototype, so lesson production can start at renewal)
2.4Interoperability: one high-value platformBQY2the connector proven end to end (the DI-01 API and adapter architecture land in Y1B, ready for the Y2A build)
2.5Accessibility, Security, Performance, AcceptanceBQY2the full test package (interim security and accessibility gates run from Year 1; the formal package lands here)
2.6Promotion and MarketingEDCY2technical SEO/AEO groundwork feeding the report
2.7Launch of Learning Lab 2.0ALLY2the hardened initial public release with expansion potential
2.8Summative ReportEDCY2evidence, analytics, and next-step platform recommendations

Keyed to the EDC deliverables document, 7.9.26 revision (Year 1, Oct 2026 - Sep 2027 = prototype: alpha flows, then the functional prototype platform; Year 2, Oct 2027 - Sep 2028 = beta cohort, 24 lessons, one connector, the compliance package, launch). Parenthetical notes mark the platform groundwork this plan stages ahead of each deliverable; migration and identity-at-scale sit outside the deliverable set and are carried in the risk register (R12).

13

What could move the plan

Every risk carries a probability, an impact, a response strategy, and a single owner; the register is re-scored monthly in steering. Assumptions and the change-control rule sit alongside, so the scope baseline this plan defends is explicit.

P: low

P: medium

P: high

I: high

moderate

R3

serious

R1R2R8

critical

I: med

low

R9R10

moderate

R4R5R12R11

serious

I: low

low

R7

low

R6

moderate

Probability x impact; every risk carries a response and an owner in the register below. Re-scored monthly in steering.

#RiskPIResponseOwnerHandling in this plan
R1Legacy-Lab data-sharing agreement slips past M12MHMitigateEDC + SI OETMigration sits beyond the EDC deliverable set entirely; start the agreement early so expansion work can follow launch without a restart.
R2Privacy Office review delays a beta or AI featureMHMitigateBrightQuery + SI PrivacyPIAs, notice, and COPPA posture front-loaded in Y1A (SP-04..06); a recurring review step precedes each Y2 AI expansion (SP-03).
R3Security findings surface at beta go-liveLHMitigateBrightQueryInterim vulnerability scan precedes every educator session (alpha and prototype); high/medium findings fixed first; formal OCIO scans at acceptance.
R4Y1B build-peak staffing cannot be hired or sustainedMMMitigateBrightQueryRamp hiring through Y1A so the Y1B prototype-build peak is staffed; a second crunch lands in Y2A where beta, lessons, and the connector arrive together - stagger the pipelines and hire ahead of the renewal.
R5Beta identity scope creeps toward full SSOMMAvoidBrightQuery + EDCBETA-02 fixes the prototype year at invite-based accounts with basic roles; full SSO/rostering is planned Y2B (DI-04), with identity-at-scale tracked in R12.
R6Kahoot integration path is ambiguous (not an LTI consumer)MLMitigateBrightQuery + EDCKahoot rides the content API + share/embed paths (DI-01, DI-06); confirm the exact classroom workflow with the cohort and Kahoot before the Y2A connector build.
R7SOW lesson-matrix arithmetic (24 vs 18) creates scope disputeLLAvoidEDC + BrightQueryResolved 2026-07-08: the EDC deliverable set fixes the matrix at 12 social studies + 12 science; carry the number into the formal SOW.
R8Smithsonian-side dependencies late (EDAN/DAMS access, TRB slots, OCIO environments)MHMitigateSI OET + EDCNamed in the process lane from M1 (PR-04, AR-04..08); TRB reviews scheduled at phase boundaries; on-prem posture decided before Y2B testing.
R9The M12 renewal decision rests on prototype evidence only (beta arrives in Year 2)LMAcceptAll partiesMake the prototype sessions evidence-rich: structured educator tasks, instrumented analytics from day one, documented alpha findings - so the M12 renewal case stands on data.
R10SEL remains unexpressed while districts weight itLMMitigateEDCSEL enters the Year-1 content strategy (CS-01); competency mapping and a discovery facet build in Y2A (CS-G1).
R12Migration and identity-at-scale are absent from the EDC deliverable set while the RFP requires themMMAvoidEDC + BrightQueryRaise in the suggesting-mode review; carry both as named expansion modules so the omission is recorded as a decision.
R11Support-hours commitment (Pacific) conflicts with the RFP maintenance window (Eastern)MMAvoidBrightQuery + EDCWritten diligence answers state an 8:30-17:30 Pacific support window; the RFP sets maintenance M-F 9-5 Eastern. Reconcile to Eastern or split coverage in the formal SOW before it is filed.

Assumptions and change control

  • The period of performance follows the EDC 7.9.26 deliverable calendar: Year 1 Oct 1 2026 - Sep 30 2027 (specifications, alpha prototypes, the Functional Prototype Platform); Year 2 Oct 1 2027 - Sep 30 2028 (beta cohort, content, connector, testing, launch)
  • The lesson matrix is 24 = 12 social studies + 12 science across the four grade bands, produced in Year 2 (EDC deliverable 2.3)
  • ONE classroom connector ships in Year 2 (EDC 2.4; Google Classroom expected, chosen with cohort tool commonality); further connectors are expansion modules on the same adapter architecture
  • RLMG owns educator-facing interface design and the front-end build; BrightQuery owns the AI and platform engineering - backend, integrations, testing, and the pipelines that process Smithsonian data
  • Migration and identity-at-scale are not in the EDC deliverable set; they remain solicitation obligations carried as expansion modules (see R12)
  • The Smithsonian provides EDAN/DAMS access and environment provisioning in Year 1; TRB reviews at the gates
  • Engineer-week classes: S under 2, M 2-8, L 8-16+; midpoints 1 / 5 / 12; 26 productive weeks per phase
  • Change control: scope changes are written change requests, impact-assessed against this baseline, and decided in monthly steering; the M12 renewal gate may re-scope Year 2

14

How the project runs

The operating rhythm: a fixed meeting and review cadence, a definition of done no published resource can skip, and the success measures the cohort semester exists to produce.

Cadence

Weekly
EDC + BrightQuery working sync: progress, blockers, decisions needed
Bi-weekly
Sprint review with working software; backlog re-planned against the scope baseline
Monthly
Steering with Smithsonian OET: milestones, risks, change requests; risk register re-scored
Per deliverable
Draft then final, with the 5-day review + 5-day correction windows (GV-03)
Phase boundary
TRB reviews (Requirements, System Design, Production Readiness) as blocking gates (GV-04)

Definition of done - a published resource

  • Passes the four suitability planks: age-appropriate, defensible, engaging, easy (CS-08)
  • Standards alignment human-confirmed, capped, and registry-resolvable (ST-03, ST-05)
  • Accessibility checks pass: alt text, headings, contrast, captions where media (AX-01, AX-10)
  • Provenance recorded end to end: who made it, who approved it, when (GV-10)
  • Approved by a designated Smithsonian reviewer; publish is blocked otherwise (GV-01)

Success measures

Cohort activation · Y2A
Share of onboarded beta teachers who run at least one lesson
Repeat use · Y2A
Teachers returning to run a second lesson within the term
Search success rate · Y1B
Searches ending in an open or save, and top failing queries (AN-05)
Time to first lesson · Y2A
Minutes from sign-in to a classroom-ready lesson in hand
p95 latency · target Y1A, evidence Y1B
Search and page render against the published performance targets (DS-10, AN-07)
508 pass rate · every release
Automated accessibility checks per release, plus the documented test process (AX-02)
Alignment accuracy · quarterly
Sampled human audit of published standards alignments (ST-09)
Curation throughput · Y2A onward
Resources moved through the review gate per week (CS-12)

15

The plan in full

The complete plan. Filter by phase, delivery owner, or domain, or search any capability; each row carries its solicitation citation, so any line item traces back to the RFP, SOW, or Environmental Scan on demand. The owner is the party that does the work (the R of the RACI above): BrightQuery in blue, EDC in green, Smithsonian in violet, genuinely joint work in gray. This table is also the accessible twin of every figure above.

181 of 181
IDPhaseOwnerEffPlan of workSolicitation source
CS-01MUSTPROCEDC-Content strategy written and OET-approved before Y1A authoring/curation build starts; every taxonomy facet, curation rule, and template cites its strategy section.RFP SOW item 3; RFP n.b. 'meet us where we are'; Scan Gaps #1 (sec 7); Through-line (a)#4
CS-02MUSTY1AEDCMComplete the beta-subset audit (asset-to-new-structure mapping, keep/transform/exclude + reason) on the BrightQuery-built audit pipeline; ingest gate blocks unaudited assets.SOW: Subset of artifacts, subjects, grade bands, standardsafter CS-01RFP Deliverables pre-launch (content audit); RFP SOW item 3; Scan Gaps #3 (sec 7)
CS-03MUSTY1BEDCMImplement the bounded 'best of' beta corpus: inclusion criteria enforced at ingest; teacher search/browse scoped to the curated subset, never the full 6M inventory.SOW: Subset of artifacts, subjects, grade bands, standards, educator use casesafter CS-02Scan sec 8 thesis + Gaps #3 (DocsTeach model); Through-line (a)#2; RFP problem statement; RFP Goal 1
CS-04Y1BBrightQueryMAutomated quality gates in the curation pipeline: blur/low-res detection, placeholder-thumbnail, context-free-record and bare-link exclusion; auditable excluded list.after CS-02Scan Gaps #3 (sec 7); Scan sec 3 thumbnail critique; sec 4 'no blurry images'; Through-line (c) MUST AVOID
CS-05MUSTY1AEDCMDefine the ready-to-go standard; wrapped classroom-ready resource is the default teacher unit for the 24 exemplar lessons; report ready-to-go share vs 87% benchmark.SOW: Six exemplar lessons per grade band PreK-2/3-5/6-8/9-12 (24 lessons)after CS-06RFP Goal 1 'ready-to-go'; RFP launch deliverables (templates); Scan #6 87% benchmark; Through-line (a)#6
CS-06MUSTY1BBrightQueryLBuild the instructional-format template system (lesson plan, activity, discussion Qs, assessment, bellringer, exit ticket); every resource typed and labeled in browse.SOW: lesson-plan templatesRFP launch deliverable (templates); Scan sec 3 'collection has no schema'; Through-line (c) MUST DO #3
CS-07MUSTY1AEDCMGrade-band/subject/standards metadata model with quality gates: caps flag over-tagged standards and over-broad bands for review; teacher filters reflect tight alignment.SOW: aligned to selected standardsRFP Goal 2; RFP Educator needs (grade/subject); Scan Reptiles case (14 NGSS, K-5 too wide); Through-line (c)
CS-08Y1BEDCSEncode Age-Appropriate/Defensible/Engaging/Easy as pass/fail rubric gates inside the review workflow; publish blocked until all four are recorded per resource.after CS-11Scan sec 8 Figure 8 hierarchy (four gating planks); Through-line (d)#4; RFP Goal 2
CS-09Y1BEDCMAccuracy and representation review steps recorded per resource; provenance/expert-review metadata; corpus-composition reporting against representation goals.after CS-11Scan #8 quality/representation (64% UGC unusable); Scan Gaps sec 7 equity/trusted source; Through-line (d)#7/#9
CS-10Y2AEDCMBuild VTS-explicit, ready-to-go object-based learning experiences on gated high-quality assets for beta day one; Y1B educator sessions supply the validation evidence.SOW: object-based learning supportsafter CS-04RFP differentiator (object-based learning); RFP SOW item 5; Scan sec 3 white space (2 of 15); Through-line (d)#2
CS-11MUSTY1BSmithsonianLAuthor/reviewer/approver governance workflow with enforced Smithsonian approval gate: unapproved content technically unpublishable; approval state audited per resource.RFP C.10.a exclusive artistic/editorial control; RFP Plan of Accomplishment IV; Through-line (b)
CS-12Y2ABrightQueryMCorpus-maintenance tooling for the Y2 expansion: dead-link/stale/low-performer detection fed by engagement analytics, re-review queue, logged add/update/retire actions.RFP n.b. 'ongoing and evolving'; RFP SOW item 7 + analytics deliverable; Scan sec 8; Scan Gaps #3/#4
CS-G1Y2AEDCMSEL named in the Y1 strategy doc (CS-01); Y2A builds the holdings-to-SEL-competency mapping plus an SEL discovery facet alongside the subject/format expansion.after CS-01Scan Gaps SEL plank (line 457); district-selection signal (line 324); research goal (line 487); RFP SOW item 3
CS-G2MUSTPROCEDC-Program-level go/no-go gate at the Y1B-to-Y2A boundary (the M12 renewal): alpha and prototype educator-session evidence vs the 'immediately useful, trusted, adoptable' bar can trigger rescope or no-go before the beta.SOW: collect feedback, refine before broader launchScan line 468 (redesign not foregone); Through-lines 12/8 (lines 526, 603); RFP launch bar (line 83)
DS-01MUSTY1BBrightQueryLY1B: facet data model + query engine for grade band, subject, standard, topic, skill over the curated beta subset; combinable multi-facet queries from day one.SOW: subjects, grade bands, standardsRFP Goal 1 + educator needs (L43-49); at-launch deliverable L77-78; Scan L339, 438
DS-02MUSTY1BBrightQueryLY1B: curation pipeline with PK12-viability flags, default-result exclusion of non-viable objects, classroom-fit relevance ranking; beta teachers see 'just right' sets.SOW: Subset of artifactsRFP problem statement L29 + Goal 1 L43; Scan L267, 453, 490, 506 (DocsTeach, deliberate curation)
DS-03MUSTY1BBrightQueryMY1B: filter panel over DS-01 facets plus format-type and learning-modality facets, live result counts on apply/remove; formats map to teacher-recognizable types.after DS-01, DS-08RFP at-launch IA/filtering L77-78; Scan browse schemas L438; filter-count leaders L374
DS-04MUSTY1BBrightQueryMY1B: ingest CCSS+NGSS taxonomies (extensible model), standard-code search, alignment badges on every result; beta scoped to the SOW's selected standards.SOW: aligned to selected standardsafter DS-01RFP Goal 2 L44 + educator need L49; Scan L339, 424-426, 432
DS-05Y1BBrightQueryMY1B: tagging lint in the publish pipeline - flag implausible standards counts and over-broad grade bands for review; ranking ignores tag volume. Gates beta content.after DS-04Scan 'Remarkable Reptiles' L397, 516 + MUST AVOID L580; RFP Goal 2 L44
DS-06MUSTY1BBrightQueryLY1B: production text search - index, analyzers/synonyms, relevance tuning + eval harness so natural teacher queries beat a generic web search over the beta corpus.after DS-01RFP at-launch 'robust search' L78 + problem L29; Scan search-engine behavior L339, 397
DS-07MUSTY2BBrightQueryMY2B: full SEO/AEO - structured data on resource pages, sitemaps, indexability + answer-engine checks; beta is a closed cohort, so public crawlability lands at launch.SOW item 6 'fully optimized for search and answer engines' L64; Scan L339-340
DS-08MUSTY1AEDCLY1A: educator-recognizable IA - format/grade/subject/standard taxonomy, browse paths, per-resource format classification; 'collection' demoted. EDC card-sort validates.RFP at-launch IA L77; Scan 'collection has no schema' L391, 514; fix terminology L454
DS-09Y2ABrightQueryMY2A: ingest/derive reading-level (Lexile) and ELL differentiation metadata, expose as filter facets; rides Y2 metadata expansion for multilingual learners.SOW: multilingual learnersScan Lexile L430 + Newsela L373 + equity audiences L334, 443, 605; RFP reach L31
DS-10MUSTY2BBrightQueryMY2B: run the load-test harness against the p95 latency targets set in the Y1B build, tuned to pass with the live cohort; evidence into Master Test Plan. Speed is a Y1A design constraint.after DS-01, DS-06Scan 'slowest platform' L394, 516, 597; RFP Master Test Plan C.4.4.1 L95-96
DS-11Y2ABrightQueryMY2A: suitability metadata (age-fit, defensible, engaging, ready-to-go) as pass/fail gates in default ranking + 'why surfaced' explanations; needs matured metadata.after DS-02Scan suitability hierarchy L470-478, 524; MUST DO gate L563
DS-12Y2ASharedMY2A: trending sort from Y1B engagement signals + editorial 'best of' PK12 sets per subject/grade; both surfaces draw only from the DS-02 viable corpus.after DS-02Scan popularity browse L438 + DocsTeach 'best of' L365, 453, 561; RFP Goal 1 L43
AU-01MUSTY1ABrightQueryMDefine the six-format taxonomy plus per-format data models; every beta asset is typed, labeled, and rendered as its format. Legacy remap lands with Y2 migration.SOW: lesson-plan templatesRFP Sec 4 Deliverables ln 80; Scan Sec 3 verdict; finding 6
AU-02MUSTY1ABrightQueryLCore asset model for the beta: raw materials composed with wraparound (instructions, prompts, sequencing) into one classroom asset; objects reusable without duplication.SOW: lesson-plan templates, object-based learning supportsRFP Goal 2 ln 44; Scan Sec 3 container model; finding 6
AU-03MUSTY1BBrightQueryMTemplate engine plus one standardized template per format so the 24 exemplar lessons are authored into a fixed, consistent scaffold from day one of the beta.SOW: lesson-plan templatesafter AU-01, AU-02RFP Deliverables ln 80; Scan Sec 3 table (Khan Academy/DocsTeach)
AU-04MUSTY1BBrightQueryLFull no-code authoring suite (create, arrange, draft, preview, publish, version history) in place before the beta cohort goes live, so the 24 exemplar lessons (12 social studies + 12 science) are authored in it.SOW: six exemplar lessons per grade band PreK-2/3-5/6-8/9-12 (24 lessons)after AU-02, AU-03RFP Deliverables ln 80, background ln 27; Scan Sec 3 table
AU-05MUSTY1BBrightQuerySStructured rich-text storage for all authoring fields (selectable, searchable, AT-exposed) plus a11y checks; bans the incumbent image-text failure from day one.Scan Sec 3 verdict, finding 7, MUST-AVOID; RFP C.4.6 WCAG/508 ln 115
AU-06MUSTY1BBrightQueryMStructured standards/grade/subject fields with controlled vocabularies for the beta's selected standards subset; multi-value, queryable by discovery filters.SOW: aligned to selected standardsRFP Goal 2 ln 44, educator needs ln 49; Scan Sec 2, Sec 5
AU-07Y1BBrightQuerySAdmin-configurable warning thresholds on standards-tag count and grade-band breadth so exemplar and beta authoring avoids the documented 14-tag / K-5 red flags.after AU-06Scan Sec 3 case study; finding 7; MUST-AVOID ln 580
AU-08Y1BBrightQueryMTeacher-facing facilitation-move and background-knowledge fields in templates, tied to specific objects and hidden from student views; PD travels with the beta lessons.SOW: lesson-plan templatesafter AU-03, AU-09Scan gaps/opportunities ln 458-459; RFP UX ln 47, Goal 2
AU-09MUSTY1BBrightQueryMElement-level teacher/student designation, dual render plus dual preview, and a shareable student supplemental output; required for real classroom use in the beta.SOW: test the model with teachers in classroomsafter AU-02Scan Sec 3 verdict, finding 7; RFP audience ln 47
AU-10Y1BBrightQueryMVTS-style object-based template variant plus hi-res deep-zoom and 3D model embeds with resolution preserved; delivers the SOW's object-based learning supports.SOW: object-based learning supportsafter AU-03RFP differentiator ln 33; Scan Sec 3 white space, Sec 4-5, finding 5
AU-11Y1BBrightQueryMReadiness states plus curator workflow; default educator discovery surfaces only PK-12 ready-to-go assets, enforcing the curated beta subset from day one.SOW: subset of artifacts, subjects, grade bandsScan gaps ln 453, finding 6; RFP Goal 1; content audit ln 73
AU-12Y1BBrightQueryMPublish gate validating each format's required wraparound (grade, standard, facilitation, student output) with admin-editable rules; backs the beta review/publish gate.after AU-03, AU-11RFP ln 80, Goal 2 ln 44; Scan hierarchy gate ln 470-478, MUST-DO 4
AU-13MUSTY1ABrightQueryMOpen, documented, exportable metadata schema for assets and raw materials, exposed via the modular API; precedes all asset writes to reuse SI's metadata structures.RFP SOW item 4 ln 62; n.b. ln 67; modular API deliverable ln 79
AU-14Y2ABrightQuerySY1A model is built extensible (new formats/wraparound via config); Y2A proves it by adding formats and educator types without core redesign, extension path documented.SOW: more lesson formatsafter AU-02, AU-13RFP phased capabilities ln 83; modular arch ln 79; SOW item 2 ln 60
OB-01PROCEDC-Validation plan + VTS-familiarity measures run in Y1B educator sessions, then the Y2A beta; go/no-go record gates each OB feature at the phase boundaries, descoping what fails.SOW: test the model with teachers in classrooms; collect feedback, refineScan goal #5 p.486; Scan p.390, p.512 (differentiator-and-trap); RFP SOW item 5
OB-02Y1BEDCLBuild the routine engine: activity-type schema, a VTS inquiry sequence around a single object, packaged discussion prompts; beta teachers need runnable routines day one.SOW: object-based learning supportsRFP Goal 2; Scan p.429/p.486 (VTS), p.399, p.382 (aspirin)
OB-03Y1BBrightQueryLAsset pipeline for hi-res masters, deep-zoom close-looking viewer, 3D asset embed, and quality rules excluding blurry imagery; close looking is the beta's core premise.SOW: subset of artifactsScan p.412 (3D plug-in), p.396, GAP #3 p.453; RFP C.9.1 (hi-res masters)
OB-04Y2AEDCMObject-level teacher-background model + skimmable point-of-use rendering, authored for the beta's curated object set; out-of-field teachers in the cohort need it.SOW: object-based learning supportsafter OB-02Scan p.458 (embedded PD), p.289 task #2, p.442; RFP Goal 2; RFP Part I.D
OB-05Y1BEDCMStep-by-step facilitation moves plus a time-boxed scenario schema ('if you only have one day') inside each routine; SOW-named OB supports must exist before the cohort.SOW: object-based learning supportsafter OB-02Scan p.365/p.377 (DocsTeach, USHMM), p.458 (Desmos/DocsTeach), p.459
OB-06Y1BEDCMGrade-band/subject filters on routines plus standards tagging with a tight-tag default and over-tag flagging, scoped to the beta's selected standards.SOW: grade bands, standards; aligned to selected standardsafter OB-02RFP Goal 2; RFP Part I.D; Scan p.397 (14-tag anti-pattern); Scan MUST-AVOID p.580
OB-07Y1BEDCMCuration tooling + curated PreK-12 'best of' entry points over a small activity-type set; defines the beta artifact subset so it precedes cohort testing.SOW: subset of artifacts, subjects, grade bandsScan GAP #3 p.453, p.365 (DocsTeach model), p.490; RFP Goal 1 + content audit
OB-08MUSTY1BBrightQueryMNamed format templates (activity, discussion set, bellringer, exit ticket) with class-period fit; the must-have packaging for the 24 exemplar lessons in the beta.SOW: lesson-plan templatesafter OB-02RFP launch deliverable (recognizable formats); RFP Goal 1; Scan p.391, p.383, p.390
OB-09Y1BBrightQueryLReal text-field editing of prompts/questions/scope plus save-an-adapted-copy; teachers modify nearly everything, so the beta needs genuine editability.after OB-02Scan p.395/p.516 (image-file editing), p.347-348; RFP authoring deliverable; MUST-AVOID p.583
OB-10Y1BBrightQueryMDistinct student-facing render plus an exact student-preview mode hiding facilitation moves and background; classroom beta puts routines in front of students on day one.after OB-02Scan p.393, p.454/p.565 (role split + preview), p.459; RFP at-launch UX
OB-11Y2BBrightQueryLPublic embed API exposing curated objects/3D and routine metadata plus one demonstrated plug-in target (e.g., Google Slides); the Y2 SOW's expanded integrations work.SOW: more platform integrationsafter OB-03, OB-07Scan p.412 (Digital Plug-in), takeaway #6 p.599; RFP Goal 3; RFP modular API deliverable
OB-12Y1AEDCSRepresentation/accuracy criteria encoded in the curation review gate plus attribution/context fields; rides the Y1A review workflow before any beta content ships.after OB-07Scan p.352-353, GAP #5/#6 p.455-456, p.342 (no errors); RFP mission; RFP C.10.a
DI-01MUSTY1BBrightQueryLDesign and build the core content/search/export API (OpenAPI, auth, versioning) with decoupled channel adapters; every later integration (Classroom in Y2A, then Canvas/Kahoot) rides it.RFP Deliverables doc sec 4 (modular API-driven); SOW item 4; Goal 3; Scan finding #10 / takeaway #6
DI-02Y2ABrightQueryMFirst build of share-to-Classroom: OAuth consent, post as assignment/material with working link-back, student-view render verified against a live Classroom test account.SOW: high-value platforms (Canvas, Google Classroom, Kahoot)after DI-01Scan Fig 15 (Google Classroom ~10/15); Goal 3 'work in harmony'; Part III Q7/Q8
DI-03Y2BBrightQueryLSOW menu names Canvas: LTI 1.3 lands in Y2B - OIDC launch, role claims, deep linking, Canvas registration; Teams and other LMSs reuse the same tool afterward.SOW: high-value platforms (Canvas, Google Classroom, Kahoot)after DI-01Scan Fig 15 (Canvas ~5, Teams ~5, Blackboard/D2L); Goal 3; Part III Q7
DI-04Y2BBrightQueryLIdentity lands in Y2B: Google/Microsoft OAuth sign-in plus Clever rostering with automatic provisioning; data handling documented against the COPPA/PIA posture per SP-03.after SP-03Scan Fig 15 (Clever ~4/15); Part III Q8 district adoption; Goal 3
DI-05Y2BBrightQueryLBuild SCORM/xAPI packaging plus an open web/print export in the Y2 'more lesson formats' expansion; packages import into an LMS test instance keeping standards metadata.SOW: more lesson formatsafter DI-11Scan Fig 15 (SCORM, xAPI); SOW item 4 portable; C.4.2 portability plan; Goal 3
DI-06Y2BBrightQueryMKahoot is an SOW-named high-value platform: build the filtered partner-feed API and prove the Kahoot feed end to end; PBS/Nearpod/Newsela/Edpuzzle/Pear Deck tuning follows post-launch.SOW: high-value platforms (Canvas, Google Classroom, Kahoot)after DI-01, DI-11Scan Sec 4 Partnership Model 1 'Smithsonian as Publisher'; Goal 3 partnerships
DI-07Y2BBrightQueryLY2 'more platform integrations': curated object-archive API serving high-res and 3D assets with rights metadata, plus a reference plug-in (e.g. Google Slides add-on).SOW: more platform integrationsafter DI-01, DI-11Scan Sec 4 Partnership Model 2 'Digital Plug-in' (SI 3D program); Goal 3; RFP doc sec 4 modular API
DI-08Y2BBrightQueryMLate-scale, approval-gated: package licensed content sets with license terms and auditable rights; fee/e-commerce stays off until Smithsonian written OK (C.10.c).after DI-11Scan Sec 4 Partnership Model 3 'Curriculum Partner' (CK-12, CommonLit et al.); RFP C.10.c constraint
DI-09MUSTY1BBrightQueryLBeta's curated subset must pull from SI systems: connect metadata structures, digital-education URL repository, and asset storage; integration inventory from day one.SOW: subset of artifacts, subjects, grade bandsSOW item 4 Technical considerations (metadata structures, URL repository, asset storage; doc sec 3/5)
DI-10MUSTY1ABrightQueryMBinds the integration layer at build time: open standards (REST/GraphQL, OAuth, LTI, SCORM), open-source delivery per C.9, C.4.2 portability doc, TRM SD-940-01 mapping.after DI-01SOW item 4 (maintainable, portable, open source; doc sec 3); C.4.2 portability plan; TRM SD-940-01 C.4.1
DI-11Y1ABrightQueryMSchema work before the subset ships: machine-readable grade/subject/standards plus rights/attribution on every resource; powers standards-aligned discovery and feeds.SOW: aligned to selected standardsafter DI-01Goal 2 educator needs (doc sec 2); Scan Part2-4 partner feeds; I.4.7/C.10.c rights; doc sec 6 schemas
ST-01MUSTY1BBrightQueryMGrade-band and subject tagging in the core content model plus search facets; zero-untagged publish gate so the 24 beta exemplar lessons all carry grade+subject.SOW: subset of artifacts, subjects, grade bands, standardsRFP Goal 2; educator needs by grade+subject (lines 44,49); Scan browse schemas + finding map (lines 438,536)
ST-02MUSTY1BBrightQueryLIngest CCSS+NGSS frameworks, per-code alignment records, and search/filter by standard code (e.g. 4-ESS1-1); scoped to the beta's selected standards, built to scale.SOW: aligned to selected standardsRFP Goal 2 (line 44); educator need (line 49); Scan CCSS/NGSS/C3/EAD + 4-ESS1-1 task (lines 424-426,290)
ST-03MUSTY1BBrightQuerySConfigurable max-standards threshold with warn/block in the curation workflow plus an over-tag audit report; enforced before any beta content publishes.after ST-05Scan Remarkable Reptiles 14-NGSS red flag (lines 397,516); MUST AVOID over-tagging (lines 563,580); RFP Goal 2
ST-04Y1BBrightQuerySGrade-span breadth check flags over-broad bands (K-5 style) for curator confirmation; rationale captured for intentional multi-band tags.Scan Remarkable Reptiles K-5 too-wide (lines 397,516,580); Defensible plank (lines 473,524)
ST-05Y1BBrightQueryMAlignment lifecycle states (AI-suggested/unconfirmed vs human-confirmed) with confirmer+timestamp records; publish gate blocks unconfirmed alignments before beta.RFP authoring deliverable (line 80) + AI/Privacy trigger (line 55); Scan 64%/double-edged tagging (352,432,518)
ST-06Y1ABrightQueryMStore alignments against CASE GUIDs/ASN URIs from day one and expose via API so beta data never needs remapping; full framework breadth lands in Y2A.after ST-02RFP API-driven (79), portable/open (62), Goal 3 (45), Part III Q7 (209); Scan partner distribution (405,522)
ST-07Y2ABrightQueryMBuilt as Y2A full CASE packages land: framework-version diffing flags resources on changed/retired codes into a human re-confirmation queue with documented SLA.after ST-05, ST-06Scan frameworks evolve (421-432); RFP evolvable arch (79) + C.4.2 upgrade path (94); Defensible gate (524)
ST-08Y1BBrightQuerySResource view renders confirmed standard codes with human-readable descriptions plus grade band and subject; only human-confirmed alignments are shown.after ST-02, ST-05Scan Defensible plank (473,563) + vetting criteria (342); RFP Goal 2 (44) + educator-centered UX (77)
ST-09PROCEDC-Governance procedure (roles, parsimony criteria, QA sampling) approved before Y1A alignment authoring; QA results at every TRB gate; assessed in the Y2B full-corpus audit (MG-01/MG-02).RFP content audit (73); SOW item 3 (62); TRB/acceptance gates (85,103); Scan curation mandate (352,453,518,563)
UX-01MUSTY2BBrightQueryLBudgets measured from Y1B hardening; the acceptance gate is the formal load/stress run on SI infrastructure vs the legacy baseline at production launch.RFP C.4.4.1 load/stress + C.4.3 Master Test Plan; Scan §3 verdict slowest reviewed; Gap #4
UX-02Y1BBrightQueryMDual render modes (teacher vs student) built into every resource component from day one; student view strips authoring, notes, cite, download, analytics.Scan §3 + §6 no role distinction; Gap #4; RFP audience (teachers primary, students via teacher-sent)
UX-03Y1BBrightQuerySOne-click 'preview as student' on any shareable resource, rendering the exact student view via UX-02 render modes; teacher exits preview without losing work.after UX-02Scan §3 no student preview; §6 blind spot; Gap #4
UX-04Y2ABrightQueryMFull-screen projection mode free of teacher chrome, reachable in 1-2 actions with responsive navigation; core whole-class delivery modality for the Y2A beta classrooms.after UX-02Scan §6 no presentation mode; §3 vs PowerPoint/Slides; Gap #4
UX-05MUSTY1BBrightQueryLRich-text authoring core: instructional text stored as editable text, never image files; edits persist to student view; underpins templates + exemplar lessons.SOW: lesson-plan templatesRFP at-launch authoring/templates deliverable; Scan §3 image-file editing MUST AVOID; Gap #4
UX-06Y1BBrightQueryMImage derivative pipeline for sharp thumbnails at all browse/search sizes, designed non-generic placeholders, and quality guidelines applied to the curated beta corpus.Scan §3 thumbnails verdict; Gap #4; Distribution §4 no blurry images
UX-07MUSTY1BSharedLBuilds the IA: navigation shell, content organization, consistent labels, streamlined find/ready/deliver workflows; teacher usability validation runs in the Y1B educator sessions.RFP at-launch educator-centered UX deliverable; Plan of Accomplishment I; Scan through-line (b)
UX-08MUSTY1BBrightQueryLTyped formats (lesson plan, activity, discussion Qs, bellringer, exit ticket) with consistent renderers + browse/search filter; replaces 'collections'.SOW: lesson-plan templatesRFP templates in recognizable instructional formats + Goal 1; Scan through-line #6 (87% ready-to-go)
UX-09Y1BEDCMFour-plank pass/fail rubric wired into the review/publish gate; curated subset and 24 exemplar lessons must pass all four planks before beta surfacing.after UX-10, UX-11Scan Figure 8 hierarchy of needs; through-lines #11, (d)#4; MUST DO #4
UX-10Y1BEDCSGrade-band metadata constraints with documented breadth caps enforced in authoring/curation; grade filters return genuinely matching resources for the beta subset.SOW: subset of artifacts, subjects, grade bands, standardsScan §3 Reptiles case (K-5 too wide); MUST AVOID #4; RFP Goal 2 grade alignment
UX-11Y1BEDCSStandards display capped to genuinely aligned tags with curation review; teacher-facing alignment display and find-by-standard trust for the beta's selected standards.SOW: aligned to selected standardsScan §3 Reptiles 14 NGSS tags; MUST AVOID #4; RFP Goal 2 standards alignment
UX-12Y1BEDCMPer-resource facilitation moves + skimmable background at point of use (Desmos/DocsTeach model), hidden from students; the SOW object-based learning supports.SOW: object-based learning supportsafter UX-02Scan Gap #7 (Desmos/DocsTeach models); Tier 2 Task 2; RFP Goal 2; MUST DO #6
UX-13Y1BBrightQuerySBackground/context/facilitation panels rendered teacher-side only, consistent across browse, resource, preview, and presentation; student view stays clutter-free.after UX-02Scan §3 panels confuse students; Gap #9 teacher-facing panels
UX-14Y2ABrightQueryMLayered on UX-12: extra scaffolding paths for newer/out-of-field teachers, skippable by veterans; fits the Y2 expansion to more educator types.SOW: more artifacts, lessons, subjects, educator typesafter UX-12RFP audience note (may differentiate by teaching experience); Scan through-line (b) + §6
UX-15MUSTY1BBrightQueryLWCAG 2.1 AA/508 built into components from day one: keyboard, contrast, focus order, screen-reader labels across all views; formal 508 evidence follows in Y1B.RFP C.4.6 WCAG 2.1 AA + 508 warranty; C.4.4; Master Test Plan; PoA II; Scan §9 equity
AX-01MUSTY2BBrightQueryMFull WCAG 2.1 AA/508 audit with the beta live: axe + manual keyboard/screen-reader passes on every template, remediation to zero A/AA failures, 508 mapping, ACR/VPAT.after AX-10, AX-02RFP C.4.6 warranty; C.2.3 most-stringent; grounding Pt1 s6; Plan of Accomplishment sub-point II
AX-02MUSTPROCBrightQuery-Master Test Plan 508 section (tools, scripts, AT coverage, pass/fail) written before Y1A exit; executed at each acceptance milestone and re-run every release through Y2B.RFP C.4.3 Master Test Plan; C.4.4; Plan of Accomplishment sub-point II
AX-03MUSTY1BBrightQueryMBuild beta discovery accessible from day one: keyboard-operable search/facets/pagination, ARIA live announcement of results and filter state, AA contrast/target sizes.after AX-10RFP at-launch 'robust search... meeting accessibility standards'; at-launch UX deliverable; C.4.6
AX-04MUSTY1BBrightQueryLBeta authoring AT-operable and emitting accessible output: required alt text, real text (no rasterized pages), caption prompts; end-to-end audits of template output.SOW: lesson-plan templatesafter AX-10RFP at-launch authoring-tools deliverable; C.4.6; Scan Pt2 s3 / Pt3(a) #7 image-file 'editing' failure
AX-05MUSTY1BBrightQueryMAccessible media player + caption/transcript pipeline for the curated beta subset: synced captions, visible transcripts, audio-description path, keyboard controls.SOW: Subset of artifactsRFP C.4.6; C.4.4; Scan Pt2 s3 'Remarkable Reptiles'; Pt1 s1 media-heavy corpus
AX-06Y2ABrightQueryMY2 multilingual-learner support: per-element language tagging (WCAG 3.1.1/3.1.2) plus a translation/glossing mechanism for ELL content, validated with high-ELL educators.SOW: multilingual learnersScan Pt2 s6, s7 gap 5 (English Learners); s2 cultural background; s5 WCAG lang baseline
AX-07Y2ABrightQueryMY2 AI-enabled reading-level supports: Lexile/grade-band tagging with discovery filters plus generation/selection of differentiated text levels, validated with teachers.SOW: more sophisticated AI-enabled supportsScan Pt2 s3/s5/s6 (Newsela, Lexile, struggling readers); s2 SHEG 34%; s8 'Age Appropriate' plank
AX-08Y1AEDCSBake documented representation/inclusion criteria into Y1A curation of the beta subset; record review results in the publish gate so the launch corpus shows diversity.SOW: Subset of artifacts, subjects, grade bandsScan Pt2 s2 (64% / representation gap); s7 gap 5; Pt3(d) takeaway 9; SOW item 3 curation
AX-09PROCEDC-Governs recruitment: the Y2A beta cohort and Y2B testing must include low-income/high-ELL/struggling-reader educators as primary; findings tracked into design.SOW: Teachers apply as beta testersScan Pt2 s6, s7 gap 5; Pt3(d) takeaway 9; RFP SOW items 5 (iterative delivery) + 1 (user journeys)
AX-10MUSTY1BBrightQueryLCertify the shared component and instructional-template library WCAG AA before content flows: semantics/focus/contrast/name-role-value audits + regression tests.SOW: lesson-plan templates, object-based learning supportsRFP at-launch UX + templates deliverables; C.4.6; C.12 / SD 950, IT-950-TN06 (grounding Pt1 s6)
AX-11Y2ABrightQueryMCarry a11y metadata (alt, captions, lang, structure) through Y2 export/embed APIs; verify a Google Classroom embed passes AA; document the partner metadata contract.SOW: platform integrationsRFP Goal 3; API-driven architecture deliverable; Scan Pt2 s4 / Pt3(c) MUST DO 7; C.4.6
GV-01MUSTY1BBrightQueryMPublish gate built in Y1B: draft/pending/published states, SI approval recorded (approver, version, time), publish blocked by default before beta content goes live.RFP C.10.a (exclusive editorial control, no publish w/o written approval); SOW item 5 (SI governance)
GV-02MUSTY2BBrightQueryMRBAC ships with identity in Y2B: SI-only approver role, author/contractor submit-only, auditable role grants; until then the prototype and beta rely on the GV-01 gate with named SI reviewers.after DI-04, GV-01RFP C.10.a; RFP I.4.1 / SI clause 62; SOW Part II.B (SI governance, design/security review-approval)
GV-03MUSTPROCEDC-Bites at every deliverable both years: draft+final each scheduled with 5-day SI review / 5-day correction windows; stage accepted only on recorded SI sign-off.RFP / Sample Contract Sec C/E - staged delivery, draft+final, 5-business-day review/correction cycles
GV-04MUSTPROCSmithsonian-TRB gates at phase boundaries: Requirements Review pre-Y1A, Design Review pre-Y1B prototype build, Readiness Review pre-Y2B launch; SI design+security approval per deploy.RFP C.2.2, C.7.7 (TRB gates); SOW Part II.B (design + security review/approval)
GV-05MUSTPROCEDC-Bites at each phase handoff: all source/designs/content delivered as SI work-for-hire, rights assigned, any pre-existing BQ IP flagged in writing at every delivery.RFP p.13; RFP I.4.1 (work made for hire, irrevocable assignment); SI clause 62 Rights-in-Data
GV-06MUSTY1BBrightQuerySBuilt into the Y1B publish gate (GV-01): restricted-category flags (downloadable software, third-party-licensed, commerce) block approval unless an SI consent record exists.after GV-01RFP C.10.c - no user-downloadable software, third-party-licensed materials, or e-commerce without consent
GV-07Y1BBrightQueryMY1B: per-asset rights/license + clearance-status fields mapped at ingest; review screen flags uncleared assets and blocks approval before beta content clears review.after GV-01RFP I.4.7 (contractor clears licenses/permissions); RFP I.4.5 / SI clause 62(e) indemnification; Scan p.267
GV-08Y2ABrightQueryMY2A adds a sensitivity tag plus a routed curatorial/SME review branch and collection-source provenance as content scales beyond the curated beta subset.after GV-01Scan sec 7 findings 5/6, line 518 (cultural representation gap); RFP C.10.a editorial control
GV-09Y1BBrightQueryMY1B adds a required accuracy checkpoint to review: standards tags and grade band confirmed per item before approval; every exemplar lesson passes it before reaching the cohort.after GV-01Scan p.342 (accuracy 'no errors of any kind'); Scan 397/516/580 (over-tagging red flags); RFP Goal 2
GV-10Y1BBrightQueryMY1B: append-only audit log of submit/approve/reject/publish/unpublish/edit (actor, role, time, version) with export; captures history from the first beta publish.after GV-01RFP Plan of Accomplishment IV (data governance); RFP I.1.6(b) (audit/IG access); RFP C.10.a
GV-11Y2ABrightQueryMY2A: SI-reviewed badge on published content, curated vetted-set collections distinct from unvetted material, jurisdiction-fit sensitivity filters as scale content lands.after GV-01Scan lines 307-315, 520, 601 (18-state restrictions; trusted-source need); Scan sec 7 finding 6
GV-12Y2ABrightQueryMY2A: outside/user content routed through the GV-01 gate; vetted vs unvetted split in data model and UI, needed as educator contributions arrive in the beta, ahead of the Y2B migrated collections.after GV-01, GV-02RFP line 27 (~2,900 of 12,000+ collections SI-created); Scan p.352/518 (64% UGC unusable); RFP C.10.a
AR-01MUSTY1ABrightQueryLLay down the modular service architecture with documented, versioned APIs (search, content, authoring, analytics) as the beta's foundation; OpenAPI/schema published.RFP Sec 4 at-launch deliverable (modular, API-driven); SOW item 4
AR-02MUSTY1ABrightQueryMOSS-only licensing, dependency/license inventory, reproducible builds and maintainer docs enforced from the first Y1A commit; licensing cannot be retrofitted later.SOW item 4 (verbatim: maintainable, portable, open source); RFP Sec 5
AR-03MUSTY2BBrightQueryMUpgrade-path/portability plan written and proven by redeploying to a clean SI-spec environment at acceptance; config externalization itself lands in Y1A under AR-08.after AR-08RFP C.4.2 upgrade-path plan; SOW item 4 (portable)
AR-04MUSTY1ABrightQueryMTRM SD-940-01 conformance matrix and deviation approvals written against the Y1A design; SI design/security review and TRB gates cleared before the beta build hardens.RFP C.4.1; Attachment D (TRM IT-940-01 v8.0); SOW item 4
AR-05MUSTY1BBrightQueryLBeta content pipeline consumes SI's existing metadata structures and digital-education-URL repository via defined interfaces; field-level mapping, no forked copies.SOW: subset of artifactsSOW item 4 (metadata structures, URL repository); SOW n.b. (meet us where we are)
AR-06MUSTY1BBrightQueryLStand up the education-asset store plus master-to-derivative rendition pipeline serving the beta subset; design sized and documented for the full 6M-object corpus.SOW item 4 (long-term storage); RFP C.9.1 (hi-res masters); Scan Sec 4
AR-07MUSTY2ABrightQueryLBuild the cross-SI connector/ingestion framework, integrate at least one new SI source beyond the existing repository, roadmap unit onboarding; feeds Y2 'more artifacts'.SOW: more artifactsafter AR-05, AR-06SOW item 4 (net-new centralization); Plan of Accomplishment III; RFP Sec 5
AR-08MUSTY1ABrightQueryLDay-one constraint: self-hostable stack only (DB, search, object store); containerized deploy proven on an on-prem-equivalent env. SI datacenter cutover lands in Y2B.RFP C.8 (SI datacenter default, CO waiver for external); C.2.7
AR-09MUSTY2ABrightQueryLFirst production build of the Google Classroom share (the contracted 2.4 connector) delivered on the public API so beta teachers push content into their tools; Canvas and Kahoot follow (DI-03/DI-06).SOW: integrations with high-value platforms (Canvas, Google Classroom, Kahoot)after AR-01RFP Goal 3; Part III Q7; Scan Sec 4 (Google Classroom dominant)
AR-10MUSTPROCBrightQuery-Bites at every acceptance gate: buildable source + install docs each phase; full delivery (config report with DB strings, VM/cloud copies) at Y2B production acceptance.RFP C.9/C.9.1; C.4.3 config report; I.4.1 / SI clause 62
AR-11MUSTY2BBrightQuerySEnable and verify dual-stack IPv6 on all web-facing endpoints during beta hardening; connectivity test evidence and compliance statement (or priced path) delivered.RFP H.3 (IPv6 compliance or priced migration path)
AR-12Y2BBrightQueryMNumeric targets defined in the Master Test Plan, load/stress runs on SI acceptance infrastructure, tuned until search/retrieval demonstrably beats the legacy Lab.after AR-08RFP C.4.4.1 load/stress; Master Test Plan C.4.3; Scan Sec 3 (slowest platform)
SP-01MUSTY1BBrightQueryMInterim vulnerability scan is a hard gate on every educator session and the Y2A beta go-live (high/med fixed first); formal OCIO web/vuln scans on SI infrastructure gate Y2B acceptance.after SP-02RFP SOW Pt II/III S.3 design+security review; C.4.4.2 OCIO scans gate acceptance (S.6); Plan sub-pt VI
SP-02MUSTY1ABrightQueryLBuild to OCIO IT Security Standards + TRM v8.0 from first architecture; keep a control-to-standard compliance matrix; support SI pen-test and IG audit rights.RFP Plan sub-pt VI; I.1.6; C.4.1/Att D TRM SD-940-01 IT-940-01 v8.0; I.1.6(b) pen-test/IG (S.5-6)
SP-03MUSTY1ASmithsonianSPrivacy Office gate before beta: feature flags + release checklist list AI and student credentials as gated; reviews approved before Y1 AI supports enable.RFP SOW Privacy Office trigger for AI/student credentials (S.3); through-line d.10
SP-04MUSTY1ABrightQuerySComplete PIAs for beta data flows (teacher applications, accounts, feedback); publish privacy notice linking current PIAs before cohort recruitment.RFP I.1.3 PIAs + privacy-notice links (S.6); I.1.1 PII/SPII definitions
SP-05MUSTY1ABrightQueryMCOPPA assessment plus school-authorization/parental-consent and data controls for teacher-sent student flows (under-13 PreK-2/3-5 bands) before beta.RFP I.1.9 COPPA (S.6); audience S.2 PreK-12 students via teacher-sent materials
SP-06Y1ABrightQuerySDesign beta student quiz/assessment flows accountless; data inventory justifies each element; no student credentials/PII absent Privacy Office review + PIA.Scan S.2 supplemental-materials model; RFP SOW credential trigger (S.3); d.10; Plan sub-pt IV
SP-07Y1BBrightQueryMHuman confirm step in the Y1B review/publish workflow: recorded approver + timestamp on AI-assisted content; no path surfaces AI output to users unreviewed.after SP-03RFP C.10.a exclusive editorial control (S.7); SOW AI Privacy trigger (S.3); Scan takeaway 9 accuracy/trust
SP-08MUSTPROCBrightQuerySBites from the first real teacher PII (Y1B educator sessions, then the Y2A cohort go-live): breach alerting + 1-hour OCIO Service Desk/Privacy Council runbook in place; yearly tabletop evidence.RFP I.1.7 1-hour breach notice; Att B SI-147B-Privacy; SD 118 (S.6)
SP-09MUSTPROCBrightQuery-Written IR plan + critical-issue SLAs delivered before the Y1B educator sessions; re-baselined at the Y2A cohort go-live and the Y2B migration and launch gates; consistent with the SP-08 1-hour path.after SP-08RFP Part III Q9 IR plan, Q18 critical-issue SLAs (S.10); I.1.7 (S.6)
SP-10MUSTY1ABrightQuerySModern TLS on every PII/SPII path from first deploy (no SSL3/TLS1.0/1.1); CO-approved endpoint controls for devices handling PII; media sanitization procedure.RFP I.1.6(a) TLS for PII/SPII; I.1.6(c) endpoint controls + media sanitize/degauss/destroy (S.6)
SP-11MUSTY1BBrightQueryMOpt-in consent layer before any analytics: cookies/beacons/geolocation off by default, trackers gated on consent, decline never blocks content; inventory kept.RFP I.3 opt-in tracking/geolocation, no content denial on decline (S.5)
SP-12MUSTY1ABrightQueryMGovernance/security/privacy policies mapped to SD 950/SI-147B/SD 940 from first ingest; access controls + classification; 15-day return/delete-with-certificate process.RFP Plan sub-pts III/IV; C.12 SD 950, IT-950, SI-147B, SD 940, SD 184 (S.6); 15-day termination return (S.9)
SP-13MUSTPROCBrightQuery-Bites at proposal submission (pre-award): disclose certifications, security measures, privacy-law/COPPA compliance for Part III Q4-Q6; keep current post-award.RFP Part III Q4 certifications, Q5 security measures, Q6 privacy-law compliance (S.10)
SP-14MUSTPROCEDC-Bites before staff touch SI networks (Y2B migration data access and SI-infra deploys): SD 931 affirmations, annual training, SI badges, background checks.RFP C.6.2/C.6.3 SD 931 + Rules of the Road, training, SI Security Credential, fingerprint/background (S.6)
AN-01MUSTY1BBrightQueryLProduction event pipeline: taxonomy, capture, storage, OET dashboard for sessions/searches/views/saves/sends; live for the beta cohort so the feedback goal is measurable.SOW: test with real users, collect feedbackafter AN-10RFP at-launch deliverable 'Baseline engagement analytics'; Plan of Accomplishment sub-point V
AN-02MUSTY1BSharedMAgree KPI framework with OET (definitions, sources, targets, leading vs outcome) and stand up recurring dashboards/reports on the beta pipeline.after AN-01SOW item 7 'Measuring success - key metrics and ongoing tracking'; Part III Q14
AN-03MUSTY2BBrightQueryMReach metric (unique educators + student reach via sends) vs 600K baseline and 4M/49M trajectory with documented dedup; dedup needs production identity, which lands in Y2B (DI-04).after AN-01, DI-04RFP reach goal: 600K+/yr baseline toward 4M teachers / 49M+ students (lines 31, 541, 543)
AN-04Y1BBrightQueryMLog zero/low-result and abandoned searches with query text; make saves/sends/exports resource-attributable; ship curation gap/underperformer view to refine beta content.SOW: collect feedback, refine before broader launchafter AN-01Scan content-strategy critique + 'curate ruthlessly' (lines 387, 453, 543); SOW item 3
AN-05Y1BBrightQueryMSearch-effectiveness reporting: success-rate formula, top/failing queries, grade/subject/standard filter usage, CTR and result-to-action rates, proven on beta traffic.after AN-01RFP Goal 1 + 'robust search and discoverability' launch deliverable; Scan 'just right' thesis
AN-06Y1BBrightQueryMAdd grade-band/subject/standard dimensions to engagement reporting plus coverage-gap and over-tagging views over the beta's selected standards subset.after AN-01RFP Goal 2 standards/grade alignment (lines 44, 49); Scan browsing schemas + over-tagging flag
AN-07Y1BBrightQueryMProduction telemetry: page/search median+p95 latency and error rates vs OET targets, aligned to the Master Test Plan; evidences beta speed goals.Scan 'slowest platform Wondrus reviewed' (line 394); RFP C.4.4.1 performance testing + Master Test Plan
AN-08Y2ABrightQueryMInstrument shared/embedded content in Canvas/Classroom/partner surfaces; attribution+dedup rolls off-platform reach into AN-03 with distributed split.SOW: more platform integrationsafter AN-03RFP Goal 3 integration/partnerships (lines 45, 79); Scan distribution-not-destination (lines 522, 599)
AN-09MUSTY1BBrightQueryMAnalytics data model normalizes assets from multiple SI sources for unified reporting (scored Plan sub-point III); proven on beta sources.after AN-01Plan of Accomplishment sub-point III 'aggregate data across SI' (lines 92, 169); SOW item 4
AN-10MUSTY1ABrightQueryMConsent-gated tracking (opt-in cookies/beacons/geo, content never denied), student-data minimization, governance doc; clears privacy review before beta go-live.after SP-03RFP I.3 opt-in web tracking; COPPA I.1.9 + PIAs (lines 128, 132); Plan sub-point IV
AN-11Y2BBrightQueryMNew vs returning educators, activation rate, week/month cohort retention, district segmentation; needs production identity (Y2B, DI-04) plus usage history from the beta year.after AN-01, DI-04Part III Q8 district adoption + Q14 customer success; Scan 'immediately useful, trusted, adoptable'
AN-12Y2ABrightQuerySEquity-lens reporting over ELL/leveled/representative content tags, privacy-safe (no student PII), feeding the AN-04 curation loop; needs Y2A's richer content tagging.after AN-06, AN-10Scan: equity audiences are 'the wedge', heaviest supplement-seekers (lines 334, 443, 605)
MG-01MUSTY2BBrightQueryLPost data-sharing agreement: machine-readable inventory of 62k+ collections/6M objects w/ provenance, author class, media, PK-12 viability; SI-reviewed export.RFP Deliverables: pre-launch content audit; SOW item 3; Scan Gaps #3; Scan core problem (6M objects, 12k collections)
MG-02MUSTY2BEDCMDraft triage criteria, get SI approval, then run rule-driven keep/transform/archive over the MG-01 inventory with reason codes and a queryable, reversible decision log.after MG-01RFP Deliverable: content audit mapped to new structure; SOW item 3; Scan Gaps #3 'Curate ruthlessly'
MG-03MUSTY2BBrightQueryLMigrate the ~2,900 SI-educator collections first as trusted core: ETL to new content model, attribution/metadata intact, sampling verification, no silent archive.after MG-02, MG-08Scan core problem (~2,900 SI-built of 12k); Scan Gaps #6/Through-line #9 (trusted source); C.10.a editorial control
MG-04Y2BBrightQueryLMap 600k legacy accounts onto the Y2B identity stack (DI-04); migrate with user comms, staging sign-in verification, and PIA/COPPA-approved handling of student-linked accounts.after DI-04, SP-03RFP core problem (600k+ users); SOW item 4; I.1.9 COPPA; I.1.3 PIA; Privacy Office student-credential trigger
MG-05Y2BBrightQueryMBulk-migrate 50k+ keep/transform user collections linked to migrated accounts; lineage labels on transformed items; old-URL reachability; sampled verification.after MG-02, MG-04RFP core problem (50k+ user collections); Scan #6 (no schema); RFP Deliverable templates/instructional formats
MG-06Y2BBrightQueryMRedirect map from MG-02 dispositions; 301s for kept/transformed URLs, 410/parent-301 for archived; canonical tags; validation crawl shows zero 404s at cutover.after MG-02SOW item 6 (search/answer-engine optimization); Scan sec. 2 (teachers discover via Google); RFP reach ambition
MG-07MUSTY2BBrightQueryMSitemaps, titles/meta, schema.org markup per instructional format for migrated pages; pre/post crawl proves no indexability regression at production launch.SOW item 6 ('fully optimized for search and answer engines'); Scan sec. 2; Through-line #6 (discovery)
MG-08MUSTY2BBrightQueryLStand up the long-term education-asset store early in Y2B, reusing SI metadata structures + URL repository, so migrated assets resolve through it, not siloed copies.SOW item 4 (long-term storage solution the new Lab can pull from); Plan of Accomplishment III (aggregate across SI)
MG-09MUSTY2BBrightQueryMReconciliation harness built before the first migration run: counts, checksums, metadata/attribution fidelity, link checks, per-stage report; idempotent + rollback.after MG-01Master Test Plan C.4.3 (pass/fail criteria); Sample Contract C/E staged acceptance; SOW item 3 audit basis
MG-10MUSTY2BBrightQueryMPublish open, documented schemas for migrated content in the long-term store; deliver the C.4.2 upgrade-path/portability plan; demonstrate lossless bulk export and re-import.after MG-08C.4.2 upgrade-path/portability plan; SOW item 4 ('maintainable, portable, open source'); modular API-driven deliverable
MG-11Y2BBrightQueryLPost-launch pass: re-render transform-class collections via templates into lesson/activity formats; OCR image-based text to editable where feasible; provenance kept.after MG-02RFP Deliverable (templates -> instructional formats); Scan #6 (no schema); Scan #7 (image-file 'editable' text)
MG-12PROCBrightQuery-Plan approved before the first Y2B migration run; gates each migration stage via SI acceptance; sets redirect timing, rollback, dual-run through the Y2B cutover.RFP Deliverables (trusted launch product, phased 2.0); SOW items 2 and 5; Sample Contract C/E staged delivery
PR-01MUSTPROCEDC-Named iterations with documented teacher input feeding each increment; bites at every increment review from Y1A sprint 1 through Y2B, retrospectives kept as records.SOW: test with real users, control scope, collect feedback, refine before broader launchRFP SOW item 5 (iterative, user-informed); Sample Contract Sec C/E agile staged delivery; Scan p.468
PR-02MUSTPROCEDC-Prototype-with-teachers gate before full build of each major capability; bites before the Y1B prototype build (OBL supports, templates) and before each Y2 expansion item.SOW: beta platform to test the model with teachers in classroomsRFP SOW item 5 (early prototyping with teacher feedback); Scan p.591; Scan MUST-DO #2/#4
PR-03MUSTPROCEDC-Sequencing gate: content audit + educator-needs content strategy accepted before any authoring/content-tooling build milestone; bites before Y1A tooling work starts.RFP SOW items 3 and 5; RFP pre-launch content-audit deliverable; Scan p.451/510 (strategy first)
PR-04MUSTPROCEDC-Month-1 discovery deliverable inventories SI's existing research, audit/strategy, metadata, and URL repository with reuse decisions; bites before Y1A design.RFP SOW n.b. (meet us where we are); RFP SOW item 4 (robust metadata structures, URL repository)
PR-05MUSTPROCEDC-Launch-essential vs later-phase feature register with useful/trusted/adoptable criteria per item; bites at Y1A scope-set and re-baselines at Y2A beta scope planning.RFP SOW item 2 (functionality prioritization); RFP Deliverables (immediately useful, trusted, adoptable)
PR-06PROCEDC-Research plan mapped to the scan's six classroom-centered goals, findings organized by teacher need; bites in Y1A discovery and when Y2A beta-cohort evidence is analyzed.RFP SOW item 1 (user journeys and needs); Scan six research goals p.480-488
PR-07PROCEDC-Named proceed/adjust/stop gates with teacher-evidence criteria per major capability; bites at Y1A prototype reviews and the M12 prototype-to-beta renewal decision.Scan p.468 (avoid problematic investment); Scan takeaways #8/#12; RFP Deliverables launch bar
PR-08MUSTPROCEDC-Staged delivery with SI review/acceptance per stage; draft+final on narrative deliverables; 5-day review/correction windows bite at every stage boundary Y1A-Y2B.RFP Sample Contract Sec C/E (staged acceptance; draft+final; 5-day windows; time is of the essence)
PR-09MUSTPROCBrightQuery-Milestones map to TRB gates: Requirements Review before Y1A build, System Design Review before the Y1B prototype build, Production Readiness Review before Y2B launch.RFP C.2.2 / C.7.7 (TRB gates); RFP SOW item 5 (governance, accessibility, security maintained)
PR-10PROCEDC-Delivery narrative ties each process choice to risk reduction and technical credibility; bites at proposal (pre-award) and each phase-boundary re-plan.RFP Part I.F (best value; combined technical factors outweigh cost); Scan takeaway #8
PR-11MUSTY2BBrightQueryLProduction launch gate on SI infra: run Master Test Plan, load/stress then security testing, fix high/medium vulns before acceptance; Y1B was only a prototype-scale pass.RFP SOW item 5; RFP C.4.3 Master Test Plan; C.4.4.1 perf/stress; C.4.4.2 security before acceptance
PR-12PROCEDC-Comms plan with cadence/channels for progress and risk, maintained risk register, change-control routing; bites from kickoff and at every status review both years.RFP Part III Project Management questions; Sample Contract staged acceptance, time is of the essence
PR-G1MUSTPROCBrightQuery-3-month post-acceptance warranty (2-month free browser/OS fixes), M-F 9-5 ET maintenance, critical-issue SLA; priced up front, bites at Y2B acceptance handoff.RFP I.6 warranty; I.6.1 maintenance M-F 9-5 ET; Part III Q17 customer service, Q18 SLA
PR-G2MUSTY2AEDCMBuild and run SI educator/admin training and onboarding as SI authoring lands at scale: materials, sessions, ongoing-support track continuing post-launch.RFP Part III Q16 (training/onboarding during and after implementation); Q21 (training/support fees)
PR-G3MUSTPROCEDC-On-site downtown-DC presence for kickoff and key technical presentations; key personnel 8:30-5:30 ET; bites at kickoff and each TRB gate, priced as travel.RFP C.7.9 (on-site DC for kickoff/key presentations); C.7.10 (key personnel 8:30-5:30 ET)
PR-G4MUSTPROCEDC-Engagement-wide QA methodology (definition of done, design/code review, defect prevention) distinct from Master Test Plan and draft/final acceptance; bites from Y1A on.RFP Part III Q10 (how do you ensure the quality of your work)
PM-01MUSTPROCEDC-Plan drafted by end of Y1B; email/PPC/owned-media campaigns execute through Y2 with spend tracked vs the 4M/49M reach goal, peaking at Y2B public launch.after PM-02RFP SOW item 6 (email/PPC/owned media); Scan sec 4 (multichannel distribution)
PM-02MUSTPROCEDC-Educator-discovery research (search/peers/social) completed during the Y1B educator sessions and early Y2A beta so the PM-01 channel mix is evidence-based before Y2B campaign spend commits.RFP SOW item 6 (audience research on discovery); Scan sec 2 (search/peers/social)
PM-03MUSTY2BBrightQueryMschema.org/LRMI metadata, sitemaps, SSR meta + AEO checklist on published resource pages; verify target queries. Y2B: beta is closed-cohort, public SEO pays at launch.after DS-07RFP SOW item 6 (optimized for search and answer engines); Through-line (b)
BETA-01MUSTY2AEDCMBeta-tester program intake: teacher application form, EDC-set selection criteria (including the AX-09 equity quotas), cohort onboarding and comms. Live before Y2A cohort recruitment.SOW: Teachers could apply to serve as beta testersafter SP-04EDC Year-1 SOW (added work item beyond the 179)
BETA-02MUSTY1BBrightQueryMBeta identity slice: invite-based teacher accounts with basic roles (teacher, author, reviewer, approver) carrying saved work, the approval workflow, and per-user feedback. Full SSO/rostering stays DI-04 in Y2B.SOW: test the platform with real usersEDC Year-1 SOW (added work item beyond the 179)