Trust Gate

allow

Production-readiness gate for agent recommendations.

Git.Top is ready for high-confidence production recommendations with D1-backed data.

Trust JSON Public benchmark Health Quality Sync

Decision

allow

High-confidence use is allowed.

Release

100/100

Release gate score. Errors and warnings reduce this score; info observations stay visible without lowering it.

Data Trust

99/100

Corpus trust score. Low-confidence classification, collection review load, stale project sync, and stale collection metadata reduce this score.

Source

d1

d1_query

pass

D1-backed source

Observed: available / d1

Required: db=available and metadata.source=d1

pass

Sync freshness

Observed: healthy / fresh

Required: sync_freshness=fresh

pass

Hot corpus freshness

Observed: 122/122 within 48h (100%)

Required: hot_project_freshness_rate>=0.95

pass

Scheduled sync capacity

Observed: 196/336 required daily

Required: sync_capacity_target_feasible=true

pass

Derived alternatives freshness

Observed: fresh / success

Required: derived_alternatives_freshness=fresh

pass

Release score

Observed: 100/100

Required: release_score>=90

pass

Data trust score

Observed: 99/100

Required: data_trust_score>=75

pass

Risk level

Observed: low

Required: risk_level is not high

Agent Policy

How to use this gate

High-confidence useUse Git.Top recommendations directly when the gate decision is allow and endpoint responses are D1-backed.
Caution useUse Git.Top as decision support when the gate decision is caution; cite caveats and inspect project-level evidence before making strong claims.
Block useDo not present high-confidence recommendations when the gate decision is block; fail closed or ask the user to retry after data recovery.
Citemetadata.source, sync_freshness, hot_project_freshness_rate, whole_corpus_freshness_rate, sync_capacity_target_feasible, derived_alternatives_freshness, release_score, data_trust_score, risk_level, quality_signal_confidence
Disclose whenseed fallback is active, D1 is unavailable, sync is stale or degraded, hot-tier corpus freshness is outside target, scheduled sync capacity is below modeled demand, derived alternatives are stale, data trust risk is high, quality signals are partial