Engine / Evidence / Demonstrations
Follow the request.
Examine the evidence.
Explore the OODA Engine and the application security demonstration: where application authorization, evidence assessment, and response reporting meet.
Revision 3 · 24 October 2026 · Documented local results
SECURITY LAB / SEPARATE TRACKSREV 3
APPLICATION TRACK
Application authorizes → permits or denies
ASSESSMENT & REPORTING TRACK
Completed scene → frozen C assessment
Optional local HTTP response → CLI recipientNo engine control executed. Browser examples are illustrative.
Application protection
Permissions determine allowed operations.
Engine assessment
Evidence is evaluated as a separate responsibility.
Response reporting
A field communicates an advisory signal.
Explore
Choose your next step.
01
Architecture
Follow the responsibilities of the application, C assessment process, and reporting recipient.
02Demonstration
Explore a fictional application scenario and a separate assessment and reporting flow.
03Evidence
Read the documented local results with their dates, scope, and limitations.
04Development
See the research questions and implementation work that remain open.
The protocol layer
A shared signal for HTTP responses.
Learn how Enforcement-Action relates to observability, trust boundaries, and measurement.