Skip to content

docs: align OpenClaw disclosure & installation docs with the daemon-owned model#741

Merged
ojongerius merged 3 commits into
mainfrom
claude/hpke-openclaw-plugin-kuLWP
Jun 8, 2026
Merged

docs: align OpenClaw disclosure & installation docs with the daemon-owned model#741
ojongerius merged 3 commits into
mainfrom
claude/hpke-openclaw-plugin-kuLWP

Conversation

@ojongerius

@ojongerius ojongerius commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

The docs site still described the OpenClaw plugin as a Flavor A, in-process configuration surface for disclosure. Under ADR-0010 (daemon process separation) the daemon owns disclosure and the plugin is a thin emitter. This brings both affected pages in line with the shipped plugin.

Changes

specification/parameter-disclosure.mdx

  • The "Disclosure modes" section claimed "the daemon and the OpenClaw plugin offer the same four modes" and that the plugin's JSON config accepts an array allowlist. Reworked to state plainly that disclosure is configured on the daemon under ADR-0010; dropped the OpenClaw plugin from the allowlist-spelling note.

openclaw/installation.mdx (added after review surfaced the contradiction)

  • The page still documented the pre-ADR-0010 in-process model: a local keyPath signing key, daemonForwarding as opt-in, and parameterDisclosure as an active plaintext field-disclosure setting.
  • Now leads with the daemon requirement, documents the actual config surface (daemonDbPath, daemonPublicKeyPath, taxonomyPath), and marks dbPath / keyPath / daemonForwarding deprecated and ignored.
  • Rewrote the parameter-disclosure section: disclosure is daemon-configured via --parameter-disclosure + a forensic key; shows the opaque HPKE envelope shape rather than a plaintext flat map; notes ar_query_receipts' disclosed flag and that the plugin never decrypts.

Docs-only; no spec/ changes.

Review feedback addressed

  • Copilot: dropped the undefined "Flavor B" label and stopped asserting plugin-specific behaviour on the spec page (which had conflicted with installation.mdx) — then fixed installation.mdx itself so the two pages agree.

Companion plugin-side work is in agent-receipts/openclaw#153 (same branch name).

Under ADR-0010 (Flavor B) the daemon owns parameter disclosure; the OpenClaw
plugin no longer controls it (its parameterDisclosure config is a deprecated
no-op). The parameter-disclosure page still described the plugin as a live
config surface offering the four modes and accepting a JSON-array allowlist.
Correct both passages to reflect daemon-only configuration.

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

Updates the Parameter Disclosure specification page to remove stale claims about OpenClaw being a configuration surface for disclosure policy, aligning the docs with the daemon-owned configuration model described in ADR-0010.

Changes:

  • Clarifies that parameter_disclosure is configured on the daemon (not via OpenClaw).
  • Updates the allowlist “spelling” note to remove OpenClaw JSON config as an accepted array surface.

Comment thread site/src/content/docs/specification/parameter-disclosure.mdx Outdated
Address review feedback: drop the undefined "Flavor B" label and stop
asserting OpenClaw-plugin-specific behaviour on the spec page (which
conflicted with the still-Flavor-A openclaw/installation.mdx). State
plainly that disclosure policy is configured on the daemon under
ADR-0010; this still removes the original stale claim that the plugin is
an equivalent config surface, without introducing an internal contradiction.
The OpenClaw installation page still documented the pre-ADR-0010 in-process
model: a local keyPath signing key, daemonForwarding as an opt-in, and
parameterDisclosure as an active plaintext field-disclosure setting. That
contradicts the shipped plugin, which requires the daemon and treats
parameterDisclosure as a no-op.

- Lead with the daemon requirement; document the actual config surface
  (daemonDbPath, daemonPublicKeyPath, taxonomyPath) and mark dbPath/keyPath/
  daemonForwarding deprecated and ignored.
- Rewrite the parameter-disclosure section: disclosure is daemon-configured
  via --parameter-disclosure + a forensic key; show the opaque HPKE envelope
  shape rather than a plaintext flat map; note ar_query_receipts' disclosed
  flag and that the plugin never decrypts.
@ojongerius ojongerius changed the title docs(disclosure): correct stale OpenClaw config claims docs: align OpenClaw disclosure & installation docs with the daemon-owned model Jun 3, 2026
@ojongerius ojongerius force-pushed the claude/hpke-openclaw-plugin-kuLWP branch from c3820ee to c82d2a6 Compare June 8, 2026 10:44
@ojongerius ojongerius merged commit 7e24398 into main Jun 8, 2026
13 checks passed
@ojongerius ojongerius deleted the claude/hpke-openclaw-plugin-kuLWP branch June 8, 2026 10:47
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