Skip to content

Track owning-library remediation and final qualification #13

Description

@stefan-jansen

Create one ecosystem tracking issue with a checklist linking the owning issues in Data, Engineer,
Backtest, Specs, Live, Diagnostic, and Models. Each library issue is created and closed in its public
release repository by its dedicated agent; sidecars hold private working state and local drafts
only. Website, Skills, and ITCH Parser findings are likewise filed in their owning repositories.

After the seven agents finish, collect their pull requests, CI results, releases, sidecar states,
instruction approvals, and deployed documentation evidence. Run the ecosystem audit against current
default branches and latest PyPI artifacts. Confirm that obsolete identities are gone, approved
compatibility aliases still pass, all common gates pass, and library-specific checks remain intact.
Regenerate current status and retain a dated qualification snapshot. Done means all seven checklist
items are verified and closed, or each remaining item records an exact unavailable user decision,
credential, or third-party condition after all independent work is complete.

Library remediation checklist

  • Data owning issue and remediation PR
  • Engineer owning issue and remediation PR
  • Backtest owning issue and remediation PR
  • Specs owning issue and remediation PR
  • Live owning issue and remediation PR
  • Diagnostic owning issue and remediation PR
  • Models owning issue and remediation PR

Plan reference: .workspace/work/ecosystem-standardization/plan.md - Issue 5 in milestone
2026-09-08 - Public library consistency.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions