Duality Lab — James C. Davis

Industry case studies

ReconstructionGitLab · software / DevSecOps platform

MAGE did not run at this company. This page reads an independent practitioner report through MAGE’s vocabulary, to see how cleanly an outside system maps onto the theory. Every correspondence below is the book’s reading of the source, never a claim the company makes about MAGE.

These cases are practitioner reports, not replications of MAGE and not causal tests. A correspondence cell states how cleanly the source's described behavior maps onto a MAGE construct as the BOOK reads it — never a claim Cloudflare (or any site) makes about MAGE, and never proof. not-described means the SOURCE is silent; absence from a report is NOT evidence the company lacks the practice.

Meet the case

GitLab documents how customer instructions enter agent workflows and how identity, tool permissions, and CI checks limit their authority.

Distinctive starting point: customer instructions bounded by identity, permissions, and project checks

What the case shows

The documentation makes several authority boundaries explicit. It does not establish deployment prevalence or the effectiveness of every configured check.

What the agents do

Agents use customer-provided context and tools within configured permissions; the security-review agent produces findings without authority to approve a change.

Setting: · not specified

The engineered environment

Object territory

source-code policies

Representations

informal-knowledge tests

Mechanisms observed

constrained-api merge-gate

Where authority sits

Composite identity limits permissions to the intersection of the human and service account. Group-level tool restrictions constrain project settings; the security-review agent cannot approve a change.

Mapping into MAGE

Each row is one MAGE construct, the strength of the correspondence, and how the book reads the source against it. The note is the book’s reading; the strength is not a score.

Construct and proposition correspondences for this account have not been assessed. An unassessed entry does not mean that its sources lack the mechanism.

What the case adds to MAGE

—

What MAGE adds that this case does not reach

Honest bounds

The limitations the analysis records, and the theoretical propositions whose components the case bears on:

Public documentation and interested engineering reports describe particular workflows; they do not independently establish general effectiveness.

—

Source

FieldValue
Citationgitlab2026customize
Source typevendor-report
Independencevendor-aligned
Account typearchitectural
Evidence horizon
Author roleGitLab product documentation and engineering playbook

Sources used in the current chapter account:

gitlab2026customize gitlab2026identity gitlab2026playbook gitlab2026securityreview gitlab2026toolgovernance

Theory coverage at a glance

Where the source’s described behavior maps onto each MAGE construct: ✓ strong · ◐ partial · ~ tension · ✗ counterexample · — not described.

MAGE constructCorrespondence
Alignmentunassessed
Modelingunassessed
Knowledge repunassessed
Bootstrapunassessed
Conversionunassessed
Determinizationunassessed
Reasoning horizonunassessed
Engineer's seatunassessed
Graduated governanceunassessed