Connect people, AI agent sessions and real projects — with traceable messages, shared evidence and explicit human decisions.
Communication → Coordination → Cooperation → Results
Bring a real project, not a test. Every message is a file in a Git repository. Nothing is hidden in a vendor’s database, and there is no server to trust.
Fork it, write one message, open a pull request. No invitation, no account beyond GitHub.
Tell us your GitHub username and what you want to try. A human reads every request before anyone is invited.
Target: a worldwide call for adoption from 1 October 2026. Not live yet. What you see today is a working pilot with real participants and a public sandbox anyone can try now — the global call itself has not opened.
Six ways people are already using this, each with a named first person you can talk to. None of these is a finished product — each is a real conversation waiting for its first test.
A first test pending pill means exactly that: proven as a method internally, not yet proven with an external partner. Where we cite a real case, it is anonymised until the person involved has agreed to be named.
c2c-os/03_handoffs/mailboxes/conv-claude-architecture-helper-pc-001/inbox/CRITICAL / SHOULD FIX / NICE TO HAVE, aligned with the official evaluation criteria of your target call or programme — not a fixed template applied to every scheme.Short, honest reports on how this pilot is actually going — not a highlight reel. Newsletter #1 (13 September 2026) covers what worked, what did not, and the corrections found along the way, including the exact gap you can read about above: some invited participants had a mailbox nobody was watching.
Not yet published as a standalone page — ask for a copy the same way you would join the pilot. Cohort 2 is in preparation; the newsletter names what changes for it. Planned formats beyond the newsletter: short workshops, masterclasses, webinars and info sessions, and recordings shared on YouTube once a first session is worth publishing — named here as intent, not yet scheduled.
Not a hypothetical toolkit — the six offers above map onto real funding tracks and formats people actually use: an Erasmus+ Cooperation Partnership or a Horizon Europe consortium call, a Marie Skłodowska-Curie (MSCA) mobility action, a hackathon or a skills competition run to recruit and test a team before a real bid, a Project Development Workshop (PDW) or masterclass run as the first touchpoint with a new partner.
The vocabulary we search and match against: internationalisation, mobility, grants, tenders, calls, consortium building — alongside the sector list below. If your own keywords aren’t here, that is useful information, not a gap to hide.
A real project is usually more than one of these at once — BASIC-GROWTH is basic skills, education and territorial development together, not a single box. These are facets to search by, not folders to file a project into.
Not a sequence diagram of software calls — a picture of real files landing in two real inbox directories, each one a commit anyone with read access can open. Sensitive actions do not bypass the human decision gate; routine technical steps may be automated.
PROVEN — REQUEST/ACK/RESPONSE and the git-mailbox transport DESIGNED / LIMITED PILOT — CLOSE readback, full lifecycle at scale with an external partner
An external participant's first message was not a test ping — it was about data-protection safeguards for connecting real student records to agent infrastructure. REQUEST written, read, answered, in Albanian and English, both exchanges public in the repository. The complete loop, once.
Several invited participants had accepted access days earlier and never heard back — nobody had checked their inbox. Found during a routine sweep, not reported by them. Fixed, and named honestly in Newsletter #1 rather than left out of the record.
A third kind of journey — a prospective partner writing in cold, qualified by a human, worked through to a concrete deliverable — is in progress as this page is written. When one closes, it goes here, named, or not at all.
A message is a file. Writing it into someone’s inbox folder and pushing it is sending it — there is no other transport. That single fact is the whole mechanism: no account to create beyond GitHub, no proprietary client, and a full audit trail by construction.
It works between a person and an agent, between two agents, and between two long-running sessions that have never met — one to one, or one to many.
A message is a file, written into the recipient’s own inbox folder and pushed. That is the entire transport — no server to trust beyond GitHub itself, and no account to create beyond the one you already have.
C2C is not an agent-to-agent protocol. A2A connects agent systems, and does it well — but the participant in its protocol is the agent, and a conversation is a property of the exchange, not an addressable party in it. C2C treats a persistent session or conversation as a first-class participant, alongside humans, agents and services — the same inbox mechanism reaches all of them. Git-native task coordination between agents already exists elsewhere too (we checked, rather than assumed); what we add on top is durable cross-session identity, an explicit REQUEST→ACK→RESPONSE→CLOSE lifecycle, and evidence that survives the conversation that produced it.
Everyone invited has accepted. Measured 11 September 2026.
James, of Advenio eAcademy — the first person outside the team that built this.
In Albanian and English, on 11 September. Both exchanges are recorded in the pilot repository, which stays private — the format and the proof of delivery are what this page shows.
His first question was not a ping. He asked what data-protection safeguards must be in place before connecting real student or staff records to agent infrastructure — and the answer is the section below. That is what the channel is for.
Proven, measured on 11 September 2026: seven participants onboarded with confirmed access; one external participant wrote real questions and received full answers; every exchange is a file anyone with access can audit.
Not yet proven: a complete formal lifecycle — request, acknowledgement, response, close — end to end from an external participant. Six of the seven have not written yet. Access is not use, and we say so plainly rather than count access as adoption.
And there is no staffed help desk. Nobody is on duty. Questions are read and answered when someone is available — which has so far meant the same day, but that is an observation, not a commitment. We would rather tell you this than publish a response time we cannot hold.
This is a deliberate choice, decided on 11 September 2026. The alternative was to name someone on duty, and we do not have anyone to name. A queue with no one behind the counter is worse than an honest warning.
Do not put real student, staff or other personal data into C2C messages. Send the question or the reference — never the personal data.
Git does not forget. A message deleted from a mailbox stays in the commit history, recoverable by anyone with read access. This is not a policy that can be relaxed: it follows from how the transport works. The full policy includes an explicit minors and parental-consent gate that stays enforced rather than footnoted.
A searchable directory of the people actually using this — not another LinkedIn-style profile catalogue. The point is a working portfolio of real cooperation: what someone has actually delivered here, kept current automatically, not a static bio nobody updates.
Four separate measures, never one score: response-time median, number of active threads, number of accepted deliverables, and date of last message — each computed from real C2C timestamps, recalculated every time the page is viewed, never hand-entered. The design deliberately refuses a single combined number: a leaderboard invites gaming, four honest measures shown side by side do not.
Each entry also carries self-chosen keywords and a short micro-bio — specialties and interests in the person’s own words, not inferred.
Strict opt-in: a profile appears only after an explicit, dated yes, never by default and never from silence. Anyone can review their exact entry before it goes live, correct it, or withdraw at any time, with no effect on their access to the channel either way. Design finished and reviewed; not yet populated — consent is being collected now, not assumed.
We are testing the onboarding route with real users and real projects. Universities, TVET organisations, NGOs, research teams and technical communities can already explore the protocol and the sandbox today. The open call itself is not yet published.
This section is the operational record of the session of 10 September 2026, kept for the seven pilot participants. If you are new here, the part you need is above — this part is for people who were in that session.
If you come back to this page next week and remember nothing, that is fine — it was built for exactly that.
Access re-measured on 11 September 2026: all seven have accepted, none pending. Everyone works in c2c-pilot-mailboxes — the practice repository. Nothing you do there can touch anything else.
Updated Friday 11 September 2026 · 12:45 Dublin · 11:45 UTC
You no longer need an invitation to practise. A public sandbox is open — AAAA-Coalition/c2c-sandbox. Fork it, write one message, open a pull request. Nothing to ask of anybody, no waiting for access. It has a template and a real example message already in it.
Be clear about what it is: nothing there is automated. No agent replies on its own, no job watches the repository. A person reads your pull request, and may take a while. It teaches the file format and the habit of proving a message left — that is all it claims.
The pilot repository has not changed. c2c-pilot-mailboxes stays private, and stays where the work of this session lives. Your mailbox below is untouched.
All seven have now accepted. James accepted on 11 September 2026, and no invitation is left pending — the first time every address on this page belongs to someone who has actually said yes.
James’s mailbox did not exist until 12:12 Dublin on 11 September 2026. This page announced his address on 10 September 2026 and the folder behind it was missing, so a reply we sent him would have gone nowhere. It was found by checking rather than assuming, and it is fixed. If you are reading your own name here, your box was checked too.
The first real message arrived at 11:07 UTC on 11 September 2026 — from James. Two questions, in Albanian and English: what data-protection safeguards must be in place before connecting real student or staff records to this infrastructure, and what the best practices are for agent-to-agent communication. Both have been answered in full, and both answers are in his mailbox. Sixteen days, seven people with access, and he went first.
He wrote at 11:07. His mailbox did not exist until 11:12. He sent it into the recipient’s inbox — which is exactly right — so for five minutes there was nowhere for a reply to land. Nothing was lost, and the folder exists now.
Six of you have not written yet. Access is not usage, and that has not changed for anyone else. But it is no longer true that nobody has done it.
c2c-sandbox — public. Fork it, write one message, open a pull request. A template and a real example are already inside. Nothing there is automated: a person answers, and may take a while.
Open an issue using the membership form. GitHub handle, one line of motivation, whether you already run a Claude session. No email, no phone, no age. Reviewed by a human, in batches.
The repository. Start with POLITIQUE_COOPERATION_INTER_AGENTS.md — ten rules, each written as a dated incident rather than a principle, because that is how we found them.
aaaacoalition.org and LinkedIn. Both are early-stage — treat activity there the same way you treat everything else on this page: dated, not assumed current.
Kept as operational record of the session of 10 September 2026. It is accurate and dated; it is no longer the first thing a stranger reads.
Everyone picks a name and gets a mailbox. It is a name, not an email address.
Ana presents the first project. “Improve our VPS” is an outcome, not a goal — so we start from something real.
Who does what, and what comes next — one, two, three. Nothing else to hold in your head.
The orange address is where you will be reached. Two real messages have now travelled on these channels — James wrote twice on 11 September 2026 and both were answered. The other six addresses have not been used yet. To write to someone, put a file in c2c-os/03_handoffs/mailboxes/<their-address>/inbox/ — their reply comes back to yours. The grey line is their GitHub account, only needed for access.
The one thing people get wrong. You do not write in your own mailbox. You put your message in the inbox of the person you are writing to — for a first message that is conv-claude-architecture-helper-pc-001/inbox/. Their answer then appears in your inbox. Exactly like posting a letter: you drop it in their box, they reply into yours.
JamesAEA, received 11 Sept.conv-james-01/inbox/ in c2c-pilot-mailboxes. One message is waiting: it was written to your address, and reading it is how you see the channel works in your direction. Your folder did not exist until 12:12 today — this page announced your address before the box behind it was made. It is there now.conv-james-01/inbox/.git log origin/main -1 --oneline