Skip to content

P3: REC automation write/readback probes #34

Open
Open
P3: REC automation write/readback probes#34
Labels
api-dependentDepends on live FL API evidence or known API limitations.area:apiFL Studio API capability, limitation, or probe-related work.area:safetySafety contract, rollback, readback, audit, or verification work.github-source-of-truthTracked in GitHub as source of truth for generated Markdown snapshots.priority:p3Low priority or later.write-safe-requiredAny persistent write must use snapshot, readback, changelog, and rollback.
Milestone
Experimental/API-dependent

Description

@thunderdew-dawn
thunderdew-dawn
opened on Jun 8, 2026

Source: ROADMAP.md P3.

Scope:

  • Probe REC automation write/readback behavior safely.
  • Treat automation writes as unsafe until explicit snapshot/readback/rollback behavior is proven.

Acceptance criteria:

  • Probe checks API presence, target selection/focus, indexing, readback timing, state, and rollback.
  • No persistent user-facing automation write ships before safety proof.
  • Findings update Knowledgebase/API audit.

Activity

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

    api-dependentDepends on live FL API evidence or known API limitations.area:apiFL Studio API capability, limitation, or probe-related work.area:safetySafety contract, rollback, readback, audit, or verification work.github-source-of-truthTracked in GitHub as source of truth for generated Markdown snapshots.priority:p3Low priority or later.write-safe-requiredAny persistent write must use snapshot, readback, changelog, and rollback.

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions