Profile: Read-only current-state
Table of Contents
This page is a named element-scope MASD profile instantiating ORE Studio Variability Model § "Profiles: naming a recurring configuration point". A model file binds to this profile (rather than authoring each feature individually) to guarantee the exact feature combination below, with no ad hoc variation.
1. Purpose
Some tables are written by the system and read by everyone else. A bootstrap record, a derived state row, a projection the application never edits: each is read over the wire and never written through it, and each holds one row per key rather than a history.
Before this profile the two facts were authored per entity, as
:read_only: true and :current_state: true in two different drawers, and
each new model re-decided a combination the codebase had already settled. The
combination is what makes it a profile: ores.iam.login_info set it first,
and the database metadata table and the next such entity need the same
answer.
Binding it is enough. The profile carries both flags through the Assignments
table. read_only reaches the entity root, where wire_write_enabled reads
it, and current_state reaches the SQL namespace, where the table shape is
decided.
2. Reference entity
ores.iam.login_info — login
tracking and security state, one row per account, written by the login flow
and read by the administration surface. Its protocol carries
list_login_info, get_login_info and get_many_login_info, and nothing
else.
3. Assignments
One row per feature this profile fixes a value for — any feature not listed here is left to the model's own choice:
| Feature | Value |
|---|---|
| read_only | true |
| current_state | true |
4. See also
- ORE Studio Variability Model — the model this profile instantiates.
- Variability Profiles — the catalogue of named profiles.