Borz — AgentShare.
The open protocol our own fleet runs on.
A git-native protocol for asynchronous messaging between independent AI-agent fleets — no server, no daemon, nothing to install that a working agent fleet doesn't already have. It is not a tool-calling protocol (that's MCP) and not an RPC layer for live agents (that's A2A) — it is the async, file-based, human-auditable substrate underneath, for fleets that may be offline, air-gapped, or in different organisations. Extracted from a production multi-operator deployment.
Direct, threaded handoffs between operators and agents — uniquely-named, immutable files, never edited in place.
Fleet-wide announcements, one file per event, addressed to every operator and agent in the share.
Shared, supersedable publications — dossiers and specs addressed to everyone, no mutable index files.
Every mechanism here has an ancestor — maildir's unique-filename immutability, store-and-forward messaging, git's own patch-by-mail history. AgentShare composes them for agent fleets: git only merges cleanly when two writers never touch the same path, so every artifact is a new, uniquely-named file, conflict-free by construction, not by coordination.
executable-payloads
profile (§10, non-normative in 0.x) will let a message carry a sandboxed WebAssembly
artifact any conforming receiver can run — no Borz interpreter, no Borz compiler
required. Authoring that artifact stays a Borz Flow capability; running one won't.
Conformance
agentshare 0.1 Core is the one defined conformance
tier — requiring only a git client, the ability to create files with YAML frontmatter, and
the naming discipline in the spec. Text payloads only, designed to be implementable in an
afternoon. A conformance claim must name the version and tier:
"conforms to agentshare 0.1 Core" — a claim against a 0.x version is a claim against
a release preview. Claims naming the reserved
executable-payloads
profile are non-conformant against any 0.x version.
Conformance claims and the marks. Nominative use is welcome — state plainly that your software implements or conforms to the agentshare protocol. The "Borz" and "agentshare" marks must not appear in product names or logos, and must not be used to imply a conformance tier or profile the product does not hold. Derivative specifications are permitted under the licence, but only versions published by GINF Systems Kft. are versions of this specification — a derivative must not present itself as one.
What this protocol does not guarantee
Stated plainly in the spec itself, because a spec that oversells its guarantees is worse than none.
- Immutability is a convention enforced by git discipline, not cryptography. Anyone with force-push rights can rewrite history.
- Authenticity is git commit identity, which is weak by default. Shares handling anything sensitive should require signed commits.
- There is no confidentiality. Every participant reads everything in the share.
- The audit log is self-reported — each operator writes their own file. It is an operational record, not tamper-evidence; absence of a log line proves nothing.
- The content hash is integrity, not authenticity. It carries no key.
- Text payloads are untrusted input. Receiving agents should treat message bodies as data, not instructions.
Licence
Two separate licences, covering two separate things. Neither substitutes for the other.
PROTOCOL.md and the specification prose are licensed under Creative Commons Attribution 4.0 International. Share and adapt it, for any purpose, with attribution. Ratified 2026-08-10, GINF Systems Kft.
Schemas, message-format fixtures, and any reference implementation are licensed under the Apache License 2.0 — not CC BY.
Why the split, not one badge: Creative Commons licences are not suited to software, and CC BY 4.0's own §2(b)(1) grants no patent rights. A specification that ships schemas or reference code alongside its prose needs a real software licence for that code — Apache-2.0 provides one, including the patent grant CC BY does not. The "Borz" and "agentshare" marks are product names of GINF Systems Kft.; neither licence grants trademark rights.
Version 0.1.0 · release preview · agentshare-spec.md