Skip to main content
← Back to list
01Issue
FeatureShippedSwamp Club
Assigneesstack72

Relationships

#1117 Document vault read-access audit trail

Opened by stack72 · 7/13/2026· Shipped 7/13/2026

PR #1830 (swamp-club#1109) added a vault read-access audit trail feature, but the documentation site has no coverage of it.

What's missing

Reference (content/manual/reference/vaults.md):

  • auditReads is not listed as a vault configuration field
  • swamp vault audit-trail is not in the CLI commands section
  • No documentation of the JSONL audit entry format (timestamp, vaultName, vaultType, secretKey, callerContext)

How-to (content/manual/how-to/vaults/):

  • No guide for enabling and querying vault read audits (five other vault how-to guides exist)
  • The index page at content/manual/how-to/vaults.md has no link for audit

Explanation:

  • The existing audit system docs (the-audit-system.md) cover command-level audit hooks for AI agent activity — a completely separate feature. There is no explanation distinguishing vault read-access audit from command-level audit.

Suggested changes

  1. Reference: Add auditReads to the vault config fields table, add vault audit-trail to the CLI commands section, document the audit entry format and callerContext values
  2. How-to: Add a new audit-reads.md guide under content/manual/how-to/vaults/ and link it from the vaults index
  3. Explanation (optional): Add a note to the-audit-system.md or a new page clarifying the distinction between command-level and vault read-access audit
02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 3 MOREPR_MERGED+ 1 MORENOTIFICATION_SKIPPED

Shipped

7/13/2026, 9:49:13 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack727/13/2026, 8:14:59 PM

Sign in to post a ripple.