Work Anatomy library

AFPT Anatomy

Services
Web app, Content platform, API, MCP
Year
2026

Everything AFPT teaches about the body, in one place.

AFPT educates personal trainers in Norway, in Sweden and internationally. We built the library their students learn anatomy in, and the one source their other apps get it from.

  • The library
    The library
  • Every side of a muscle
  • On a phone
    On a phone
  • The body as a map
  • Programme design
    Programme design
  • Learning as a game

Where it started

Four course sites, one language each

The anatomy text lived on four separate course sites, one for each language and school. The records behind it sat in an older database, and a muscle was shown from a few fixed angles.

AFPT needed one place to get it right, in every language, for every app that teaches it.

What we built

One library, where everything is connected

  1. See it from every side

    Before: a muscle was a few pictures from fixed angles.

    Now: every structure turns under your finger. The turntables are rendered in 3D and put on the site with one command.

  2. Everything is connected

    Before: a muscle was a page of text.

    Now: a muscle knows where it attaches, what it moves, which nerve runs it and which exercises train it. Follow any of them.

  3. The body as a map

    Before: you had to know the name to find the structure.

    Now: point at the body and read what is there. The same map turns into a quiz when it is time to test yourself.

  4. Movement you can see

    Before: a movement was a sentence to memorise.

    Now: joints and exercises move on the screen, with the working muscles lit as they work.

Learning

A game built from the curriculum

Before: a teacher at AFPT had made a quiz game on the side, with its own questions, apart from the teaching content.

Now: the game is part of the library. Its questions are made from the library's own records, so they are right when the records are, and the server keeps the score.

Programme design

The syllabus as a tool

The need: students learn to design a training programme in nine steps, and need somewhere to practise them.

What we did: the nine steps are a tool. A student designs for a made-up client, picks exercises from the library, and sees the volume add up as the programme grows.

One source

Written once, read everywhere

Before: each language had its own copy of the anatomy, kept up by hand.

Now: a record is written once. A translation is drafted by AI and marked as a draft until a person has approved it, and other apps can only read what is published and approved.

Below: one correction by a teacher, and every place it reaches.

A teacher, in the library

Biceps brachii: it bends the elbow and turns the palm up.

Review the Swedish draft

Function

Approve

Back to the teacher

The correction is in three languages, and every app that reads the library has it.

The anatomy library

  1. Saved in one place

    Changes
    One field of one record
    Copies
    None to keep in step
  2. The translations are marked as out of date

    Norwegian, Swedish
    Marked by themselves
    Nobody
    Has to remember them
  3. AI drafts the new translations

    Marked
    As a machine draft
    Leaves
    Latin names and cross-references as they are
  4. A person approves each one

    Checks
    The draft against the corrected text
    Approves
    That version, and no later one
  5. Other apps get it once it is approved

    Until then
    They are given the English
    After
    The approved translation
  1. The record

    One per muscle, bone and joint. The reader, the game and the programme designer all read it

    • Is saved once
  2. OpenAI

    Drafts each translation from the corrected text

    • New drafts are made
  3. The API

    What other apps read: published records, approved translations

    • Other apps follow

Written once. Nobody copied it anywhere.

MCP

What happens when the staff ask their assistant

Which records lack pictures

AFPT's staff, in their own AI assistant

Which records have no pictures yet?

Back in the assistant

A list of what is missing, instead of sixty screens to click through.

The staff server of the library

  1. Signed in as themselves

    Who
    One of AFPT's staff
    May
    What they may do in the admin, nothing more
  2. Looked through the library

    Finds
    Records with no picture
    Changes
    Nothing
  1. Roles and permissions

    What each person may do in the admin

    • Is recognised
  2. The library

    Every muscle, bone, joint and exercise, with its pictures and translations

    • Looks for the gaps

Only a read. Nothing was changed.

For Swedish drafts

AFPT's staff, in their own AI assistant

Draft Swedish for everything that lacks it.

Back in the assistant

The drafts are being made. Each one waits for a person to approve it before other apps get it.

The staff server of the library

  1. Signed in as themselves

    Who
    One of AFPT's staff
    May
    What they may do in the admin, nothing more
  2. Shown as a count before anything is made

    Would draft
    What has no approved Swedish
    Needs
    A yes
  3. One draft per record

    Marked
    As machine drafts
    Leaves
    Latin names and cross-references as they are
  1. Roles and permissions

    What each person may do in the admin

    • Is recognised
  2. The library

    Every muscle, bone, joint and exercise, with its pictures and translations

    • Counts first
  3. OpenAI

    Drafts each translation

    • Drafts are made

Logged in their name, like everything else they change.

To set an exercise's muscles

AFPT's staff, in their own AI assistant

Which muscles does this exercise work? Add the core as a stabiliser.

Back in the assistant

Done. The core is added as a stabiliser, and the change is logged in your name.

The staff server of the library

  1. Signed in as themselves

    Who
    One of AFPT's staff
    May
    What they may do in the admin, nothing more
  2. The exercise, with its muscles

    Shows
    Each muscle and the part it plays
    Roles
    Primary, secondary or stabiliser
  3. The change is shown before it is made

    Would add
    One muscle, as a stabiliser
    Needs
    A yes
  1. Roles and permissions

    What each person may do in the admin

    • Is recognised
  2. The library

    Every muscle, bone, joint and exercise, with its pictures and translations

    • Reads the exercise
  3. The log

    Every change, and who made it

    • Shows it first

Set in one sentence, with no form to fill in.

What changed

What we solved for AFPT

Anatomy is one thing now, not four copies of it. What a teacher corrects is corrected for every student, in every language, in every app.

  • One library instead of four course sites
  • Three languages from one text
  • Every structure seen from every side
  • Students practise on the real content
  • Other apps read from one source
  • Staff keep it right by asking

Let's talk

Tell us what you want to build, and we will work it out together.