Capstone: produce a defensible Mach-O analysis
Analyze only course fixtures, your own software, or software you are authorized to inspect.
Choose a course fixture or another Mach-O file you are authorized to analyze.
Produce an analysis package containing:
- SHA-256 and basic file identity;
- universal-container description if applicable;
- parsed Mach header;
- full load-command inventory;
- segment/section map with file and virtual ranges;
- dependency and dynamic-link summary;
- symbol/runtime-metadata observations;
- code-signing and entitlement observations;
- three behavior hypotheses, each linked to concrete evidence;
- at least one small parser or verification script you wrote;
- a section titled What I cannot conclude from this evidence.
The last section is required. Technical competence includes knowing the boundary between evidence and inference.
Credential standard
A verified course credential should mean the learner completed the required lessons, passed the final assessment, and submitted the capstone evidence package.
The public credential will attest to course/version completion. It will not publish private learner artifacts unless the learner explicitly chooses to expose them.