@@ -30,7 +30,7 @@ I. Canonical Permission Model
3030=============================
3131
3232Normalize all checks to Subject-Action-Object-Context (S-A-O-C)
33- ----------------------------------------------------------------
33+ ---------------------------------------------------------------
3434* We express authorization as: is **Subject ** allowed to do **Action ** on **Object ** under **Context **?
3535* This normalization is used in policies, code, queries, and audits.
3636* Examples:
@@ -98,7 +98,7 @@ Use centralized enforcement
9898* In both cases, services must not embed authorization logic directly.
9999
100100VI. Engines and Integration
101- ============================
101+ ===========================
102102
103103Use proven frameworks with ABAC support and an adapter
104104------------------------------------------------------
@@ -117,7 +117,7 @@ Use proven frameworks with ABAC support and an adapter
117117 - Ensures consistent logging and decision tracing.
118118
119119VII. Extensibility
120- ===================
120+ ==================
121121
122122Make roles, permissions, and resources pluggable
123123------------------------------------------------
@@ -130,7 +130,7 @@ Make roles, permissions, and resources pluggable
130130* Applications must keep calling the same consistent check (e.g., *can(subject, action, object) *), while the schema or policy evolves underneath.
131131
132132VIII. Auditability
133- =================
133+ ==================
134134
135135Make all decisions explainable
136136------------------------------
0 commit comments