Documentation
Canon-backed docs for every surface.
Use this guide to understand the Meridian canon, the rollout model, and the implementation patterns that keep the product consistent across teams and releases.
Getting started
Meridian documentation is organized around the product canon so every team can use the same language when they talk about workflows, roles, and rollout stages.
- Start with the canon so you understand the shared terms.
- Move into implementation once the workflow shape is clear.
- Use the rollout guide to decide what should happen in pilot, expand, and scale.
Core canon model
Programs, cohorts, sections, progression levels, and role assignments form the backbone of the academic model. Workflows such as attendance, interventions, approvals, and audit trails are mapped on top of that structure.
Structure
Programs and cohorts
These describe how the academic organization is grouped for reporting, access, and workflow routing.
Ownership
Roles and assignments
Role assignments keep accountability visible so requests do not float without an owner.
Evidence
Workflow records
Every action should leave a trace that is useful for review, support, and governance.
Rollout guide
Pilot
Scope one school or one workflow family, keep the team small, and learn what needs to be simplified before wider rollout.
Expand
Add the next set of workflows, tighten ownership rules, and review where approvals or data checks need to change.
Scale
Roll the same model across more teams once the process is stable, documented, and measurable.
Example shape
The example below shows the kind of structure Meridian expects when a team maps a workflow into the canon model.
{
"workflow": "attendance_follow_up",
"owner": "class_teacher",
"inputs": ["absence_signal", "context_note"],
"actions": ["review", "escalate", "close"],
"evidence": ["comment", "approval", "closure_status"]
}Glossary and next steps
The glossary keeps the language consistent across the product, the documentation, and the implementation process. If a term is ambiguous, it should be clarified in the canon before it spreads elsewhere.
- Canon: the shared source of truth for product terms and structures.
- Pack: a grouped delivery area that scopes what is active now and what is planned next.
- Evidence: the record that shows what changed, who changed it, and why.