Use casesRun the NOC

A fix is waiting on you. Approve it, hold it, or roll it back.

NetPulse proposes and you decide. Every recommendation carries its reason, a rollback plan and a blast radius, and every decision lands in a ledger. This is how to read one quickly and decide.

  • Timeabout 10 minutes
  • ForNetwork lead, NOC engineer, Security analyst
  • ScreensGoverned Brain, Accuracy, Remediation

Recognize it

You’re here if

  • An incident shows a remediation waiting for approval.
  • You are asked whether a change is safe to make.
  • An auditor asks who approved what, and why.

Do this

5 steps, in order

  1. Open the incident and read the ledger

    Open Governed Brain and select the incident. Read the decision ledger from the top.

    Open Governed Brain
    Look for
    Every decision NetPulse took, in order, each with its reason and confidence.
    What it means
    If the reasoning does not hold up, stop. You do not have to approve a fix you cannot explain.
  2. Check the call before you trust it

    Open Accuracy and read how often the root-cause call has been right for this kind of incident.

    Open Accuracy
    Look for
    A measured rate, by difficulty and by entity type.
    What it means
    An incident class where it is often wrong needs a human to confirm the cause first.
  3. Read the action, rollback and blast radius

    Open Remediation. For the action, read what it does, whether it can be reversed, and how many entities it touches.

    Open Remediation
    Look for
    An action, a rollback plan and a bounded scope.
    What it means
    No rollback plan means it stays recommend-only. A very large scope means it needs a named approver.
  4. Approve or hold

    Approve it, or hold it with a reason.

    Open Remediation
    Look for
    The run moving to approved or staying pending.
    What it means
    A held fix stays on the ledger with your reason.
  5. Confirm it worked

    After the action, check the verification against the same condition that fired the alert.

    Open Remediation
    Look for
    The original alarm clearing, or an automatic rollback if it did not.
    What it means
    Unverified means unfinished. Do not close the incident on the action alone.

Then decide

What you found decides what you do

  • IfNo rollback plan, or class accuracy is low

    ThenRecommend-only. Do it by hand with your own change process.

  • IfReversible, bounded, accuracy proven for the class

    ThenApprove, then verify.

  • IfThe same class has been approved and verified many times

    ThenIt may qualify for earned autonomy. Review the tiers.

Watch out

Where this goes wrong

  • Every approval, hold and verification is recorded. Connect your change tooling so approved fixes can be applied directly; until then, take the recommendation into your own change process.
  • Autonomy is earned per playbook and per incident class, and it reverts on a regression.
You’re done when

You have approved or held with a reason, and the result is verified or rolled back.