EVIDENCE CASE
Removing a deprecated Cosmic SDK through evidence-led codebase analysis
A real Rocket maintenance pass used the complete Codebase Intelligence pack to separate live Payload runtime ownership from historical Cosmic compatibility and safely remove one obsolete SDK write path.
01
Problem
Determine whether Cosmic references still represented a live public-runtime dependency after the Payload cutover, then remove only what repository evidence proved obsolete without breaking migration compatibility, local fallbacks, database behavior, or UI.
02
Methods applied
- 01Mapping Existing Codebase StructureReplaces architectural guesswork with a scoped structural map whose claims point back to concrete code and configuration evidence.
- 02Investigating a Codebase SemanticallyLocates the code that owns a behavior without requiring the requester to know its symbol names, filenames, or repository vocabulary in advance.
- 03Tracing Code Execution PathsMakes runtime-relevant flow reviewable without overstating reachability, correlation, or textual matches as proven behavior.
- 04Analyzing Change Blast RadiusSurfaces evidence-backed risk and unresolved impact before a team chooses implementation slices or protection strategy.
- 05Planning Codebase Changes with EvidenceGives architecture, engineering planning, testing, or debugging a traceable handoff grounded in the codebase before executable work is designed.
Decision record
- 01
Map ownership before deleting legacy references
Trace Home and Publications through Payload and their local fallbacks before treating repository-wide Cosmic search hits as one dependency surface.
- 02
Separate compatibility from package dependency
Keep the historical migration path because it reads Cosmic through native fetch, while rejecting migration and CDN configuration hits as proof that the deprecated SDK is still required.
- 03
Bound the blast radius to the observed writer
Remove only the cosmicjs dependency, populate npm entrypoint, obsolete population writer, and derived lockfile records; leave runtime loaders, migration semantics, schema, database, and visual code untouched.
- 04
Prove the boundary with RED→GREEN CI
Start with a regression contract that fails on the existing SDK, regenerate the lockfile through npm, and accept the cleanup only after the canonical Rocket pipeline passes on the final evidence HEAD.
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
The deprecated cosmicjs SDK and obsolete Cosmic write-only population path were removed.
- 02
Historical Cosmic-to-Payload migration remains available through native fetch.
- 03
Public Home and Publications remain Payload-first with their local fallback behavior intact.
- 04
The final Rocket CI passed dependency install, Payload type drift, full tests, lint, typecheck, and production build.
- 05
All five Codebase Intelligence methods contributed to the decision, blast-radius boundary, implementation plan, or verification evidence.