PRIESTAI | COMPANY EVALUATION BRIEF

Company/team:
Workflow to evaluate:
Owner and reviewer:
One measurable result:
Representative task and current baseline:

SCOPE
Confirm Windows requirements and the product version being evaluated.
List the workspace, permitted data and allowed tools.
For security work, obtain written asset-owner permission; list permitted actions and stop conditions.
Agree the timeline, spending limit and recovery steps.

DATA BOUNDARY
Name the model and any approved cloud provider.
Record what each connected tool may read, change or send.
Local inference does not make network-connected tools, setup or updates offline.

ACCEPTANCE CRITERIA
Engineering: a readable patch, repeatable checks and a named review decision.
Security: reproducible findings, risk prioritisation, a proposed fix and regression checks.
Support: source-checked answers, recorded uncertainty and a human escalation path.

EVIDENCE
Product version and model/provider:
Task inputs and expected result:
Setup and completion time:
Output quality and checks run:
Tool approvals and provider cost:
Failures, recovery and unresolved issues:

DECISION
Compare with the existing workflow on the same task.
Record proceed, revise or stop, with evidence.
Agree deployment requirements, ownership, licensing and support terms before expansion.

PriestAI is a Windows beta. This proposed evaluation scope is not a quote,
certification, service commitment or production approval.
Do not include credentials, source code or customer data in an initial enquiry.

Product and data terms: https://priest.locker/terms/
Contact: support@priest.locker