Documentation
¶
Overview ¶
package: main / cmd type: logic job: the REST client the generator contributes through limits: transport only; the graph it carries is the grower's (-> graph.go)
package: main / cmd type: logic job: the fixture identity and the graph shapes it signs limits: builds claims only; delivering them is the client's (-> client.go)
package: main / cmd type: entrypoint job: the generator binary — a client that seeds a running ranke-db over its REST API limits: a client only: no config, no adapters, no archive of its own (-> cmd/ranke-db serves)
Seeding belongs to a client: a contributor is an application-held key (§5.7), so a fixture signs its own claims and the server attests only the merge. Filling a dev archive therefore goes through POST /contribute, the path everything else uses.
package: main / cmd type: logic job: the release-process scenario — a fixed script, not a grown shape limits: builds claims only; delivering them is the client's (-> client.go)
The graph of `docs/use-case-release-process.png`, built for real — a fixed script, where `chain` grows an archive by rule. Building it is also a claim about the model: a picture that cannot be built cannot honestly be presented. Two things the slide elides: every entity is introduced by a source it derives from (D1), and the process runs several times.
Source Files