Skip to main content
A decision is a governed record of something your room has settled, such as “We deploy only through the release pipeline”. It has a key, an author, a status and a person who decides it. Once it is accepted, Ainomos uses it in the room’s answers and gives it to connected agents as binding. Drafts and rejected decisions bind no one. You find a room’s decisions in Knowledge, then Decisions.

Decision types

Every decision has a type. The type sets its key and who decides it. You may also see two types you do not create with the form. Association (is-a) records state that one thing belongs to a category, and come from a chat answer or an import. DREAM records come from an accepted dreaming proposal; nobody accepts them by hand, but a decider can reject them.

Write a new decision

Who can do this: every member of the room.
1

Open the form

In Knowledge, open Decisions and select Create. The New decision dialog opens.
2

Choose the type and title

Pick the Type (ADR, BDR or SDR) and write a short Title. Select Create.
3

Fill in the draft

The draft opens on its own page. Complete the fields below, then select Save (or press Ctrl+S).
Who can edit a draft: its author, and anyone who may decide its type. Everyone else sees it read-only. An accepted decision cannot be edited.

The sentence agents will follow

This is the one line that binds. Write it as a short, plain instruction, for example “Use the company password manager for every shared account”, and put the reasoning in Content. After acceptance it shows under Agents follow, and Ainomos gives it to the model and to connected agents.

Keys and numbering

Each room numbers its decisions per type on its own, so ADR-017 in two rooms are two different records. A draft gets its final key when you create it and keeps it when accepted. A rejected or archived draft keeps its key, and the number is never used again. Room owners can set where numbering continues, for example when a team moves its records from another tool: open the room details and change the next number per type under Decision numbering. Numbers in use are skipped.

Aliases

A record can be found under every key it ever had, such as the key in the source it was imported from. The record page lists these aliases next to the key as also. Search, links and agents accept them like the key. Room owners can add an old key with Add alias, and remove aliases added by hand or imported.

Scope

Who can change the scope: room owners, deciders of the record’s type, and the author while it is a draft. A scope names the parts of your systems a decision governs. Under Scope, choose the Kind of entry (Folder or file, Module, Service or Command), type the path or name, and select Add. A path covers everything below it: services/org also covers services/org/api. A decision holds at most 32 entries. When a question or an agent names such a path or name, Ainomos brings the decisions that govern it into the answer. Entries marked suggested, not confirmed were found in the decision text and count only after someone confirms them with the check mark.

Statuses

Who decides and how approval works

Room owners decide every type. A room can also name a decider per type under Responsibilities in the room details, who then decides that type alongside the owners. The record page names the Decision maker. Drafts waiting for you show as To decide in the list, and drafts from apps and imports also reach your Inbox. Platform admins decide only where they hold one of these responsibilities. Agents never accept a decision. On a draft, a decider has these choices:
  • Accept: the draft becomes binding at once.
  • More, then Accept with changes: accept and add a Change note (optional).
  • More, then Accept and supersede …: accept and pick the binding records it replaces.
  • Reject: with an optional reason.
  • More, then Archive: put the draft aside. The author can do this too.
In the decision list you can tick several drafts you may decide and accept or reject them together. Every acceptance, rejection and status change writes an evidence record, the audit entry Ainomos keeps for every action.

Drafts from apps

Apps connected through MCP, the open standard AI apps use to connect to Ainomos, can propose drafts. The draft names who proposed it and through which app. Each proposer can hold 10 open drafts per room unless room owners or curators set another number in the room details.

Supersede, end or withdraw a decision

Who can do this: room owners and deciders of the record’s type. Each step except superseding needs a reason. The rarer actions sit under More. A superseded record cannot be reopened: write a new decision that supersedes its successor.

Relations

The Relations tab shows the record on a small map with every record linked to it, for example one it refines, depends on or conflicts with. Dreaming proposes new links, and a person confirms them.

Ratings

Who can rate: every member of the record’s room. Agents cannot rate. Select Rate decision, choose a Score from 1 to 10 for how clear, useful and effective the decision is, and add an optional Comment that every reader sees. Each person has one rating per record: saving again replaces it, and the history keeps earlier scores. A rating never changes the status. Ratings are given in the record’s own room while it is a draft or binding, and close when it ends. The Ratings tab shows the average, the spread and every rating.

History

The History tab lists every step: where the record came from (chat, dreaming, an app, an import or by hand), acceptance with person and date, approvals taken back, and how it ended. Open evidence opens the evidence behind a step. A superseded record links to the version in force.