Does permitted work finish?
Confirm that an allowed action completes and that the resulting change matches the agreed task. Record errors, interruptions and time spent reviewing it.
PLAN A LIMITED PRODUCT TEST
Choose one task or investigation question. Write down what a useful result would look like, what the product may use and when the test should stop. The planner helps you prepare that discussion; Praxenor must confirm the available build and setup before testing.
Proposed test. Product in development. Availability and setup must be agreed first.
PLAN A USEFUL EVALUATION
Write a proposed test for Agent Defender or Swarm Hunter. Review the exact build, available setup and suitability with Praxenor before testing.
Use only general descriptions. Keep customer records, passwords, access keys and confidential details out of this planner. Your entries stay in this browser page. The planner does not save or submit them.
These are proposed evaluation tracks. A product choice does not confirm availability or connect software.
Confirm the build and configuration before the evaluation. A website version is not a product build.
Keep the scope small enough to review the result and repeat the test.
Suggestions are checks to consider, not passed tests or promised capabilities. Edit them to match the build and agreed setup. Include fresh ordinary cases and fresh cases with a known expected result.
State what will be counted or reviewed, using which cases and reference. Agree targets before the test. No target is supplied by this planner.
Confirm the responsible person before an evaluation begins.
Choose a product and complete the required fields. Nothing runs or connects through this planner.
Review the plan and agree the setup before testing. The plan is guidance. It grants no access and installs or executes nothing.
Keep any downloaded file in an approved location. These downloads contain your entries. Nothing is sent to Praxenor.
Prefer a blank document? Download the existing planning worksheet. The worksheet and planner are guidance, not test results. Copy or download your entries before leaving this page.
AGENT DEFENDER / PROPOSED ACTION CHECKS
Choose one harmless task in a disposable environment. Identify the action, the permission given and the exact point where the tool sends the action through the check. Actions outside that connection are outside coverage.
Confirm that an allowed action completes and that the resulting change matches the agreed task. Record errors, interruptions and time spent reviewing it.
Propose an action outside the permission and inspect whether it pauses or is refused. Check changed or replayed approvals and what happens when a required check is unavailable.
Keep the request, permission, decision, reason and actual effect together. Compare the saved record with the task and the disposable environment, then confirm recovery steps.
These are proposed evaluation questions. The dated pilot describes a limited local practice project, not broad protection or an email integration. Availability, supported actions and the exact build must be confirmed before a test.
Inspect Agent Defender’s dated evidenceSWARM HUNTER / PROPOSED INVESTIGATION REVIEW
Choose one question and a small sample of activity records you’re allowed to use. Start with an example, then agree on a sample for the test. Make sure everyone knows where the records came from and what’s missing.
Add supported records, review related events, write down your assessment and save the case. Check that the saved or exported copy keeps the information you need.
The test won’t provide automatic blocking or complete monitoring, and it won’t prove that AI caused an event. A missing warning doesn’t mean the activity is safe.
FROM RECORDS TO A REVIEW
The October 4 status review documents local build 0.6.1; the published October 3 brief describes 0.6.0. These are dated records, not confirmation of the build available today. Confirm the exact build and supported inputs before testing.
Read the dated technical briefAGREE BEFORE TESTING
You can find the records behind each finding, see their limits and tell what information is missing.
Save, reopen and export the case. Check that your notes, sources and settings remain intact and the original records do not change.
Use fresh cases that were not used to develop the tool. Count useful findings, false warnings, missed issues, unfinished reviews and the time people spend reviewing them.
Decide what would count as success before seeing the results. Completing the steps does not prove accuracy. Repeating the same fictional example does not create independent evidence.
BEFORE ANY CUSTOMER DATA
Contacting us starts a discussion. It doesn’t sign you up, install software or give us access to your systems. Any test, cost or support arrangement must be agreed first. We don’t publish prices or guarantee a response time here.
Describe the question, the kind of records available and the result you need. Leave out passwords, private records, customer information and suspicious files.
Start the evaluation discussion