Utility Brook

Utility Brook

Engagement path

How a Utility Brook consultation moves from first note to findings workshop — so your team knows what to expect before access begins.

Secure code review and hardening advisory work best when both sides know the sequence. This page is the map we use with clients in Taiwan and remote teams elsewhere.

The path

  1. Inquiry You write with release timing, repositories, and concerns. We ask clarifying questions — we do not auto-book calendars without scope.
  2. Proposal You receive a written scope: surfaces in, surfaces out, timeline, fee, and access requirements. Accept in writing to proceed.
  3. Access & freeze You grant read access, provide staging notes if agreed, and optionally freeze feature merges on reviewed branches for the window.
  4. Review window Reviewers work the agreed days. We may ask short clarifying questions; we do not expand scope silently.
  5. Report & workshop The findings document arrives before the workshop. We walk severities, debate false positives, and help you sequence fixes.
  6. Optional hardening If you want pairing on remediations or a re-check, we schedule Application Hardening Advisory as a separate scope.

What we need from you

A technical owner who answers within one business day, architecture notes (even rough), and honesty about known fragile areas. Surprises mid-review waste both calendars.

What you should not expect

Guaranteed zero findings. Legal certification. Unlimited retesting inside the original fee. If residual risk remains, we name it.

Natural next actions