Re-running Analysis

## Re-running Analysis

Re-running analysis is how SyntaxValid verifies change.

Fixes, refactors, or policy updates only affect results after a new analysis run confirms them.

---

## Why re-running analysis matters

SyntaxValid results are always tied to a specific code snapshot.

This means:

- Fixing code alone does not update results

- TrustScore reflects only verified states

- Merge readiness is restored only after confirmation

Re-running analysis ensures accuracy and accountability.

---

## When should you re-run analysis?

Re-run analysis when:

- Blocking issues have been fixed

- High-severity risks are addressed

- Fix with AI patches are applied

- Significant refactors are completed

- Policies or severity thresholds change

Re-analysis confirms whether risk is truly reduced.

---

## What happens during re-analysis?

During a re-run:

1. A new code snapshot is created

2. Relevant rules are executed again

3. Policies are re-applied

4. Issues are re-evaluated

5. TrustScore is recalculated

Each run is independent and traceable.

---

## Full analysis vs diff analysis

### Full analysis

- Scans the entire repository

- Best for major changes or baseline checks

- Provides the most comprehensive signal

### Diff analysis

- Scans only changed files

- Faster and focused

- Ideal for pull requests and incremental fixes

Choose the analysis type based on scope.

---

## Re-running analysis and TrustScore

TrustScore changes only after verification.

- Fixed but unverified issues still affect TrustScore

- Verified fixes restore TrustScore immediately

- Blocking status updates reflect policy compliance

TrustScore always represents the latest verified snapshot.

---

## Common misconceptions

- Re-running analysis does not auto-fix issues

- TrustScore does not change without verification

- Closing an issue manually does not update results

Verification requires analysis.

---

## Best practices

- Re-run analysis after every blocking fix

- Use diff analysis for quick validation

- Use full analysis periodically for baseline accuracy

- Avoid stacking unverified fixes

Consistent re-analysis builds trust.

---

## Next steps

- Policies and rules

- GitHub and IDE integrations

- Using SyntaxValid in team workflows