AS-OF Policy

Purpose

This memo documents how AimwellBio time-stamps and discloses the freshness of every data artifact published on aimwellbio.com. It is the kind of disclosure a Big-4 audit team or sovereign-grade due diligence reviewer would expect to find before relying on any signal, count, or entity claim presented on the platform.

We publish this policy publicly, not in a members-only annex, because the credibility of an adversarial-validation layer depends on the verifiability of its own data lineage.

The AS-OF Standard

Every vertical's underlying data is persisted as JSON with an embedded generated_at timestamp at the moment the SCOUT ingest pipeline writes the file. That timestamp is the canonical AS-OF marker for the dataset.

• Format: ISO 8601 UTC (YYYY-MM-DDTHH:MM:SSZ)
• Location: Top-level generated_at field in each signals-{vertical}.json and atlas-{vertical}.json artifact
• Display: Pages render the timestamp as AS OF YYYY-MM-DD HH:MM UTC in a small caption near the headline counts on /signals, /atlas, and each /report/{vertical} dashboard
• Scope: Applies to all seven indications: wound-care, diabetes, oncology, cardiovascular, renal, metabolic, and ccRCC

Refresh Cadence

• The SCOUT ingest pipeline can be re-run on demand. There is no fixed cron interval; freshness is governed by the operator, not by a scheduled job.
• At the start of every working session the pipeline is re-evaluated and re-run if material upstream changes are detected (new ClinicalTrials.gov registrations, new PubMed publications inside the 5-year window, new SEC EDGAR filings from the monitored ticker list, new FDA openFDA actions).
• Partners and members may request an on-demand re-pull for any specific vertical. Re-pulls produce a new generated_at timestamp; prior versions are not overwritten without a new ingest event.

Verification

Any partner can verify the AS-OF timestamp on any vertical by querying the JSON directly. Example:

curl -s https://aimwellbio.com/signals-ccrcc.json | python3 -c "import json,sys; d=json.load(sys.stdin); print(d.get('generated_at'), d.get('counts'))"

The same pattern works for every vertical: signals-wound-care.json, signals-diabetes.json, signals-oncology.json, signals-cardiovascular.json, signals-renal.json, signals-metabolic.json, and signals-ccrcc.json.

Why This Disclosure Exists

A platform that calls itself the adversarial validation layer for AI-generated biopharma science cannot publish stale numbers behind a polished UI. The AS-OF policy is the operational guarantee that every count, every signal, every entity in the corpus is traceable to a specific moment in time, and that the moment is disclosed, not hidden.

Big-4 audit teams expect this. Sovereign procurement teams expect this. This document is here so neither has to ask.

For questions about data lineage, ingest provenance, or methodology variance between verticals, see the Methodology (Section 08 covers the ccRCC build specifically). For lineage or procurement questions, contact corporate@aimwellbio.com.