Section 5.17 · server-side enforcement

Approval gate

Nothing leaves the platform without a recorded approval. The gate is enforced on the server, so hiding a button or calling the endpoint directly makes no difference to the outcome.

Back to dashboard

The button state is a courtesy. The check is server-side. A disabled control in this interface is a hint about what will happen, not the mechanism that stops it. Every gated action re-evaluates the approval record on the server at the moment of the request, and refuses without one.

Awaiting approval

Across the pipeline

Approved today

Both analyst level

Rejected today

Reason recorded

Blocked attempts

Refused server-side, logged

Northgate Facilities Services Ltd

Stage

Stage 2 complete, awaiting release approval

Quality score

72 of 100

Recommendation

Attractive only below £1,740,000

Distress signals

None detected in the eight implemented checks

Open gaps

4 outstanding

Required approval level

Analyst, with operator counter-signature because an override is present

Gated action	Requires	State	Control
Release Stage 1 deck internally	Analyst	Approved k.patel, 22 Aug 2026 14:02	Open deck
Release Stage 2 report internally	Analyst	Pending Requested 23 Aug 2026 09:16
Export PDF investment report	Analyst, after Stage 2 release	Blocked Upstream approval missing
Send to a party outside the platform	Operator	Blocked No operator approval on record
Contact the vendor or broker	Operator, explicit per-contact	Blocked Outbound contact is never automated
Enable a public_web source adapter	Operator, plus a signed AUTHORISATION record	Hard stop Authorisation record unsigned	View sources

Approval request

Action Approver Reason for request

I have read the four open gaps and accept that the analysis is incomplete without them

I have reviewed the one mandate criteria override on owner independence and its recorded reason

Both acknowledgements are stored with the request. An approval given without them is not accepted by the server.

Audit trail

When	Event	Actor
23 Aug 09:41	PDF export attempted, refused, upstream approval missing	k.patel
23 Aug 09:16	Stage 2 release requested	k.patel
23 Aug 08:55	Mandate criteria override recorded on owner independence, reason supplied	k.patel
22 Aug 16:30	Direct API call to export endpoint refused, no approval token	service account
22 Aug 14:02	Stage 1 deck release approved	k.patel
22 Aug 13:47	Quality score computed, 72	platform
22 Aug 13:44	Entity resolved to company 09912345, confidence high	platform

The trail is append-only. Entries are never edited or removed, including refused attempts, which are the entries most worth keeping.

Rules the gate enforces

No document leaves the platform without an approval recorded against that document version.
Re-generating a document invalidates its approval. The new version is approved on its own merits.
An approval names the approver, the action, the version, the timestamp and the acknowledgements given.
Approving your own request is permitted only at analyst level, and only when no override is present.

Any outbound contact with a vendor, broker or adviser is operator level and per-contact. It is never batched or scheduled.
Enabling a source adapter with a public_web basis requires a signed authorisation record, not an approval click.
A refused attempt is logged with the same detail as a successful one.
The interface never holds the only copy of the rule. Removing the gate from the front end changes nothing.

AcquiScope produces analysis and modelling, not regulated investment advice. The names, timestamps and events shown here are invented for the prototype.