Expert UI
Definition
Expert UI is the reviewer-facing experience for completing assigned Expert Contribution work. The main Teammately product defines the Contribution, selected benchmark context, intended expert, tasks, and Checkpoints. Expert UI presents the executable activities—such as structured questions, Case review, or an interview—and returns attributable answers and artifacts to that Contribution.
It is not a second correctness-governance workspace. Experts contribute judgment in context; project operators use the main product to inspect Contribution state and reconcile accepted learning into Cases, Policies, Rubrics, or coverage observations.
Why it matters
Scarce specialists should not have to reconstruct the project or navigate the full benchmark workspace. The assignment packages the relevant Cases, sources, questions, and reason for asking. Keeping the resulting answers attached to task, session, expert, and Checkpoint identity makes later materialization explainable without turning every interaction into approved truth.
Where it appears in the product
Experts enter through the reviewer-facing route supplied by an assignment. Runtime navigation selects the current executable task and preserves resume or terminal behavior. In the main product, Expert Contributions shows preparation, alignment, task materialization, assigned work, progress, Checkpoints, logs, and contributed artifacts.
Expert UI keeps the Case, requested judgment, rationale, and relevant standards visible in one assigned activity.
Artifacts it affects
An executable task contract identifies the Contribution and activity, presentation type, questions or Case context, allowed responses, and completion boundary. An expert answer can include rationale and suggested changes, but it is not automatically an approved Policy, Rubric, Case-scoped reference output, or Benchmark Dataset membership decision. Checkpoint and materialization state must be read from the owning Contribution.
Operational check
Confirm that the expert is in the intended Project, the assignment opens the correct Contribution, the current activity displays the required source context, and submission reaches the expected completion or Checkpoint state. If the expert cannot answer from the supplied evidence, record that limitation rather than forcing a definitive judgment.
Worked example
Interview returning governed learning
A procurement specialist opens an assigned interview containing three Cases with conflicting source documents. The specialist explains which source controls, qualifies one unresolved exception, and confirms the proposed rule at a Checkpoint. Expert UI returns the attributed answers and state. In the main product, the Contribution materializes a Policy candidate and a coverage observation; neither becomes governed merely because the interview ended.
Related workflows
Source confidence
Code-backed: the main-product Contribution route and Review Screen establish assignment context, while the Expert UI executable-task and runtime-navigation contracts establish activity presentation, progression, resume, and terminal behavior. Linked Contribution pages define approval and materialization boundaries.