EvidCue is a concept for answer cues on a separate phone during permitted live conversations. Explore how approved wording, source evidence, and reviewed AI drafts could be kept distinct.
THE IDEANot every question needs the same engine. Reach for approved wording first, source evidence next, and a clearly marked AI draft only when the question calls for reasoning.
The prewritten, approved response appears here. No new wording is generated.
Status: approved wording · source shown in productSelect a route to see what the companion view would show. The order describes relative complexity and expected response posture, not measured latency.
Illustrative routing only. No numeric speed or accuracy claim; real performance depends on the implementation and device. Read the guide to approved cards, source evidence, and AI drafts.
EvidCue should make it obvious whether you are looking at an approved line, a sourced passage, or generated reasoning. The person speaking remains responsible for what they say.
Explore a proposed way to distinguish controlled answer cards from retrieved source passages and AI drafts during authorized customer, training, or internal conversations. Organization-specific content, governance, and validation would need to be built before deployment.
Explore a proposed phone companion for permitted calls or conversations. Check the rules of the setting first; do not use outside assistance where it is prohibited, including restricted assessments or interviews.
EvidCue is a concept for a separate-phone companion that displays answer cues during permitted live conversations. This website is an interactive preview, not a live answering service.
The proposed design has three routes: bounded local matching to approved cards, retrieval of relevant source passages, and clearly labelled AI drafts for complex questions. Source evidence is not approved wording; AI drafts require human review.
No. This website is a concept preview. An older local prototype demonstrated a phone companion view and bounded matching, but the standalone three-route service and domain-specific validation are not established.
An ordinary share of a computer window need not include a separate phone, but cameras, mirroring, whole-device capture, and other setups can expose it. Use assistance only where permitted and disclose it where required.
This is a concept website. An older, separate Logan-specific local prototype demonstrated a phone companion view and bounded cue matching. The EvidCue three-route illustration here is not connected to a live answering service or a validated, approved corpus. Audit-grade logs, approval/version metadata, and domain-specific validation remain future work. Explore the routes as an explanation of the design, not as answers to rely on in a real conversation.