Playbook Post Submission Follow Up

Post-Submission Follow-Up

This page is explanatory. The canonical workflow is docs/submission-followup.md.

Objective

Track submitted reports, preserve context, and prepare response-ready triage fragments.

Inputs

• submitted reports or tracker
• local drafts, sent packs, or gate notes
• known triage state

SMEs involved

Usually chief-of-staff, the original SME when needed, and security-qa if a follow-up response materially changes the claim.

Flow

1. load tracker state
2. recover verifiable metadata
3. separate grounded traceability from admin gaps
4. write follow-up tracker
5. prepare short response fragments

Gates

• do not invent report IDs or URLs
• label missing metadata explicitly
• avoid reopening the hunting lane unless new evidence requires it

Outputs

• tracker
• response-ready follow-up fragments
• next-step priority order

Limitations

Local artifact timestamps are not automatically submission timestamps.

Sanitized example

Prepare short responses for likely objections such as “works as documented” or “local crash only.”