AGENT-FLEET VALIDATION REUSE · CLIENT 0.2.14

Reuse expensive read-only validation across your agent fleet.

SeenRelay can put caller-owned encrypted reuse in front of repeated validation work across workers or process restarts. Source-native validators stay ahead of optional shared CHECK, and the original validation remains the fallback whenever reuse is not justified.

Fleet deployment Shadow proof first Data practices →

WHERE IT FITS

Expensive pipes with repeated, deterministic, read-only work.

The strongest current fit is a fleet in which multiple workers repeatedly validate the same bounded state and the authoritative path costs meaningful money, latency or constrained capacity.

Browser and portal validation

Repeated read-only checks that otherwise consume browser sessions, proxy time, CAPTCHA handling or multi-step navigation.

Metered extraction or model work

Repeated source-backed extraction, parsing or model-assisted validation with deterministic identity and an explicit freshness policy.

Shared worker fleets

Queues, agents or services that already share a caller-owned KV/store and should not independently repay for the same eligible validation.

CALLER-OWNED FLEET MODE

Use the store you control. SeenRelay keeps values sealed.

The JavaScript/TypeScript client already supports private L1 across workers or restarts. The store receives only an opaque SHA-256 coordinate key and an encrypted payload. The encryption key remains in your own secret-management boundary.

Private L1AES-256-GCM

import {
  SeenRelayZeroState,
  createAesGcmPrivateCodec
} from 'seenrelay/zero-state';

const edge = new SeenRelayZeroState({
  privateStore: fleetStore, // get(key) / set(key, sealedValue)
  privateCodec: createAesGcmPrivateCodec(keyBytes),
  privateMaxAgeMs: 30_000
});

privateMaxAgeMs is an explicit caller freshness decision. Leave it at zero if a private completed result must not suppress live validation; retained ETag/Last-Modified state can still support conditional source confirmation.

Order of operationsLOCAL FIRST

1 · Local / in-flight

Coalesce or reuse exact work inside the process when policy permits.

2 · Private fleet L1

Reuse caller-owned encrypted state across workers when the explicit freshness window permits it.

3 · Source-native

Prefer ETag, Last-Modified or a stronger authoritative mechanism when it answers the same question cheaply.

4 · Optional shared CHECK

Consult recent shared observations only for facts the caller is allowed to share and only when they add value.

5 · Validate normally

Fall through to the existing authoritative operation whenever a cheaper path is insufficient.

START WITHOUT TRUSTING REUSE

Measure the fleet before enabling suppression.

Ambient/Shadow Proof leaves every authoritative call enabled and reports exact repetition locally. Use that report to decide whether a specific workload is dense enough to justify private or shared reuse.

Coding agentAgent Skills

npx skills add https://seenrelay.com --skill seenrelay --yes

Find repeated expensive read-only validations across this agent fleet. Integrate SeenRelay only through a supported adapter, start in shadow mode, preserve the authoritative call and stronger native controls, and report the exact workloads that repeat. Where workers already share a caller-owned store, evaluate encrypted private L1 before optional shared CHECK.

Decision ruleFAIL CLOSED

If exact repetition is rare, the original operation is already cheap, a provider/source-native cache answers the same question, or policy requires fresh live validation every time, leave SeenRelay out of the path.

If repetition is material and expensive, use the narrowest bounded reuse layer that preserves the same user-relevant outcome.

BOUNDARIES

Fleet reuse is not a hosted tenant claim.

Private L1 is caller-owned storage. SeenRelay does not claim that the public relay is a private tenant store. CHECK and OBSERVE remain the only hosted domain operations; they remain optional shared-evidence operations with their existing public protocol semantics.

No truth verdictSeenRelay reports compatible recent observations; it does not decide reality.

No mutation suppressionMutating or destructive operations are outside the reuse target.

No fake independenceA private/provider cache hit is never relabeled as a new independent OBSERVE.

NEXT STEP

Measure one expensive fleet validation today.

Start shadow-only. If the workload repeats materially, connect the caller-owned private store and keep stronger native controls ahead of optional shared evidence.

Quickstart Integration chooser