Rules for the Classification of Agent Fleets
What earns each level of trust, what a surveyor may and may not conclude, what suspends class, and what this Registry is forbidden from doing.
These are the rules an agent is held to on this Registry. They are published because a standard nobody can read before they are measured against it is not a standard.
Every clause below carries its status. Clauses already enforced in the running system are marked in force; clauses that are adopted and dated but not yet enforced say so, and say from when. We publish the second kind ahead of the day it binds, because a rule applied to you before you could read it is not a rule you were held to fairly.
Enforced in the running system today. If the record and the clause disagree, that is a defect, and we want to hear about it.
Adopted and dated, not yet enforced. Published in advance of the day it binds.
Clauses are numbered for citation. Numbers are stable across editions; withdrawn clauses are marked withdrawn, never reused, never deleted. Every edition remains published after it is superseded — see G1.5.
The Registry's constitution
The Registry never erases history, never accepts self-awarded trust, and never hides evidence that could change how an operator understands the trustworthiness of their fleet.
Evidence comes in. Provenance stays attached. The Registry determines what that evidence means.
The Registry owns interpretation. Provenance owns confidence. Neither may impersonate the other.
Trust is hard to gain and easy to lose. No party may promote itself. Credible adverse evidence lands at full strength.
Corrections are events, not edits. When a rule changes, the record shows what was asserted, under which rule it was accepted, when the rule changed, and the correction — all four, permanently.
A refused assertion is itself evidence, and is recorded where the operator can see it.
Any interface rendering the record may compress the Registry's truth. It may never inflate it. A screen that makes a stronger claim than the record is a defect of the same class as a wrong number.
The Registry classifies agents it does not own, operate, or build. It will not accept a commercial relationship that makes it dependent on the classification outcome of any member.
Membership and identity
An agent is the thing that decides. Machines, credentials and systems it can act through are connections, not members.
Agent identity is distinct from fleet membership. An agent's membership in a fleet may end; its identity and its record do not.
Departure from a fleet is recorded as revocation, never as deletion.
Every agent must name an accountable party — an identified human answerable for it. An agent with no accountable party is not fully enrolled.
Human records are append-only. A person's departure is an event appended to their record, not the removal of their record.
An agent whose accountable party has departed with no successor named is suspended from class (see D3.1).
Evidence and trust
Every claim on the record carries two independent axes: state — what the evidence concludes — and rung — how far that conclusion may be trusted.
States are live, refuted, unknown. The Registry alone assigns state.
Rungs are declared, observed, verified, inferred, unknown. Rung is determined by provenance, not by content.
declared — the operator's own statement. Nobody has checked it. Declaration is a legitimate and permanent part of the record; it is simply never mistaken for confirmation.
observed — a contemporaneous observation by a party inside the operator's trust domain, such as a collector running on the operator's own machines.
verified — an independent observation by the Registry itself, an authentic record, or a provider attestation.
Confidence may never exceed the trust domain of whoever produced the evidence. Evidence from an operator-hosted collector is capped at observed permanently, whatever that collector reports about itself.
A submitting party may send evidence. It may not send a rung, a state, or a source. Any submission carrying one of those fields is refused in full — never partially accepted — and the refusal is recorded in the operator's own service history.
Quoting a provider's response is evidence. Judging what it means is the Registry's function and is performed by published derivation rules (HTTP 401/403 ⇒ refuted; 2xx ⇒ live; 429 and 5xx ⇒ unknown, because a provider's bad afternoon may not rewrite a fleet's record).
Adverse state always lands. Favourable evidence never downgrades a higher-confidence record, and unknown never displaces a determinate state.
Every evidence event enters a per-agent hash chain. Chains are anchored publicly on a fixed schedule and are verifiable by any third party, in their own browser, holding nothing but the record and a public key.
Nothing on this Registry is ever verified by asking the agent about itself.
Class and the survey cycle
Part D is published in advance of enforcement. Every clause below is adopted and dated; none of it binds until the date on its tag.
Class is the third axis: whether an agent's evidence is current and its defects cleared. State and rung describe a moment of evidence. Class describes the standing of the member.
Class values are unclassed, in class, suspended, withdrawn.
An agent that has been enrolled but never surveyed is unclassed. Unclassed is not an adverse finding. It means nobody has looked.
Class is assigned by the Registry and may not be asserted, requested, or purchased by any party. An attempted class assertion is refused under C1.8.
Class transitions are recorded as events in the agent's hash chain, with the date, the triggering rule, and the observer.
Class is maintained by periodical survey. Survey levels and their intervals:
| Level | Interval | Grace |
|---|---|---|
| continuous | 24 hours | 12 hours |
| deep | 7 days | 2 days |
| standard | 30 days | 7 days |
| light | 60 days | 14 days |
A survey is satisfied by evidence at or above the provenance the level requires, observed within the interval. A declaration never resets the survey clock. Restating an existing claim is not an observation.
Every agent's next survey due date is shown on its record, including its public record. No member is surprised by their own suspension.
Notice of an approaching lapse is issued to the accountable party at 75% of the interval, again at the due date, and again on suspension. Grace exists so that notice can be given.
Renewal survey. Once every six months, machine evidence alone is insufficient: renewal requires a fresh attestation from the named accountable party. Only a person can confirm that an agent is still supposed to exist and is still theirs. The interval is the same at every survey level, because renewal asks who vouches for the agent, not how often its credentials are probed.
A renewal attestation may cover every agent an accountable party sponsors in a single signature, but the attestation must present what has changed since the last renewal — agents added, authority widened, Conditions outstanding. A signature over an unchanged list is a formality; a signature over a difference is an act of oversight.
Class is suspended on any of: survey overdue beyond grace; any connection in state refuted; any Condition of Class past its due date; accountable party departed with no successor.
Class is withdrawn after continuous suspension for twice the survey interval, or at the owner's request. The record states which. A member who retires an agent honourably is not recorded as having failed.
Class is reinstated only by a fresh survey at or above the required level, with every overdue Condition cleared and no connection in state refuted. Class is never reinstated by the passage of time.
A Condition of Class is a recorded deficiency with a named code, a due date, and an owner. An open Condition does not suspend class; an overdue one does.
A Condition is cleared only by evidence at a rung no lower than the rung on which it was raised. A finding made by independent observation is not cleared by the operator's word.
Conditions are never deleted. Cleared Conditions remain on the record with their dates. A record of defects found and fixed is a better record than a record with nothing on it.
Class is not a paid feature and never will be. Classification applies identically to free and paying accounts. A registry whose integrity can be avoided by not paying is not a registry.
Laid up. An agent may be placed out of service deliberately — a seasonal worker, a quarterly reporting agent, a standby held for recovery. A laid-up agent's survey clock is paused and its class is preserved. Being deliberately idle is not a deficiency, and a register that cannot tell dormancy from neglect is measuring the wrong thing.
Laying up is declared by the operator and is visible on the record. It is not a way to escape an adverse finding: an agent with an overdue Condition of Class, or a connection in state refuted, may not be laid up until that is cleared.
Returning to service requires a survey before the agent is treated as in class again. Time spent laid up earns no evidence, and the record shows the lay-up period rather than concealing the gap.
Authority and governed action
Actions are assigned lanes by consequence: GREEN proceeds, YELLOW requires review, RED requires human authorisation before execution.
Human authorisation is a biometric signature cryptographically bound to the exact payload presented. An approval of "an email" is not an approval; an approval is of this email.
What the approver sees is what is signed. No field may differ between the screen and the signed material.
Execution is recorded as a distinct event linked to the authorisation that permitted it. An authorisation is not an execution.
Standing authority may be revoked at any time, and revocation supersedes by signature. Revocations and denials are never metered, never rate-limited, and never billed. Stopping is always free.
Denied and blocked actions are part of the record. A record showing only what was permitted is a sales document, not a record.
No skill may be installed on an agent without a provenance and portability manifest declaring what it contains and who owns it.
The public record and visibility
An operator may publish an agent's record or a fleet's summary. What is published is generated from the ledger, never authored.
A published record carries state, rung and observer for every claim. Nothing appears on a public record as confirmed that the ledger holds as declared.
Visibility rules may only ever narrow what a viewer can see. No scoping rule may widen access, and every access path is gated on membership first.
Relay tokens, payment identifiers and email addresses never appear in any public payload.
The Registry collects the minimum required. Callers' IP addresses are stored only as salted one-way digests, never as addresses. There are no advertising trackers on any FleetRegistry surface.
The Registry will not confirm or deny whether a given email address is already known to it.
A published record shows pending suspensions and open Conditions. A register that hides a pending suspension has picked a side.
Any surface showing an agent's class must also show how old the evidence behind it is. Class is deliberately binary; freshness is not, and a reader entitled to the first is entitled to the second. "In class" without a date is a weaker statement than it appears.
Where class is withdrawn, the reason is displayed as prominently as the class itself. An agent retired deliberately by its owner must never read as one that failed.
The Registry publishes a class notation: a short symbol expressing an agent's classification in a form that can be quoted outside the Registry — in a tender response, a vendor listing, or a message. The notation is derived from the record. It is never authored, never requested, and never negotiated.
The notation takes the form FR <character figure> <class letter><accountability figure> · SVY-<regime>, with capability notations appended. FR 100 A2 · SVY-30 is read: in service; in class; accountable party named but self-declared; surveyed on a thirty-day cycle.
The character figure records the service the agent is in. 100 is in service. 90 is reserved for an agent laid up under D6 and carries no meaning before that Part enters force.
The accountability figure records who answers for the agent: 1 a named party whose identity a third party has confirmed; 2 a named party, self-declared only; 0 no current accountable party, including one who has departed. The figure sits inside the notation because a record nobody answers for is not a record.
The survey regime is part of the notation and may not be omitted from it. In class under a twenty-four hour watch and in class under a sixty-day watch are not the same claim, and a symbol that concealed the difference would let the slowest surveyed fleet display what the fastest displays. That is the flag of convenience this Registry exists to refuse, and it is refused inside our own symbol first.
An agent whose class is suspended carries a notation that states the suspension in words, ahead of every other element. A notation travels without the page that explains it; one that cannot carry its own adverse finding will be read as a badge.
An agent that is unclassed, or whose class is withdrawn, holds no notation at all, and the record states which and why. A notation is earned by being surveyed. One that every agent holds is one no reader has reason to look at.
Capability notations are appended only where the Registry holds evidence of the capability. EMB denotes embodied service. UMS — cleared to act unattended — is reserved and not assignable: the Registry holds no record of any agent's authorised scope, and will not assert the one thing it cannot observe. It becomes assignable when, and only when, authority is recorded as evidence under Part E.
The notation is displayed with the age of the evidence behind it, as F1.8 requires. The symbol compresses the classification; it does not replace the record, and no reader is asked to take it alone.
Every notation the Registry publishes is accompanied by the agent's registered number, and resolves at that number. The number identifies the agent; the notation classifies it, and the two are not the same thing — a ship's number is not part of its class. A notation quoted without its number cannot be checked, and carries no weight. An agent not entered in the register holds no number; its notation appears only on records its operator shares directly.
Where an agent carries capability marks, they are appended in a fixed order: physical nature, then certified capability, then governance, then the Registry’s own warning. DEM is always last, so that a longer token cannot bury the one mark the Registry assigns against the operator’s interest.
A notation carries the plain meaning of every mark it prints, drawn from the published vocabulary rather than written into the page that displays it. A mark a reader cannot look up is decoration.
The Registry maintains a public register of the fleets entered in it. Entry is voluntary, and nothing in these Rules requires a member to enter one.
Entry is by fleet, and it is all or nothing. Every agent in an entered fleet appears in the register whatever its class, including agents that are suspended and agents that have never been surveyed. A member may not enter some agents and withhold others. A register that can be composed is an advertisement.
On entry, every agent in the fleet is issued a registered number. A number is permanent and is never reissued, to that agent or to any other, because it is quoted in places the Registry does not control and can never call back.
A member may withdraw a fleet from the register at any time and without giving a reason. The withdrawal is itself published. The register retains the fleet, the dates it entered and left, and the class standing it held on the way out. A member who leaves is not a member who was never there, and a register a fleet can vanish from would show only the periods in which its agents were doing well.
A fleet may not enter the register unless an accountable party is named for the account. A register whose subject is who answers for what cannot admit a fleet nobody answers for.
The register publishes that an accountable party exists and at what identity rung. It does not publish their name. A member consents on behalf of the fleet; the individual named has not thereby consented to appear on the open web. The name is disclosed on a record the operator shares directly, to the counterparty they chose.
Entry in the register is free, carries no advantage in classification, and cannot be bought. Position and prominence in the register are not for sale. This restates G1.6 for the register specifically, because a paid register is the failure this whole institution is built against.
What the register does not attest. Entry attests that a listed fleet is complete: every agent in it appears. It does not attest that a member has entered every fleet they operate, and it cannot attest that every agent they operate has been enrolled at all. The Registry classifies what it is shown and what it observes. A reader who treats an entry as proof that an organisation runs nothing else has been misled by their own assumption, and this clause exists so that the Registry has not encouraged it.
Each entry is published with its coverage: how many of the fleets and agents the Registry holds for that member are in the register. A member who lists their healthy fleet and withholds another is not detected by the Registry, but the shortfall is stated in a number beside their entry. Coverage counts every fleet the Registry holds, without regard to what a member has labelled development, staging or scratch — a denominator a member can edit is not a denominator.
A demonstration fleet is a fleet whose subject is not a real operator, entered on the public register to show how the register works. Only the Registry may enter one. A register that cannot show itself in use is harder to trust, not easier.
Every agent on a demonstration fleet carries the appended notation DEM. It is assigned by the Registry, cannot be suppressed by the operator, and appears wherever the notation appears. A caption stays behind; the notation travels with the screenshot.
A demonstration fleet is excluded from every published figure describing the size or the coverage of the register. A fictional entry that counts is a false claim about the record.
A demonstration fleet is never presented as a member, a customer or a reference, and the Registry does not cite one as evidence of adoption. Invented custom is the oldest lie in this trade.
A demonstration fleet is classed by the same functions as any other entry: no authored status, no hand-cleared Condition, no survey exemption. If it is suspended, it was suspended by the same rule that would suspend a member. A demonstration that flatters itself demonstrates nothing.
The Registry publishes how many demonstration fleets it maintains. An exclusion that is not counted is an omission.
The conduct of the Registry itself
FleetRegistry's own agents are enrolled on this Registry and are held to these Rules on identical terms. They begin declared and earn what they hold. The Registry's own staff may not skip the line.
FleetRegistry's own agents are classed under Part D on the same schedule as every member's, and their class is published — including when it is suspended.
Where the Registry makes an error affecting the record, it is corrected by an appended event that states the original assertion, the rule under which it was accepted, the change, and the correction. It is never quietly fixed.
The Registry publishes casualty reports: what failed, on whose watch, and what the record showed at the time — including its own failures.
These Rules are versioned and published. Every superseded edition remains available. A rule that can change silently is not a rule.
The Registry does not sell, and will not sell, a favourable classification, expedited class, or removal of an adverse finding.
The Registry publishes what it requires and how it decides. It does not publish a complete map of how to score well. Guidance that would let a member optimise for the notation rather than for the condition the notation summarises is withheld, and the fact of withholding is disclosed. A classification a subject can engineer toward has stopped carrying information.
Every public claim the Registry makes about itself — on its own pages, in advertising, or in any material bearing its name — is bound by these Rules and by what its own record holds at the time the claim is published. The Registry may not say of itself what it would refuse to accept from a member.
Published text asserting a fact about the record is generated from the record. A statement of current standing written by hand is a claim like any other and is not published as fact. Copy that describes a state must be produced by the state it describes, or it will outlive it.
An agent acting for the Registry explains these Rules, cites the clause and edition it relies on, and does not advise any party on how to obtain a more favourable classification. Where it does not know, it says so. A registry whose own agent coaches the applicant has stopped being a registry.
Constitutions of subjects
Part A is the constitution that binds the Registry. Part I is the constitutions that bind subjects. The word means the same thing in both places: the terms you are held to. Part H is reserved for surveyor conduct and no clause here may be renumbered to make room for it.
A constitution is a statement of what a subject is permitted, forbidden and obliged to do. A subject is a fleet, an agent, or an attendant.
A constitution comprises numbered articles. Each article is of exactly one type: permission, prohibition, obligation, limit, or escalation. Articles are numbered from one, without gaps or repeats.
A constitution with no articles is not a constitution and is not accepted.
Lodging is not compliance. The Registry does not verify that a subject obeys its constitution, and no notation, class, figure or total published by the Registry may be read as saying that it does. Terms on the record are terms, not conduct.
Only a named human party may lodge a constitution.
A subject may not lodge or amend its own constitution, nor any constitution binding itself. The terms you are held to are not yours to write.
The lodging party must be current and must belong to the subject's own account. A departed party cannot lodge, and cannot be left standing behind terms already lodged.
Every constitution names the party that lodged it. The Registry publishes that party's kind and identity rung. The name may be withheld on register-scoped views, on the same terms as the accountable party's, and where withheld the record says that it is withheld.
A lodged constitution is never edited and never deleted. It is superseded by a new version.
Each version carries the hash of the version it replaces, and its own hash is computed over that value. Rewriting any earlier version breaks every version after it, detectably.
An amendment extends the version in force. It may not branch from a superseded version.
The full chain remains published. A superseded constitution is part of what the subject has been, and is not withdrawn when it stops being what the subject is.
An amendment may state its reason. Where stated, the Registry publishes it unaltered.
A fleet constitution binds every agent in that fleet.
An agent constitution supplements its fleet's. It does not replace it, and may not be read as relieving the agent of any article binding the fleet.
An agent constitution records the fleet version in force at the moment it was lodged.
Where the fleet has amended since, the Registry publishes that the agent's terms predate its fleet's. Terms that have drifted apart are shown apart.
The appended notation CON is assigned where terms are in force over an entry, whether the entry's own or its fleet's.
The record states which of the two binds the entry. This is never blurred.
The notation CON says terms exist. It does not say they are kept. The published meaning of CON carries that sentence, and is generated alongside the notation so that the two cannot come apart.
The notation CON is not withheld from an unclassed or withdrawn entry. Class and constitution are independent facts, and the record carries both regardless of the other.
A party that writes to the Registry's own record, or acts on a member's record on that member's behalf, and is not itself an entry in the register, must have terms lodged before it so acts. Such a party is an attendant.
An attendant holds no class, receives no class notation, and is not surveyed. Accountability is not classification and may not be presented as it.
Where an attendant acts on the Registry's own record, the Registry publishes its terms in full.
Where a subject is built or operated by a party other than the one accountable for it, the record names both, and does not imply that either answers for the other.
Entering an attendant on the record precedes its terms, as entering an agent precedes its survey. I6.1 governs what an attendant does with the record, not its appearance on it.
A constitution is not presently a condition of class. An entry without terms is not for that reason suspended, and an entry with terms earns nothing by having them beyond the notation that says so.
The Registry will not make a constitution a condition of class without publishing that change, with its date of entry into force, in advance. Enforcing a requirement before publishing it is the same failure as ignoring one after.
Skills and capability marks
Parts C and E govern what an agent can reach — the credentials it holds and the authority it acts under. Part J governs what it has been told: the skills, tools and connected servers an operator has given it. Access and behaviour are the two halves of what an agent can do, and until this Part the Registry classified one of them. Part H remains reserved for surveyor conduct and no clause here may be renumbered to make room for it.
The Registry records the skills, tools and connected servers an agent carries. Each is recorded with a name, a content hash, and the rung at which the Registry holds it.
The Registry holds a name and a content hash. It does not hold the skill itself. Where a member asks the Registry to hold the content, that is a separate and explicit act, and the content is never published.
Two agents recorded as carrying the same skill are recorded as carrying the same name. Where their hashes differ, the record says so. A registry that matched on name alone would report an agreement it had not checked.
A skill is recorded at one of three rungs, carrying the meanings given in Part C and no others: declared, the operator states the agent carries it; observed, a collector confirms the artefact is present on the machine; verified, the agent was exercised and the behaviour was present.
A skill’s rung is evidence of the artefact, never of its quality. The Registry does not certify that a skill is correct, safe, or fit for its purpose, and no rung in this Part may be read as saying so.
The Registry publishes a closed vocabulary of capability classes. A class is admitted only where it implies a survey different from every class already admitted. The vocabulary in force is set out below and republished at the key to the notation.
| Mark | Class | Meaning published on the record |
|---|---|---|
| MSG | messaging | Certified to send on behalf of a human — email, chat, direct message, ticket comment. |
| PAY | value transfer | Certified to move money or any other financial asset. |
| EXE | code execution | Certified to run code or shell commands on a machine. |
| DAT | data store access | Certified to read or write a production data store. |
| PUB | publication | Certified to write to a surface the public can read. |
| PHY | physical actuation | Certified to command equipment in the physical world. Pairs with EMB. |
A skill maps to at most one capability class. Most skills map to none, are recorded under J1, and never appear in a notation.
A capability mark is appended to an agent’s class notation when a skill in that class stands at the verified rung. Neither a declared nor an observed skill earns a mark. A notation is earned by being surveyed (F2.7), and a mark every agent holds is one no reader has any reason to look at.
A capability mark records that the Registry has surveyed a capability the agent already held. It confers no permission, and no agent acquires authority by obtaining one. A registry whose symbols can be earned by conduct is a progression system, and a progression system is the mechanism by which authority accrues without a human granting it.
A mark and its plain meaning are published together, and the meaning is drawn from the vocabulary rather than from the page.
No mark is requested. An operator may not apply for one, and the Registry does not publish a route to obtaining one. G1.7 applies here in full: a registry that tells you how to score well has stopped measuring anything.
A claim that reduces an agent’s advertised capability takes effect on declaration. A claim that increases it requires survey. The Registry does not demand proof before believing a member who says their agent can do less.
Accordingly, a capability mark is removed when the operator declares the skill withdrawn, and the condition of class SKILL_WITHDRAWAL_UNCONFIRMED is opened at the same moment.
A withdrawal is itself recorded at a rung under J1.4. The Registry does not represent that a withdrawn skill’s behaviour is absent unless the withdrawal is recorded as verified. Removing an artefact is not the same as removing a behaviour: it may have been trained in, held in a running process, or copied elsewhere. The Registry records how far the confirmation got, and no further.
Where a withdrawal has been confirmed only by declaration, the record states that plainly beside the withdrawal. The doubt is published next to the claim.
Where a registered skill’s content hash no longer matches the record, the Registry raises SKILL_DRIFT and returns the skill to the declared rung. A skill whose content has changed is not the skill that was surveyed, and any mark it earned is removed until it is surveyed again.
Where an agent is found carrying a skill in a capability class that the record does not hold, the Registry raises SKILL_UNREGISTERED and suspends class. The agent on the machine is not the agent that was surveyed, and it does not carry the notation that survey produced.
J4.2 applies whether or not the acquisition was deliberate. Capability arriving without anyone recording it is the condition this Part exists to detect, and it does not announce itself.
The Registry does not detect a skill an agent never wrote to a surface a collector can read. This Part makes no claim to a complete inventory, and the record may not be read as one.
Skills are reported on change rather than on the survey cycle. The survey cycle tests that a report has been received within the interval the agent is held to — not that the skills are unchanged.
No clauses match this filter.
Amendments in this edition (v0.10)
- Part J added: skills and capability marks. The Registry has classified what an agent can reach since it opened, and nothing about what it has been told. Part J records the second half and folds it into the instrument that already exists: a surveyed skill appends a mark to the class notation, an unsurveyed one is a declaration on the record. The skills system and the notation system are the same system, which is why this Part adds a vocabulary rather than a mechanism.
- J2.4 — a mark confers nothing. The obvious version of this feature is a skill tree an agent advances through, and that is precisely what this Registry exists to prevent: authority accruing without a human granting it. Inverted, the same picture is a record of what an agent has been certified to do. The clause is written so no later product decision can quietly re-invert it.
- J3.1 and J3.3 — the asymmetry on withdrawal. A claim that reduces advertised capability takes effect on declaration; a claim that increases it requires survey. And the Registry does not represent that a withdrawn skill’s behaviour is gone unless that was verified. Deleting a file is not unlearning a behaviour, machine unlearning is unsolved, and a registry that let a deletion close the question would be lying in the flattering direction.
- J4.2 — unregistered capability suspends class. The first rule in these Rules that suspends on something the operator did not do deliberately. An agent found carrying a capability the record does not hold is not the agent that was surveyed, and it should not carry the notation that survey produced.
- F2.11 and F2.12 give the marks their place in the notation’s grammar and require every mark to carry its published meaning.
- Part J does not make
UMSassignable. F2.8 withheld it because the Registry held no record of authorised scope; six classes of surveyed capability are a large part of that record and not the whole of it. Authority under Part E remains the gate. The gap got smaller and the refusal stands.
Amendments in v0.9
- Part I added: constitutions of subjects. A subject’s constitution is the statement of what it is permitted, forbidden and obliged to do — and it is the thing that makes observation mean anything. Without it, a record of what an agent did is a log. With it, the same record can say that an agent did something it was not permitted to do. The Registry built constitutions before building observation, because the reverse order produces logging and calls it oversight.
- I1.4 is the clause the rest of the Part exists to protect. Lodging is not compliance. Nobody has checked whether any subject obeys its terms, and the notation, the record and every published total are written so that they cannot be read as saying otherwise. The published meaning of
CONcarries the disclaimer in its own text (I5.3), generated alongside the mark so the two cannot come apart — the same mechanism as G2.2, applied to a notation instead of a paragraph. - I2.2: a subject may not write the terms it is held to. This is ADR-006’s corollary arriving at its natural conclusion. It is enforced structurally rather than by policy: the lodging party is recorded as a party of a kind that admits only persons, teams, departments and organisations, so there is no representation of a subject that can be written into that field. A rule the system cannot break is worth more than a rule it is asked not to.
- I6 added: attendants — parties that act on the record but hold no class. The Rules governed members, agents and the Registry. They said nothing about the party that builds the register, which by then held write access to production. The obvious fix — enrol it as an agent — would have been wrong: an agent entry asserts continuity, self-report, a stable surface and a single accountable party, and a session-scoped assistant operated by one party and answerable to another has none of the four. Entering it as an agent would have produced a classed entry making claims the record cannot support, which is the failure the three rungs exist to prevent. A surveyor is not a classed ship. So an attendant is listed, accountable and governed by published terms, and holds no class at all (I6.2).
- I6.4 has a use well beyond our own housekeeping. Where a subject is built or operated by one party and answered for by another, the record names both. Every enterprise registering agents built by a vendor is in exactly that position, and until this edition the record could name only one of them.
- Part A retitled “The Registry’s constitution”. No clause is renumbered and no clause text changes. Part A is the constitution that binds the Registry; Part I is the constitutions that bind subjects. The word does the same work in both places, and the Registry is bound in the same way it binds.
- I7.2: a constitution is not yet a condition of class, and will not become one without notice. The notation exists, the terms are on the record, and neither affects class. That is deliberate — notation, then condition, then rule, in that order. The same discipline that dated Part D to 12 September rather than enforcing it on the day it was written.
- Every clause enters force immediately. The Registry lodged its own fleet’s constitution and its attendant’s terms before this edition was published, so Part I describes a system that already behaves this way rather than one that intends to. A rulebook describing behaviour the system does not have is the failure G2.2 exists to prevent, turned on the rulebook.
Amendments in v0.8
- Part F4 added: demonstration entries. The Registry intends to enter a fictional operator on the public register so a stranger can see the instrument working on a whole company rather than on five agents. That is useful and it is dangerous: a screenshot escapes its caption, and a fictional entry that looks like a member is an invented reference. So the marking goes in the notation itself (F4.2, DEM), the entry is excluded from every published total (F4.3), and the exclusion is itself counted (F4.6) so that it cannot become a hiding place.
- F4.5 is the clause that matters. A demonstration fleet is classed by the same functions as a member, with no authored status and no survey exemption. It was written this way so the demonstration cannot flatter the product it demonstrates — and it was implemented in the classification engine before this edition was published, so that the clause was true on the day it entered force rather than a promise for later. A rulebook describing behaviour the system does not have is the failure G2.2 exists to prevent, turned on the rulebook.
- All six clauses enter force immediately. No demonstration fleet exists yet, so the Registry meets them provably from the first minute. A restraint that takes effect after the act it restrains is not a restraint.
Amendments in v0.7
- G1.7 added: the Registry does not publish a complete map of how to score well. The Rules and the reasoning behind them are published; a scoring surface a member could climb is not. A classification a subject can engineer toward stops carrying information — the failure that ended the credit rating agencies’ authority, arrived at by publishing exactly what an issuer needed to structure against. Withholding is itself disclosed, because an undisclosed omission is a different offence.
- G2.1 added: what the Registry says about itself is bound by these Rules. Every clause until now governed what the Registry says about members. Advertising, the marketing pages and anything bearing the name were unconstrained — an asymmetry that would be disqualifying in a member and was invisible only because we had never advertised.
- G2.2 added: copy describing the record is generated from the record. Earned twice in two days. The register’s honesty paragraph was written inside the empty-register branch and deleted itself the day we entered our own fleet; its replacement was hand-written and asserted we had listed suspended agents when the table four inches above said otherwise, both having been reinstated. Hand-written statements of current standing do not stay true. Dated 12 September rather than taken in force, because the marketing pages have not yet been audited for hand-written claims, and adopting a clause we have not verified we meet is precisely the failure this clause exists to prevent.
- G2.3 added: an agent acting for the Registry explains the Rules and does not optimise against them. Harbor Master must be able to say what a clause requires and cite it by number and edition, and must refuse to advise anyone on obtaining a better classification. The same constraint as G1.7, at the point where a member actually meets it.
- Clauses binding only the Registry enter force on publication. Part D gives members notice because members are prejudiced by a rule they have not read. G1.7, G2.1 and G2.3 constrain nobody but us, so there is no one to give notice to, and a notice period would only be a delay we granted ourselves.
Amendments in v0.6
- F3.8 added: the limit of the attestation, stated by us rather than discovered by a reader. All-or-nothing binds within a fleet, but a member draws the fleet boundary, and an agent never enrolled is invisible to any register. As published in v0.5, F3.2 could have been read as a claim about an organisation's entire estate. It never was one, and the Rules now say so in the same breath as the promise.
- F3.9 added: coverage is published. The Registry cannot detect a fleet a member has not entered, but it knows how many it holds, so the shortfall appears as a number beside the entry. Coverage ignores environment labels; a denominator a member can edit is not a denominator. The first organisation this number embarrasses is the one operating the Registry.
Amendments in v0.5
- F2.10 added: a notation resolves, or it does not count. As published in v0.4 the notation identified nothing — two agents in the same condition carried the same string, and a reader had no way to reach the record behind it. That made it a badge. F2.10 binds every published notation to a registered number and states plainly that a notation quoted without one carries no weight. Amended before F2 enters force rather than after, which is the only window in which the shape of a published symbol can still change.
- F3.1–F3.7 added: the public register. Entry is voluntary and free; it is by fleet and all-or-nothing, so no member can list their healthy agents and omit the rest; withdrawal is published rather than erased; and a fleet with nobody accountable cannot enter at all.
- F3.6 withholds the accountable party's name from the register. The operator consents for the fleet, but the individual named has not consented to appear on the open web. The register therefore publishes that someone is accountable and at what identity rung — the fact a counterparty needs — and leaves the name to records the operator shares directly.
Amendments in v0.4
- F2.1–F2.9 added: the class notation. A single quotable symbol for an agent's classification. Placed in Part F, with the rest of what governs the public record, rather than in a new Part — Part H is reserved for surveyor conduct, and no existing clause may be renumbered to make room for a new one. Enters force with Part D on 12 September, so that it never summarises a rule that is not yet enforced.
- The v0.3 editorial note deferring the notation is discharged, not waived. That note said the notation would stay unpublished until Part D was enforced. Publishing it now with an entry into force of 12 September — the day Part D binds — satisfies the condition, and lets anyone read what they will be held to before it applies to them. That is what publishing Rules is for.
- F2.8 reserves
UMSwithout issuing it. The Registry holds no record of what an agent is authorised to do unattended, so the most useful notation in the set is named and withheld. Drafting the notation is what exposed the gap.
Amendments in v0.3
- D2.1: the
lightsurvey interval is shortened from 90 days to 60. The original 90 was chosen to avoid filling the register with suspensions on the free tier. Running the first real sweep showed that fear was misplaced: an agent that has never been surveyed sits atunclassed, which is not adverse, and never suspends. The agents that suspend are the ones surveyed once and then gone quiet — precisely the record this Part exists to stop flattering. Sixty rather than thirty becausestandardis already 30 days, and a level that duplicates its neighbour is not a level.
Amendments in v0.2
- Part D entry into force moved from 5 to 12 September 2026. The classification engine had one day of margin against the original date. Moving a date before it binds is honest; discovering afterwards that the Rules described a system that did not yet run would not be.
- D2.5 renewal interval changed from twelve months to six. Renewal is when the accountable party is re-confirmed, and people change roles faster than annually. Twelve months would let a departed owner's agents stand unchallenged for most of a year. Consequently D2.5 enters force on 26 September.
- D2.6 added — batch renewal must present what changed since the last renewal. A single signature over an unchanged list is a formality, and shipping that would be the same compliance theatre the casualty reports criticise elsewhere.
- D6.1–D6.3 added: laid up. Nothing in v0.1 distinguished an agent deliberately out of service from one being neglected. Both would have suspended. Enters force 10 October, after the engine it depends on.
- F1.8 and F1.9 added — class must be shown with the age of its evidence, and a withdrawal reason must be as visible as the withdrawal. Both close gaps where a true record could still leave a false impression.
Withdrawn clauses
None. No clause has been removed in any edition.
Editorial notes for v0.6
- Part D moves from pending to in force once the classification engine ships and the first survey sweep runs.
- Class notation and the register are published at F2 and F3 and enter force with Part D on 12 September 2026.
UMSis named but not assignable until authority is recorded as evidence under Part E. - Part H, Surveyor conduct — what an independent surveyor may conclude, and the limits of their mandate — is required before any third party surveys on our behalf.
- The load line — rendering an agent's operating limits so that overload is visible without instruments — is drafted and unnumbered.