# Boundary Notes Template

Use this template when a dedicated `Limitations` section is too heavy or too venue-specific.

You can surface these notes in any of the following places:

- a short `Discussion / Scope Note` section
- a caveat paragraph at the end of `Main Results`
- a boundary paragraph in `Conclusion`
- a standalone drafting file such as `paper/boundary_notes.md`

Suggested structure:

```md
# Boundary Notes

## Supported Today
- State the strongest supported claim.

## Not Claimed
- State the stronger claim that is intentionally not made.

## Evidence Boundary
- Name whether the evidence is simulator, local runtime, or runtime.

## Validation Gaps
- List the smallest missing validations that prevent stronger wording.
```

Writing rules:

- Keep this concrete and artifact-specific.
- Prefer a short, sharp boundary note over a generic limitations section.
- If the manuscript already has a natural home for caveats, fold these points there instead of forcing a dedicated section.