axiom audit concurrency

Engineering 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 3: Identify Default Isolation Strategy

Read 2-3 key files (App entry point, main view model, a networking layer file) to understand: Is this a MainActor-by-default codebase or per-type isolation? Where are the actor boundaries? (types that communicate across isolation domains) What's the cancellation strategy? (stored Tasks, cleanup in deinit/onDisappear)

Output

Write a brief Isolation Architecture Map (5-10 lines) summarizing: Default isolation strategy Actor boundary locations Concurrency entry point pattern (structured vs unstructured) Cancellation approach

Phase 2: Detect Known Anti-Patterns

Run all 8 existing 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
Engineering
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
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

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

01
Phase 1: Map Isolation Architecture

Phase 1: Map Isolation Architecture

02
Step 1: Identify Isolation Boundaries

Step 1: Identify Isolation Boundaries

03
Step 2: Identify Concurrency Entry Points

Step 2: Identify Concurrency Entry Points

04
Step 3: Identify Default Isolation Strategy

Read 2-3 key files (App entry point, main view model, a networking layer file) to understand: Is this a MainActor-by-default codebase or per-type isolation? Where are the actor boundaries? (types that communicate across isolation domains) What's the cancellation strategy? (stored Tasks, cleanup in deinit/onDisappear)

05
Phase 2: Detect Known Anti-Patterns

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

06
Phase 3: Reason About Concurrency Completeness

Using the Isolation Architecture 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 there unstructured `Task {}` in loops where TaskGroup would be better? · Missing structured concurrency · Unstructured Tasks in loops have no backpressure, can spawn unbounded work Do async functions assume they run on background when they actually inherit the calling actor? · async ≠ background misconception · Common cause of UI freezes — async functions stay on MainActor unless explicitly moved off

07
Phase 4: Cross-Reference Findings

Bump severity for these combinations: Finding A · + Finding B · = Compound · Severity Unstructured Tasks in loops · No error handling in those Tasks · Silent failures at scale · CRITICAL Missing @concurrent on CPU work · @MainActor caller · UI freeze · CRITICAL Stored Tasks without deinit cleanup · No cancellation on view disappear · Resource leak + zombie work · HIGH

08
Phase 5: Concurrency Health Score

Scoring: READY: No CRITICAL issues, <3 HIGH issues, >80% isolation coverage, 0 escape hatches NEEDS WORK: No CRITICAL issues, some HIGH issues, or escape hatches with migration comments NOT READY: Any CRITICAL issues, or escape hatches without migration plan

Discussion

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