Choose your path
landlock-genprof has different prerequisites depending on what you want to do. Start with the path that matches your goal; you do not need to read the documentation in order.
Before you begin
The product observes runtime behavior and turns it into a reviewable policy candidate. Observation is not authorization, and generation is not enforcement. The normal lifecycle is:
observe → synthesize → review → approve → apply → verify
Read the governed workflow for the responsibility of each stage. Before testing enforcement, check the enforcement prerequisites: filesystem, network, and syscall policy depend on separate enforcement mechanisms.
Find the right kind of documentation
| If you need… | Go to… |
|---|---|
| A task-oriented walkthrough | Usage guide |
| Exact flags and command syntax | CLI reference |
| Components and data flow | Architecture overview |
| Security assumptions and limitations | Security model |
| Proof of what works today | Demonstrated capabilities |
| Intended future capabilities | Product roadmap |
Status vocabulary: “generated,” “applied,” “enforced,” and “verified” are distinct claims. The progress page is the canonical record of demonstrated behavior; the roadmap describes intent and sequencing.