Federation
A cooperative keeps a record of its own work, and sooner or later that record has to meet other people’s. This page states what federation means to this cooperative: how the record is meant to travel, what decides which part of it leaves, what we commit to, and what we invite. It is a vision, written down so nobody has to ask, and it is nobody’s obligation but ours.
What federation means here
Not a merger, and not a platform anybody joins. Federation is two bodies keeping their own records, in their own words, and being able to hand each other a defined part of what they hold, under a rule each of them wrote down first. Nothing about it requires either one to move onto the other’s system, adopt the other’s vocabulary, or give up the ability to walk away.
That reading has consequences the cooperative takes as position rather than preference. The first is that there is no single-protocol future worth planning for: the work a body does internally and the record a public reads want different properties, and one substrate serving both serves neither well. The second is that the join between two bodies is not a wire. It is shared vocabulary and shared governance, which is to say it is mostly a writing problem, and the technical part is the easy half.
One record, two rings
The cooperative keeps one record. An entry is written once, carries its provenance, and is never edited, which is what lets it travel later without losing its authority. That record stands in two rings, and there is a written rule between them.
Where the work happens
Coordination, approvals, the day to day, and the identities that speak for the cooperative. The full record lives here, and it belongs to the members, who are the people it is about.
Operational. Not public, and not published by default.
What the public may read
A defined digest of the inner record, at a stated grain, published so that anyone can read it, cite it, and hold the cooperative to it. Today the outer ring is this web estate, the pages you are reading.
Public. A projection of the record, never the source of it.
What crosses between them is decided by rule, not by judgment on the day. The Egress Doctrine is that rule: whose the record is, whose the public digest is, and a written table deciding which subset departs, at what grain, through which named door, with corrections travelling outward through the same door a claim did. The doctrine stands drafted. It binds when a person with standing adopts it, and not before.
Deny by default is the starting position. A record without an egress rule leaks by accident and hoards by default, usually both at once, and the cure for both is the same written table.
What the cooperative commits to
Four commitments, stated from this cooperative’s own record and binding on nobody else. They are the shape any federation with us would have to fit, and they are written here so that a reader can hold us to them before there is anybody to federate with.
- The record travels with its provenance, or it does not travel. A claim that leaves this cooperative carries where it came from and how fine its citation is. A digest that cannot be traced back to an entry is a rumour with good typography.
- Our vocabulary is published, and mapping beats merging. The words the record uses are a versioned artifact, held in agreement with the page that governs them by a check that fails when they drift. Across a boundary the deliverable is a mapping, not a merger: this term here means that term there, at this grain, with these losses. Neither body has to adopt the other’s language, and neither should be asked to.
- Nothing leaves except by a rule written in advance. What may be said publicly about a member, a program, or a transaction is decided by an adopted doctrine and not by whatever an interface happens to expose. Where the rule is still a draft, as it is today, the answer is that nothing leaves.
- Identity is meant to end up the person’s. The end state this shape implies is that a person carries their own identity and their own record of practice between bodies that federate, rather than holding a separate account inside each of them. An identity that can leave with the member sits closer to open and voluntary membership than any account table we would build for ourselves. It is not built, and today the account you sign in with here is the cooperative’s.
What it invites
No invitation on this page is addressed to a particular body, because none has been extended and this is not the place one would be. What the cooperative invites is narrower and more useful than a partnership: read the rule before it hardens, and tell us where it is wrong.
Three things are readable today, and all three are drafts:
· The Egress Doctrine, the rule for what leaves. One of the elections it leaves open is whether a member’s consent to being named is gathered once, standing, or per departure. That is a question for the people it would name.
· The Lexicon, the cooperative’s vocabulary as an artifact a machine can read, which is the half of federation that is cheapest to do early and the half that decides the rest.
· The Almanac, the register where every piece of this is addressed, marked, and open to being argued with. This page is entered there at X-30.
Anyone building along these lines is welcome to take the vocabulary, the doctrine, or the argument and use it. Nothing here asks for a relationship in return, and nothing here creates one.
Two pieces, at two grains
This page has a companion, and the relationship between them is the doctrine above, applied to itself.
The full account belongs to the members. This is the digest.
The cooperative’s members read a longer version of this on the intranet: the same two rings and the same rule, plus the sequencing, the horizons in the order that would unlock them, and the part a public page has no business carrying, which is what any of it would mean for a particular person’s share, sign-in, and record. That page is at the members’ federation strategy, and it is readable to members.
This page is the outer-grain version of the same thing: what federation means to us, what we commit to, what we invite. It is thinner on purpose, and thinner is not a euphemism for vaguer. Everything on this page is true at the grain it is stated, and the part held back is sequencing and member detail rather than position.
Two ledger addresses, X-29 and X-30, so that either can be adopted, corrected, or withdrawn without the other. Not one document published twice.
The bounds
Named here rather than left implied, because a vision page is exactly where scope quietly widens.
- Nothing on this page is adopted.
- It was drafted by the cooperative’s agent under the standing drafting grant in the grant register, staged on its own branch, and entered in the register at X-30 with the drafted mark. Publishing it puts a draft on the estate. It commits the cooperative to no protocol and puts no rule in force.
- No other organization is named, and none is implied.
- This page describes no agreement, assumes nobody else’s plans, and should not be read as announcing that anything exists beyond this cooperative or that any relationship has been agreed. A federation vision that named its intended partners would be a negotiation conducted in public, and that is not a thing to do to people who have not agreed to it.
- A federation act is a governance act.
- Any dependency taken on another body, any protocol the cooperative commits to operating, and anything published outward as the cooperative are acts for named humans with the standing to bind it. No amount of technical readiness makes them otherwise.
- Where this page and an adopted instrument differ, the instrument is right.
- This page is then the defect, and it owes a correction published the way corrections are published rather than quietly edited. Every instrument named on this site, with its status, is on the legal shelf.