EVIDENCE CASE
Hardening Space voice credential authorization
A real PING authorization hardening pass moved active Space membership validation into the media credential trust boundary, then repaired a stale advisory-lock test double without another production change.
01
Problem
A Space voice credential issuer was relying too heavily on an upstream join claim. Make the credential boundary independently prove that the requester is still an active member of the Space tied to the voice channel, while preserving established Server and DM behavior.
02
Methods applied
- 01Selecting Working MethodsPrevents skill overload and overlap while preserving clear ownership between discovery, implementation, verification, review, and delivery.
- 02Reviewing API SecurityFinds API-specific security failures that generic web review often misses, especially authorization and business-invariant violations.
- 03Building Regression TestsMakes bug fixes durable and proves the new test actually detects the defect instead of merely passing alongside the fix.
- 04Testing Integration BoundariesFinds serialization, persistence, protocol, and failure-mode defects that mocks and isolated unit tests cannot prove away.
- 05Shipping GitHub and Vercel ChangesMoves repository changes toward review and release without mixing unrelated work, duplicating pull requests, or overstating deployment readiness.
Decision record
- 01
Put authorization at the credential boundary
Resolve the voice channel back to its Space and require an active SpaceMember record before issuing Space media credentials instead of treating the upstream join claim as sufficient proof.
- 02
Prove the unauthorized path first
Encode the stale or unauthorized Space membership claim as a deliberate RED regression before changing production code.
- 03
Diagnose the post-merge failure separately
When main exposed a stale advisory-lock transaction fake, keep the security fix intact and repair only the test double that no longer represented the credential boundary contract.
- 04
Verify the final main merge
Count the case only after the test-only follow-up merged and the canonical main workflow passed tests, formatting, lint, typecheck, and build on the final merge commit.
03
Verification
Treat this report as evidence for the methods and verification shown here. Related-pack overlap alone is not proof that a pack was used or fully validated.
04
Result
- 01
Space voice credential issuance now independently verifies active membership in the Space tied to the channel.
- 02
The security regression moved from deliberate RED to GREEN while existing Server and DM credential semantics remained covered.
- 03
The only post-merge failure was isolated to a stale advisory-lock test double and repaired in a test-only follow-up with no additional production change.
- 04
The final main-branch workflow passed tests, formatting, lint, typecheck, and build before this case was recorded.