Software Analysis Intake Template

AXIOM Analysis

Software Analysis Intake Template

Version 1.0 | April 12, 2026
Working template for structured software runs in the AXIOM portal.

Purpose

Use this template to prepare a software analysis run in AXIOM.

It is designed for:

This is a structured analysis intake, not a substitute for full engineering review, security testing, or production sign-off.

Best AXIOM Settings

Code / Change Review

Use this when the main goal is to examine:

Architecture Review

Use this when the main goal is to examine:

Combined Technical Review

Use this when you want the broadest decision-support pass across code and structure.

Quick Triage Only

Use this only for a rapid first-pass scan, not your best final review.

Important Input Note

For the cleanest current behavior:

Best current upload shape:

You do not need all five files for every run.

For first tests, do one of these:

  1. Paste the full technical material directly into the request box and upload nothing.
  2. Upload the material files and use the short prompt file only.

Do not duplicate the entire same code/context in both places unless you have a reason to.

Data Collection Checklist

Collect as much of the following as possible before running the analysis.

1. Run Basics

2. System Basics

3. Review Goal

4. Scope Definition

Collect:

5. Expected Behavior

Collect:

6. Code / Change Evidence

For each important change or code area, collect:

7. Architecture Context

Collect:

8. Risk Set

Collect the strongest known risks:

9. Validation Material

Collect:

10. Environment / Runtime Assumptions

Collect:

11. Known Weak Spots

List anything already suspected:

12. Source Map

Separate clearly:

This is one of the most important quality steps. Do not mix them together.

13. Missing Inputs

List what is not yet known:

14. Output Goal

What should the AXIOM report help you do?

Suggested File Pack

File 1: 01_request.md

Use this for the decision context:

System / project name:
Run type:
Decision to support:

Top questions:
1.
2.
3.

Known constraints:

Known uncertainties:

File 2: 02_system_context.md

Use this for the basic system picture:

System overview:

Main components:

Languages / frameworks:

Runtime / deployment context:

Expected behavior:

File 3: 03_code_or_change_scope.md

Use this for the review target:

Files / modules in scope:

What changed:

Behavioral change intended:

Known concerns:

File 4: 04_architecture_and_runtime.md

Use this for structure and interfaces:

Component boundaries:

Data / control flow:

Dependencies:

Runtime assumptions:

Stress points already suspected:

File 5: 05_logs_tests_and_risks.md

Use this for evidence and validation:

Logs / traces:

Tests present:

Tests missing:

Risks:

Open questions:

Fill-In Intake Block

Copy this block into a working .md file and complete it.

System / project name:
Run type:
Prepared by:
Prepared on:

Decision to support:

Primary review questions:
1.
2.
3.

Product / service:
Languages:
Frameworks:
Runtime / platform:
Environment:
Team / ownership:
Delivery stage:

What is being reviewed:
Why now:
What changed:
What worries us most:
What would make this unsafe to ship:

Scope:

Expected behavior:

Observed behavior:

Code / change evidence:

Architecture context:

Validation material:

Key risks:

Runtime assumptions:

Known weak spots:

Source map:

Missing information:

What a useful AXIOM output should focus on:

Use this template together with:

Best pattern:

  1. fill out this intake
  2. upload this intake plus the actual technical material
  3. use the short prompt file in the portal request box

Practical Notes For Better Results

Caution

AXIOM can help surface:

It should not be treated as a full security audit, full performance benchmark, or final production sign-off.

End of Software Analysis Intake Template v1.0