Data freshness

How current is the data you can query right now? Here "freshness" is measured by source_fetched_at — when jpcite retrieved the source — not by the original publication date at the source.

What to check

  • Fresh (within 30 days) — somewhat old (30–180 days) — old (over 180 days).
  • Most published rows carry a primary-source URL and fetch timestamp. Each response exposes source_url, source_fetched_at, and known_gaps.
  • Use source_fetched_at to decide whether a returned record is fresh enough for your workflow.
  • Pair freshness checks with Data sources and the public audit log (change-detection RSS) for source and change context.

Update heatmap (19 series)

Daily / weekly / monthly updates for 19 series — adoption RSS, e-Gov laws, enforcement actions, municipal subsidies, patents, EDINET, invoice registrants, and more — are arranged across four lanes (ingest / settle / monitor / weekend) and rolled up every day at 10:00 JST. The data is available as JSON from /analytics/freshness_rollup_latest.json.

SLA = a latest run within 24h, no failure/timeout, and a 24h success_rate ≥ 50%. SLA breaches trigger a Telegram notification.

LaneSeriesUTC cronJSTSLA (h)TargetPurpose
AKnowledge graph0 17 * * *02:0024Program dataSearch-assist index update
AProgram portfolio30 17 * * *02:3024Program dataProgram-combination update
AEntity risk0 18 * * *03:0024Entity dataEntity risk-score update
AEDINET30 19 * * *04:3024Disclosure dataEDINET disclosure ingest
AAdoption RSS0 20 * * *05:0024Adoption dataAdoption RSS ingest
BProgram recommendation45 20 * * *05:4524Program dataAggregation for recommend / compare
Be-Gov law amendments0 21 * * *06:0024Law datae-Gov law-amendment detection
BQuality metrics15 21 * * *06:1524Public metricsPublished quality metrics
BEnforcement actions0 22 * * *07:0024Enforcement dataEnforcement-action press
CBudget → subsidy0 23 * * *08:0024Program dataBudget → subsidy chain
CJPO patents30 23 * * *08:3024Patent dataJPO patent publication
CInvoice registrants0 0 * * *09:0024Invoice dataInvoice-registrant delta
DMunicipal subsidies0 18 * * 0 (Sun)03:00168Municipal data47-prefecture municipalities
DDefinition updates0 18 * * 4 (Thu)03:00168Program dataDefinition promotion
DPartnership opportunities0 20 * * 0 (Sun)05:00168Program dataPartnership-opportunity aggregation
DMultilingual0 4 * * 0 (Sun)13:00168Translation dataEN / KO / ZH fill
DExpansion corpus0 2 * * 2 (Tue)11:00168Public materialsDiet / council / brand mentions
DMonthly report0 21 1 * * (Day 1)06:00744Public metricsMonthly PDF
DLong-range forecast0 19 4 * * (Day 4)04:00744Program data30-year subsidy-cycle forecast

Lane definitions: A = ingest (03–05 JST) / B = settle (05–07 JST) / C = monitor (07–09 JST) / D = weekend & monthly. For the operating model, see the SLA / operations page.

Reading freshness as an Evidence Packet, before the AI answers

When an AI cites a program basis, treat the Evidence Packet's source_url as the primary-source URL and source_fetched_at as the fetch time. Check old rows and not-yet-fetched areas alongside known_gaps, and in the answer text separate "what could be confirmed" from "what is unconfirmed".

To try anonymously, see the free 3-checks-per-day quick start; for source agencies and licenses, see Data sources.

Program feeds (RSS)

Program feeds you can subscribe to in Feedly / Inoreader / Google Discover — usable as an alternative to municipal sites or chamber-of-commerce pages. Each feed holds up to 100 items and is regenerated weekly.

Per-prefecture feeds are enumerated in /assets/rss-feeds.json (47 prefectures, up to 100 items each across Tier S+A+B+C).

For the live Japanese freshness screen, see the Japanese page. For English FDI use cases, see jpcite for foreign-invested entities.