Set privacy and network egress boundaries

Before release, define what the artifact refuses to do. Validate ranges, minimize retained data, pin the reviewed configuration, and assign an owner who can disable the feature. Safety is implemented at the boundary and release process; it is not a warning paragraph placed after an unsafe function.

Privacy policies often forbid cloud fallback for specific data classes. Enforce that in code, not in a wiki. Block network egress in those modes.

The artifact's user-facing goal is specific: answer allowed tasks locally when hardware permits, otherwise follow an explicit fallback policy. Its accepted input is prompt, model tag, timeout, and policy flags for whether cloud fallback is allowed. Those statements are intentionally narrower than “build an AI system.” Narrow scope lets us inspect every input and expected result, and it prevents a toy result from being presented as a production claim. System shape for this chapter: Ollama manages model weights and a local HTTP inference process; a thin application adapter applies a system policy, timeouts, and structured logging; an evaluation harness compares quality, tokens per second, memory use, and privacy requirements before enabling cloud fallback. Keep model calls behind adapters, keep authorization and validation in deterministic code, and carry stable IDs and versions through every response. That separation lets you decide whether a bad result came from input handling, retrieval, inference, validation, or deployment. This page's job is the safety and operations step: before release, define what the artifact refuses to do. Setup baseline for the chapter (run once per machine, not secrets in git):

# Install Ollama from the official site for your OS, then:
ollama pull llama3.2:1b
python -m venv .venv && source .venv/bin/activate
pip install httpx

If hardware or a hosted provider differs, preserve the interface and expected behavior. Do not present provider syntax as universal—when a vendor adapter is unavoidable, keep it behind a thin boundary and test with a fake first. The deliverable is not “it ran once”; it is a reproducible artifact another developer can inspect, including expected output and one deliberate failure related to hanging local inference or silent privacy-violating fallback. Operationally, write down the owner of this stage, the command you ran, the observed output, and the next page's dependency on that output. If you cannot point to a file, fixture, metric, or config key, the stage is not done. Prefer small, reviewable increments: one contract, one path, one metric, one failure, one gate. When tradeoffs appear—latency versus quality, hit rate versus false hits, local privacy versus cloud quality—record both numbers instead of moving the threshold until the report looks green. The chapter ships only when evidence for golden task pass rate, tokens/sec, peak memory, and fallback rate within policy and a rehearsed recovery path exist beside local-first router with LOCAL_MODEL_ID and ALLOW_CLOUD_FALLBACK pins.

Save this as lesson.py and run python3 lesson.py. Prefer the standard library or the pinned packages from the setup block so the example stays reproducible.

def egress_allowed(allow_cloud, destination):
    if destination=="local": return True
    return bool(allow_cloud)
print(egress_allowed(False, "cloud"))

Expected output: False cloud egress when disallowed. Exact floating-point formatting may vary slightly, but the asserted behavior must not. Read the output as evidence about this stage, not merely proof that the interpreter started.

Run a negative authorization or safety test. A perfect quality score with a broken boundary must still fail the release. At the safety and operations stage, save the smallest failing fixture beside the expected result. Change one cause at a time and rerun the exact command printed above; that makes the repair reviewable and keeps this chapter's progressive artifact reproducible.

Security and ops gates are blockers. Missing controls fail the ship checklist even when demos look good. For this safety and operations page, preserve the fixture and result as evidence for the next page. Label observations separately from conclusions: a passing assertion establishes the behavior it names, while broader usefulness requires the chapter's full evaluation set and stated operating limits. Primary metrics for the chapter remain golden task pass rate, tokens/sec, peak memory, and fallback rate within policy.