openworld-honesty
Closed-world tools stay on the machine
The sections below are generated from the CLI (methodology 0.3-draft, CLI 0.3.0); the same text is printed by sealmark explain openworld-honesty.
- pack
effects- weight
- scored
- scope
- server (annotations vs what the sandbox observed during the harness's own benign calls)
- decided by
- listener
- since
- 0.2-draft (methodology 0.3-draft)
- config keys
checks.openworld-honesty.enabledchecks.openworld-honesty.severitysandbox.enabledtools.overrides
Probes
controleach tool declared openWorldHint: false is called with its control argument; the loopback listener records any connection
Settings and thresholds
Every check also takes checks.openworld-honesty.enabled and checks.openworld-honesty.severity; they are described once in the configuration reference.
This check has no numeric threshold.
| Key | Default | Standard | Meaning |
|---|---|---|---|
tools.overrides | {} | locked | Per-tool classifier overrides: { tool: { class, params } }. An override always wins and is printed. |
How the verdict is established
- Scoring. scored: pass = 1 point, part = 0.5, fail = 0. A fail lowers the pack's percentage but never caps the letter.
What to fix
Set openWorldHint: true on a tool that makes network connections, or stop the connection; a tool that claims a closed world must not contact the harness listener.
False positives
None known: a tool that connects to the harness's loopback listener while claiming a closed world is open-world.
False negatives
Path and git tools cannot be pointed at the listener, so for them this confirms only that nothing connected out during the control call. Only URL tools can contradict the annotation.