# Trust model

`sdd-agentic-flow` is inspectable local tooling: its CLI, skills, configuration, docs, and validation scripts are part of the package. It has zero external runtime npm dependencies (build-time libraries may be bundled), and no telemetry, postinstall hook, or outbound CLI network access by default.

Network access has **three explicit entry points** (never silent/background):

1. **`doctor --check-updates`** — diagnostic read-only check (one npm registry request).
2. **`upgrade`** (including `--check` / `--plan`) — upgrade-specific operations; mutations only after interactive confirms. A confirmed update runs the exact checked package version and reconciles only missing or changed files under the managed skills and shared layer. `--skills-only` does not use the network.
3. **Interactive bare welcome opt-in** — on human-rich TTY only (stdin+stdout TTY, no `CI`), the CLI may offer an explicit update-check action. Declining keeps zero network; choosing it starts the same check path as `upgrade`. Set `SDD_NO_UPDATE_PROMPT=1` to skip update prompts.

Machine / pipe / CI / `--quiet` / human-plain bare welcome never prompt and never call the registry unless you pass an explicit flag or command above. Offline is never reported as “up to date”. See `src/update-check.ts` and `src/upgrade.ts`.

Installation and configuration are explicit local writes. By default (`install`'s `user`
scope), skills are written only to per-agent global directories outside the project. See
[installation scope](installation-scope.md) for the two scopes and their ownership boundary.
`.sdd-agentic-flow/config.yml` and `.sdd-agentic-flow/context/project-context.md` always live in the project, created
explicitly by `init`/`context refresh`. The CLI does not automatically commit, push, merge, deploy, or
publish. `doctor`, `doctor --json`, and `doctor --smoke` provide local evidence; publishable
files are scanned for blocked private-context markers.

## Formal product requirements

> **Local-first installation.** The default installation scope MUST be local-only and
> repository-neutral: `install` MUST NOT create, modify, or delete any file inside the
> consumer project unless repository integration is explicitly requested via `--scope project`.
>
> **Cross-platform, shell-independent.** `sdd-agentic-flow` MUST provide a consistent
> installation and usage experience across supported Windows, macOS, and Linux environments,
> without requiring a specific interactive shell. The CLI MUST NOT rely on Bash, Zsh,
> PowerShell, CMD, or other shell-specific behavior for core functionality. Only Node.js APIs
> (`fs`, `path`, `os`, `child_process` with argument arrays, never shell-string interpolation)
> may drive core behavior. Shell-specific commands MAY appear in documentation as illustrative examples, but product
> behavior MUST NOT depend on them.
>
> **Git is an optional integration capability, not a runtime requirement.** Node.js is
> required; Git is not. Where the CLI reads Git state (repository revision/branch), absence of
> Git or of a Git repository MUST degrade gracefully, never fail the command.

See [environment compatibility](environment-compatibility.md) for the supported OS/Node/shell
matrix this promise is checked against.

The TLC and TDD baselines are local references. They guide planning and code-task
evidence without installing an external methodology package.

These boundaries do not guarantee correctness or safety for every input or agent. Review generated work, preserve the licensing notices, and keep a human as the final decision maker.