Complete an Expert Contribution
Complete a Contribution by following its prepared task sequence and making the requested specialist judgments from the evidence shown. The expert experience can adapt between structured forms, agent chat, interviews, case review, and checkpoints.
Prerequisites
- A valid Contribution link or authenticated expert entry point.
- Access to the Contribution and its assigned tasks.
- Enough source and case context to explain each answer.
- A stable connection when the task uses realtime agent interaction.
Steps
- Open the Contribution and read its objective, selected cases, and expected components before answering.
- Complete each task according to its type. Planned activities can be Case Review, Form, Chat, or Interview; Curation, Comparative, and Trajectory components shape the prepared work those activities present.
- Use attachments and visible case materials as the evidence boundary. State uncertainty when the supplied material does not resolve the question.
- At a checkpoint, inspect the proposed summary or artifact meaning. Checkpoints prepare and reconcile requirements, consolidator or Policy statements, interview requests or records, and Rubrics. Confirm only what matches your judgment; retry, revise, or leave unresolved anything that does not.
- Continue through the task handoff until the Contribution reaches its final step.
- Review the completion state. If the experience shows a waiting, retry, or synchronization state, do not assume the administrator has received final evidence until the product confirms it.
Object and state changes
Answers create durable task responses and can advance task sessions, checkpoints, handoffs, and Contribution status. Chat or interview activity can produce transcripts and structured learning. Case review can attach judgment to selected cases. Completion makes the contribution available for reconciliation and materialization but does not itself make every proposed artifact governed.
Review tasks can be PREPARING, BLOCKED, READY, IN_PROGRESS, COMPLETED, SKIPPED, or SUPERSEDED. The expert runtime can be PREPARING, READY, ACTIVE, FINAL_CHECKPOINT, COMPLETED, or EXHAUSTED. Checkpoints can be preparing, ready, or reconciled, with individual requirements pending, retryable, materialized, empty, or failed. These layered states explain why a Contribution can be active while one task is blocked or a final checkpoint is still pending.
Success criteria
- Every answer addresses the Contribution objective and cites the visible evidence where needed.
- Case-level judgments remain connected to the relevant case.
- Checkpoints distinguish accepted, revised, and unresolved meaning.
- The final state is visibly complete rather than inferred from navigation.
- Uncertainty or source conflict remains explicit for the administrator.
Common failure modes
- Answering from private background without identifying that the supplied evidence is incomplete.
- Treating an agent summary as accurate without checking the checkpoint.
- Leaving a form or chat task in a local unsynchronized state.
- Continuing after a stale task handoff instead of following the current Contribution route.
- Assuming that completion directly changes policies, rubrics, cases, or coverage.
Worked example
Example: checkpoint correction
An interview summary says that every expired agreement should be ignored. The expert corrects the checkpoint: expired agreements may still be relevant when the current agreement explicitly incorporates them. The corrected statement remains attributable and prevents an overbroad policy from being materialized.
Related reference pages
Related troubleshooting pages
Source confidence
Code-backed: the current expert experience supports form, chat, interview, case-review, checkpoint, completion, waiting, and task-handoff routes with durable command and reconciliation behavior.