docs(audit): erratum — /tmp/aerie.pid is no longer standard-compliant

[hyperpolymath]

docs/compliance-audit-2026-04-10.adoc is a frozen snapshot ("do not update it"). Its aerie row calls /tmp/aerie.pid a "standard-compliant predictable name", which was only true of the 2026-04-10 standard.

This PR leaves every frozen row untouched. It adds a dated erratum under the banner saying that, under the current launcher-standard_praxis.deed (#62; canonical copy in hyperpolymath/standards#1076), a /tmp or $TMPDIR pid file is non-compliant (CWE-377). The row therefore stops being citable as precedent.

Part C3 of the launcher /tmp cure.

🤖 Generated with Claude Code

https://claude.ai/code/session_0136eszqrQ53Kj7aBH1D4rXK

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 8883707c-a8e5-45c4-b686-e413774ab5f1

📥 Commits

Reviewing files that changed from the base of the PR and between 31ccfde and 005752e.

📒 Files selected for processing (1)

• docs/compliance-audit-2026-04-10.adoc

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details

⏰ Context from checks skipped due to timeout. (13)

• GitHub Check: rust-ci / Detect Cargo.toml
• GitHub Check: governance / Licence consistency
• GitHub Check: governance / Well-Known (RFC 9116 + RSR)
• GitHub Check: hypatia / Hypatia Neurosymbolic Analysis
• GitHub Check: governance / Trusted-base reduction policy
• GitHub Check: governance / Security policy checks
• GitHub Check: governance / Language / package anti-pattern policy
• GitHub Check: governance / Code quality + docs
• GitHub Check: governance / Guix primary / Nix fallback policy
• GitHub Check: governance / Check Workflow Staleness
• GitHub Check: Build, count, mint, lint
• GitHub Check: CodeQL Analysis (actions, none)
• GitHub Check: semgrep-cloud-platform/scan

🔇 Additional comments (1)

docs/compliance-audit-2026-04-10.adoc (1)

24-30: LGTM!

---

📝 Summary

Summary by CodeRabbit

• Documentation
  • Added an erratum clarifying that the aerie row’s PID-file configuration met the 2026-04-10 standard but does not comply with the current standard. It also explains the security risk and notes that the row is not precedent for current assessments.

Walkthrough

The audit document adds an erratum. It distinguishes the aerie row’s classification under the 2026-04-10 standard from the current standard for PID files in /tmp and $TMPDIR.

Changes

Compliance audit erratum

Layer / File(s)	Summary
Clarify PID-file classification docs/compliance-audit-2026-04-10.adoc	The erratum states that predictable PID-file names in world-writable temporary directories are non-compliant under the current standard. It also states that the aerie row is not precedent for that standard.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 00575

The erratum clarifies that /tmp and $TMPDIR PID files violate current policy and that the audit row is not current precedent. The available repository evidence does not establish whether the row complied with the April 10 standard, but also does not demonstrate an error requiring a merge hold.

Architecture Summary

Architecture risk: 🔵 Low · up to 00575

The change affects 1 system.

Changed systems: docs

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — docs (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in docs/compliance-audit-2026-04-10.adoc: Adds an erratum distinguishing the aerie PID-file classification under the 2026-04-10 standard from the current standard: /tmp and $TMPDIR PID files are now classified as non-compliant due to the risk of another user choosing the PID killed by stop; the aerie row is not precedent.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding an erratum that records the changed compliance status of /tmp/aerie.pid.
Description check	✅ Passed	The description accurately explains the frozen audit snapshot, the added erratum, the current standard, and the compliance impact.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit reads the audit page
And marks the erratum with care
The PID-file rule is now made clear
The old row stays in its own time
Then off it hops beneath the moon}

_{Comment @coderabbitai help to get the list of available commands.}