Skip to content

docs: add sealed probes guide - #6734

Merged
lpcox merged 1 commit into
sealed-probe-information-budgetsfrom
docs/sealed-probes-guide
Jul 29, 2026
Merged

docs: add sealed probes guide#6734
lpcox merged 1 commit into
sealed-probe-information-budgetsfrom
docs/sealed-probes-guide

Conversation

@lpcox

@lpcox lpcox commented Jul 29, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • explain sealed probe use cases and trust boundaries
  • document configuration fields, defaults, constraints, and sensitivity budgets
  • describe schema, accounting, timing, agent interface, and failure semantics

Validation

  • cd docs-site && npm run build
  • npx markdownlint-cli2 docs-site/src/content/docs/guides/sealed-probes.md

Stacking

This documentation PR is stacked on #6728 because sealed probes are not yet on main.

Document sealed probe configuration, budgets, schemas, timing, and failures.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: ca8d9d74-46ab-48db-b05f-640cbc6d47be
Copilot AI review requested due to automatic review settings July 29, 2026 22:48
@github-actions

Copy link
Copy Markdown
Contributor

Documentation Preview

Documentation build failed for this PR. View logs.

Built from commit 3bc83c3

@lpcox
lpcox merged commit ea6f4fe into sealed-probe-information-budgets Jul 29, 2026
4 checks passed
@lpcox
lpcox deleted the docs/sealed-probes-guide branch July 29, 2026 22:50

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a user guide for the sealed-probes feature introduced in stacked PR #6728.

Changes:

  • Documents architecture, configuration, sensitivity budgets, schemas, timing, and failure semantics.
  • Provides invocation guidance and examples.
Show a summary per file
File Description
docs-site/src/content/docs/guides/sealed-probes.md Adds the sealed-probes guide.

Review details

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 1/1 changed files
  • Comments generated: 5
  • Review effort level: Medium


An `internal` repository with a 64-bit budget can fund 12 consecutive boolean questions (60 bits), leaving 4 bits for one `const` question. If every query uses a `const` schema, it can fund 16 questions.

`maxInvocations` is a separate, independent operational limit. It counts every response -- including those rejected by schema validation, budget exhaustion, or malformed requests -- and is unrelated to the bit ledger.

When sealed probes are enabled the agent container receives:

- A Unix socket directory (read-write) mounted at `$AWF_SEALED_PROBE_SOCKET`

- `--repo` must appear exactly once. The value must be a valid `owner/repo` slug matching a configured repository.
- `--schema` must appear exactly once. The value is a JSON document (at most 4096 bytes) conforming to the finite schema DSL.
- The probe script arrives on **stdin**. Interactive terminals are rejected.
{"status":"error"}
```

**Probe environment.** The script runs as an unprivileged user (uid 65534) with no network and a read-only filesystem, except for `/probe`. The repository tree is at `/probe/repo/`. The script must write exactly one JSON value conforming to the declared schema to `/probe/out`. Stdout and stderr are discarded and never reach the agent.
| Max `union` variants | 16 |
| Max literal string length | 64 bytes |

In practice the 4096-byte size limit is the binding constraint for wide `enum` or `object` schemas well before the count limits are reached.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants