Skip to content

refactor(aidd-telemetry): make measurement consent discoverable end to end #873

Closed

Description

@blafourcade

Problem

The first aidd-telemetry skill is named 00-init, although it owns the full consent lifecycle around measurement: allowing project measurement, verifying it, choosing whether a person is identified, withdrawing that identity, and erasing measured data.

The current skill description also routes people who want to stop measurement, but none of its actions calls the already implemented and tested aidd telemetry off. Renaming alone would improve discovery while leaving that promised exit incomplete.

Scope

  • Rename the skill directory and skill identity from 00-init to 00-consent.
  • Name the router Consent and describe the responsibility rather than the first moment of its lifecycle.
  • Add a route and action for stopping project measurement through aidd telemetry off.
  • Before stopping, distinguish project measurement from withdrawing this person's identity and from erasing stored measurements.
  • Relay that stopping measurement keeps data already measured, leaves the separate identity choice unchanged, and can be reversed later.
  • Keep the existing enable, verification, identity, withdrawal, and erasure behavior unchanged.
  • Update every live reference in the same change: plugin README and catalog, framework documentation and generated prompt catalog, tests, fixtures, golden output, and any skill or script that names the old identity.
  • Preserve historical telemetry records carrying 00-init as data. They remain reportable and are not rewritten.

The new description must cover all entry points: allow or stop project measurement, verify recording, attach or withdraw a person's identity, and preview or erase locally measured data.

Acceptance criteria

  • The installed skill identity is aidd-telemetry:00-consent; no active 00-init skill alias remains.
  • The description routes requests to start or stop measurement, verify recording, attach or withdraw identity, and erase measured data.
  • A request to stop project measurement runs aidd telemetry off and accurately explains what stops and what remains.
  • Stopping project measurement never withdraws the person's identity and never deletes previously measured data.
  • Identity withdrawal and measured-data erasure remain separate choices with their existing confirmation and safety behavior.
  • Every live repository reference is updated in the same change, while historical changelogs and stored run records are left intact.
  • 01-cost and 02-check keep their current names and responsibilities.
  • Focused skill-contract, documentation, fixture, and generated-catalog tests pass.

Evidence

  • plugins/aidd-telemetry/skills/00-init/SKILL.md already routes enabling, verification, identity, withdrawal, and erasure.
  • aidd telemetry off is implemented and tested; it turns off the project switch and commit trailer integration without deleting existing measurements.
  • The current skill description already claims requests to stop are in scope, but no current action handles them.

Out of scope

  • Changing CLI behavior, telemetry storage, record schemas, or consent semantics.
  • Rewriting historical telemetry records from 00-init to 00-consent.
  • Renaming or changing 01-cost or 02-check.
  • Splitting withdrawal or erasure into a separate skill.

Activity

  1. added theissue type on Sep 22, 2026
  2. changed the title [-]refactor(aidd-telemetry): the consent skill is named after its first minute[/-] [+]refactor(aidd-telemetry): make measurement consent discoverable end to end[/+] on Sep 24, 2026
  3. moved this from Ideation to Todo in AIDD Roadmapon Sep 24, 2026
  4. blafourcade commented on Oct 15, 2026

    @blafourcade
    ContributorAuthor

    Done in #993: aidd telemetry status says whether a clone is measured, and the plugin README walks consent end to end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Priority

    Medium

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions