officeStructure
What an office is and may do
definition`: establishment, title, seat count, seat of the office · `powers`: mandate, competences, signing authority
This meta-model describes public offices as durable positions of authority and the people who hold them: how an office is established and empowered, how a person is appointed or seated into it, how tenure runs and ends, and the accountability instruments (oaths, declarations, integrity rules) that attach to holding it. It is its own model because an office outlives any holder and any single administration, and because the office register is the reference point that lawmaking (A10), elections (A13), permitting (A14) and enforcement (A18) all resolve officeholders against.
What an office is and may do
definition`: establishment, title, seat count, seat of the office · `powers`: mandate, competences, signing authority
Who holds an office and when
appointment`: acts of appointing or seating a person · `termAndSuccession`: terms, vacancies, acting arrangements
Duties that attach to holding office
declaration`: asset and interest declarations of holders · `integrityRules`: incompatibilities, recusal duties, sanctions
Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.
Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.
Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.
CRUD procedures and interface bindings are not declared in this legacy version.
The appointing authority for each office family acts as registrar of this model; the register itself is public per its A12 mandate. Declarations and other graded layers are opened only by owner grant through S1 ownership and S2 access rules.