Question 1

What is a bounded safe review sprint?

Accepted Answer

A sprint is a deliberately scoped batch of dependency work: Bivouac investigates the selected updates, opens tested patch work, and evaluates each change against the repository policy and CI gates. The boundary is intentional: when compatibility, policy, or test evidence is unresolved, the sprint stops for review instead of widening its scope or presenting a guess for approval.

Question 2

What human-review guardrails and stop conditions apply?

Accepted Answer

Bivouac keeps human judgment in the loop for policy-sensitive or security-sensitive changes, ambiguous compatibility decisions, and failed verification. A failed build or unmet policy gate blocks the change; a passing build prepares the tested PR for review, but a human still approves and merges it. The audit trail records the signal, decision, test result, and any human override so your team can review the boundary before enabling a rollout.

Question 3

Can Bivouac run with a private or self-hosted runner?

Accepted Answer

The self-hosted posture is designed for a signed runner on infrastructure your team controls, including private and regulated environments. During an enterprise evaluation, confirm the deployment boundary, supported Git platform, network egress, credential scopes, data-residency needs, and whether an air-gapped or locally operated model-proxy arrangement fits your policy. The exact runner shape is part of that evaluation, not an assumption to make from this page.

Question 4

What is public in the activity stream, and what stays private?

Accepted Answer

The public activity stream is a product-level view of patch and decision activity: it helps an evaluator see the shape of the loop without exposing a customer repository. Repository source, lockfiles, credentials, and private operational details remain within the private deployment and access boundaries being evaluated. Use the activity page for the public signal; use the enterprise conversation to confirm exactly what your tenant, runner, and audit records expose.

Question 5

How do we start an enterprise inquiry?

Accepted Answer

Use the enterprise contact form to share your repository fleet, rollout scope, security controls, runner and residency requirements, and the dependency work you want to evaluate. The Bivouac team can then confirm fit, evidence, and the safe pilot boundary with you. If your question is specific to procurement, private deployment, or rollout sequencing, include that constraint so the first response can address it directly.