NOTE

Vault Audit Tool Spec

titleVault Audit Tool Spec date2026-04-24 typepermanent aliasesagent-maintenance-spec, vault-tool-schema statusactive authorgemini-cli

Vault Audit Tool Spec

Following the agent-tools standard, this document provides the formal schema for the maintenance tools located in 02_System/.

1. YANP Compliance Auditor

  • File: 02_System/audit-yanp.ps1
  • Description: Scans 01_Wiki/ to ensure all files follow lowercase kebab-case naming and contain a valid type (permanent, literature, or fleeting) in the YAML frontmatter.
  • Execution Command: powershell.exe -ExecutionPolicy Bypass -File 02_System/audit-yanp.ps1
  • Inputs: None.
  • Outputs: A PSCustomObject table showing compliance status per file.

2. Orphan Note Checker

  • File: 02_System/orphan-check.ps1
  • Description: Performs a global scan for markdown files in 01_Wiki/ that have zero incoming wikilinks from other notes.
  • Execution Command: powershell.exe -ExecutionPolicy Bypass -File 02_System/orphan-check.ps1
  • Inputs: None.
  • Outputs: A list of orphan note basenames or a success message.

3. Tier-2 Compliance Auditor

  • File: 02_System/test-tier-compliance.ps1
  • Description: Audits Tier-2 PowerShell automation in both 02_System/ and 04_Experiments/, enforcing two hardening invariants: $ErrorActionPreference = 'Stop' and a top-level try/catch.
  • Execution Command: powershell.exe -ExecutionPolicy Bypass -File 02_System/test-tier-compliance.ps1
  • Inputs: None.
  • Outputs: A PSCustomObject table with scope, relative path, and compliance status per script.

Experimental runners created via 02_System/new-experiment.ps1 -IncludeScript start from a compliant scaffold so ad hoc tooling does not bypass the Tier-2 contract.

Usage Guide for Agents

When an agent enters this vault to perform an Ingest or Online Evaluation, it should run the YANP Compliance Auditor after every file modification to ensure protocol integrity.

See Also