Review the work
with its evidence
intact.
Inspect scope, sources, changes, unresolved items,
review observations, and handoff context in a mode
designed to keep review traceable.
Need to structure or progress the work first? Workflow Mode remains a
separate destination.
defined action slot
Three layers, one connected review.
A recommended structure for how a bounded package of work moves through
inspection. Select a layer to see what it shows.
Receive & scope the review
What arrived from Workflow Mode, what isincluded, currentness, unresolved work andthe review boundary.
Inspect & challenge
Sources and evidence, changes, checksand comparisons, findings and questions,with uncertainty kept visible.
Disposition & handoff
A source-defined outcome, conditions, thereturn and change cycle, next destinationand history.
Layer 1 in the workspace below: the package summary and scope rail (A, H).
Inspection first. Outcome second.
Review controls dominate; workflow progression controls are absent. Annotations sit
outside the frame so the interface stays credible.
provided
Source B
permission and package
state allow
Bounded review
Package title, scope and source workflow reference stay visible.
Evidence intact
The selected object links to its source and currentness.
Attention state
Unresolved, missing, conflicting and changed states shown in text.
Inspection, not execution
No workflow progression controls.
Finding linkage
Observations tie to an object and evidence.
Outcome boundary
Permission and state dependent; no unsupported Approve/Reject.
Traceability
History and version relation without taking over.
Workflow relationship
Source and return handoff are visible.
What a reviewer can inspect.
Recommended UI contracts for each area. Behaviors marked conditional render only
when the product confirms them.
Review intake & scope
- Package title, purpose, source Workflow Mode reference, state, version and currentness
- Included scope and an explicit excluded or out-of-scope list
- Readiness summary: unresolved, missing, restricted, conflicting
- “Ready” appears only if the product defines it
Actions
- Open first attention item
- View evidence
- View history
- No disposition until inspection state permits
AI never outruns evidence.
Kriton™ AI Advisor is a primary navigation destination, but its
behavior inside Review Mode is not established here. This
page links to the authoritative source instead of describing
AI review.
advisor panel shell only if
integration is confirmed
History is part of the product
story.
Package, finding, evidence and outcome events stay
traceable where supported. Specimen events use neutral
role labels and placeholder times. No export or download
is shown unless a real export exists.
Package received
Role: review participant · Time placeholder · State: received
Finding updated
Finding 02 · Open → Addressed (example labels)
Evidence superseded
Source A · current version replaced; review impact shown if known
Returned for change
To Workflow Mode · unresolved findings carried across
Doing and checking stay distinct.
Provisional boundary: Workflow Mode structures and progresses work. Review Modeinspects it after handoff. The two remain separate destinations.
Workflow Mode owns
- Definition, context, sequence, work state
- Dependencies, exceptions, evidence capture
- Progression controls and work correction
Review Mode owns, as source-approved
- Intake and scope, inspection context
- Checks, findings, questions
- Outcome, return-for-change, review history
Route each question to its authoritativesource.
Trust claims live on their own pages and are not repeated here.
Governance
How review decisions are governed.
Compliance
What compliance evidence exists.
Privacy & Security
How review data is protected.
Technical detail: API Reference, Release Notes, Accessibility and Provider Due Diligence appear once approved. Until then, technical evaluation runs
through sales.
Find the proof that matters to you.
Lenses help you navigate. They are not product roles, editions or permissions.
Finance / Accounting
Scope, source evidence, changed items, unresolved work, outcome history.
Controller / Reviewer
Inspection context, comparisons, findings, return cycle, traceability.
Operations
Handoff, state visibility, unresolved work, version cycle.
IT / Architecture
Object model, permissions, events, integration boundary.
Risk / Governance
Evidence lineage, responsibility, findings, history.
Procurement / Enterprise
Trust routes, evaluation path, accessibility.
See how Review Mode fits your review process.
Bring the workflow handoff, evidence, review, governance, integration anddecision requirements that matter to your team. We will route the conversation tothe appropriate evaluation path.
Submission does not guarantee pilot availability, approval capability, automated checking, AI review or accounting outcomes.