gnomonlearn
Docs/RFC-0025/Reference catalog

RFC-0025 · Reference catalog

Versioned draft snapshot

RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.

Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.

← Read the authored RFC

Generated reference catalog. This page renders structured Lean data for RFC-0025: defined terms, diagnostics, dependencies, and invariants. It does not establish proof coverage or runtime conformance. The authored narrative lives in RFC-0025.

This page is generated from the lean/Gnomon/Spec/ module for RFC-0025. Edit that source and regenerate this catalog.


Title: HTTP Protocol Binding
Status: draft

Depends on: RFC-0001, RFC-0006, RFC-0008, RFC-0024
Extended by: RFC-0028, RFC-0034, RFC-0046

Proof citations in source: 6 / 6. Standalone proof verification is pending.


Definitions

(none defined)

Diagnostics

CodeSeverityDescription
M25510ErrorInput field not placed by any binding modifier, path template token, query: list, or body: slot. The field will not be sent.
M25511ErrorHTTP 4xx or 5xx response with no matching selector in the errors {} block.
M25512ErrorHTTP request timed out with no timeout selector in the errors {} block.
M25513Errormethod: slot missing from an HTTP operation in a client that imports gnomon.io.http.
M25514ErrorField carries a per-field binding modifier and also appears in an operation-level path: template, query: list, or body: slot — conflicting location assignments.
M25515InfoField carries path modifier but its name does not appear as a {token} in path: — compiler auto-synthesizes the path token from the field name.

Dependency neighborhood

graph LR
  nRFC_0025["RFC-0025"]
  nRFC_0001["RFC-0001"]
  nRFC_0025 --> nRFC_0001
  nRFC_0006["RFC-0006"]
  nRFC_0025 --> nRFC_0006
  nRFC_0008["RFC-0008"]
  nRFC_0025 --> nRFC_0008
  nRFC_0024["RFC-0024"]
  nRFC_0025 --> nRFC_0024
  nRFC_0028["RFC-0028"]
  nRFC_0028 --> nRFC_0025
  nRFC_0034["RFC-0034"]
  nRFC_0034 --> nRFC_0025
  nRFC_0046["RFC-0046"]
  nRFC_0046 --> nRFC_0025

Invariants

  1. A field MUST NOT carry more than one binding modifier. (enforced by: compile-time)
  2. A field with a binding modifier MUST NOT also appear in operation-level path:, query:, or body: slots. (enforced by: compile-time)
  3. An unresolved $ENV_VAR_NAME in baseUrl: without a default MUST cause a startup-time error rather than a per-call error. (enforced by: boot-time)
  4. Credential values MUST be retrieved from the runtime credential store at call time and MUST NOT be embedded in the compiled bundle. (enforced by: runtime)
  5. Explicit headers {} entries MUST take precedence over headers an auth scheme would otherwise emit. (enforced by: runtime)
  6. If a required credential is missing at call time, the runtime MUST raise a non-retryable error before making the network request. (enforced by: runtime)
  7. Required fields declared in returns but absent from a 2xx response MUST cause a non-retryable runtime type error. (enforced by: runtime)
  8. When path: begins with http:// or https://, baseUrl: MUST be ignored and the path is treated as the absolute final URL. (enforced by: compile-time + runtime)

Normative Statements

Statements are structured source data. Proof citations, where present, have not passed a standalone Gnomon proof gate.

Auth Scheme Implementations

  1. MUST_NOT — When an explicit headers {} entry conflicts with an auth-scheme header, the runtime MUST NOT override the explicit entry. (proof citation: rfc0025_b10_grounded; verification pending)

Parameter Location Rules (Fallback Algorithm)

  1. MUST — A field with a binding modifier that also appears in an operation-level slot MUST produce error M25514. (proof citation: rfc0025_b2_grounded; verification pending)
  2. MUST_NOT — Fields MUST NOT be assigned to more than one location across both passes. (proof citation: rfc0025_b8_grounded; verification pending)
  3. MAY — For POST/PUT/PATCH with no body declared, the compiler MAY collect remaining input fields into an implicit body object. (proof citation: rfc0025_b6_grounded; verification pending)

Slot Extensions

  1. MUST_NOT — A field MUST NOT carry more than one binding modifier. (proof citation: rfc0025_b4_grounded; verification pending)
  2. MUST — A field that carries a binding modifier and also appears in an operation-level path/query/body slot MUST produce error M25514. (proof citation: rfc0025_b0_grounded; verification pending)

Linked References

DirectionTarget
Depends onRFC-0001
Depends onRFC-0006
Depends onRFC-0008
Depends onRFC-0024
Extended byRFC-0028
Extended byRFC-0034
Extended byRFC-0046