NextGenSoftware.OASIS.API.Providers.GoogleCloudOASIS 2.0.6

dotnet add package NextGenSoftware.OASIS.API.Providers.GoogleCloudOASIS --version 2.0.6
                    
NuGet\Install-Package NextGenSoftware.OASIS.API.Providers.GoogleCloudOASIS -Version 2.0.6
                    
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.GoogleCloudOASIS" Version="2.0.6" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="NextGenSoftware.OASIS.API.Providers.GoogleCloudOASIS" Version="2.0.6" />
                    
Directory.Packages.props
<PackageReference Include="NextGenSoftware.OASIS.API.Providers.GoogleCloudOASIS" />
                    
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.GoogleCloudOASIS --version 2.0.6
                    
#r "nuget: NextGenSoftware.OASIS.API.Providers.GoogleCloudOASIS, 2.0.6"
                    
#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.GoogleCloudOASIS@2.0.6
                    
#: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.GoogleCloudOASIS&version=2.0.6
                    
Install as a Cake Addin
#tool nuget:?package=NextGenSoftware.OASIS.API.Providers.GoogleCloudOASIS&version=2.0.6
                    
Install as a Cake Tool

NextGen Software WEB4 OASIS API Google Cloud OASIS Provider

GoogleCloudOASIS uses the Google Cloud SDKs. Canonical OASIS avatar/detail/holon persistence uses Firestore; optional Cloud Storage and BigQuery clients are separate capabilities, not covered by Firestore-only evidence.

Username/email exports resolve the current avatar identity; version selects exported holon roots, not the avatar's independent history. Use the current username/email even for older holons. Linked children keep independent versions. Explicit versioned avatar lookups still support historical identity fields. Negative export versions fail before identity I/O.

Current direct verification

Single-holon hard deletes also validate the SDK acknowledgement timestamp before publishing deletion success. Invalid acknowledgement retains reconciliation-required evidence even when independent inspection shows the original was deleted; do not replay it blindly. Existing server precondition conflicts remain known rejections. Transactional avatar deletion acknowledgement and durable recovery still require separate verification.

Avatar export roots are selected by CreatedByAvatarId, not merely ParentHolonId. Native regressions cover ID, username and email routes synchronously and asynchronously. Existing descendant projection is unchanged; this does not establish an authorization policy for graph descendants.

Use the retained local runner Scripts/TestHosts/Run-ReusableGoogleTests.ps1. It requires the already-installed Firestore emulator, reuses cached dependencies/fixed outputs, takes an exclusive environment lease and stops its owned Java process afterward. No implicit installation or production credentials. Test results are scoped to native Firestore SDK calls, not hosted cloud authorization, charges or complete provider/interface certification.

Trusted application subclasses are projected into canonical Core DTOs before saving, including selected recursive graph nodes through the shared planner. Stored JSON continues to use the restricted type binder; consumer-only CLR type names are not a persistence contract. Avatar-detail provider keys are stored and published only after acknowledgement. Arbitrary explicit-interface/proxy implementations and extra application-specific fields are not certified by these subclass tests.

Historical reads currently reject positive versions. General concurrency, acknowledgement/recovery, all fields/options/interfaces, Cloud Storage/BigQuery and hosted/API/release gates remain open. Activation can perform service-side health/setup operations; Firestore tests disable Cloud Storage/BigQuery and use the loopback emulator. Current evidence and limitations: Docs/WIP/HyperDrive-Providers/HYPERDRIVE_V2_CURRENT_RELEASE_GATES.md.

Single-record saves now require a nonnull SDK WriteResult with a nondefault native server UpdateTime before publishing caller IDs/keys. This validates the acknowledgement, not application CreatedDate metadata. Missing/uninitialized acknowledgements retain the attempted document path and reconciliation marker; no server transaction ID is invented. Inspect original state before retrying. The check adds no extra native requests and does not provide durable recovery or certify every mutation path.

Initial Release targeting OASIS API v2.3.1 (Current LIVE REST version):
https://api.oasisplatform.world

Full documentation and source code can be found here:
https://github.com/NextGenSoftwareUK/OASIS

Make sure you check out the Overview and Benefits Of Building On The WEB 4 OASIS API sections above! 😃 Thank you!

Anonymous public Cloud Storage metadata CQL

GoogleCloudPublicMetadataSource is a separate read-only adapter over the existing CQL interfaces. Its public constructor always creates the pinned SDK's anonymous client. It reads object metadata, with SDK retries disabled and no billing-project setting; it never downloads imagery or creates/uploads/deletes cloud objects. Canonical Firestore persistence remains a separate capability.

Configure one to eight distinct printable-ASCII keys (maximum128characters each), a bounded general-purpose bucket name and a stable nonempty source-owner GUID. Retain that GUID with the catalogue: it participates in the deterministic native-to-holon ID. The current native sample uses three official public Landsat objects and needs no Google account, emulator or new runtime.

// Read these values from the retained source configuration.
// Changing sourceOwner would change the mapped holon identities.
using var source = new GoogleCloudPublicMetadataSource(
    bucketName,
    sourceKeys,
    sourceOwner);

var activated = await source.ActivateQuerySourceAsync(cancellationToken);

if (activated.IsError)
    throw new InvalidOperationException(activated.Message, activated.Exception);

// Select several native objects by their metadata key.
// Use sourceKeys.Take(2).ToArray() to show the smaller subset.
var selectedKeys = sourceKeys;

var query = CosmicQuery<Holon>
    .Create(CosmicQueryScope.Named(ProviderType.GoogleCloudOASIS).Result)
    .Where(holon => selectedKeys.Contains(
        CosmicQueryMetadata.Value<string>(
            holon,
            GoogleCloudPublicMetadataSource.ObjectKeyMetadata)))
    .Result;

// The common planner checks the adapter's actual capabilities before I/O.
var planned = CosmicQueryPlanner.Plan(
    query,
    ProviderType.GoogleCloudOASIS,
    new[] { new CosmicQueryTarget(ProviderType.GoogleCloudOASIS, source.QueryCapabilities) });

if (planned.IsError)
    throw new InvalidOperationException(planned.Message);

var rows = await source.ExecuteCosmicQueryAsync(
    planned.Result,
    cancellationToken: cancellationToken);

if (rows.IsError)
    throw new InvalidOperationException(rows.Message, rows.Exception);

Supported source filters are GCSObjectKey equality and bounded membership; paging follows complete selection validation. General Name/Description filters, ordering, aggregate or arbitrary bucket-scan queries are rejected at planning. Output includes name/description and native bucket/key/ETag/generation/size/checksum metadata. Size, generation and metageneration are decimal strings to preserve native integer precision in WEB4/JavaScript. A failed/invalid selected response publishes no partial page.

Verification on31October2026:17controlled cases and1real anonymous SDK/CQL case (three records/two-record subset), no skips. WEB4 task code now registers this as an isolated optional read source via CQL_GCS_PUBLIC_SOURCE_JSON; independent query-only permission/tariff and host read policy are required. The exact JSON schema is schema, bucket, keys, owner with schema1; credentials, billing projects and endpoint overrides are rejected. This is not deployed in the hosted sandbox, and actual Mongo pairing remains unverified. Do not describe it as hosted CQL/Firestore parity. Official public-data access and public datasets.

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.GoogleCloudOASIS:

Package Downloads
NextGenSoftware.OASIS.OASISBootLoader

The OASIS BootLoader provides a single entry point to initialise the entire OASIS ecosystem in any .NET application. Reads OASISDNA configuration, registers and activates all configured providers, sets up Auto-FailOver/LoadBalancing, and returns a ready-to-use OASIS instance. Integrate 55+ decentralised networks into your app with just a few lines of code. Part of the OASIS Omniverse at https://oasisomniverse.one

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.0.6 151 11/14/2026
2.0.5 149 11/14/2026
2.0.4 349 10/13/2026
2.0.3 218 9/28/2026
2.0.2 170 9/28/2026
2.0.0 341 7/12/2026

NextGenSoftware.OASIS.API.Providers.GoogleCloudOASIS v2.0.6

WEB4 OASIS API GoogleCloudOASIS Provider is one of the many WEB2/WEB3 providers that plug in and integtate into the OASIS.

What's new since v2.0.5
- Initial validated package contents and metadata for this release line.

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