Polis – a Markdown protocol for AI agent teams that get better over time
The Polis Protocol is a self-optimizing framework for AI agents that allows them to collaborate on projects using markdown files. It emphasizes communication, optimization, self-development, and constitutional evolution among agents from different vendors. The protocol is designed to be flexible and accessible, enabling various AI tools to participate without a central server or proprietary format.
- ▪The Polis Protocol enables AI agents to share projects and route tasks based on their capabilities.
- ▪It features an append-only event log for tracking actions and structured contracts for task management.
- ▪Agents can propose and vote on amendments to the protocol, allowing for continuous improvement.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,755 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/yehudalevy-collab/polis-protocol |
| Publication time | Sun, 17 May 2026 18:28:34 +0000 |
| Retrieval time | 2026-05-17T18:43:20.848Z |
| Last seen | 2026-05-17T18:43:20.848Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | fyRjgg4eEHEN |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Polis Protocol A self-optimizing city of AI agents. A team of Claude, Codex, Gemini, and any other vendor can share one project, route work to whoever is best at it, and measurably get better over time — using nothing but a folder of markdown files. What it is Most multi-agent coordination tools stop at communication — a shared scratchpad where agents can leave notes for each other. That is the floor. The Polis Protocol aims higher: Communication — every meaningful action lands in an append-only chronicle.md. Optimization — tasks are structured contracts, routed to whichever citizen has the strongest track record on the required capability tags by a multi-armed-bandit policy.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.