The application a project team sees is only one layer. Brian Platz explained in 2018 that most applications also rely on an application layer and a database beneath it. His database discussion is useful because it moves data governance below the dashboard.
The visible screen can look shared while control, meaning, permissions, and history remain fragmented underneath it.
Shared visibility is not the same as shared control
Brian described a common arrangement in which one organization controls the main dataset while other participants receive access or audit rights. He contrasted that model with a shared database maintained by multiple participating organizations.
The distinction is about stewardship: a participant can see a record and still depend on another organization to preserve, interpret, or change the canonical version.
Meaning can drift while the data moves
In the construction portion of the episode, a shipping term could refer to movement between a yard, plant, storage location, or jobsite. Brian Platz compared that kind of vocabulary drift to the game of telephone.
A common source does not remove every disagreement. It can give participants one place to define the identifier or term being used so the next handoff does not depend on a fresh translation.
Permission rules belong close to the record
Brian said access logic was often repeated across many applications. In the architecture he described, permissions were stored with the data: “The data is secured at the source.”
That was Fluree's 2018 product approach, not a universal database rule. The broader governance question is whether permission decisions remain consistent when several applications use the same record.
History matters when the current screen is no longer enough
Brian also described retrieving what a database showed at an earlier point in time without overwriting the permanent history. He connected that capability to audits and the effort required to understand what happened during a dispute.
Choose one record that moves through several applications and trace its control, vocabulary, permission rule, and prior state. That review keeps the team focused on the record people must trust, not only the interface they happen to use today.
