Open Agila: Architecture, Ada & V

Module 1 – Architecture and trust boundaries

Page 2 of 3 · About 15 minutes per lesson, including practice.

Caller identity must come from a trusted boundary

15-minute session: read for 3 minutes, trace for 3, experiment for 7, and complete the check for 2. Spend longer whenever you need.

The host port API accepts a caller number. It checks that number against the owner or allowed sender. An application in the same process can choose a different number, so this is a policy model, not authenticated isolation. A future syscall must obtain identity from trusted task state. Inspect Send and the C header together.

Your experiment

Mark the input that a caller controls. Write a future syscall contract that removes that input and obtains the current task internally.

Practice and evidence

Keep three notes: your prediction, the actual result, and why they match or differ. The completion check grades understanding; the practice task builds skill.

Language reference

Example code on Agila Forge ↗