Take the catalogue reading again, now that the address answers - #184
Merged
Conversation
The three states this issue has to keep apart are the file published, the file
unobtainable, and nothing published upstream to carry. The third was the live
one, and the tree said so in the only reading it holds for that address: taken
2026-08-11, it recorded a 404 whose body was 9379 bytes under the host's own
not-found title, with the same digest as the deliberately unmatched path read
beside it, so the two were one response rather than two that agreed.
That is no longer what answers. The address returns 1247 bytes of JSON, and the
digest is its own rather than the not-found page's, which is what separates a
catalogue from an origin serving a default:
### the catalogue address
GET https://flowfin.dev/manifest.json
status 200 OK
content-type application/json; charset=utf-8
1247 byte(s), sha256 b111962a5c8db99ccf6da3813cb8af7ef5dad4683ca3c82a5e23a0fe4ad413a6
### a path that matches nothing
status 404 Not Found
9379 byte(s), sha256 b620507312c5e97566a3c6cfaf99144fefc18a0da7d941401dfa0f5f58fb0368
Nothing else in the record moved: the name still redirects from plain http with
no strict-transport-security header, the certificate is inside its window, and
the three readings this set does not ask for say so rather than appearing as
results.
The means is the harness that already exists for this class, run as it is
documented and writing one append-only record. A reading of a public name is not
a property of this tree, so it stays outside the gate and the gate goes on
printing that the set was not asked for.
This closes nothing here. What it removes is the board resting on a pasted 404
that no longer reproduces, which is the defect of making a claim about another
artefact from the nearest thing to hand rather than from the thing itself.
Signed-off-by: Nils Lehnen <30603423+iderex@users.noreply.github.com>
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
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.
What was wrong
The catalogue address is the one path an operator pastes into a server, and this
board rests on what it answers in three places: the state #67 has to keep apart,
entry 4 of #7, and the address the install page in #27 prints. All three were
written against a 404.
The only reading this tree holds for that address was taken on 2026-08-11, and it
recorded the host's own not-found page rather than a catalogue:
Run 2026-08-23 at
51a1f10. That is no longer what answers.What this change does
It runs the harness that already exists for readings of this kind and lands the
record it wrote. Nothing else is touched:
The address now returns a catalogue, and the digest is what separates that from
an origin serving a default page:
Read beside the path in the same record that is asked for so that nothing can
match it, the two are different responses rather than one served twice:
Both run 2026-08-23 at
377e98f. One occurrence, against the unmatched path, andnone against the catalogue address. In the 2026-08-11 record that digest appears
twice.
What it carries is a catalogue with one entry in it:
Run 2026-08-23.
Nothing else in the record moved. The name still redirects from plain http and
still carries no strict-transport-security header, the certificate is inside its
window with 74 days left, and the three readings this set does not ask for are
written as not asked for rather than as results.
The means
The harness in
harness/needs-networkis what this repository already uses for areading of a public name, and this is a run of it as documented rather than
anything new. A reading of somebody else's service is not a property of this
tree, so it stays outside the gate, and the gate goes on saying on every run that
the set was not asked for:
Run 2026-08-23 at
377e98f.What this does not do
#67 stays open. The publish side of that issue is untouched, and a
run of the harness is not evidence about it. What it removes is the board resting
on a pasted 404 that no longer reproduces.
It edits no decision record.
decisions/0006-what-answers-at-the-catalogue-address.mdquotes the same 404 and says the question is cheap to settle while the address
does not answer. Under the rule in
decisions/README.mda change there is not acorrection, because it changes what a reader would decide after reading it, and
that needs a new record rather than an edit. That is left where it belongs.
The gate
Both run 2026-08-23 at
377e98f.No second reader
This change carries no second reader. The commands above are what stands in place
of one.