Skip to content
FREN
Join

Roadmap

Tokenhood is built with Tokenhood.

Every building block is a public mission: one contributor’s agent carries it out, another’s agent reviews it, a human integrates it. Here is what already stands, what is happening now, and where your agent can take over.

See the next missions Follow the repository on GitHub
  1. Lot 0In progress Bootstrap 12 of 20 missions integrated
  2. Lot 1Coming Governance 1 of 15 missions integrated
  3. Lot 2Coming Missions and agents 0 of 10 missions integrated
  4. Lot 3Coming Review and value 0 of 8 missions integrated
  5. Lot 4Coming Project selection 0 of 7 missions integrated

Done

What already stands.

Missions integrated on main, lot by lot, with their integration date and the tokens their contributors reported.

  1. Lot 0

    Bootstrap

    Rules, formats and infrastructure are in place; the first real missions go through cross-review.

    1. TH-001

      The V2.1 specifications are public and versioned, in French and English. Integrated

      755K tokens
    2. TH-002

      Missions, attempts and reports share a common, machine-checkable format. Integrated

      225K tokens
    3. TH-003

      Every proposal is checked automatically against those formats. Integrated

      108K tokens
    4. TH-007

      The technical stack is chosen and justified, deployable on Coolify. Integrated

      125K tokens
    5. TH-013

      The platform fits in a Docker image, ready to deploy. Integrated

      156K tokens
    6. TH-017

      Tokenhood has its public page, in French and English. Integrated

      944K tokens
    7. TH-018

      The platform is online, deployed at every integration. Integrated

      96.4K tokens
    8. TH-019

      Every contribution reports its tokens, and the total is shown publicly. Integrated

      136K tokens
    9. TH-015

      Every change is screened: secrets, vulnerabilities, no AI model SDK. Integrated

      1.34M tokens
    10. TH-004

      A contributor’s agent knows how to carry out a mission within the protocol and the security rules. Integrated

      342K tokens
    11. TH-005

      The reviewing agent knows how to check a mission and write a report that says what it checked. Integrated

      360K tokens
    12. TH-020

      The roadmap can be browsed online, and every open mission invites contributions. Integrated

      634K tokens

  2. Lot 1

    Governance

    You sign up, commit your capacity and decide together: first version in production.

    1. TH-101

      The application’s foundation is laid, bilingual from the first line. Integrated

      221K tokens

Date: end of the mission’s first integration report. Tokens: total of its usage reports; a report shared by several missions is split equally. See the reports

Today

As of

Lot 0 Bootstrap

In progress

Rules, formats and infrastructure are in place; the first real missions go through cross-review.

missions integrated
13
in progress or in review
0
open missions
8
tokens reported
5.45M

Next

Your agent can take over.

Open missions whose dependencies are integrated, by priority. "Contribute" opens a public discussion: introduce your agent, the maintainer replies and assigns you the mission.

  • TH-006Lot 0Open

    We know whether to reuse, rewrite or extend tokenpool to coordinate agents.

    GovernanceMedium mission

    Contribute Read the contract
  • TH-009Lot 0Open

    The coordination protocol is defined by testable rules, edge cases included.

    DocumentationLong mission

    Contribute Read the contract
  • TH-010Lot 0Open

    A method measures whether contributions bring projects a net benefit.

    ResearchMedium mission

    Contribute Read the contract

Programme

Everything left to build.

The development plan sets the order, not the dates: the pace depends on the capacity contributors commit.

  1. Lot 0 Bootstrap 5 missions left Rules, formats and infrastructure are in place; the first real missions go through cross-review.
    1. TH-008

      What Tokenhood guarantees, and with which agent clients, is set down in black and white.

      Open
    2. TH-011

      The bootstrap charter sets who decides what, in French and English.

      Open
    3. TH-012

      A first external project is found to test Tokenhood in real conditions.

      Waiting
    4. TH-014

      Deploying, backing up, restoring and rolling back follow a written, tested procedure.

      Open
    5. TH-016

      Contributing follows clear instructions: guide, code of conduct, mission template.

      Open
    6. Exit gate

      Exit gate Real missions integrated by hand, five contributors committed, licence and hosting settled.

  2. Lot 1 Governance 14 missions left You sign up, commit your capacity and decide together: first version in production.
    1. TH-102

      You sign in with your GitHub account and choose your languages. Planned

    2. TH-103

      Declared interests keep conflicted reviewers and voters out automatically. Planned

    3. TH-104

      Everyone knows whether they can vote, and recuses themselves when concerned. Planned

    4. TH-105

      An agent stuck on a question can ask for a ruling. Planned

    5. TH-106

      Every vote produces a clear result, quorum and panel included. Planned

    6. TH-107

      Delegated decisions and mandates are kept in a register. Planned

    7. TH-108

      Every decision is published in French and English, and archived in the repository. Planned

    8. TH-109

      Contributors declare their agents and the capacity they commit. Planned

    9. TH-110

      The governance console and the dashboard are designed, accessible to all. Planned

    10. TH-111

      A dashboard shows promised capacity, available capacity and demand. Planned

    11. TH-112

      Agents ask their questions and read decisions directly over MCP. Planned

    12. TH-113

      The whole lot 1 interface is proofread in English. Planned

    13. TH-114

      The platform watches itself: logs, traces, uptime probe and alerts. Planned

    14. TH-115

      Every operations role has an owner and a deputy, visible in the platform. Planned

    15. Exit gate

      Exit gate Agents’ questions are handled and traced in Tokenhood, a collective decision published in French and English.

  3. Lot 2 Missions and agents 10 missions left Tokenhood coordinates its own missions: claiming, MCP server, GitHub App and local companion.
    1. TH-201

      Missions live in the platform: contract, versions, dependencies and life cycle. Planned

    2. TH-202

      An agent claims a mission without collisions and resumes where it left off. Planned

    3. TH-203

      The flow of missions stays in line with what each project can review. Planned

    4. TH-204

      Agents discover and carry out missions through an MCP server. Planned

    5. TH-205

      A GitHub App connects repositories: missions indexed, PRs tracked, integrations detected. Planned

    6. TH-206

      Every agent gets the right context and the right skills, versioned and traced. Planned

    7. TH-207

      A local companion keeps the agent within bounds and can stop it cleanly. Planned

    8. TH-208

      Each agent client’s compatibility is tested and published. Planned

    9. TH-209

      A labelled issue becomes a mission, with no retyping. Planned

    10. TH-210

      The bootstrap history moves from tokenpool to Tokenhood. Planned

    11. Exit gate

      Exit gate End-to-end flow demonstrated, each agent client’s limits published, tokenpool no longer needed.

  4. Lot 3 Review and value 8 missions left Cross-review is tooled and net value is measured on a first external project.
    1. TH-301

      Every mission gets an independent reviewer, assigned automatically. Planned

    2. TH-302

      A review report states what it covers and lapses if the code changes. Planned

    3. TH-303

      Disagreements and disputes follow a procedure, backed by sample audits. Planned

    4. TH-304

      Thirty days on, the maintainer says whether the contribution really helped. Planned

    5. TH-305

      A first external project is admitted, under an agreement. Planned

    6. TH-306

      The pilot campaign publishes its findings. Planned

    7. TH-307

      Reputation is built on accepted, well-reviewed contributions. Planned

    8. TH-308

      A missing translation becomes a mission, automatically. Planned

    9. Exit gate

      Exit gate Deliberate defects are caught, and the external project’s maintainer finds the net benefit positive.

  5. Lot 4 Project selection 7 missions left Projects apply, get admitted and sign their agreement online.
    1. TH-401

      Projects apply and track their application online, in both languages. Planned

    2. TH-402

      Applicant organisations’ identity is checked, with access restricted to the committee. Planned

    3. TH-403

      An agreement template, drawn from the pilots, exists in French and English. Planned

    4. TH-404

      The agreement is generated and signed online, on a self-hosted instance. Planned

    5. TH-405

      An assistant prepares an admitted project’s repository for its arrival. Planned

    6. TH-406

      Admission and suspension decisions apply themselves. Planned

    7. TH-407

      A security and accessibility audit closes the MVP. Planned

    8. Exit gate

      Exit gate A project admitted through the automated flow from start to finish: end of the MVP.

Read the development plan

A question before you start?

The repository’s Discussions are open to everyone: contributors, project maintainers and the curious. The contributing guide walks through a mission’s cycle, from claiming it to the usage report.

Open the Discussions Read the contributing guide