# Final Packet Manifest Template

Use this manifest as the final inventory for a reviewable RFC packet. List public deliverables and evidence artifacts separately so a maintainer can audit what is publishable versus what remains proof material.

## Packet metadata

| Field | Value |
| --- | --- |
| Packet ID | `PKT-YYYYMMDD-01` |
| Packet Date | `YYYY-MM-DD` |
| Owner | `<owner>` |
| Draft Version | `<version-or-digest>` |
| Evidence Version | `<version-or-digest>` |
| Overall Status | `<ready | ready-with-notes | blocked | superseded>` |

## Public files

| File ID | Path | Title | Status | Claim Coverage Ref | Capability Coverage Ref | Example Coverage Ref |
| --- | --- | --- | --- | --- | --- | --- |
| `PUB-0001` | `<path>` | `<title>` | `included` | `<claim-ref>` | `<cap-ref>` | `<example-ref-or-none>` |

## Evidence files

| Evidence ID | Path | Kind | Supports | Required for Publication | Status |
| --- | --- | --- | --- | --- | --- |
| `EVD-0001` | `<path>` | `claim-ledger` | `PUB-0001` | `yes` | `included` |

## Deferred or excluded items

| Item ID | Kind | Reason | Risk | Approval Ref |
| --- | --- | --- | --- | --- |
| `EXCL-0001` | `escalation` | `<reason>` | `low` | `<approval-or-none>` |

## Integrity checks

| Check | Required Result | Actual Result | Evidence Ref | Notes |
| --- | --- | --- | --- | --- |
| Every included public file exists and is current. | Yes | `<pass/fail>` | `<VAL-ref>` | `<notes>` |
| Every public file has claim and capability coverage. | Yes | `<pass/fail>` | `<VAL-ref>` | `<notes>` |
| Required evidence files are present. | Yes | `<pass/fail>` | `<VAL-ref>` | `<notes>` |
| No undispositioned blocker remains. | Yes | `<pass/fail>` | `<VAL-or-ESC-ref>` | `<notes>` |

## Handoff summary

| Field | Value |
| --- | --- |
| Public files included | `<count/list>` |
| Evidence files included | `<count/list>` |
| Deferred items | `<count/list-or-none>` |
| Validation report | `<ref>` |
| Packet ready for review? | `<yes/no>` |