SSPACEAGEDOCUMENTATION/
Release and Assurance

SpaceAge Public Claims Audit

Updated Aug 27, 2026   |   2.5 KB   |   docs/Public_Claims_Audit.md

SpaceAge Public Claims Audit

Updated: 2026-08-04

Current Status

The shipping README.md has been replaced with current, conservative product language. Historical changelog material, deprecated Pad-proxy architecture, and future plug-in-hosting discussion no longer ship as the product introduction.

Resources/PublicClaimsRegistry.json binds the complete shipping README by SHA-256 and maps each present-tense claim to passed IDs in the canonical 72-check release ledger. Conditional Instrument and MIDI statements name the still-open checks and retain explicit beta qualifiers. MPE, MIDI 2.0, universal hardware compatibility, and third-party plug-in hosting are expressly excluded from current claims.

The longer Marketing_Copy_Drafts.md, Synth_Lineup_Marketing.md, and SpaceAge_Feature_Outline.md are classified and hash-bound as internal material. Their disclaimers must remain present, and they are not copied into the customer package by the current packaging workflow.

Automated Contract

Run tools/test-public-claims.ps1 to verify:

  • The exact shipping and internal source inventory.
  • SHA-256 identity of every reviewed source.
  • Unique typed claim IDs.
  • Exact claim text in the shipping README.
  • Passed readiness evidence for every present-tense claim.
  • Visible qualifiers for every conditional claim.
  • Explicit negative boundaries for unimplemented protocols and hosting.

Public packaging must eventually run the validator with -RequireHumanApproval. The registry intentionally remains pending, and release check R08 remains open, until Shane reviews the exact customer-facing README and any About, website, store, Kickstarter, manual, and release-note copy that will actually ship or be published.

Human Approval Checklist

  • Read the complete shipping README as a customer, not as a developer.
  • Confirm every current statement describes behavior demonstrated in the intended release candidate.
  • Confirm every beta limitation is understandable and prominent enough.
  • Compare the About page, website, store listing, Kickstarter copy, manual, and release notes with this registry.
  • Remove or qualify claims that imply true MPE, MIDI 2.0, universal hardware support, zero-latency performance, third-party plug-in hosting, or completed clean-machine/host validation.
  • Set human_review_status to approved only after reviewing the exact hash-bound sources.
  • Mark R08 passed only after the public surfaces and registry agree.