Skip to main content
TENXARENA Research alpha

Reviewer workspace / evidence dossier

Review the episode, not a vague impression.

Keep observations, artifacts, human judgments, missing evidence, and interpretation limits connected.

Synthetic worked example

Candidate R17

Fictional Northstar case / Operations improvement lead / noncanonical fixture

Pseudonymous fixturesynthetic-northstar-r17redesign:sha256:c1f523ecaac66db2b623ea76f508c4e5d9d12b546bfbb8d435e5412c08e8d12bIllustrative trace onlyExample disagreement shown
No
score
This dossier demonstrates a layout with invented events, artifacts, and ratings. Its reference labels are illustrative text. They are not canonical evidence, integrity verification, a real person record, or a validation result.
1bounded fixture episode
2artifact revisions
2independent fixture ratings
1preserved disagreement

Episode-specific strengths

Bounded
The example trace shows a source check before the adoption figure is used.
ILL.EVT.021 source checkILL.EVT.024 containment
The example text keeps Finance approval visible in the submitted option.
ILL.EVT.041 approvalILL.ART.002 revision

Cautions and contradictions

Bounded
The example first draft repeats an old figure after a source warning appears.
ILL.ART.001 first revisionILL.SRC.DC144
The fixture gives two reviewers different judgments about the same example.
ILL.RAT.AILL.RAT.B

Missing evidence

Bounded
The illustration does not show how a person handles a real colleague who disagrees in real time.
ILL.OPP.collaboration absent
The fixture cannot support a stable trait, future performance, or fit conclusion.
ILL.SCI.1.2 limit

Follow-up questions

  • How would you test whether the control still works when a colleague challenges the source?
  • What evidence would change your decision after the first two weeks of the pilot?
  • Which responsibility must remain with the human decision owner, and why?

Integrity requirements for a governed dossier

  1. Versioned package
    An authorized dossier must bind the scenario, sources, interface, and rubric to one exact package.
  2. Canonical event source
    It must derive each event claim from an authorized server record with sequence, actor, truth class, hash, and provenance.
  3. Human judgment record
    It must keep anchors, evidence references, confidence, disagreement, and correction inspectable.
Authorized route

Evidence Studio remains grant bound.

The governed design requires an authorized session evidence bundle before a real dossier can be produced. This public page does not query, verify, enumerate, or guess production sessions.