Approve Sources, Caps, Cost, and Privacy

What you will complete

A collection contract enforced outside the user interface.

Make the operating decision

Allowlist exact providers, source lanes, queries, or URLs. Set a small canary, full-run cap, poll timeout, charge ceiling, and disabled add-ons. Record robots and access requirements. A capped scan is partial coverage and the report must state what was requested, accepted, returned, excluded, and failed.

Keep tokens and credentials in supported secret storage. They never enter browser code, reports, raw distributable fixtures, prompts, or chat. Private URLs, cookies, custom authentication, personal contact lists, a second paid provider, or a new external destination require a separate structural decision.

Do not retry a paid run automatically. Stop on authentication, billing, policy, quota, timeout, schema drift, or unexpected scope. Preserve a sanitized error and the approved input. Invalid input should fail before a provider call.

Worked fictional example: Harborline Safety Training

Harborline's fixture configuration allows two fictional official-source lanes, five canary records, a bounded timeout, and no enrichment. The live-provider field remains unconfigured. A private URL fails validation before collection.

Harborline Safety Training, Northstar Distribution, Dockside Logistics, Westbank Storage, all events, excerpts, people, and URLs are fictional fixtures. They do not prove a live source, lead, contact route, or business outcome.

Complete workbook section 3

Use the evidence available for your own bounded job. Write unknown when the evidence is missing, and record the person or action that can resolve it.

1. List exact approved sources and queries.
2. Set canary, full-run, timeout, and cost ceilings.
3. Disable enrichment, contact discovery, and unused add-ons.
4. Write stop and no-auto-retry conditions.

Open the course workbook PDF or read the workbook details.

Critical gate before continuing

• Limits are enforced outside the browser.
• Secrets stay out of artifacts.
• Private or unbounded input fails before collection.
• Paid failures do not loop.

If a gate fails, repair the current section, narrow the scope, leave the route manual, or record a blocked or stop decision. Continuing is not the only successful learner action.

Common failure modes

• Expanding beyond a collection contract enforced outside the user interface. before the current artifact can be graded.
• Turning a missing value, unavailable source, or blocked integration into a confident conclusion.
• Treating a prompt instruction as proof that the effective tool or permission boundary works.
• Marking a manual, simulated, or untested route as live.

Check your application