Skip to content

docs: add UMS API dotnet applied reference#3

Merged
beyondnetPeru merged 6 commits into
mainfrom
docs/api-dotnet-applied-reference
May 28, 2026
Merged

docs: add UMS API dotnet applied reference#3
beyondnetPeru merged 6 commits into
mainfrom
docs/api-dotnet-applied-reference

Conversation

@beyondnetPeru

Copy link
Copy Markdown
Contributor

Adds a UMS architecture reference for the Dotnet API with bilingual documentation and portal links. The reference maps current API source evidence to the Evolith API standard and separates reusable promotion candidates from UMS-local implementation details. No workflows or hooks were changed.

@beyondnetPeru beyondnetPeru merged commit 2a4b032 into main May 28, 2026
2 of 3 checks passed
@beyondnetPeru beyondnetPeru deleted the docs/api-dotnet-applied-reference branch June 1, 2026 11:18
beyondnetPeru added a commit that referenced this pull request Jun 4, 2026
…only filtering

Two correctness gaps closed (AC-1, AC-3):

1. Published-only resolution: LoadAsync and ReloadTenantAsync now filter
   configs to Status.Id == 2 (Published) before populating any scope bucket.
   Draft and Archived values no longer participate in runtime resolution.

2. Full scope invalidation on reload: ReloadTenantAsync now also evicts all
   Suite and Module buckets that belong to the tenant being reloaded before
   repopulating. Previously only _tenant was evicted, leaving stale Suite/Module
   entries in cache after an Archive or Update operation.

3. Extract BucketTenantConfigs helper to remove duplication between LoadAsync
   and ReloadTenantAsync.

3 new cache tests: stale Suite eviction, overwrite semantics, Published-only absence.
Tracker: gap #3 marked closed.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant