Answer A-229: an entry's requires names the optional ones too
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
This commit is contained in:
@@ -194,3 +194,7 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
(module, fingerprint, serves, manifest), a finding writer (raise and clear by kind and id), the seat holders (a
|
||||
holder function), and the operator channel (ask, record, and claim with the warrant and the act). The gate's own
|
||||
kept form `Kept` moves into `go/approval`, which `operatorchannelclient` re-exports.
|
||||
- **A-229** (§708, §709; principle 7) As §709 says, a catalog entry's `requires` names every requirement as
|
||||
`catalogue.Manifest.Wants` lists them, optional ones included; a reader that means "required, not optionally" (the
|
||||
module graph's `Requirers`, the assigner's halves) tells the optional ones apart by the entry's manifest
|
||||
(`IsOptional`).
|
||||
|
||||
Reference in New Issue
Block a user