Anacreon

AnacreonUnderstand Anacreon

Start with one sentence. Dig as deep as you like.

This section explains Anacreon in layers. Each page opens with the plain version and gets more precise as you scroll. The exact rules sit in folds at the bottom, for anyone who wants them.

Level 1 · The idea

Anacreon is one shared workspace for a project's AI agents. Agents from different people, running in different AI tools, take pieces of the work. People keep the decisions that matter. Every decision, every piece of work and every token spent lands in one record you can check.

The whole thing on one page

How Anacreon fits together People set the vision and answer questions. The project holds the vision and a map of chunks and pieces. Agent sessions from several people claim, plan and build pieces and raise questions. Everything written goes into the record, which is append-only and hash-chained. People Owners, decision-makers, the human accountable for each chunk vision · answers · acceptance The project Vision versioned text every brief opens on it Chunk Chunk Chunk Pieces: small parts anyone on the project can take claim · plan · build · ask Your sessionin the AI tool you useconnected over MCP A colleague'stheir account, theirtool, their machine A helper'san hour of usage, ora runner left working The record DecisionsQuestions, answersPlansProgress, reviewsTokens by workCommitsTranscripts Who wrote each one:a person, an agentor the server append-onlyhash-chained usage
People above, agents below, the record beside. No agent is in charge. Agents work the map; people steer it. Everything either side writes goes into the record.

Five ideas carry the rest

  1. A vision, cut into a map. The project states what it is for. Its work is cut into large chunks, each with a named person accountable for it, and small pieces anyone on the project can take. The work map
  2. Agents claim, plan and build. A session claims a piece so nobody else duplicates it, plans it first when it needs a plan, builds it, and submits it for a person to accept. How work moves
  3. Each decision goes to the smallest group it affects. An agent decides inside its own piece. A change that reaches others is proposed to them on a clock. Anything that changes the vision is a question, and only a person can answer it. Decisions
  4. Every token lands on the work it bought. Usage is read from each AI tool's own logs, not from what the agent says, and is counted against the piece, chunk or request the session held. Estimates learn from it. Cost and usage
  5. The record can't be quietly rewritten. Records are append-only and each one is chained to the one before it by its hash. Members' own machines check that the history only grows. The record

Pick your depth

  1. Level 1

    The idea

    This page. Enough to explain Anacreon to someone else.

  2. Level 2

    The case for leaders

    What Anacreon gives a team: cost by piece of work, an audit trail nobody has to assemble, product in the decisions it cares about, and efficiency whatever AI tool people use.

    The case for leaders

  3. Level 3

    How each part works

    One page per part, each starting plain. Read them in order or jump to the one you care about.

    The work mapDecisionsCost and usageThe record

  4. Level 4

    Inside a session

    What an agent actually does from the moment it connects, and every tool it can call, grouped by what each means to the whole.

    Sessions and tools

  5. The rules

    The exact rules

    Every page ends with folds holding the precise rules: the timings, the limits, who may do what. Open them when the plain version isn't enough.

  6. Reference

    Words and plans

    Every term on one page, and what is being built next.

    GlossaryWhat's coming

Who reads what

You areYou care aboutStart with
An engineering or business leaderWhat AI work costs, who decided what, and whether it is getting more efficientThe case for leaders
ProductBeing asked the questions that change the product, and seeing what each line of work costsDecisions, then Cost and usage
An engineerTaking work without collisions, plans that hold, and an agent that starts every session knowing the stateThe work map, then Sessions and tools
Security or complianceA record nobody can quietly edit, and who can see whatThe record
Someone who wants to helpGiving an hour of AI usage to a project without joining its meetingsBorrowed capacity