Source archive

This directory preserves the sources used to make implementation decisions. A printed or offline copy must include the records, their linked source/license assets, and SHA256SUMS. Start new records from TEMPLATE.MD. Original URLs remain provenance; specification citations point here.

Capture all material relevant to a relied-upon claim, including limits and recovery conditions. Archive full originals when redistribution permits; otherwise preserve the relevant technical facts in a clearly labeled account. Never present a paraphrase, unverified command, or forum report as a complete authoritative original. Exact per-OS utility manuals and successful runtime transcripts belong here when adapters are implemented; until captured, those adapters remain unvalidated.

Use UTF-8 plain text, meaningful filenames, local links, explicit dates, and versioned records. Keep multiple independent copies, print the catalog and checksums, and periodically verify and migrate storage media. No file format or medium alone guarantees a century of preservation. Hashes detect byte changes; they do not establish authorship or durability. Printouts must include the captured text, not just an asset URL.

Catalog

Each source has one primary entry. Related records link across subjects; original filenames remain stable. Descriptions identify evidence, not successful implementation tests.

Apple platforms and system behavior

• Apple Configuring System Integrity Protection — NVRAM scope, Recovery changes, and limits of the 2015 SIP guide.
• Apple default login shell — OS defaults, account state, and separate Terminal settings.
• Apple macOS Human Interface Guidelines (Mojave, 2018) — Historical website capture, original assets, and local replay in the documentation library.
• Apple Signed System Volume Security — Hash-tree integrity, boot snapshots, T2 boundaries, and FileVault prerequisites.
• Apple Writable Root Volume Discussion — Big Sur failures, snapshot reports, and the writable-data alternative.

Hardware compatibility and CPU architecture

• Mac Pro 2013 Compatible Operating System — Model identification and the supported Monterey ceiling for MacPro6,1.
• OWC Intel Mac Transition Report — Dated secondary report on macOS 27 and affected Intel owners.
• X86 64 Microarchitecture Levels — Cumulative CPU features and OS register-state requirements.

Homebrew releases, support, and history

• Homebrew 5 Release — Download concurrency, API opt-in, and the announced Intel schedule.
• Homebrew 6 Release — Tap trust, API defaults, sandbox scope, cooldowns, and install steps.
• Homebrew 7 Release and Intel Support — Intel Tier 3, execution cutoff, services, GUI, and installation safeguards.
• Homebrew Historical Overview — Secondary release chronology and the Monterey date discrepancy.
• Homebrew Monterey Discussion 5603 — September 2024 CI reallocation and later support/communication debate.
• Homebrew Support Tiers — Configuration-dependent support, bottles, and scheduled removal.

Build infrastructure and runner availability

• GitHub Intel Runner Retirement — Hosted labels, brownouts, migration, and Intel retirement schedule.
• Homebrew Intel CI Discussion 7044 — Reported CI slowdown and August 2026 bottle cessation ahead of schedule.

Signing, trust, and supply-chain security

• curl Mozilla CA Extraction — PEM conversion, omitted browser constraints, and trust limits.
• Homebrew Attestation Proposal 17019 — Historical proposal, flag spelling, and unresolved bootstrap questions.
• Homebrew Provenance Beta Implementation — Verification identities, backfill alternatives, credentials, and beta limits.
• Homebrew Provenance Beta Sigstore — Public rollout and the generation/verification distinction.
• Homebrew Security and Supply Chain — Signed metadata, provenance, shared infrastructure, and execution boundaries.
• SmartCard HSM Algorithms — Token capabilities versus minisign and TUF compatibility requirements.
• The Update Framework Specification — Complete roles, metadata, root updates, freshness, and client workflow.
• YubiKey PIV Algorithms — Firmware-specific PIV capabilities and older-device limits.

Formats, schemas, and serialization

• JSON Schema 2020 12 Core — Complete fixed draft: dialects, resources, references, applicators, and closure.
• JSON Schema 2020 12 Validation — Complete fixed draft: assertions, presence, formats, and annotations.
• libarchive tar format manual — Complete tar(5): records, pax overrides, checksums, and extensions.
• RFC 8785 JSON Canonicalization Scheme — Complete JCS algorithm, Unicode/numeric rules, sorting, and vectors.
• SQLite storage, compatibility, and recovery — Official WAL fixes, synchronization, backup, salvage, schema compatibility, query controls, contention, optimization, and compaction.
• TOML 1 0 Specification — Complete language syntax, distinct from project semantics.
• TOML Schema Specification — Complete schema language, effective constraints, closure, and evaluation.
• Zstandard Compression and the application/zstd Media Type — Complete compression format, frames, dictionaries, and resource considerations.

Libraries, ABI, and toolchain behavior

• Apple Dynamic Library Design Guidelines — Loader versions, interface evolution, and the dlopen exception.
• libcxx Vendor Configuration — Runtime builds, matching ABI settings, visibility, and private installation.

Coverage

The catalog contains 34 records. Thirteen have complete source assets: eight retained standards/manuals and five Homebrew release/policy originals added in the 2026-09-26 review. Twenty are attributed technical or discussion accounts, including the SQLite documentation account added for DATABASE. The Mojave HIG record adds a historical website capture in the documentation library, with per-resource coverage. Complete assets retain their notices; the inventory names uncaptured dependencies and unresolved evidence.

The review recovered content from every primary source using direct HTTP or the web reader. Direct HTTP recovered Homebrew 6 after the web reader failed; Apple's forum returned an HTTP security challenge, so its account uses the web reader's visible thread. All eight existing complete assets matched fresh downloads byte for byte. Live branch/page accounts without immutable revision IDs remain dated snapshots, not evidence of earlier content. Discussion pages with collapsed comments remain partial even when their opening page loads successfully.

Read each record's claim links, source locators, context, interpretation, and omissions together. A link inside a complete source remains external unless separately captured. Full specification text does not imply that its dependencies, implementation, or runtime acceptance evidence is present. Historical comparison and package-download examples are tracked in the inventory.

Maintenance and verification

Use TEMPLATE.MD for new records and substantive revisions. Preserve older relied-upon editions when upstream changes. The archive grants no blanket copying exemption for technical documents. Retain per-source permissions and notices, including Homebrew's BSD-2-Clause notice for the added originals.

Sources marked incomplete cannot establish a validated implementation. New external implementation dependencies must add a record, applicable license, exact revision, and offline content in the same change.

Regenerate SHA256SUMS over every file in this directory except itself, sorted by filename. Run python tests/check_contracts.py and git diff --check. The contract check verifies asset coverage and bytes, not attribution, source accuracy, validator conformance, or runtime safety; those require the record-level review described in the template.

Source document