# TenVur public data freshness manifest

This manifest publishes TenVur's source freshness, cache, and stale-data handling policy for official public-data feeds. It does not perform live uptime probes, expose credentials, store private pulls, certify current upstream availability, approve partner claims, or activate cash commissions.

Sources: 1
Near real-time sources: 0
Server-only sources: 0
Live probe status: not_run_public_manifest
Source clock: provider_cadence_only

## Rollup policy

Serve the manifest with public, max-age=60, s-maxage=300. Cache actual source pulls by each policy's sourceCacheWindow, not by this manifest TTL.
Use server routes or scheduled jobs for source pulls, keep required headers and free keys server-side, and publish only compact derived context to client pages.
If a source is stale, keep evergreen source labels but pause current-value, urgency, ranking, safety, eligibility, or revenue claims until refreshed.

## NASA POWER API

Provider: NASA Langley Research Center POWER Project
Cadence class: release_bound
Max public cache age: 86400 seconds to provider release cycle
Stale after: Climatology and temporal dataset dependent
Claim status when fresh: historical_context_only
Claim status when stale: historical_context_only
Failure posture: Use as historical context with release-window labels and avoid customer-specific conclusions.

Next action: Publish source cards and partner briefs with release-window labels, claim boundaries, and account-credit disclosure.

## Guardrails

- Do not claim this manifest proves an upstream source is currently available.
- Do not expose private pulls, API keys, required headers, customer identifiers, or raw lead data through freshness endpoints.
- Do not turn public-data recency into guaranteed demand, safety, compliance, eligibility, revenue, ranking, or property-level claims.
- Do not treat source freshness as live cash commission approval, payout eligibility, or billing configuration.