You Already Have an Ontology

Описание и применение

Разработчики часто создают несколько несовместимых определений доменных понятий, что приводит к дрейфу и ненадёжности агентов. Консолидация этих определений в единую схему устраняет несоответствия и повышает надёжность.

Задача

Developers often create multiple, inconsistent definitions of domain concepts across codebases, leading to drift and unreliable agent behavior.

Результат

Consolidating scattered ontology definitions eliminated mismatches, ensured agents had a reliable, authoritative knowledge base, and reduced maintenance overhead.

Рабочий процесс

• Audit existing code to identify duplicated domain concepts.
• Map each concept to its occurrences across backend, frontend, and UI layers.
• Create a unified definition (e.g., a shared TypeScript enum or a JSON schema).
• Replace all local definitions with the unified one, updating serializers and UI components.
• Add tests to ensure consistency and catch future drift.
• Document the ontology in a central place (e.g., README or internal wiki).

Доказательства

The frontend believes in form_too_complex and unsupported_ats, which the backend cannot produce.

Источник

The status vocabulary is the same story. ApplicationStatus has seven values in Python and five in TypeScript.

Источник