# Ashoon pilot evaluation

Suggested scope: 5–10 participants, two weeks, one team, approved sources.
This is an evaluation worksheet, not a trial offer or commercial commitment.
Agree access, any allowance and support with your rollout contact before installation.
Keep this file in your own approved workspace; do not include credentials or private admin links.

## Decide before starting

- Owner:
- Participants (use pseudonyms):
- Start / end dates:
- Connected sources and approved content:
- Allowed destinations:
- Useful-answer target:
- Acceptable checking/correction time:
- Usage allowance and stop conditions:
- Who investigates problems:

## Three jobs to evaluate

1. Ask a current policy question and open the cited source. Ask an undocumented question and check that missing evidence is acknowledged.
2. Ask about a real ticket and linked pull request. Compare blockers and owners with the tools. Have a person without repository access check the same question.
3. Summarize a real thread and draft a follow-up. Verify decisions and owners against the messages; review exact content and destination before approval.

## Record one row per attempt

| Date | Person | Job | Useful: yes/partly/no | Sources support answer? | Checking/correction minutes | Old workflow minutes | Access issue? | Follow-up needed |
|---|---|---|---|---|---|---|---|---|
| | | | | | | | | |

Any unauthorized disclosure stops the pilot until it is investigated and fixed.

## Decide after two weeks

- Attempts and useful answers per job:
- People who returned in week two without a reminder:
- Unsupported claims and examples:
- Checking/correction time compared with the old workflow:
- Access problems (over-restricted or disclosed):
- Setup time and admin assistance:
- Usage and support required:
- Continue / change / stop, and why:

Report only observed results. Obtain consent before using customer names or quotations publicly.