Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/TWO-PILLARS.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,10 @@ them. It is prose, not proof; the obligations it points at live in
*conditional* on a declared `O` (see <<metal>>).

| Composition
| Closes cleanly: nothing ∘ nothing = nothing.
| Closes when the first program is *closed* (every jump targets one of its
instructions or its end):
`cno-composition` in the active Agda takes `Closed p₁`, and
`closedness-needed` shows the hypothesis cannot be dropped.
| Does *not* close cleanly (see `OND-ROADMAP.adoc` §5–6). The negative result
is first-class.

Expand Down Expand Up @@ -209,7 +212,8 @@ Three reasons the pillars are siblings, not parent-and-child:
cannot mean.

A fourth point is investigated rather than asserted: *composition*. CNOs
compose cleanly. ONDs may not — two operations each individually constant over
compose when the first program is closed (`cno-composition`; without
closedness `closedness-needed` refutes it). ONDs may not — two operations each individually constant over
the secret can, run together, expose a *joint* observable that leaks (the same
shape as the "max-composition is unsound for quasi-identifiers" worry from the
echo/residue work). The OND pillar therefore ships a *negative* composition
Expand Down
Loading