Skip to main content

FR-079: Install feedback submission path and governance

Type: Feature Request (FR)
ID: FR-079
Submitted: 2026-04-09
Submitted By: User
Priority: CRITICAL
Severity: HIGH
Status: COMPLETE

Implementing Task: E6:S07:T112

Summary​

Define and implement a first-class feedback submission path that converts local install telemetry artifacts into high-quality, governable feedback submissions that AI Dev Kit maintainers can triage and use for continuous product hardening.

Problem Statement​

Even with high-fidelity local install event logging, quality feedback loops remain weak unless there is a clear submission contract and governance path. External adopters need a deterministic way to package, validate, and submit install evidence while preserving privacy and data integrity.

Requirements​

Functional Requirements​

  • FR-079-F1: Define a canonical submission artifact schema and versioning contract for feedback payloads.
  • FR-079-F2: Provide a deterministic submission workflow (CLI and/or documented process) for sending install feedback artifacts to maintainers.
  • FR-079-F3: Include provenance/correlation fields required to tie submissions to local install runs (install_run_id, framework/version context, environment summary).
  • FR-079-F4: Add submission preflight validation (required fields, schema compatibility, payload completeness).
  • FR-079-F5: Define clear submission outcomes (accepted, rejected, needs-redaction, needs-more-context) and user-visible diagnostics.
  • FR-079-F6: Document maintainer intake/triage path and mapping from submission payloads to FR/BR workflows.

Non-Functional Requirements​

  • FR-079-NF1: Enforce privacy and security controls for payload handling (redaction, safe defaults, no secret leakage).
  • FR-079-NF2: Ensure submission process is resilient to partial failures and provides deterministic retry guidance.
  • FR-079-NF3: Keep submission UX concise enough for external adopters while preserving forensic usefulness.
  • FR-079-NF4: Maintain compatibility boundaries with FR-078 logging artifacts and schema evolution policy.

Acceptance Criteria​

  • Submission workflow can package and validate telemetry from a logged install run and produce deterministic outcomes.
  • Rejected submissions provide actionable diagnostics and remediation guidance.
  • Maintainer triage documentation can map payload fields to reproducible investigation steps.
  • Redaction/security tests confirm payload safety constraints.
  • FR-078 and FR-079 boundaries are explicit and non-overlapping.

Scope Analysis​

Problem Domain: Feedback operations, submission governance, maintainer triage
Affected Areas:

  • CLI and submission workflow docs
  • Validation and schema tooling
  • Maintainer intake guidance and FR/BR mapping
  • Security/redaction controls for outbound payloads

Estimated Complexity:

  • Simple (1-3 days)
  • Medium (1 week)
  • Complex (2+ weeks)
  • Very Complex (1+ month)
  • FR-078 - Local event-contract logging responsibility
  • FR-047 - Baseline install logging
  • FR-003 - Adoption telemetry goals

Release trace​

  • v0.6.7.112+2 (SemVer v0.4.726+2, E6:S07:T112, RW with --art): Implemented deterministic feedback payload prepare/validate/submit flow with outcome diagnostics, redaction checks, local submission receipt generation, and user docs/tests.