jschoubben
acd5a0d80b
Against a real ACME server the proxy orders, the challenge is answered at the name on port 80 through the proxy itself, the authorisation goes valid, finalisation is accepted, and the authority issues a certificate. The client then posts to an empty URL to collect it, and never does. Read from the authority's own log rather than inferred. Across one run it issued two certificates and accepted finalise three times: the client reaches issuance every attempt and fails at the same step after it. Ruled out and recorded, so nobody repeats it: the directory is complete; the authority's API certificate covers the address; the challenge path works. A hand-written server config was suspected and was wrong — replacing it with the server's own default, changing only the challenge port, gives the identical error. Filed rather than pursued because what remains is interop between two libraries against a server that exists to be a test server, and may say nothing about a real authority. What the mesh needed to show, it showed: a routed name gets a certificate ordered from a configured authority, and an unrouted one gets nothing — that second assertion passes. Phase 1 closes with this one item partly open. Two of its four tasks needed no code at all, the network shape was built, and the next thing to learn comes from moving a module rather than a fourth lab run.
03-DESIGN
The authoritative specification. Implementation is built against what is written here.
Two layers
| Folder | What it is |
|---|---|
00-as-is/ |
The mesh that exists today. Shipped behaviour, described as it is — including behaviour nobody would choose again. |
01-to-be/ |
The mesh being built toward. Every statement traceable to a record in 02-DECISIONS/. |
They are never mixed. A statement about the future does not belong in an as-is document, and an as-is document is never edited to describe an intention.
When a to-be design ships, it does not move. Its as-is counterpart is written or updated,
the to-be document's status becomes implemented, and both stand — one describing what runs,
the other recording what was intended. Deleting the intention loses the reasoning, which is
the expensive half.
Frontmatter
Every design document (not the READMEs) carries:
---
layer: as-is | to-be
status: designed | in-progress | implemented | abandoned
code: [] # owning code repo(s), from 00-META/repos.md
updated: YYYY-MM-DD # date of the last status change, not of text edits
decisions: [] # 02-DECISIONS/ records this document rests on
---
For an as-is document, status: implemented is the normal state — it describes something that
runs — and code: names where that implementation lives.
Status changes when implementation state changes, never because design text was edited. An
implemented claim must be defensible from the owning repository's main branch, not from
intent. If it cannot be checked, it is in-progress.
Cross-cutting views are generated from this frontmatter by the hq-status skill and never
written to disk.
What belongs here
Functional analysis, architectural description, and specification — prose and diagrams
only, no code. A manifest field may be named; a manifest may not be pasted. A document
enters the to-be layer only after the decision behind it is recorded in 02-DECISIONS/
and the research that produced it is closed.
Subfolders are encouraged where a layer grows enough to need them.