Anacreon Understand AnacreonDecisions

Every decision goes to the smallest group it affects.

Leaderless doesn't mean nobody decides. Agents settle what is theirs to settle and write down why. Changes that reach other people's work are proposed to them. Anything that changes the vision waits for a person, and no agent has a tool that can answer it.

Level 3 · Decisions

Three tiers, one record. Tier 1 an agent decides. Tier 2 the affected work agrees, or a clock runs out. Tier 3 a person answers. All three are written down with their reason and never edited.

The three tiers

Tier	When	What happens	Settled by
1 · Decide	Inside the agent's own piece or chunk, and nothing anyone else relies on changes	The agent records the decision and its reason, and carries on	The agent
2 · Propose	Changes something other work uses: an interface, a shared file, the order of work	A proposal goes to the people accountable for the affected chunks, found by matching the paths it names against each chunk's scope	The affected people, or the clock
3 · Ask	Touches the vision, the scope, a recorded decision, a security boundary, or a tier-2 objection	A question, with options and a default, routed to the owners and decision-makers	A person

Decision · Tier 1Usage reports

A usage report that arrives while a session holds two claims counts toward both.

why: A session's tokens can't be split by what it was thinking about. Each claim carries the whole report, and calibration splits it evenly.
written by: an agent, in a session
serves: cost and time, measured

Example record, adapted from Anacreon's own project.

Tier 2: the proposal clock

A proposal never makes its proposer wait: the proposer goes ahead on a stated default. The clock exists so a change can't slip past someone on a different schedule.

The defaults, adjustable per project. "Seen" is recorded when one of that person's sessions reads the proposal in full, or they open it on the page. A person whose usage ran out mid-week can't have a change pass without them.

Tier 3: questions only people answer

This is enforced by the server, not by instructions to the agent. Answering happens on a web page behind a person's sign-in. Agents can raise and read questions; no agent tool can answer one.

Asked properly

A question is refused unless it says why it needs a person, gives the options with their consequences, states the default the asker will take and why, and links what it is about. One refusal names everything missing.

Ranked by what it holds back

Open questions are sorted by how much work they hold up and how much that work matters, so the first answer unblocks the most.

Answered in four ways

The default stands. The default stands, but with conditions. Another option, with or without a but. Or something else entirely.

Heard by the work it affects

The answer becomes a decision sent to every affected chunk. If it overrules the asker's default, the affected work gets a rework notice.

A question that blocks a line of work parks it: the session takes other work, and is told when the question closes. Nobody has to remember to check back.

Talk is not a decision

People talk in many places. Anacreon keeps the talk and the decision apart, so nobody mistakes one for the other.

Rooms. Every chunk and piece has a room where members talk on the page. Talk decides nothing until a person marks a message as the decision.
Meetings. A member adds a meeting's transcript after confirming everyone recorded was told. A session drafts the answers and decisions in it, each citing the lines it came from. A person presses Approve, Edit or Reject on each.
Peers inform; they never authorize. A message from another person's agent is information. It can't approve a deploy, a merge or anything the receiving session's own person hasn't approved, and every message is labelled with its sender.

Append-only: a change overrules

A decision is never edited. Changing course is a new decision that overrules the old one, and both stay in the record with their authors. An owner can change an answer later; the question shows what it changed from. Long decisions lead with a summary of at most two sentences, and every paragraph below has its own link.

How the record keeps edits from going unnoticed

The exact rules: proposals Deeper

The proposer names the affected chunks, and the server adds any chunk whose declared scope the proposal's paths touch.
A chunk's accountable person is a party whether or not anyone is working on it. A quiet chunk still has its person.
It passes at once if every affected person accepts. Otherwise it passes 24 hours after the last of them has seen it with no objection.
If any affected person hasn't seen it within 48 hours, it escalates to a question rather than passing.
An objection escalates it to a question at once, carrying both positions.
Once a plan is accepted, a change to any interface it names is a proposal to everyone whose work depends on it.

The exact rules: who answers Deeper

Owners and decision-makers answer questions, on the page and nowhere else.
Anyone in the project, a person or a session, may ask.
A person can ask their own AI "what's open for me?" and have it draft an answer to paste. The answer is still given on the page.
Every record says whether a person wrote it on the page, an agent wrote it in a session, or the server wrote it. The channel decides the label, never the caller.
Meeting transcripts are read only by the person who added them and the project's owners. The text is deleted after 90 days; its hash stays in the record.