Skip to content

Commit 539f32a

Browse files
committed
fix(policy-schema): fail closed on unsupported fields
Signed-off-by: Johnny Greco <[email protected]>
1 parent b43ece7 commit 539f32a

6 files changed

Lines changed: 174 additions & 316 deletions

File tree

‎architecture/security-policy.md‎

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -34,15 +34,10 @@ path normalization.
3434
Consumers project that syntax into purpose-specific models. `openshell-policy`
3535
owns protobuf conversion, composition, merge behavior, raw-protobuf checks, and
3636
validation that depends on runtime components. The existing prover retains its
37-
risk model but parses with the schema crate's `RuntimeStrict` profile. Maximum
38-
policy containment uses `ContainmentInput`, which retains managed metadata,
39-
review annotations, and unknown closed-object fields so the solver can report
40-
unsupported authority instead of misclassifying it as malformed input.
41-
42-
`RuntimeStrict` requires `version: 1` and rejects managed annotations and every
43-
unknown field. `ContainmentInput` requires the same known field types and
44-
version, but returns unknown field paths and values to the containment support
45-
audit. Middleware `config`, query and persisted-query names, and recursive MCP
37+
risk model but uses the same fail-closed parser as the runtime. The parser
38+
requires `version: 1` and rejects managed annotations and every unknown field
39+
before any consumer-specific projection runs. There is no permissive parsing
40+
profile: unsupported policy fields always invalidate the document. Middleware `config`, query and persisted-query names, and recursive MCP
4641
parameter names are open user-data maps rather than schema extensions.
4742

4843
Before applying Landlock, the supervisor enriches baseline filesystem paths that

0 commit comments

Comments
 (0)