# The Systems Pavilion — Platform & Internal Operations

Canonical HTML: https://brendan-davies.dev/platform-internal-ops/

This Markdown companion summarises the public HTML page. It is a worked example of platform and internal-operations judgement — hypothetical category-level practice, not documentation of a named employer.

## Role

Platform & Internal Operations.

## Exhibition

THE SYSTEMS PAVILION — infrastructure as architecture; workflows as installations.

Public room: The Desk.

## Patterns seen before

Shared inbox → queue ownership. Underwriting → risk and decision state. Enterprise SaaS → knowledge and handoff drift. Studio → scope and evidence. The technology changed; the work still needs a visible state, a next action and someone accountable for it.

## The Desk

Commercial Operations & Internal Tooling.

Thought: Internal tools are products.

Standard path: Enquiry → Assist → Identify → Enrich → Route → Owner → Reply / Action → Audit.

Needs review: Enquiry → Assist → Identify → Enrich → Route → Review → Owner.

Assist suggests. An owner remains accountable. Assist is not owner.

One enquiry: assist classifies and drafts → named owner checks the draft → action → audit record. Rejected: automatically send every generated reply; generation is not ownership. Measurement design: time to first owner touch, queue age, unowned items; sends without owner approval target zero.

## Build / buy / prompt

Prompt extraction, classification, drafting, anomaly suggestions and owner routing; the consequential write remains owned. Buy mature payment rails, identity-verification vendors, CRM and commodity infrastructure. Build workflow orchestration, audit history, ownership, custom policy, state boundaries and data contracts where the operating model is the product.

## Themes

Internal tools as products; operations and product translation; risk; named human review; AI assistance with a named owner.

## Contact

https://www.linkedin.com/in/brendan-davies/

## Challenge before commit

Start with the real problem, constraints and outcome. Models explore alternatives, challenge assumptions and cross-review answers. A synthesis pass produces one candidate plan with assumptions and failure modes to check against tests, source evidence or human review. Providers can change; Brendan remains responsible for the decision and commit. Assist suggests. Evidence challenges. A person commits.

## Blueprint

[See the same operating principles applied to a two-sided marketplace.](/blueprint/) An independent design exercise.

[Agents: persistent memory, permissions and owner gates.](/agents/)