feat: account-wide sending trust ladder and daily allowance visibility - #1064
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an opt-in account-wide external-recipient trust ladder, replacing independent domain progression. Accounts start at 20/day and reach 2,000 on the thirtieth clean active day, subject to the plan cap. Shared-identity sends consume that allowance and are additionally capped at 50/day; internal recipients do not consume daily capacity.
Reservations serialize across identities, retain uncertain exposure, and preserve idempotent late settlement. Clean-day credit uses immutable accepted-attempt provenance, including across recipient reclassification and runtime-policy changes. Bounded retention preserves earned progress. Immediate refusals and queued holds explain current usage and reset time;
/v1/account, both SDKs, CLI, MCP, and dashboard expose the same optional contract.Validation (final head
d756e2212: 28 CI checks passed, one skipped):Independent and adversarial review both have no remaining blockers after fixes for late-attempt attribution, internal-only retries, recipient reclassification, and policy-toggle provenance. The final reviewed build passed the isolated local SMTP checks again.
Both flags default off. This PR does not enable hosted enforcement. Reviewed grandfathering, the policy-source rollout/observation window, and detector automation remain separate rollout work; see
docs/design/account-trust-ladder.md.