How It Works
Four steps from
regulation to
engineering work
Landfall translates regulatory requirements into actionable engineering tasks — with full traceability and approval gates at every step.
Step 1
Context Intake
Describe your product
Answer questions about your service — audience, data practices, profiling, safety measures. Your answers become structured assumptions that drive obligation mapping.
- Does your product target or is it likely to be accessed by users under 18?
- Does your product use algorithmic profiling or recommendations?
- What personal data do you collect from users?
Step 2
Obligation Mapping
AI reads the regulation. You confirm.
Based on your context, Landfall suggests which obligations apply. You confirm, override, or flag each one — every decision requires rationale.
- Obligation ID linked to regulation source
- Applicability status with reviewer badge
- Plain-language rationale for every decision
Step 3
Engineering Tickets
Obligations become work items
Each applicable obligation produces prioritised work items with acceptance criteria, priority levels, and full traceability back to the source regulation.
- MoSCoW priority assignment (Must / Should / Could)
- Acceptance criteria for each item
- Multiple item types: Feature, Edge Case, QA Test, Logging
Step 4
Export & Audit
Ship with confidence
Export to Jira, Linear, or as audit-ready packages. Every export includes cryptographic integrity verification and complete decision trails.
- Push directly to Jira or Linear
- SHA-256 integrity verification
- Self-contained HTML audit packages
Built on three principles
Human-in-the-Loop
AI suggests, humans decide. Every mapping requires explicit approval with documented rationale.
Ambiguity Detection
When regulatory text is unclear, Landfall flags it for human resolution — no silent interpretations.
Full Traceability
Every work item links to an obligation, which links to specific regulation text. Complete audit trail.