[Buyer Product Gap] Build accessible visual analytics, exact-value tables, and evidence exports

[seonghobae]

Buyer problem

The approved product requires buyers to inspect bitemporal evidence, event/topic trajectories, multiple membership, model invariance, uncertainty, and leakage. TEPP is currently a headless Rust/API platform, so a buyer cannot complete the core interpretation and audit workflow without custom code. Visual analytics is not decorative: it is the product surface that makes uncertainty, provenance, and next actions usable.

Required workspace

Design and implement a coordinated visual-analytics application backed only by stable versioned TEPP contracts. The initial inventory must cover:

1. Bitemporal Lens;
2. Temporal Document/Event Graph;
3. Topic River and lineage/activity state;
4. Semantic/Lexical/Measurement/Method Drift comparison;
5. TDT detection and tracking console;
6. CHRONOS event-schema canvas;
7. Cross-Classified Multiple-Membership view;
8. Dynamic ESEM/DSEM builder and result inspector;
9. Invariance dashboard;
10. Knowledge-cutoff and leakage audit.

Design authority and tooling

• Create the actual Figma file before implementation of the high-complexity interactions.
• Record the real Figma File ID in the owning ADR; placeholders or invented IDs fail review.
• Define reusable design tokens and Storybook components; repeated graph/table/filter/evidence objects must not be copied ad hoc.
• Derive UI state transitions from the versioned API/artifact contracts rather than inventing frontend-only scientific states.

Acceptance criteria

• Every chart/graph has a semantically equivalent exact-value table with units, uncertainty, provenance, missingness, and sample basis.
• Keyboard, touch, screen-reader, reduced-motion, no-JavaScript fallback where applicable, print, PDF, and high-zoom states are designed and tested.
• Graph layout distance is not described as statistical distance; association is not described as causation.
• Users can filter by language, time/cutoff, organization, author, department, project, role, episode, model run, posterior draw/summary, and evidence status without losing provenance.
• Evidence drawers resolve every visible claim or value to immutable artifact, model/config/cutoff, and exact source-span references allowed by authorization.
• Uncertainty, instability, unresolved language profile, failed invariance, convergence failure, partial lineage, stale evidence, access denial, and policy rejection are first-class UI states.
• Topic/event/cluster labels are visibly distinguished from numerical identities and reviewed facts.
• Users can compare model K candidates, seeds, time windows, languages, backends, and ablation variants without silently mixing incompatible runs.
• Exports are generated from the same source data as the screen and include SVG, accessible PDF, CSV, JSON, JSON-LD, GraphML, Arrow, or Parquet as appropriate.
• Figma interaction frames, Storybook inventory, design-token tests, component tests, button/action edge tests, i18n consistency, accessibility automation, visual regression, and realistic end-to-end user journeys pass.
• All customer-facing text tells the user what the evidence means, what remains uncertain, and the next valid action.
• The UI can be deployed separately but also integrated modularly into LineageWeave and other CWL products through public contracts.

Product proof

Demonstrate a realistic anonymized buyer journey from a knowledge cutoff and project/event question to:

relevant evidence
→ topic/event trajectory
→ membership/context comparison
→ uncertainty/invariance check
→ source-span inspection
→ reproducible export
→ documented next action

The journey must be usable without hover-only values and must survive print/PDF review.

Security and privacy

The client never receives provider credentials, identity-mapping secrets, unrestricted source text, or cross-tenant data. Purpose-bound fields and re-identification paths remain server-authorized. Sensitive values cannot leak through URLs, telemetry, screenshots, exports, error text, or cached client state.

Authority

Use PRD §15, Architecture, API Contract, Privacy Governance, and the repository doctoring register. Implement against the latest authoritative WCAG/accessible-authoring and visualization guidance recorded in docs/research/standards-and-literature.md.