Permissions belong in the assembly context
Someone moves off the finance team at 9 a.m. on a Monday. Your sync runs nightly at 2 a.m. For The post Permissions belong in the assembly context appeared first on The New Stack .
Permissions must be integrated into the assembly context, not applied as a filter after the context has been assembled. This is because assembly is the final stage where refusing to include certain information still ensures the model hasn't encountered it. The major platform vendors in the market are developing a similar concept, but there is no consensus on a specific term for it.
In Modus, this concept is referred to as context composition, but I will use the term context assembly. The assembly process determines which pieces of enterprise knowledge a model receives for a particular individual, at a specific time, for a specific question. Upstream storage and downstream inference are where the data resides, but it is during assembly that identity either exists or does not.
While the term "permissions" is often used as a filter, it should actually be a fundamental property of how context is constructed for a specific identity, since assembly is the last opportunity to exclude something before the model processes it.
Written by urgent.news from The New Stack's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
