# Data and acceptance still required

This is a fixed historical sample, not a certified on-air feed. Its local validator
checks file integrity and agreement between published records, counts and formats.
The following items remain open.

- Cabinet and critic titles require a verified, dated source. The lean graphics
  currently contain only MLA or MP. The evidence summary records identity issues,
  including office_title_unavailable; the lean lower third omits that issue field.
- Portrait URLs and 136 cached review images are available; broadcast redistribution rights and template filename conventions still need approval.
- Party/topic colours, riding aliases and icons are proposals. Approve branding,
  on-air name formatting, aliases and font coverage using the actual template.
  glyph_check_required is a review hint, not proof that a font can render a name.
- Inspect each cohort's data-quality.json for published quality issues. Graphic rows
  expose review_required/review_status; lower thirds also expose glyph_check_required.
  Member/month evidence summary.json files provide identity_issues and further
  presentation context. No separate editorial-checks.json is shipped.
- The demo displays all positive topic counts and flags small samples. Producers still need to decide whether the sample supports the intended story. The compact lower third does not expose tie flags; consult the L-bar.
- Fine-topic tags are opt-in stored classifications, not curated on-air labels.
  Source links and matching counts do not certify classification, attribution,
  sponsorship, completeness or source availability.
- The demo now uses the approved 14-category product projection. Applying that taxonomy to the production database and live API remains separate work.
- Historical party and office affiliations are not reconstructed. Stored database
  identity is captured separately from the historical activity dates.
- No tested XPression scene is supplied. JSON/CSV/XML and browser validation do not
  prove DataLinq selection, font rendering, polling or output behavior. Run the
  operator acceptance checklist in BINDING_GUIDE.md in the installed Ross version.
- API_CONTRACT.md describes the live integration contract. The website has a
  separate summary/evidence request panel connected through the web-app backend.
  The fixed downloads do not execute query flags. End-to-end acceptance requires
  the actual broadcast API to be running and configured; polling, ETags and capture
  expiration still need deployment verification. The frontend does not independently
  certify source/portrait availability.
- The documented live capture store uses configurable SQLite storage. Deployment
  must supply durable shared storage or route pinned requests to the owning instance;
  otherwise captures may be unavailable. The temporary default is not evidence of
  durable storage across replicas. Verify this in the actual API deployment.
- PWA card routes, approved share images and QR destinations require supplied,
  validated assets and routes. They are not demonstrated by this package.
