Open questions

Open questions are structured prompts Guardix raises when the pipeline needs product or deployment context that is not obvious from code alone. They appear in system analysis after a run and may also surface during an active audit when your answers can still influence downstream analysis.

After the audit completes

On the repository Architecture tab (and in related system-analysis surfaces), open questions are listed alongside invariants, assumptions, and decisions. Each item includes:

• The question in plain language
• Priority (high / medium / low) when shown
• Status — unanswered, resolved with your reply, or skipped

Use these to close gaps between what the code does and what your team intends.

During an active audit (co-audit)

While a code audit is still running, you may see a guided question flow on the in-progress page. This is optional but valuable:

• Answer one question at a time or skip items that do not apply.
• Replies are sent as you go, so the running audit can incorporate context without waiting for completion.
• A soft timer may indicate when answers are most helpful — after that window, the audit continues with what it already has.

When the run finishes, the same questions remain as a read-only record of what was asked and how you responded.

Availability of the in-progress question flow may depend on workspace configuration.

Good answers

• State facts (roles, deployment model, trusted operators, external dependencies).
• Reference docs or tickets when they define intended behavior.
• Say “not applicable” via skip when the question does not fit your system — do not guess.

Related

• System analysis — invariants, assumptions, decisions, and system map.
• Your first audit — where documentation and scope choices are set before the run starts.