---
type: Concept
title: "The two archetypes"
description: "The composite stack and the governed path: two ways to build a connected building system, with very different custody stories. No vendors named."
tags: [thesis, archetypes, architecture]
generated: { by: claude-code/opus-5.5, at: "2026-10-09T00:00:00Z" }
status: stable
sources:
  - id: prototype
    resource: "https://github.com/DavidJCrawford/stewardship-explorer/blob/main/brain/concepts/the-two-archetypes.md"
    title: "stewardship-explorer brain: The Two Archetypes"
  - id: article
    resource: /thesis/the-article.md
    title: "Data collection and the value of control"
---

# The composite stack

Assembled from parts. "A reader from one maker passes data to a controller from
a second, then to a third party's head-end, then to a fourth's cloud."[^article]
It offers real choice and real interoperability. But every assembled element is
a [seam](/thesis/custody-seams.md), the data path crosses parties the customer
never chose, and a Data Act request lands on a stack with no single party who
can answer it.

# The governed path

"Fewer hands, a single system of record, one governed path from the edge to the
head-end."[^article] One organisation designs, makes and runs the chain from the
reader to the head-end, and usually the hosted service above it. The
manufacturer, data-holder and related-service roles fall on one company, so
the customer has one place to ask.

It is not seamless all the way up. A governed path typically runs its cloud on
a hosting provider, and the customer may send data on to anyone they choose.
Those seams are fewer, contracted and visible. That is the claim, and the
[ledger](/thesis/copies-and-hands.md) shows it rather than asserting zero.

It also [leaves things alone](/thesis/leave-it-alone.md): the most sensitive
streams stay on site, under the customer's control.

# The honest trade-off

Full-stack systems have historically meant lock-in, and openness protected
customers from it. The Data Act ended that trade: data access and portability
are now law whatever the architecture. The fair comparison since 12 September
2025 is **governed custody with exits guaranteed by law** against **custody
with seams and the same exits**. See [Openness is the floor](/thesis/openness-is-the-floor.md).

> Both architectures now owe the customer open doors. Only one can answer for
> everything behind them.

# A precedent everyone knows

Consumer electronics already showed the pattern: vertical integration from
silicon to services is what made an on-device privacy promise believable,
because one party could answer for the whole chain. One aside, never a theme;
no brand is named on the site.

# On the site

The trace plays either archetype on the same building. The switch changes who
holds each hop and the ledger's counts; it never changes the rights, because
the law is the same for both.

[^article]: Data collection and the value of control