Control Module - FIRE

FV-Relay. A path that exists only for the work.

Relay turns access from a permanent state into a temporary, purposeful event. A connection exists for the work that needs it, under the conditions that suit it, for the window it requires, and then it does not.

Time-bound

Every connection has a defined start and end

Purposeful

Each path is opened for a specific, recorded reason

Conditional

Opening depends on identity, approval and state

Self-closing

Windows end automatically, no manual cleanup

"Relay made vendor access a calendar entry rather than a standing arrangement."

Defined windows

Every Relay session has an explicit start time and end time, with the end enforced automatically.

Purpose-bound

Sessions are tied to a named purpose, owner and scope rather than to a generic always-on tunnel.

Approval-gated

Opening a path requires the right approval pattern for that path, not just the requester's intent.

Scoped reach

Sessions reach only the systems the work requires, not the wider zone they happen to traverse.

Self-closing

When the window ends, the path closes. There is no manual cleanup to remember and nothing left for someone to discover later.

Evidential record

Each session is recorded through Archive, including who requested it, who approved it and what occurred.

Step 1

Identify standing paths

Inventory the connections that are currently always-on and categorise them by who they serve and why.

Step 2

Design the sessions

Define the purposes, owners, approval patterns and acceptable windows for each category.

Step 3

Pilot with one workflow

Move a single standing path to a Relay session pattern, including the calendar, approval and evidential pieces.

Step 4

Decommission the rest

Migrate remaining standing access onto Relay sessions and close the persistent paths.