Synthetic demonstration data only. No Tribal, student, or contributor data is used here. Stand-in language content is used, and no Native language is represented. This environment is not a FedRAMP-authorized or production system.

Illustrative language-first lifecycle

This shows how the platform would sit inside a Tribally governed process. The process starts with consultation and agreement. Software comes after that.

Illustrative discussion framework only. Not a proposal, offer, quotation, or response to a solicitation. Scope, participating communities, data terms, and implementation approach remain subject to formal Tribal consultation, authorization, acquisition strategy, and funding.

  1. 1

    Tribal agreement

    Confirm goals, authority, participant roles, language and dialect, cultural protocols, compensation, and data terms.

    Required evidence
    Written Tribal approval and named reviewers
    Platform role
    Configure the tenant, its roles, reviewers, audiences and consent terms to match the agreement.
  2. 2

    Language inventory

    Identify authorized speakers, recordings, texts, sound patterns, vocabulary, existing lessons, and gaps.

    Required evidence
    Approved inventory and readiness assessment
    Platform role
    Consent registry; private media storage; per-item “written form approved” flag.
  3. 3

    Activity development

    Build a manual instructional sequence and define the language skills learners should acquire.

    Required evidence
    Reviewed activities and skill map
    Platform role
    Authoring plus the enforced review workflow: fluent-speaker → cultural → education → authorization.
  4. 4

    Technical development

    Add speech and software functions that the available corpus and activity design can support reliably.

    Required evidence
    Test results and documented limits
    Platform role
    Speech adapters are enabled only after testing. Human review remains the fallback.
  5. 5

    Learner pilot

    Deliver activities, collect skill evidence, obtain independent proficiency evidence where feasible, and revise.

    Required evidence
    Learner results and Tribal review
    Platform role
    Learner and teacher views, xAPI evidence, and recall when anything changes.
  6. 6

    Scale decision

    Determine whether quality, governance, staffing, cost, and infrastructure support expansion.

    Required evidence
    Tribal and Department approval
    Platform role
    Audit and export evidence for the decision, and a credible exit path either way.

Principles carried through every stage