https://deevnet.github.io/deevnet-docs/docs/runbook/substrate/incident-management/Recent content in Incident Management on Deevnet IoTaaSHugoen-ushttps://deevnet.github.io/deevnet-docs/docs/runbook/substrate/incident-management/incident-record-template/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-docs/docs/runbook/substrate/incident-management/incident-record-template/<h1 id="incident-record-template-inc"> Incident Record Template (INC) <a class="anchor" href="#incident-record-template-inc">#</a> </h1> <p>The shape every <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/incidents/">incident record</a> takes. Copy the skeleton below into <code>content/docs/incidents/&lt;YYYY&gt;/&lt;NNNN&gt;-&lt;slug&gt;.md</code>, numbered with the next unused <code>INC-NNNN</code> — global across years and never reused, like ADRs. Its <code>weight</code> is <code>-NNNN</code>, so the newest sorts first, and its row goes at the <strong>top</strong> of <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/incidents/">Incident Records</a> and of that year&rsquo;s page. <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/incidents/2026/0001-firewall-policy-deletion/">INC-0001: Firewall Policy Deleted, Total Connectivity Loss</a> is a worked example.</p> <p>Start the record while the incident is fresh, even with most sections empty. The timeline and the wrong turns are the parts memory loses first.</p>