Provcache library status
Verified against commit
942a18727c(2026-09-26). Re-verify with:pwsh tools/scripts/test-targeted-xunit.ps1 -Project src/__Libraries/__Tests/StellaOps.Provcache.Tests/StellaOps.Provcache.Tests.csproj -Class '*Provcache*' -BuildProjectReferences -Restore
Provcache is a library family, not a service.
| Project | Content |
|---|---|
src/__Libraries/StellaOps.Provcache/ | Contracts and services: VeriKeyBuilder composite keys, DecisionDigestBuilder, ProvcacheService, invalidation, evidence chunking, lazy fetch, revocation, OCI and minimal-proof export, write-behind queue, telemetry |
src/__Libraries/StellaOps.Provcache.Valkey/ | ValkeyProvcacheStore adapter |
src/__Libraries/StellaOps.Provcache.Api/ | MapProvcacheEndpoints minimal-API endpoint mappings (default prefix /v1/provcache) |
Production projects that reference the family: StellaOps.Policy.Engine, StellaOps.Cli (prov command group) and StellaOps.ExportCenter.Core (ProvcacheOciExporter). No host maps MapProvcacheEndpoints, so the Provcache HTTP API is not served. These libraries do not by themselves establish an operational, service-owned cache deployment.
Withdrawn PostgreSQL provider
The unadopted StellaOps.Provcache.Postgres implementation is withdrawn as of 2026-09-20 (EST-9). It and its dedicated test suite are retained unchanged under src/__Obsoleted/__Libraries/. No production project, startup registration or plugin descriptor selected that assembly. The similarly named Core registration helper was an uncalled no-op; it was removed rather than advertised as a provider. No database or cached record was deleted by this retirement. Receipt: provcache-postgres-retirement-20260920.json.
Historical feature-check records describe the earlier source layout. Their decision-digest builder evidence concerns the retained Core logic; it does not prove a deployed PostgreSQL write-behind service. Do not use those records to configure the withdrawn provider or to infer durable revocation custody from the in-memory ledger. A durable implementation needs a named data owner and a verified startup migration path.