platform self serviceself-service platformplatform product modelenable shift constrain

Organisation

Platform Self-Service

Cross-cutting functions scale as platform products — enable teams, shift work, constrain in software

MARKO ŽIVKOVIĆ In review

Platform self-service is how cross-cutting functions — security, architecture, compliance, ethics, shared infrastructure — scale as platform products instead of ticket queues. Introduction: One Authority Per Invariant — At Scale.

A platform in this corpus does three jobs at once:

Job	Meaning
Enable	Product teams get capability they could not safely build alone — APIs, policy engines, conformance checks, shared writers for invariant binds
Shift work	Operational burden moves to product teams inside the contour — they configure, deploy, and commit; the platform team owns the product, not every transaction
Constrain	In-set mistakes are structurally impossible or automatically rejected in software — not caught later by a human reviewer who should have been in the loop

Enablement and constraint are the same artefact: platform guardrails shipped as evaluable software.

Traditional function vs platform product

	Traditional function	Platform product (self-service)
Scaling model	Hire reviewers ∝ product teams	Ship policy engines, APIs, shared writers
Security example	Approve each firewall rule	Rules encoded; system checks; teams add in-set rules without human review
Architecture example	Review board on every change	Published contours + automated conformance; (A)DR on out-of-set only
Compliance example	Analyst on every case	Screening engine + thresholds; human on exceptions
Ethics example	Board reviews each feature or release	Ethics contours encoded — dark-pattern checks, consent/surveillance boundaries, values-aligned gates; ship in-set without ticket per launch; ethics owns contour and novel-harm exceptions
Platform team role	Gatekeepers	Product owners of enable + constrain

Self-service is not absence of authority. The platform domain remains single writer for the cross-cutting invariant and for contour definition (single writer principle). Product teams self-serve inside committed rules; they do not reimplement compliance locally or bypass the commitment boundary.

Relation to reservation and async binds

Reservation removes synchronous blocking at the commitment boundary — Phase 1 proceeds while platform checks run. Platform self-service removes per-case tickets for the in-set — most actions never enter a human queue because the platform product already decided what is allowed. Both are required at scale; neither replaces the other.

Out-of-set cases still use reservation, recorded delegation, or human platform binds — with full decision-making principles where stakes require.

Corpus stance

A2 — working context: Vocabulary for how platform teams should build; paired with platform guardrails and the platform self-service guardrails pattern. Counterpart anti-pattern: point approval governance.