Tervane
Menu
Tervane Academy

Credentials for shipped work, not watched videos.

Each path ends in a current public product, exact release evidence, and a human scenario review.

01

Outcome mapping and product contracts

Turn a business workflow into explicit routes, roles, data, actions, and acceptance criteria.

  1. Outcome and audience
  2. Product contract
  3. Acceptance scenarios
02

Design systems and accessible UI

Build consistent responsive interfaces with tokens, reusable components, and accessibility evidence.

  1. Direction and tokens
  2. Responsive composition
  3. Accessibility review
03

Managed data and permissions

Model records and enforce actor, role, and row boundaries in a managed application.

  1. Collections and relations
  2. Roles and permissions
  3. Data lifecycle
04

Workflow and integration safety

Design external actions with scoped credentials, idempotency, retries, and failure handling.

  1. Action contracts
  2. Provider boundaries
  3. Failure and recovery
05

Verification and release evidence

Bind build, browser, accessibility, provider, and artifact evidence to the exact release users receive.

  1. Evidence layers
  2. Release review
  3. Rollback and receipts
06

Operate and improve live products

Use outcomes, monitoring, experiments, and reviewed changes to improve a live product safely.

  1. Outcome instrumentation
  2. Health and incidents
  3. Evidence-backed experiments
07

Agency delivery and handoff

Deliver client systems with clear acceptance evidence, access, billing, and provider ownership.

  1. Discovery and scope
  2. Client review
  3. Handoff boundaries
Artifact-backed certification

Ship first. Then apply.

A reviewer checks the current exact release, its scenario evidence, and your explanation. Awarded credentials expire after one year and stop validating if the bound release becomes stale.