LOThe VOLO ontology
One model sits under every page, every tool AI agents can call and every file we publish: the kinds of things this site knows about, how they connect, and the named actions that are the only way to change them. Everything drawn here exists in that model, and every number is counted from it.
AI and people, working together
Pages and views
Agents and automation
Open data and APIs
MCPCSVJSON-LDsits inleads tocoded asclassified asoffersmade ofsupportscitescitesaligns tojudged asreadsbears onapplies infromaboutviaBusiness function13Occupation90Degree18Long-form note6Next step267Official code483Evidence record241Task470O*NET activity525Lead114Source221Judgement470Rule41Jurisdiction12Add an occupation →Map a code →Add evidence →LoopVerify →LoopAlign a task →Accept a lead →LoopChange a judgement →Read a rule →Task object
Treating, vaccinating and operating
- Occupation
- Veterinarian
- Direction
- Still human-led
- Basis
- Evidence-backed
- Verified records
- 1
- O*NET activities
- 3
- Rule
- must not · Singapore
- Assessed
- 2026-09-26
Sources
Logic
Checks and write-back
- Object — this site's judgements, evidence and readings
- Object — public reference: codes, O*NET, laws, sources
- Link
- Action — how the object is changed
- The unattended loop may run this action
- The links the card's task walks
Drawn for show, true in every part
Each object type, the direction of each link and each action is checked against the model's definition by a test: change the model without the drawing and the build fails. The screens on the top platforms are illustrations, not data.
The card is a real task
Its direction, its basis, the verified record behind it, the O*NET activities it aligns to and the rule that bears on it are read from the same graph the site and the AI-agent tools read.
Read it plainly, or take it whole
The same model as a readable list, with the rules it enforces →
volo-ontology.json · volo-ontology.jsonld · Open data