tegwick
33ebda59d4
Canon section 3 defines warden_executes narrowly and adds per-step lane, value_handling and ready_check; catalog entries need a templated body. The type gets lanes, generated-in-custody minting, a Ready gate before bind-env, memberships only from the accepted case, mfa-pinned and secret-delivered checks, and the R4-prime catalog body. 110 tests pass. Memo r3 supersedes r2 and validates on both sides. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 5457@bnt-lap001 Assistant-Session: 792bf84a-3783-4f5d-a811-cded61dd2012 |
||
|---|---|---|
| .. | ||
| tests | ||
| README.md | ||
| security_case_validator.py | ||
security-case-types tools
Validator and renderer for SecurityCaseTypes and SecurityCases
(canon/standards/security-case-types_v0.1.md, schemas
canon/schemas/security-case-type_v0.1.schema.json and
security-case_v0.1.schema.json).
# a type directory: type.yaml, README.md sections, tests, example cases
python3 tools/security-case-types/security_case_validator.py validate-type security-case-types/<type-id>
# a case against its type (security-case-types/<type-id>/type.yaml)
python3 tools/security-case-types/security_case_validator.py validate-case <case.yaml> --types security-case-types
# render a case into the composer's plan plus materialization, follow-through,
# verification and rollback; execution is never permitted
python3 tools/security-case-types/security_case_validator.py render <case.yaml> \
--types security-case-types capabilities/playbooks/*.yaml
Only implemented types accept cases. --allow-unimplemented exists for a type's
own example cases while the type is being written and acknowledged.
The validator refuses, among other things: missing sections, unknown or unpinned capabilities, attended steps without justification, steps or materialized items without a rollback, verification without a negative check or that reads a value, templates with unknown parameters, credential-shaped values anywhere, secret parameters that are not custody references, and high-risk types without founder acceptance.
To start a type: copy security-case-types/_template/, rename the directory to
the type id, and rewrite every section. The template's tests travel with it:
rename tests/test_type.py to tests/test_<type_id>_contract.py so module names stay unique.
Tests: python3 -m pytest tools/security-case-types/tests security-case-types/*/tests.