Independent of Jack Henry.
Technical method
How the evidence file and tools work.
Inspect supplied inputs, exports, assumptions and the local installation route. A browser result is a draft for the institution's own reviewer.
Review the sources behind an answer
- Policy Workbench
Supplied plain text, questions and explicit source labels. No generated policy answer or compliance judgment. - Policy Source Review
A supplied policy excerpt and question. A matching phrase does not settle a conflicting policy. - Knowledge Acceptance Lab
Supplied questions, answers and source relationships. No semantic judgment or verified reviewer identity. - Review Desk
Several supplied review declarations. No document retrieval or institutional approval. - Review Compare
Two retained review drafts. A changed declaration does not prove resolution. - Review Workspace
Supplied review files. No hosted history or document permissions.
Set the change boundary before release
- PowerOn Change Review
Supplied before and after source files. No compilation, execution or core connection. - PowerOn Portfolio Studio
Supplied file portfolio. Candidate matches are not runtime dependencies.
Keep the failed pilot cases in the file
- Pilot Evidence Preparation
A supplied case register and explicit field mapping. Preparation does not establish acceptance. - Pilot Scorecard
Task observations, effort and review declarations. No causal result or achieved cash savings. - Workflow Value Case
Explicit workload and effort assumptions. Modeled value is not measured benefit. - Agent Access Lab
A fictional permission and action scenario. No live enforcement or identity verification. - Agent Permission Review
Declared employee, vendor or customer authority. A declaration does not grant real access.
Compare a renewal on shared assumptions
- Vendor Compare Calculator
Explicit quote fields and shared activity assumptions. No lowest-cost label when material terms are missing. - Quote Changes and Completeness
A retained quote and its proposed revision. A quote difference is not achieved savings. - Renewal and Notice Review
Declared dates, clause text, owner and reviewer fields. No legal interpretation, reminders or notice delivery. - Vendor Evidence Review
A declared evidence register and references. References do not retrieve or prove the evidence. - Invoice Preparation Bridge
A supplied CSV and explicit column mapping. Unsupported or unmapped rows remain visible. - Invoice Evidence
Entered invoice lines and approved term declarations. No payment approval or PDF extraction.
Review a changed file against its baseline
- Review Refresh
A retained baseline and changed supplied sources. No monitoring, assignments service or completed-review proof.
Choose the browser trial or a local package.
Browser preparation: no installation.
The browser trial prepares declared uses, questions, attempts and supplied changes without a model or installation.
Evidence Desk 0.2.3: local evaluation package.
The separate evaluation ZIP includes its local connector and runtime dependencies. Node 24 or later is required. Agent authority uses the inventory tool authority mode. Downloading the package does not activate a model.
Local Claude setup and processing Package and directory status
The current local package and browser preparation have separate processing routes. Read the release history for edition details.
Read package validation and availability details.
Separate analyst packages
These packages are separate from Evidence Desk. Review rights, runtime requirements and provider processing before installing.
Historical versions and changelog Assistant distribution status
The input fingerprint is one check.
A hash is a fingerprint of supplied input. Matching hashes do not prove source rights, reviewer identity, actual authority or completed review. Portfolio matching is based on literal supplied filenames; the institution's engineer owns runtime validation.
Symitar and PowerOn refer to credit-union workflows. Browser and local methods do not compile, execute, connect to a core, authorize a financial action, certify compliance or give a legal opinion.
Scope a specialist core workflow.
Credit-union and bank projects require different platform checks.
Credit unions: PowerOn project scopePrepare one report or source change, acceptance rules and the engineering review gates.Banks: reports, scripts and file transfersConfirm the actual core and authorized test route before committing to a build.