This dashboard will become the verification layer for mission journals,
XP approval, badge confirmation, certificate readiness, and student progress updates.
Teachers confirm that student mission work, reflection, and evidence meet
completion expectations.
Learning Evidence
Journals + Artifacts
Reflections, written responses, uploaded work, and future video submissions
can support review decisions.
Student Impact
Progress Verified
Approved work can update student XP, badge progress, certificate status,
and portfolio records.
Teacher Dashboard V.2
Student Review Queue Layer
This queue prepares the Teacher Dashboard to organize student journal submissions,
mission evidence, XP approval, badge confirmation, and certificate readiness.
Today’s Queue
0
No submissions awaiting review today.
This Week
0
Weekly review activity will appear here.
Completed Reviews
0
Completed teacher reviews will appear here.
Priority Items
0
Urgent review items will be flagged here.
Review Queue Preview
Student Submissions
No Active Submissions
Student
Mission
Submission Type
Status
Action Needed
Sample Student
Samaritan Road Repair
Journal + Evidence
Pending
Review Reflection
Sample Student
Variables of Algebra
Journal Reflection
Awaiting
Approve XP
Sample Student
Boss Battle
Mission Evidence
Ready
Badge Review
Pending Review
0
Reflection submissions awaiting educator review.
XP Approval
0
Completed work awaiting XP confirmation.
Badge Approval
0
Badge eligibility awaiting verification.
Certificate Review
0
Students approaching certificate readiness.
Teacher Dashboard V.3
Rubric Review Layer
This rubric prepares the Teacher Dashboard to evaluate mission journals,
evidence artifacts, reflection quality, XP eligibility, badge readiness,
and certificate progression.
Concept
Pending
Does the learner understand the mission concept?
Reasoning
Pending
Does the learner explain thinking, strategy, and choices clearly?
Evidence
Pending
Does the artifact support mission completion and understanding?
Reflection
Pending
Does the learner show growth, persistence, and self-assessment?
Teacher Scoring Preview
Mission Review Rubric
Criteria
Developing
Proficient
Advanced
Concept
Basic understanding
Clear understanding
Transfers concept independently
Reasoning
Limited explanation
Explains strategy clearly
Justifies decisions with precision
Evidence
Evidence is incomplete
Evidence supports learning
Evidence is strong and well explained
Reflection
Minimal reflection
Thoughtful self-assessment
Deep connection to growth and next steps
XP Decision
Pending
Rubric review will support XP approval.
Badge Decision
Pending
Badge eligibility depends on review quality and completion.
This layer prepares the Teacher Dashboard to confirm XP awards after mission
completion, journal reflection, evidence review, and rubric evaluation.
XP Pending
0 XP
XP waiting for teacher approval.
XP Approved
0 XP
Confirmed XP ready for student dashboard sync.
XP Denied
0 XP
XP not awarded due to incomplete requirements.
Dashboard Sync
Coming Soon
Approved XP will update student progress later.
XP Approval Workflow
Review → Approve → Sync
1. Review MissionConfirm mission activity and journal completion.
2. Check EvidenceVerify student artifacts support the learning claim.
3. Apply RubricUse Concept, Reasoning, Evidence, and Reflection criteria.
4. Approve XPConfirm XP eligibility for student dashboard update.
Standard Mission
+50 XP
Default XP award for verified standard missions.
Builder Mission
+75 XP
Enhanced XP award for higher challenge missions.
Advanced Mission
+100 XP
Future XP award for advanced mission pathways.
Teacher Dashboard V.5
Badge Confirmation Layer
This layer prepares the Teacher Dashboard to confirm badge eligibility after
rubric review, XP approval, mission completion, and evidence verification.
Problem Solver
Pending
Reasoning, persistence, and solution-building.
Builder of Integrity
Locked
Responsibility, excellence, and faithful completion.
Truth Seeker
Locked
Inquiry, evidence, investigation, and clarity.
Faithful Steward
Locked
Careful growth, service, and trustworthy effort.
Unity Weaver
Locked
Collaboration, communication, and shared purpose.
Badge Confirmation Workflow
Review → Verify → Confirm Badge
1. Review EvidenceConfirm artifacts support the badge pathway.
2. Check ReflectionConfirm growth, reasoning, and self-assessment.
3. Confirm XPEnsure XP approval aligns with mission completion.
4. Approve BadgeMark the badge pathway as verified.
Approval Status
Not Approved
Badge approval requires teacher verification.
Student Sync
Coming Soon
Approved badges will appear on the Student Dashboard.
This layer prepares teachers to verify when students have satisfied mission,
journal, XP, badge, and evidence requirements for certificate eligibility.
5. Certificate ReadyStudent becomes eligible for certification.
Certificate ID
Pending
Unique IDs will support verification and tracking.
Portfolio Link
Coming Soon
Certificates will connect to portfolio records.
Student Sync
Pending
Approved certificates will update the Student Dashboard.
Teacher Dashboard V.7
Portfolio Verification Layer
This layer prepares teachers to verify which student artifacts are ready to become
part of the learner portfolio after mission completion, journal review, evidence approval,
badge confirmation, and certificate readiness.
Portfolio Artifacts
0
Student artifacts awaiting verification.
Evidence Approved
0
Evidence artifacts approved for portfolio use.
Teacher Feedback
0
Feedback records ready to attach to portfolio entries.
Portfolio Sync
Coming Soon
Approved work will later update student portfolios.
Portfolio Verification Workflow
Evidence → Review → Portfolio Record
1. Review ArtifactTeacher checks reflection, evidence, or submitted work.
2. Confirm QualityArtifact clearly shows learning, reasoning, or growth.
3. Attach FeedbackTeacher feedback becomes part of the learning record.
4. Approve PortfolioArtifact becomes eligible for the student portfolio.
Artifact Type
Pending
Journal, image, document, model, or video evidence.
Portfolio Status
Not Approved
Teacher verification is required before portfolio placement.
Student Dashboard
Pending Sync
Approved artifacts will appear in the student portfolio view.
Teacher Dashboard V.8
Parent Communication Layer
This layer prepares teachers to communicate student progress clearly to parents,
including mission activity, journal reflection, XP growth, badge status,
certificate readiness, and portfolio development.
Parent Summary
Coming Soon
Teachers will be able to summarize student progress in parent-friendly language.
Progress Notes
Pending
Notes can highlight mission completion, reflection quality, and next steps.
Family View
Planned
Future parent-facing summaries can connect to the Student Dashboard parent layer.
Parent Update Framework
What Parents Need to Know
What the student completedMission activity, journal reflection, and evidence preparation.
What growth was observedReasoning, persistence, communication, reflection, and problem solving.
What was verifiedTeacher review, XP approval, badge pathway, or certificate readiness.
What comes nextNext mission, next badge pathway, portfolio artifact, or support need.
Sample Parent-Friendly Update
Your child has begun the NOLA mission pathway and is building progress through
mission-based learning, reflection, evidence preparation, and teacher review.
As work is verified, progress may appear as XP, badges, certificates, and portfolio growth.
Teacher Dashboard V.9
Educator Executive Overview
This overview provides a quick understanding of how missions, journals,
reviews, XP, badges, certificates, portfolios, and parent communication
work together within the NOLA ecosystem.
Mission
Journal
Review
XP
Badge
Certificate
Portfolio
Teacher Purpose
Facilitate Growth
Teachers guide learning, verify evidence, provide feedback,
and confirm achievement milestones.
Verification Role
Confirm Progress
Mission completion, journal reflections, XP approvals,
badge confirmations, and certificate readiness all pass
through the teacher review process.
Student Impact
Visible Growth
Every review decision contributes to student progression,
recognition, and portfolio development.
Educator Workflow
Review → Verify → Approve → Communicate
1. ReviewEvaluate mission submissions and journal reflections.
2. VerifyConfirm evidence quality and rubric alignment.
3. ApproveAuthorize XP, badges, certificates, and portfolio artifacts.
4. CommunicateProvide meaningful feedback to students and families.
5. Update ProgressSupport dashboard synchronization and learner growth tracking.
Why This Matters
Trusted Verification
The teacher dashboard ensures student growth is supported by evidence,
reflection, review, and meaningful achievement recognition.
System Summary
One Connected Ecosystem
Missions, journals, XP, badges, certificates, portfolios,
student dashboards, and parent communication all connect
through the teacher verification process.
Teacher Dashboard V.10
Integration Summary & System Freeze Layer
This section summarizes Platform Integration Phase II and establishes the
Teacher Dashboard as the verification layer for the NOLA progression ecosystem.
Review Queue
Rubric
XP Approval
Badge Confirm
Certificate
Portfolio
Parent Update
Verification Layer
Teacher Dashboard
The dashboard now gives educators a clear framework for reviewing,
verifying, approving, and communicating student progress.
Student Progress Sync
Review → Update
Teacher review decisions prepare the system for future XP, badge,
certificate, and portfolio updates.
Instructional Role
Facilitator + Verifier
Teachers support learning by guiding reflection, checking evidence,
approving progress, and communicating next steps.
Phase II Completion
Teacher Dashboard Integration Phase II Complete
This dashboard now connects the teacher-facing verification workflow:
student review queue, rubric review, XP approval, badge confirmation,
certificate readiness, portfolio verification, parent communication,
and educator orientation.
V.1 Command Center
V.2 Review Queue
V.3 Rubric Review
V.4 XP Approval
V.5 Badges
V.6 Certificates
V.7 Portfolio
V.8 Parent Communication
V.9 Educator Overview
V.10 Freeze Layer
What This Enables
Trusted Progress Verification
Educators can clearly see how student work moves from journal submission
to review, XP approval, badge confirmation, certificate readiness,
and portfolio growth.
Next Platform Phase
Dashboard Synchronization
The next phase will align student and teacher dashboard states so that
reviewed progress can eventually update learner-facing records.
Platform Integration Phase III
Dashboard Synchronization Architecture
This bridge defines how student progress will eventually move from mission
submission to teacher verification and back into the Student Dashboard.
Student Submission
Teacher Review
XP Approval
Badge Confirm
Certificate Ready
Portfolio Update
Student Sync
Student Action
Submit Work
The student completes a mission, opens the journal, submits reflection,
and prepares evidence.
Teacher Action
Review + Verify
The teacher reviews the submission, applies the rubric, approves XP,
confirms badges, and verifies progress.
System Action
Sync Progress
Approved progress will eventually update the learner’s dashboard,
certificate status, badge collection, and portfolio record.
2. Teacher ConfirmsBadge eligibility is reviewed and approved.
3. Student Dashboard UpdatesBadge changes from Locked to Active.
4. Portfolio Records BadgeRecognition becomes part of the student's verified achievements.
Problem Solver
Monitor
Integrity
Monitor
Truth Seeker
Monitor
Steward
Monitor
Unity Weaver
Monitor
Platform Integration Phase III V.5
Certificate Synchronization Logic
This layer defines how verified student achievements become official
certificates through teacher approval and synchronized platform updates.
Certificate Candidate
Pending
Student has met the preliminary requirements for certification.
Teacher Verification
Required
Final educator review confirms readiness for certification.
Certificate Status
Awaiting Issue
System prepares certificate generation after approval.
Student Dashboard
Pending Sync
Issued certificates appear in the learner achievement record.
Certificate Synchronization Workflow
Verify → Issue → Synchronize
1. Requirements CompleteMission, journal, XP, and badge milestones are satisfied.
2. Teacher ApprovalEducator verifies the learner has completed all requirements.
3. Certificate GeneratedThe platform prepares a verified certificate with a unique ID.
4. Dashboard UpdatesCertificate status synchronizes across Student and Teacher Dashboards.
Verification ID
Pending
Unique identifier assigned during certificate generation.
Issue Date
Pending
Recorded automatically when the certificate is issued.
Portfolio Link
Pending
Certificate becomes part of the learner's verified portfolio.
Audit Record
Required
Backend logs maintain a permanent verification history.
Platform Integration Phase III V.6
Portfolio Synchronization Logic
This layer defines how verified student work becomes a permanent portfolio
artifact after teacher review, synchronization, and approval.
Evidence Candidate
Pending
Student work has been submitted for portfolio consideration.
Teacher Verification
Required
Artifacts must be reviewed before becoming portfolio records.
Portfolio Status
Awaiting Sync
Approved artifacts are prepared for portfolio integration.
Student Record
Pending Update
Verified artifacts will appear in the learner's portfolio timeline.
Portfolio Synchronization Workflow
Verify → Archive → Synchronize
1. Artifact SubmittedJournal, project, image, document, or video is uploaded.
2. Teacher ReviewsEvidence quality and learning outcomes are verified.
3. Portfolio ArchiveApproved work becomes part of the learner's permanent record.
4. Dashboard SynchronizesStudent and Teacher Dashboards display the updated portfolio status.
Portfolio Components
Mission EvidenceVerified mission artifacts.
Journal ReflectionsStudent thinking and self-reflection.
Teacher FeedbackVerified instructional comments.
BadgesRecognition milestones.
CertificatesVerified credentials.
Growth TimelineA chronological record of learner progress.
Portfolio Integrity
Verified
Only teacher-approved artifacts become permanent records.
Synchronization
Automatic
Future backend services will keep dashboards synchronized.
Long-Term Value
Learning History
The portfolio preserves evidence of growth across the learner's journey.
Platform Integration Phase III V.7
Parent Communication Synchronization
This layer defines how verified student progress can eventually be translated
into parent-friendly updates after teacher review and dashboard synchronization.
Progress Summary
Pending
Parent-facing summaries will be generated from verified progress.
Teacher Notes
Required
Teacher feedback becomes the trusted communication source.
Family View
Planned
Parents will see simplified progress, not internal review controls.
Privacy Guard
Required
Parent access must be limited to their own child’s records.
Parent Sync Workflow
Verify → Summarize → Communicate
1. Teacher VerifiesMission progress, XP, badges, certificates, and portfolio records are confirmed.
2. Summary CreatedThe system prepares parent-friendly language from verified progress.
3. Parent View UpdatesFamilies see clear progress summaries and next-step guidance.
4. Privacy ProtectedOnly authorized parent-child records should be visible.
Parent Language
Plain + Clear
Translate platform terms into family-friendly progress updates.
Next Steps
Visible
Parents should understand what the student should do next.
Communication Log
Future
Future systems can track when progress summaries are sent or viewed.
Platform Integration Phase III V.8
Notification Synchronization Framework
This layer prepares the platform to deliver timely notifications whenever
verified student progress changes through teacher review and system synchronization.
Student Alerts
Pending
Students receive notifications after verified progress updates.
Teacher Alerts
Pending
Teachers receive reminders for pending reviews and approvals.
Parent Alerts
Optional
Parents receive approved progress summaries when enabled.
System Events
Queued
Future backend services will process notification events.
Notification Workflow
Event → Queue → Deliver → Confirm
1. Event TriggeredTeacher approval creates a synchronization event.
2. Notification QueuedBackend prepares the appropriate recipient messages.
3. Message DeliveredStudent, teacher, or parent receives the update.
4. Dashboard RefreshesLatest verified progress becomes visible throughout the platform.
High Priority
Needs Revision
Immediate notification encourages students to improve and resubmit work.
Achievement
Badge / Certificate
Celebrate verified accomplishments with timely recognition.
Notification Log
Future Audit
Maintain a secure history of notification events and delivery status.
Platform Integration Phase III V.9
Executive Synchronization Overview
This overview illustrates how learning, verification, recognition,
communication, and synchronization operate together across the
NOLA Platform.
Mission
Journal
Teacher Review
Recognition
Synchronization
Communication
Growth Record
Learning System
Student Journey
Students complete missions, reflect on learning,
submit evidence, and demonstrate growth through
authentic performance.
Verification System
Teacher Review
Teachers evaluate journals, evidence,
and mission performance before approving
progress and recognition.
Recognition System
Verified Achievement
XP, badges, certificates,
and portfolio records are awarded only
after successful verification.
Complete Synchronization Cycle
Learn → Verify → Recognize → Synchronize
1. LearnStudent completes missions and reflections.
2. VerifyTeacher confirms evidence and learning quality.
3. RecognizeXP, badges, certificates, and portfolio records are approved.
4. SynchronizeVerified progress updates every connected dashboard.
Why Synchronization Matters
One Source of Truth
Students, teachers, and families all view
the same verified learning journey,
reducing confusion while increasing trust.
Platform Vision
Connected Learning Ecosystem
Every verified action contributes to a
continuously growing learner record that
supports meaningful educational progress.
Platform Integration Phase III V.10
Integration Summary & System Freeze Layer
Platform Integration Phase III completes the synchronization architecture
connecting student learning, teacher verification, recognition systems,
communication pathways, and synchronized dashboard updates into one
unified educational ecosystem.
Learning
Verification
Recognition
Synchronization
Communication
Portfolio
Growth
Learning Engine
Student Journey
Missions, journals, reflections, and evidence form the
foundation of meaningful learning.
Verification Engine
Trusted Review
Teacher review ensures every recognition is supported by
authentic evidence and instructional judgment.
Synchronization Engine
One Connected Platform
Approved progress flows across dashboards,
portfolios, parent views, and future analytics.
Phase III Completion
Dashboard Synchronization Framework Complete
Platform Integration Phase III establishes the synchronization framework
that connects student actions, teacher verification, recognition systems,
communication pathways, and portfolio growth into a unified progression
architecture ready for backend implementation.
V.1 Architecture
V.2 Status Mapping
V.3 XP Sync
V.4 Badge Sync
V.5 Certificate Sync
V.6 Portfolio Sync
V.7 Parent Sync
V.8 Notifications
V.9 Executive Overview
V.10 Freeze Layer
Platform Status
Architecture Complete
Learning, verification, recognition, synchronization,
and communication now operate as one coherent framework,
providing a solid foundation for backend development.
Next Development Phase
Backend Implementation
The next phase focuses on live data services, secure authentication,
synchronization APIs, analytics, notification delivery,
and production-ready infrastructure.
Phase IV • Production & Pilot Readiness
V.1 Production Security Framework
This framework establishes the security foundation that protects
every learner, educator, administrator, and family participating
within the NOLA Education Platform.
Identity
Authentication
Authorization
Verification
Protection
Monitoring
Trust
Identity
User Authentication
Every platform participant receives a verified identity
before accessing protected resources.
Authorization
Role-Based Access
Students, teachers, parents, administrators,
and researchers receive only the permissions
required for their role.
Monitoring
Continuous Protection
Authentication events, security alerts,
and system activity are recorded
for future auditing.
Production Security Objectives
Trust Begins Before Login
Secure Login
JWT Sessions
Password Policy
Role Security
Session Timeout
MFA Ready
Audit Logs
Encryption
API Security
Monitoring
Students
Protected
Secure learning environment with
role-restricted access.
Teachers
Verified
Secure instructional tools
with authenticated permissions.
Parents
Private
Access limited exclusively
to their authorized learner.
Administrators
Governance
Elevated permissions
protected through additional
authentication controls.
Phase IV • Production & Pilot Readiness
V.2 Production Database Architecture
This architecture defines the core data systems required to support
secure student records, teacher review workflows, XP tracking,
badge confirmation, certificate generation, portfolio preservation,
notifications, and audit logging.
Users
Schools
Missions
Journals
XP Ledger
Portfolio
Audit Logs
Identity Tables
Users + Roles
Stores students, teachers, parents, administrators, and researcher access records.
Learning Tables
Missions + Journals
Stores mission progress, journal submissions, evidence records, and review status.
Recognition Tables
XP + Badges
Stores verified XP transactions, badge eligibility, badge status, and rank progress.
Credential Tables
Certificates
Stores certificate readiness, issue status, verification IDs, and credential history.
Core Database Domains
One Structured Learning Record
usersAccount identity, login email, role, and status.
schoolsSchool, organization, cohort, and pilot partner records.
student_profilesGrade band, dashboard status, parent links, and progress summary.
teacher_profilesClassroom assignments, review permissions, and cohort visibility.
missionsMission titles, categories, tracks, grade levels, and status.
journal_submissionsStudent reflections, timestamps, evidence links, and review state.
xp_ledgerVerified XP transactions separated by source and approval record.
badge_recordsBadge eligibility, locked/active/earned status, and teacher confirmation.
certificate_recordsCertificate readiness, issue date, verification hash, and audit trail.
portfolio_artifactsApproved evidence, reflections, teacher feedback, and student showcase items.
notificationsStudent, teacher, parent, and administrator event messages.
audit_logsSecurity events, approval actions, overrides, and system changes.
Data Integrity
Verified Sources
Progress records should only update from trusted events such as
teacher review, system approval, or administrator action.
Privacy Boundary
Role-Scoped Access
Students, parents, teachers, and administrators should only see
data authorized by their assigned role and relationship.
Audit Readiness
Every Change Logged
XP changes, badge approvals, certificate issuance, and portfolio
decisions should create traceable audit records.
Phase IV • Production & Pilot Readiness
V.3 Synchronization Services
This service layer defines how verified student progress, teacher review
actions, recognition events, certificates, portfolio artifacts, notifications,
and audit records will synchronize across the NOLA Education Platform.
Review Event
Sync Service
XP Ledger
Badge Engine
Certificate
Portfolio
Notifications
Student Sync
Progress Updates
Updates rank, XP, badge status, certificate readiness,
mission history, and portfolio records after verified events.
Teacher Sync
Review Actions
Converts educator approvals, revision requests, rubric decisions,
and verification actions into trusted platform events.
Parent Sync
Family Summaries
Translates verified progress into parent-safe summaries
while preserving privacy and role boundaries.
portfolio_enginePromotes approved journals, evidence, feedback, badges, and certificates into portfolio artifacts.
notification_engineQueues student, parent, teacher, and administrator progress notifications.
audit_engineLogs security events, data changes, teacher approvals, overrides, and synchronization history.
cache_refresh_serviceClears stale dashboard states and refreshes visible records after approved changes.
Trigger Source
Teacher Review
Most progress sync events begin with educator verification.
Event Type
Approved
Approval events update XP, badges, certificates, and portfolios.
User Impact
Dashboard Update
Students and families see progress after verified synchronization.
System Guard
Audit Log
Every synchronization action should create a traceable record.
Phase IV • Production & Pilot Readiness
V.4 Administration Console
This console defines the administrative layer needed to manage schools,
pilot cohorts, teacher accounts, student enrollment, parent access,
researcher visibility, analytics, and platform governance.
Schools
Cohorts
Teachers
Students
Parents
Researchers
Analytics
School Setup
Organizations
Configure pilot schools, classrooms, partner groups, and implementation sites.
User Management
Accounts
Create, manage, disable, and review teacher, student, parent, and administrator access.
Pilot Controls
Cohorts
Group participants by school, teacher, grade band, mission track, or research segment.
Governance
Oversight
Monitor permissions, audit logs, security events, and platform activity.
Core Administration Modules
Manage the Pilot Without Disrupting Learning
school_managementSchool profiles, partner organizations, implementation sites, and launch status.
cohort_builderGroups students and teachers by class, grade band, pilot group, or research condition.
teacher_accountsTeacher onboarding, permissions, classroom links, and review queue visibility.
launch_monitorTracks readiness, known issues, deployment notes, cache checks, and uptime indicators.
Admin Role
Steward
Administrators protect implementation quality while ensuring
students and teachers receive the right access.
Pilot Role
Coordinator
Pilot leaders can monitor cohorts, feedback, system readiness,
and implementation milestones.
Research Role
Observer
Researchers should receive only authorized, anonymized, and
permissioned access to pilot learning signals.
Phase IV • Production & Pilot Readiness
V.5 Launch Readiness
This readiness layer defines the final operational checks needed before
NOLA moves from protected development into soft launch, pilot testing,
and public-facing implementation.
Performance
Mobile
Security
Backups
Recovery
Monitoring
Launch
Performance
Fast + Stable
Pages should load smoothly across desktop, tablet, and mobile devices.
Security
Protected
SSL, authentication, permissions, and audit trails must be verified before launch.
Backups
Recoverable
Site files, platform assets, forms, and documentation should be backed up.
Monitoring
Visible
Known issues, uptime, system checks, and feedback should be tracked.
Launch Readiness Checklist
Turn on the Lights with Confidence
mobile_responsivenessVerify all core pages stack cleanly on phones and tablets.
navigation_integrityConfirm all mission, journal, guild, dashboard, contact, and form links route correctly.
ssl_securityConfirm HTTPS works across all public pages and active domains.
backup_packageCreate a launch backup of public_html, assets, documents, audits, and launch files.
form_privacyDisable public response summaries and protect private form responses.
known_issues_logDocument unresolved non-blocking items such as routing anomalies or cached pages.
access_control_reviewConfirm protected dashboards are not publicly editable or exposing sensitive records.
soft_launch_testersPrepare educator, student, parent, and faith-community testing groups.
recovery_planConfirm where backups live and how the site can be restored if Bluehost fails.
Soft Launch
Controlled Access
Begin with small focus groups, guided testing prompts,
and structured feedback collection.
Pilot Launch
Measured Growth
Expand to teachers, principals, researchers, and selected
student/parent groups after soft-launch findings are reviewed.
Public Launch
January 6
Launch publicly after readiness checks, security review,
backup confirmation, and stakeholder testing.
Launch Principle
Right over Rushed
NOLA should launch when the platform is stable, trustworthy,
documented, recoverable, and ready to serve the people it was built for.
Phase IV • Production & Pilot Readiness
V.6 Pilot Operations
This operations layer defines how NOLA will support guided soft-launch testing,
pilot participation, stakeholder feedback, research signals, and structured
improvement before broader public launch.
Educators
Students
Parents
Faith Community
Principals
Researchers
Feedback
Educator Group
5 Testers
Evaluate classroom usefulness, mission clarity, journals, and teacher workflow.
Student Group
5 Testers
Evaluate engagement, clarity, motivation, progression, and next-step guidance.
Parent Group
5 Testers
Evaluate trust, child progress visibility, communication, and enrollment confidence.
Faith Community
5 Testers
Evaluate purpose, mission alignment, reflection, and values-based clarity.
Soft Launch Testing Structure
Guided Feedback, Not Random Browsing
testing_promptsEach group receives 3–5 guided prompts aligned to their role and perspective.
navigation_tasksParticipants move through Home, Missions, Journals, Guild, Dashboards, and Forms.
clarity_checkParticipants explain what NOLA is in their own words after testing.
engagement_signalsStudent testers identify what motivates them to continue or return.
trust_signalsParents and educators identify what increases or decreases confidence.
implementation_notesEducators and principals note classroom fit, barriers, and pilot readiness.
research_signalsResearchers identify observable evidence of reflection, reasoning, and growth.
issue_loggingAll broken links, unclear sections, mobile issues, and privacy concerns are logged.
revision_loopFeedback becomes prioritized improvements before pilot expansion.
Expand toward teachers, principals, researchers,
and selected student/parent participants.
Public Launch
January 6
Launch after testing, revisions, security review,
backup confirmation, and readiness checks.
Pilot Principle
Listen Before Scaling
The pilot is not only a test of the platform. It is a structured opportunity
to listen to students, educators, parents, faith-community voices,
principals, and researchers before expanding NOLA more broadly.