Risk · minimum M5 Max pilot

Trust boundary — what enters when you install

Installing ODS may bring code, binaries, models, images, networks, volumes, configuration, credentials, and user services. Localhost helps, but remote modes and extensions widen the boundary.

By the end: explain, locate evidence, and apply it to the pilot.

Complete Simple + Technical

Installing ODS may bring code, binaries, models, images, networks, volumes, configuration, credentials, and user services. Localhost helps, but remote modes and extensions widen the boundary.

Bounded analogy: Knowing the main contractor is not the same as auditing every subcontractor entering your home. Artifacts can still change by tag, digest, and update.

Under the hood

Upstream guidance favors a fixed ref, inspect-first, local secrets, and localhost. The complete signature, checksum, and SBOM chain remains incomplete. Apache-2.0 covers ODS code, not the whole aggregate.

Boundary: installation, runtime, and Docker/Compose were not executed.

14 semantic microdiagrams

Each figure teaches one relationship; the sequence is a decision map, not a health dashboard.

01 · pinned source — decision relationship

02 · tag v2.5.3 — decision relationship

03 · manual inspection — decision relationship

04 · native binary — decision relationship

05 · GGUF model — decision relationship

06 · Docker images — decision relationship

07 · networks and volumes — decision relationship

08 · .env — decision relationship

09 · secrets — decision relationship

10 · LaunchAgent — decision relationship

11 · localhost — decision relationship

12 · optional LAN — decision relationship

13 · optional egress — decision relationship

14 · open provenance — decision relationship

Command and proof boundary

git clone --depth 1 --branch v2.5.3 https://github.com/Osmantic/ODS.git ODS-v2.5.3
git -C ODS-v2.5.3 rev-parse HEAD
less ODS-v2.5.3/ods/install.sh

Do not execute by inference: install commands are only a future user-gated plan.

Allows claiming

check	reading
local	exercised contract
upstream	declared capability

Remains open

runtime	gate
health/chat/UI	live pilot
lifecycle	backup/restore/uninstall

Local sources

outputs/ods-adoption-dossier.md:118-149
work/ods-latest/ods/docs/INSTALLER_TRUST.md:58-70
work/ods-latest/SECURITY.md:34-39
outputs/ods-check-receipt.md:222-228

Includes dossier, receipt, and official source by path:line.

Practice with feedback

1 · Prediction

2 · Stepper

1. classify the need

2. locate the proof

3. decide without overclaiming

3 · Scenarios

4 · Checklist

local source cited boundary declared runtime not assumed next gate explicit

5 · Slide deck

Installing ODS may bring code, binaries, models, images, networks, volumes, configuration, credentials, and user services. Localhost helps, but remote modes and extensions widen the boundary.

A check is not runtime.

decide without overclaiming

6 · Quiz

Which control comes first?

7 · Active recall

Demo debate: incident-report + editor-feature-flags; flowchart-diagram + code-review-pr; runner-up prompt tuner