construct a Caliper AssessmentEvent with correctly typed actor, action, and generated Attempt entity
domain: imsglobal.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the Caliper event profile that matches the action (e.g. AssessmentEvent for Started/Submitted actions on an Assessment)
Populate the actor as a Person entity and the object as the Assessment entity being acted on
Attach a generated Attempt entity capturing count and assignable metadata when the profile requires it
Set the eventTime and set @context to the Caliper JSON-LD context IRI matching the spec version in use
Nest the completed event inside an Envelope data array before transmission to the sensor endpoint
Known gotchas
Each event profile mandates specific associated entities (e.g. a generated Attempt) — omitting them fails conformance even though the JSON is otherwise valid
Event and Entity objects must carry an explicit @type discriminator; endpoints reject ambiguous or missing types
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?