Skip to content

Release cycle: principal layer + tiered reporting end-to-end (3.2) #7075

Description

@bokelley

Tracking issue for the full cycle — protocol → RC → SDKs → reference implementations → docs → training → pilots. The bet: the principal layer and tiered reporting ship experimental in the 3.2 RC, the largest implementer adopts immediately (scope3data/agentic-api#12538), and the RC window is the cleanup loop before 3.2 stable.

Protocol (this repo)

SDKs (regenerate from the RC bundle, not branches)

Reference implementations

Training

  • Certification/curriculum coverage (companion issue)

Pilots

  • Core-tier pilots with partner sales agents; success metric: "implemented Core in N days with zero warehouse code"

Stable-promotion gates (before 3.2 stable / ratification)

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    claude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.epicMajor deliverable — auto-adds to roadmap boardspec / protocol

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions