yigityildiz0 Product Tracking: Implementation Guide
Map an approved telemetry contract to the actual codebase without changing source code.
Workflow
- Read the approved tracking plan and the factual audit; list missing inputs instead of inventing them.
- Locate initialization, existing wrappers, framework boundaries, authentication transitions, and representative feature paths.
- Prefer one established wrapper or boundary per runtime. Explain any intentional exception.
- Map every planned event to a file, lifecycle point, required data source, and testable acceptance criterion.
- Describe rollout order, feature flags if already available, monitoring, failure isolation, and rollback.
Deliverable
Provide a guide with:
Prerequisites and exclusions
Architecture and ownership
Event-to-code mapping
Identity and consent integration
Test plan and fixtures
Rollout, observability, rollback
Open decisions
Guardrails
- Do not generate provider credentials, secrets, or network calls.
- Do not propose broad refactors solely for telemetry.
- Treat generated events as unimplemented until a code review and representative tests pass.