Certification Intro

The pathway is introduced now as a reviewed lane, not as an instant badge machine.

This route is intentionally conservative. It describes how the future certification experience is staged, what kinds of readiness are expected, and which parts remain manual or queued until the academy and approval systems are live.

Do not treat this page as a self-serve enrollment or certificate issuance surface yet.
Keep case review, operator readiness, and role upgrade expectations explicit before automation appears.
Use this route to stabilize language, not to over-promise platform maturity.
Level Framing

The pathway is staged so operators know what kind of growth each lane represents.

These levels are intentionally described as role expectations and review lanes first. Final course stacks, LMS sync, and certificate issuance are later tasks.

Foundation observer

Learn the common SART reading language, how structural notes are framed, and how public-facing overclaim is avoided.

Clinical specialist lane

Move into supervised interpretation, case communication discipline, and more explicit operator accountability.

Master and mentor lane

Progress toward review authority, mentorship contribution, and later educator-facing responsibilities.

Readiness Expectations

The intro page explains what must be true before a lane is treated as active.

Certification is not framed as a purchase or a static badge. It depends on readiness signals, documented review, and later membership or approval rules.

Clinical baseline

The candidate needs an interpretable baseline in posture, breath, and loading language before advanced route entry makes sense.

Reviewable case evidence

Advancement assumes later case documentation and review, not only video completion or checkout history.

Association conduct

Member-facing communication, care tone, and route usage stay tied to association conduct expectations from the start.

What Stays Manual For Now

This phase makes later review and approval work clearer instead of pretending it already runs automatically.

The page names the operational boundaries now so later academy, membership, and certificate automation work can attach cleanly instead of being invented ad hoc.

Manual review remains later

The approval queue, file upload review, and role upgrade logic are not live in this step and remain later platform work.

Academy delivery remains later

Course catalogs, lesson players, progress sync, and completion automation still belong to the academy track.

Certificate issuance remains later

This page can explain the destination, but real certificate generation and later profile upgrades still wait on future implementation tracks.

This route is intentionally a certification introduction, not the final academy or approval system. It exists so language and expectations can stabilize early.