NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS 2.0.3

There is a newer version of this package available.
See the version list below for details.
dotnet add package NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS --version 2.0.3
                    
NuGet\Install-Package NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS -Version 2.0.3
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS" Version="2.0.3" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS" Version="2.0.3" />
                    
Directory.Packages.props
<PackageReference Include="NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS --version 2.0.3
                    
#r "nuget: NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS, 2.0.3"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS@2.0.3
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS&version=2.0.3
                    
Install as a Cake Addin
#tool nuget:?package=NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS&version=2.0.3
                    
Install as a Cake Tool

NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS

DynamoDB OASIS Provider — AWS managed NoSQL key-value and document database for OASIS holons and avatars via AWSSDK.DynamoDBv2. https://oasisomniverse.one

Username/email exports resolve the current avatar identity; their version selects exported holon roots, not the avatar's independent history. Use the current username/email when exporting older holons. Linked children keep independent versions. Explicit versioned avatar lookups still support historical identity fields. Export version=-1 enumerates validated stored histories and filters ownership/deletion per version; archived roots retain stored child payloads, not a cross-version graph snapshot. Export versions below -1 fail before identity I/O; ordinary reads still reject negative versions. AWSOASIS inherits this same implementation.

Installation

dotnet add package NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS

NuGet versions · Source project

Choose a published version compatible with the other OASIS packages in your application. This guide describes current source; older packages may not contain the same functionality.

Frameworks and dependencies

Declared target frameworks: net10.0.

Direct external package references:

  • NextGenSoftware.OASIS.API.Core
  • AWSSDK.DynamoDBv2

Project references and conditional dependency versions are recorded in the source project. NuGet restore resolves packaged dependencies; do not mix arbitrary DLLs from different release graphs.

Integration and configuration

Use this package for the responsibility described above, alongside its owning OASIS runtime/provider integration. Inspect the source project's public APIs and owning component documentation for construction and configuration; this package installation command does not start an API server, authenticate an avatar or provision an external service.

Provider adapters require their respective service configuration and credentials. Runtime libraries require the host application's lifecycle and persistent paths where applicable. Supply only the settings actually required by the owning component; do not copy production DNA into a client or public release.

Errors and security

For APIs returning OASISResult<T>, check IsError, ErrorCode and Message; do not treat a failed result as success. Preserve useful diagnostics without logging access tokens, passwords or private keys. Keep secrets in the host's appropriate protected configuration or platform storage.

Platform requirements

Target-framework compatibility is not proof that every native dependency or external service works on every operating system. Check the selected version's platform assets and native/service requirements before deployment. Unity/mobile integrations require their supported platform layer and packaging workflow; a managed NuGet archive alone does not establish Android/iOS, IL2CPP or two-device convergence acceptance.

Troubleshooting

  • Restore/assembly mismatch: pin a coherent set of package versions and inspect the dependency graph.
  • Configuration or authentication error: inspect the owning component's result diagnostics and service requirements without exposing secrets.
  • Native loading failure: verify OS/architecture and required native artifacts rather than suppressing the error.
  • Missing functionality in an older version: compare the immutable released source and release notes, not only the moving Development branch.

Releases and further documentation

[Verified release matrix](https://github.com/NextGenSoftwareUK/OASIS/blob/Development/Docs/WIP/Release and Status/OASIS_RELEASE_STATUS.md) · [Documentation audit](https://github.com/NextGenSoftwareUK/OASIS/blob/Development/Docs/WIP/Release and Status/RELEASE_DOCUMENTATION_AUDIT.md)

Published NuGet versions are immutable. Updated documentation ships with a new unpublished package version after checked promotion and publication. This metadata-backed guide does not replace product-specific API examples or claim unverified platform tests.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS:

Package Downloads
NextGenSoftware.OASIS.API.Providers.AWSOASIS

Connects the OASIS to Amazon DynamoDB through AWSSDK.DynamoDBv2 for holon and avatar persistence. The same SDK path supports AWS-hosted DynamoDB and DynamoDB Local for repeatable integration evidence. Part of the OASIS HOT-Swappable Provider Architecture. Ecosystem: https://oasisomniverse.one

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.0.4 134 11/14/2026
2.0.3 125 11/14/2026
2.0.2 109 10/13/2026
1.0.0 108 9/28/2026

NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS v2.0.3

DynamoDB OASIS Provider — AWS managed NoSQL key-value and document database for OASIS holons and avatars via AWSSDK.DynamoDBv2. https://oasisomniverse.one/

What's new since v2.0.2
- Admit native-sized Dynamo preparations without invented padding (86b17e1)
- Bind Dynamo transaction capacity to original ordered actions (0c49bf9)
- Capture native DynamoDB PutItem capacity for ordinary AWS saves (e406049)
- Classify explicit native DynamoDB lifecycle validation refusals truthfully (034f6d6)
- Classify persisted cloud JSON corruption at shared storage boundary (388ccb4)
- Correct Dynamo transaction capacity using native table aggregate evidence (87c176d)
- Enforce complete caller graph admission and acknowledgement in DynamoDB AWS saves (2c8afe8)
- feat(aws): add session credentials and explicit SDK credential-chain mode (2d6fd02)
- feat(aws): atomically persist conditional holon graphs and durable receipts (1209ceb)
- feat(aws): capture scoped native capacity through the official SDK pipeline (fd51119)
- feat(aws): expose native resource observations through Core capability (a37ed02)
- feat(aws): retain protected write preparations with atomic first-winner claims (d43bd7c)
- feat(dynamo): export all validated stored record versions (52254a9)
- Fence uncertain DynamoDB item mutation attempts from V2 replay (f0dbd81)
- fix: protect scoped AWS graphs and advertise cloud capabilities (c38f0d1)
- fix: report truthful AWS and DynamoDB read result counts (79362fe)
- fix(aws): count acknowledged ordinary writes before caller publication (42ef0d7)
- fix(aws): count parent-query edge in graph depth limits (bb25bc9)
- fix(aws): decouple export versions from avatar identity history (df04480)
- fix(aws): fence identity reassignment before lifecycle deletion (9e1ba0f)
- fix(aws): include pinned official SDK credential dependencies (fda8fb0)
- fix(aws): preserve committed tombstones in ordinary record saves (29efc80)
- fix(aws): project trusted consumer inputs into canonical storage records (6b5746a)
- fix(aws): reject ambiguous wallet key identity lookups (12eaa68)
- fix(aws): reject incompatible DynamoDB identity schemas on activation (b653145)
- fix(aws): report native outcomes and protect conditional tombstones (d9e1e02)
- fix(aws): require acknowledged Dynamo table creation (ba8f659)
- fix(aws): require native save acknowledgements and persist detail keys (de3583e)
- fix(aws): resolve avatar tokens through canonical native identities (e6e74f8)
- fix(aws): resolve tombstones for identity lifecycle operations (152e33c)
- fix(aws): snapshot canonical search scope before native reads (c719c22)
- fix(aws): validate direct provider signing configuration before SDK setup (4bae8e0)
- fix(aws): validate matching tombstones without rewriting history (dde2303)
- fix(dynamo): persist planned child roles in canonical history writer (ea9b5ff)
- fix(dynamo): publish committed revisions to ordinary batch callers (fee05e8)
- fix(dynamo): reject empty point identities before SDK reads (edf831b)
- fix(dynamo): reject repeated identities across read pages (34000bd)
- fix(dynamodb): atomically apply paired avatar lifecycle and V2 tombstones (ffe4e54)
- fix(dynamodb): preserve exact metadata in soft-delete history (69e271c)
- fix(dynamodb): reject invalid graph read holon types (91a06fe)
- fix(dynamodb): validate native table readiness acknowledgements (d507947)
- fix(providers): reuse exact JSON objects in DynamoDB and Firestore history (d1e1459)
- fix(storage): scope historical embedded graph exports by owner (0422e00)
- Guard acknowledged Google and AWS record publication with shared identity checks (b37ad59)
- Honor DynamoDB collection graph options through shared projector (388169c)
- Honor DynamoDB single holon graph reads and identity validation (a021528)
- Implement and verify native standalone DynamoDB avatar-detail lifecycle (028bc9d)
- Implement Azure graph saves using one shared cloud graph planner (e1300d3)
- Implement conditional DynamoDB and AWS record history with native verification (dfabb90)
- Implement conditional native hard holon deletion for DynamoDB (11e7fd9)

Full changelog
https://github.com/NextGenSoftwareUK/OASIS/commits/master/Providers/Cloud/NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS