Consequences, connected.

Every affected guarantee was evaluated on all of its prerequisites.

PR #pr:9003 Graph revision 1 Head public-demo-v1-S2 Assessment JSON

Verdict CLEAR_WITHIN_SCOPE

Why this verdict

R_ALL_HOLD1 prerequisite assumptions checked; every affected guarantee holds

What changed

Fact	Main	Proposed	Control
`emailservice.retry_max_attemptsconfig/emailservice.yaml:3`	5	8	us

How far it reaches

flowchart LR
  G_EMAIL_WITHIN_BUDGET -. promises .-> ADR_011["ADR-011"]
  classDef broken fill:#2a0f1a,stroke:#ff6b8b,color:#ffd3dd
  classDef unknown fill:#2a2310,stroke:#ffd27a,color:#fff0cc
  classDef holds fill:#0d2620,stroke:#7cf0c8,color:#d8fff2

Fig. 1. Each broken path fires from the changed assumption up to the decisions that promise or rely on it.

Dependency graph text

flowchart LR
  G_EMAIL_WITHIN_BUDGET -. promises .-> ADR_011["ADR-011"]

Guarantee	Status / baseline	Tier	Promised by	Relied on by	Exposed callers
`G_EMAIL_WITHIN_BUDGET`	holdsMain: holds	3	ADR-011		checkoutservice, frontend

Checked and not affected

No related decisions in this category.

Who should review

Remedies that survive verification

Only complete remedies may open a fix PR. Partial and rejected alternatives remain visible.

No verified remedy available for this assessment.

Assumption evidence

Assumption	State	Predicate / attestation
`A_EMAIL_BUDGET`Our retry attempts stay within the provider's allowance	holding	`8 <= 10`emailservice.retry_max_attempts / emailprovider.max_retries

The lexical gap

Fulltext search

Fulltext for attempts | emailservice | max | retry finds ADR-007, ADR-010, ADR-011, ADR-016.

Guarantee graph

The guarantee graph additionally reaches no additional decisions, whose decision bodies do not mention those terms.

Source citations

A_EMAIL_BUDGET adr/ADR-011.md:17 (local checkout)
G_EMAIL_WITHIN_BUDGET adr/ADR-011.md:12 (local checkout)
emailservice.retry_max_attempts config/emailservice.yaml:3 (local checkout)