axiom audit storage

AI Community

Skill notes

Tool Use Is Mandatory

Run every Glob, Grep, and Read this prompt lists. Do not reason from training data instead of scanning. Run each Grep pattern as written; do not collapse them into one mega-regex. Run the Read verifications each section calls for. "Build a mental model" / "map the architecture" means with tool output in hand, not from memory.

Files to Exclude

Skip: *Tests.swift, *Previews.swift, */Pods/*, */Carthage/*, */.build/*, */DerivedData/*, */scratch/*, */docs/*, */.claude/*, */.claude-plugin/*

Step 4: Read Key Storage Files

Read 2-3 representative files (FileManager extension / DownloadManager / CacheManager / SettingsService) to understand: Which directory each data type lands in Whether backup exclusion is applied consistently to non-user content Whether sensitive data goes through Keychain or files Whether App Group container is used (only matters if extensions exist)

Output

Write a brief Storage Map (5-10 lines) summarizing: Locations in use (Documents / Caches / Application Support / tmp / App Group / iCloud Drive) What goes where (user docs / cache / settings / secrets) Backup-exclusion discipline (consistent / partial / missing) File-protection discipline (explicit / default / missing)

Phase 2: Detect Known Anti-Patterns

Run all 5 detection patterns. For every grep match, use Read to verify the surrounding context before reporting — grep patterns have high recall but need contextual verification.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@CharlesWiltgen · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Required · Vendor-specific
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Map Storage Architecture

Phase 1: Map Storage Architecture

02
Step 1: Identify Storage Locations

Step 1: Identify Storage Locations

03
Step 2: Identify Persistence Channels

Step 2: Identify Persistence Channels

04
Step 3: Identify Sensitive Data Surface

Step 3: Identify Sensitive Data Surface

05
Step 4: Read Key Storage Files

Read 2-3 representative files (FileManager extension / DownloadManager / CacheManager / SettingsService) to understand: Which directory each data type lands in Whether backup exclusion is applied consistently to non-user content Whether sensitive data goes through Keychain or files Whether App Group container is used (only matters if extensions exist)

06
Phase 2: Detect Known Anti-Patterns

Run all 5 detection patterns. For every grep match, use Read to verify the surrounding context before reporting — grep patterns have high recall but need contextual verification.

07
Phase 3: Reason About Storage Completeness

Using the Storage Map from Phase 1 and your domain knowledge, check for what's *missing* — not just what's wrong. Question · What it detects · Why it matters Are auth tokens, refresh tokens, and credentials in Keychain (not files)? · Sensitive data on disk · A file write of a token even with `.complete` protection is weaker than Keychain; files leak via backups, screen recording, sample-from-disk attacks

08
Phase 4: Cross-Reference Findings

Bump severity for these combinations: Finding A · + Finding B · = Compound · Severity Files in tmp/ (Pattern 1) · Critical user data (created docs, in-progress edits) · Guaranteed data loss on next OS purge · CRITICAL Missing isExcludedFromBackup (Pattern 2) · Auto-grow cache (downloads, generated thumbnails) · User's iCloud quota silently filled, possibly to the point of failed device backups · HIGH

09
Phase 5: Storage Health Score

Metric · Value Locations in use · Documents / Caches / App Support / tmp / App Group / iCloud Drive Backup-exclusion coverage · M of N regenerable-content writes set isExcludedFromBackup (Z%) File-protection coverage · M of N writes set explicit FileProtectionType (Z%) Sensitive data in Keychain · yes / partial / no (with file count of leaked secrets)

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.