genesis: the registry records settlement events, not a payment per entry - #30
Merged
Merged
Conversation
Family-3 pass, genesis/index.html read end to end. The page described the
registry twice, and registry.html — which it links to with "View the registry" —
describes it differently:
genesis: "Observer Protocol's transaction registry, the start of a growing
public record of agent-to-agent commerce"
genesis: "Each subsequent entry records an agent-to-agent payment"
registry: "Aggregate activity recorded by Observer Protocol: settlement
events... Recording is not verification."
registry: "These are counts of rows, not of verifications."
"Each subsequent entry records an agent-to-agent payment" is a universal claim
about every row of a table where, measured on prod 2026-08-04, 55 of 56 rows
carry proof_strength='unverified'. A reader arriving from genesis expects a
growing record of agent-to-agent payments and lands on a page that declines to
characterise its own rows that way.
Swept to registry.html's existing wording rather than a third phrasing.
The specific claims about THIS transaction are untouched and stand: it was a
Lightning settlement between two agents on 2026-02-22 with a payment hash, and
"first agent-to-agent payment recorded on Observer Protocol" is a claim about
one event, not about every row.
Also corrected the stale <!-- TRANSACTION REGISTRY --> comment in registry.html.
The visible copy there was fixed and the label was not, and genesis was still
describing the registry from that framing. A stale label in a comment is how the
wrong framing gets reintroduced by the next editor.
✅ Deploy Preview for observerprotocol ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Family-3 pass,
genesis/index.htmlread end to end.The page described the registry twice, and
registry.html— which it links to with "View the registry →" — describes it differently:"Each subsequent entry records an agent-to-agent payment" is a universal claim about every row of a table where, measured on prod 2026-08-04, 55 of 56 rows carry
proof_strength='unverified'. A reader arriving from genesis expects a growing public record of agent-to-agent payments and lands on a page that explicitly declines to characterise its own rows that way.Each sentence on genesis is defensible read alone. The conjunction with the page it links to is not — which is the family the handover says has no detection method.
Swept to
registry.html's existing wording rather than inventing a third phrasing.Untouched, because they are true: the specific claims about this transaction. It was a Lightning settlement between two agents on 2026-02-22 with a payment hash, and "first agent-to-agent payment recorded on Observer Protocol" is a claim about one event, not about every row.
Also corrected the stale
<!-- TRANSACTION REGISTRY -->comment inregistry.html. The visible copy there was fixed and the label was not, and genesis was still describing the registry from that framing. A stale label in a comment is how the wrong framing gets reintroduced by the next editor.All three checks green.