Define the approved destination contract for imports
The importer accepts any URL beginning with a trusted-looking string.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Network policy
Estimated field mix
- Security60%
- Networking40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional content-import service accepts document URLs. The team needs explicit destination approval, redirect handling, and response limits before enabling imports.
Setup prerequisites
- Create a local HTTP destination simulator and DNS double with authorized address cases; contact no real external hosts.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Specify allowed scheme, hostname, port, and path scope.
- Represent exact hosts separately from subdomain rules.
- Reject unknown policy entries.
Implementation constraints
- Use fictional destinations mapped only inside the local simulator.
Verification to include
- Accept an exact approved destination.
- Reject a lookalike hostname and unapproved port.
Deliverables
- Destination policy schema.
Rollout and recovery
Default to deny until a reviewed policy exists.
Value of the work
For the engineer: Practice URL interpretation, network policy enforcement, and resource controls.
For the team: Provide a reusable fetch boundary that makes destination authority and failure behavior inspectable.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.