Reproducible operations mode

Installation for engineers and maintainers. Deterministic checks, diagnostics, and governance verification paths.

This guide targets technical users who require stable reproducibility, contract-aware testing, and explicit operational controls.

Setup

Baseline installation flow

Step	Command / note
Clone repository	`git clone https://github.com/vfi64/wrapper.git`
Enter directory	`cd wrapper`
Create/update venv	`bash scripts/setup_venv.sh`
Activate venv	`source .venc/bin/activate`
Start runtime	`python Comm-SCI-Control-App.py`

Quality assurance

python -m pytest -q tests

python -m pytest -q tests/test_app_bootstrap.py

python -m pytest -q tests/test_app.py -k "contract or panel"

Use Comm State, Comm Anchor, Comm Audit, and logs together for root-cause isolation.

Operational routine

1) Baseline check
Load ruleset and verify with `Comm State`.
2) Governance start
`Comm Start`, profile selection, optional SCI variant setup.
3) Runtime operation
Handle requests; run `Comm Anchor` and `Comm Audit` periodically in long sessions.
4) Evidence trail
Archive relevant logs/audits with timestamps for reproducibility.

Security and cost control

Topic	Recommendation
Key storage	Prefer environment variables. Local key file only for isolated single-user setups.
Key modes	`api_key_plain` (no passphrase) vs. `api_key_enc` (passphrase prompt on startup/provider switch).
Panel workflow	Use `API-Key` in panel section `Provider & LLM`; maintain keys per provider.
Provider onboarding	Gemini: key, OpenRouter: key, Hugging Face: token
Pricing awareness	Check costs before usage: Gemini, OpenRouter, HF.
Leak response	Immediately revoke, rotate, and reconfigure affected credentials and access scope.