--- title: Glossary description: Look up what each word in this manual means, from issue space, issue, and kind to waiting for, claim, member, level, and the setting file. slug: /concepts/glossary order: 1 visibility: public redirects_from: [] --- # Glossary This page defines each word the manual uses, with a link to the page that gives its rules. Read it when a word on another page is new to you. ### Issue space The place your AI keeps its issues, shared by every session and agent that works it. The word for one is a space. A space outlasts any one conversation, and several sessions work it at once. Your account makes its space with `create_issue_space`; nothing makes one automatically. ### Issue One point that must outlast a conversation: what was seen and a suggested resolution. An issue has no sub-items and no checklist, and closing it is the check-off. [Issues and kinds](/concepts/issues-and-kinds) gives what an issue holds. ### Kind What sort of point an issue is: `bug`, `gap`, `docs`, `friction`, `question`, `task`, `praise`, or `idea`. [Issues and kinds](/concepts/issues-and-kinds#kinds) says what each one means, and [Accepted words for kinds](/reference/accepted-words-for-kinds) the other words each kind reads, such as `problem` for a `bug`. ### State Where an issue stands: `new`, `open`, `waiting`, `fixed`, or `closed`. An issue is `waiting` exactly when it waits for more evidence. [Issues and kinds](/concepts/issues-and-kinds#states) describes each state. ### Outcome What a close records about how an issue ended: `verified`, `done`, `as_designed`, `declined`, `duplicate`, `superseded`, `noted`, or `unexplained`. A close records a resolution with it: what was done, or why no change is needed. ### Waiting for Who or what an open issue waits on, its `waiting_for`. It is none when the issue is ready to work, `person` when it waits for your person to act or decide, or `person:` for one member of a shared space. It is `reporter` for one of its reporters, `outside:` for an outside party or event, or `evidence`, the one value that puts the issue in the state `waiting`. `wait` and `update` set it, and `find` lists issues by it. [Waiting and claims](/concepts/waiting-and-claims) gives each value. ### Claim A label saying who works on an issue, its `claimed_by`: `session:` for one session, `agent:` for an agent, a name of your own, or `branch:` for the work on one branch. `claim` sets it and is refused while another claim is in place, and `give_back` clears it with a reason. Other sessions read the claim before they start, and leave a claimed issue alone. ### Member A person the space's owner added with `share`, by the email address of their Turn Zero account, at a level: `report`, `contribute`, or `owner`. [Sharing a space](/concepts/sharing-a-space) gives the levels and how a member connects. ### Level What a member's sessions may do in a shared space: `report`, `contribute`, or `owner`, lowest first. Each level admits every act of the levels below it, so a session at `contribute` or above works issues as well as raising them. The owner gives each member a level with `share`, and [Sharing a space](/concepts/sharing-a-space) gives what each one admits. ### Cache A copy of your space's issues kept as files on your computer, one folder per project per computer, shared by every session working there. Your AI searches it with its own file tools first, and reads an issue live before it changes it. Only a tool that runs commands, such as Claude Code or Codex, keeps one. [The cache](/concepts/the-cache) gives where it is kept and what it holds. ### Setting file The file `.tztrack/config.json` at a project's top level, giving the space the project uses. Every session in the project, on every computer, reads the same space from it, in a tool that reads local files, such as Claude Code or Codex. [The setting file](/reference/the-setting-file) gives its form. ### Report One filing of an issue's point by a reporter. An issue can have several reports, so a point raised again joins the issue it already has. ### Priority How urgently an issue needs work: 1 urgent, 2 soon, 3 when convenient. Your AI reads the urgent issues first at the start of its work. ## Related - [Issues and kinds](/concepts/issues-and-kinds) explains issues, states, kinds, and outcomes. - [Waiting and claims](/concepts/waiting-and-claims) explains what an issue waits for and how a claim is given back. - [The tools](/reference/the-tools) lists `claim`, `give_back`, `share`, and the other tools. - [What happens without asking](/concepts/what-happens-without-asking) says what your AI does on its own.