跳到正文
免费试用

People Development

One competence engine, several learning applications

面向学生教师行政

The platform's competence engine also works in other learning applications, such as the student app — and learners take their competence status with them as a signed file, shared via QR code: explicitly “Kompetenzstand – kein Zertifikat” (competence status – not a certificate).

用途#

Competence does not only arise in one course on one platform. Whoever learns in different places should be checked by the same rules everywhere and own their credentials themselves.

使用方法#

操作路径People developmentMy competencesMy records

  1. 1The domain core of the competence diagnosis is built independently — without ties to the platform's database, interface or roles, with its own version number and its own tests.
  2. 2Another learning application adopts this core as a versioned copy with an adoption log and only builds its own connections — at run time it does not depend on the platform.
  3. 3Under “My records” the person downloads their competence status as a signed file (JSON) or creates a QR share (default 30 days, at most 90, revocable at any time) — with a PDF including the QR code. Nothing is shared without explicit consent; by default a pseudonym appears instead of the name.
  4. 4Whoever scans the QR code sees on the verification page: signature valid, unchanged, issuer, date of the status and the shared competences — and in large type the notice “Kompetenzstand – kein Zertifikat. Die Signatur belegt Herkunft und Unverändertheit, keine Anerkennung.” (competence status – not a certificate; the signature proves origin and integrity, not recognition). A revocation takes effect immediately.
  5. 5Other learning applications verify a file via the platform's public verification interface (POST /api/kompetenzstand/pruefen) or with the pure verification function as a versioned copy.

设置与开关#

  • 可按租户开关默认：开模块：Kompetenzbegleitung
  • Per tenant via the feature “Signed competence status (QR sharing)” (default on); only takes effect where competence continuity is on. Off: only the unsigned competence passport draft.

How it fits together#

  • Competence engine — the rules: tasks, rubrics, evidence, level, gaps, reassessment.
  • Learning applications — the platform, the student app, the Academy's offerings; each with its own interface and its own data storage.
  • Competence status — belongs to the learner; they decide by time-limited, revocable QR sharing who sees which status.

No automatic synchronisation between the applications: larger adoptions run via a versioned adoption log.

Open standards#

The competence status is a separate, versioned format (universe-kompetenzstand/2; older files in format /1 remain verifiable; optionally the evidenced level from competence modules per competence), modelled on W3C credentials but deliberately with its own type “Kompetenzstand” instead of “VerifiableCredential” — so that no tool mistakes it for a certificate. It is signed with the same key and the same DID of the platform as the verifiable credentials (Ed25519, JWS), after deterministic canonicalisation (JCS).

Every file must carry the notice “Kompetenzstand – kein Zertifikat”. A file without this notice fails verification, even if its signature were correct.

提示#

  • The signature proves origin and integrity — it is not recognition, not a certificate and not an attestation of an exam.
  • Link, PDF and file of a QR share are only available right after creating it; only a fingerprint of the code is stored. To share again, simply create a new share.
  • Every share, every revocation and every access appears in your own log — the company does not see it.

相关功能#