Ontology-native systems for real work

Choi01 Lab

A public project hub for the systems I am building around ontology, agents, and domain MCPs. It starts with 01ontology and OntoCanvas, then points people to MCP-first tools for legal, recipe, and accounting workflows.

View the map How to use MCPs
Object search detail surface with evidence panel
Object search with evidence
Visual authoring surface for ontology edits
Visual authoring
Lineage trace showing source to fact flow
Lineage trace
Workflow timeline interface
Workflow timeline

Project structure

Four public-facing doors, one underlying ontology idea.

The first door is a product surface. The other three are best described as MCP-first tools, because they are used through Claude, Codex, or another agent client.

Flagship

01ontology & OntoCanvas

A semantic operating kernel for agents, paired with a visual canvas for packs, object types, relations, evidence, lineage, and workflows.

  • Kernel: object/action/workflow/lineage/citation/ReBAC.
  • Canvas: explorer and operator views for ontology work.
  • Best public entry: product story, docs, screenshots, GitHub.
GitHub profile MCP route
MCP tool

Theo Legal Intelligence

German law, tax, and contract intelligence exposed as MCP tools and local specialist workspaces.

  • Combines german-law-mcp, Theo Legal Suite, and Theo Legal/Tax Pack.
  • No hosted legal UI required for the first release.
  • Can later support a BYOK web client.
Usage pattern
MCP tool

Recipe Intelligence

A recipe and meal-planning knowledge graph based on 01ontology domain packs and crawl artifacts.

  • Recipe corpus, ingredients, cooking steps, tools, tags, and provenance.
  • Agent asks questions; MCP answers with grounded pack data.
  • BYOK UI can be added without hosting an LLM key.
MCP examples
Ontology pack

DATEV-FIBU & Church Finance

Accounting packs for DATEV month-close workflows, Kontoblatt evidence, and church finance reports.

  • Implemented as `accounting` and `church-finance` packs.
  • DATEV/FIBU objects live under the accounting ontology.
  • Church finance covers dues, support expenses, confirmations, and reports.
Pack usage

How people use it

MCP first, optional UI later.

Theo, Recipe, and DATEV-FIBU do not need to pretend they are hosted apps. The honest interface is: connect an agent client, bring your own LLM key when needed, and ask grounded domain questions.

Use it from Claude, Codex, or another MCP client.

The website can show setup steps, example questions, and pack names. The actual work happens through MCP tools, so each answer can keep citations, evidence, and domain boundaries visible.

Example questions DATEV 월마감 절차를 BWA, OPOS, UStVA 기준으로 정리해줘. 이번 주 저녁 식단을 예산과 영양 기준으로 추천해줘. 이 계약 조항은 독일법 기준으로 어떤 리스크가 있어?

Cloudflare fit

The first version is static, so Cloudflare Pages is enough.

`choi01.com` can be a fast static hub. Dynamic LLM or MCP interaction can later move to a subdomain.

Suggested domain routes for choi01.com
Route Purpose Hosting shape
choi01.com Public project hub Cloudflare Pages static site
ontology.choi01.com 01ontology and OntoCanvas docs Static docs or demo links
mcp.choi01.com MCP setup and examples Static guide first
ask.choi01.com Optional BYOK client Workers or Vercel later