Dictionary Tools

The dictionary of a project: the glossary (the words the project agrees on, each with one definition, the other names it goes by, the terms it leans on, its source and its review status) and the data entities (the things the project keeps records of, each with its fields, their types, flags, validation and examples, its component, its owner, whether it holds personal data and how long it is kept).

The dictionary of a project: the glossary (the words the project agrees on, each with one definition, the other names it goes by, the terms it leans on, its source and its review status) and the data entities (the things the project keeps records of, each with its fields, their types, flags, validation and examples, its component, its owner, whether it holds personal data and how long it is kept). These tools read both as the token sees them, a guest's token reading the approved entries only, so an agent drafts in the project's own words and designs a table, a form or a payload against the fields the analyst wrote down, and, for a staff token, writes them: a term (create_glossary_term, update_glossary_term, which also moves it along its review) and an entity with its fields in one call (create_data_entity, update_data_entity), each with a delete that pauses for confirmation.

Tools

How is this guide?

Last updated on

On this page

What changed recentlyEvery release of Zuse Bifrost, with the pages it touched.

For AI agents: llms.txt · llms-full.txt