[ T-07 // TRACK ]
GOVERNANCE
Markings and access control. Pairs with Academy playlist 4.
- [ FM-GV-01 ]
Markings and Access Control: When the Ontology Becomes the Access Boundary
We moved governance from theory to a working control on the FM-ON-01 Work Order type: built its first object security policy, a granular rule Asset Type is equal to pump, saved it to the branch past a first-time reindex warning, and proved it in the Test policies simulator before it touched a single user. A custom object with Asset Type pump passes with a green check and every property visible; the same object set to turbine is denied with a red X and every property red. The doctrinal spine is one sentence buried in a dialog callout, quoted verbatim: with an object security policy, users no longer need viewer access on the backing datasource to see object instances, so the ontology becomes the access boundary. We mapped both sides of that boundary, datasource-side requirements versus policy-side requirements, plus the surrounding surfaces: object type roles and permission cards, the backing dataset work_orders_closed_enriched in Compass, and the project Access requirements panel. Five field repairs, including the fifth branch wall of the series (role editing is disabled on a branch while policy creation is allowed) and the markings wall (a project owner finds zero markings to add; marking creation is org-admin territory).
- [ FM-GV-02 ]
Lineage as an Audit Weapon: Two Audit Trails and the Dataset Boundary
We audited the FM-WS-02 writeback from the lineage side and found the doctrinal spine of Foundry governance: there are two audit trails and they do not overlap. Monocle (Data Lineage) covers data up to the dataset boundary and then stops; asking it for downstream artifacts answers, verbatim, No related artifacts found. Everything past that boundary, ontology objects, Workshop apps, and every object edit, is audited in Ontology Manager: the Datasources tab's Object edits history, verbatim Store object edits history for compliance and traceability. The enriched dataset's tooltip reads up-to-date and its History shows exactly one snapshot transaction from Aug 29 with zero jobs after, while the WS-02 writeback changed objects days later. Dataset freshness says nothing about object-layer state. Then the accidental payoff: on the branch with the FM-GV-01 pump policy active, the Work Order header reads 13 objects instead of 66, and ontology SQL returns exactly one group, n=11, assetType=pump, matching the FM-PB-01 source CSV ground truth of 11 closed pump rows. Header and query disagreed at capture time (13 versus 11, likely reindex lag); trust the query during the reindex window. Six field repairs, including the empty Usage tab that must never be used for impact analysis.