Skip to content

Execute partner outreach (rc1 Tier-2 B follow-up) #472

Description

@trilamsr

Context

docs/partner-outreach.md (landed in #470) ships the artifact: persona list (P1-P12 archetypes), cold-pitch template, talking points, tracker shape, numeric success criteria.

This issue tracks the execution half — the artifact alone does not flip Tier-2 B to ☑ shipped. The cut-criterion's gate script counts non-placeholder rows in the §Tracker table of docs/partner-outreach.md; ≥3 real rows is the threshold.

Definition of done

  • SC-1: ≥5 distinct rows in the §Tracker with status ∈ {contacted, meeting-set, feedback-received, pilot-deploy-attempted, declined, deferred} (rc1 may ship with this open).
  • SC-2: ≥2 rows with status ∈ {meeting-set, feedback-received, pilot-deploy-attempted} (target pre-GA).
  • SC-3: ≥1 row with status = pilot-deploy-attempted + corresponding case-study writeup at docs/case-studies/<operator>.md (v1.0.0 GA blocker per docs/RELEASE-CHECKLIST.md GA gates).
  • Tier-2 B cut criterion flips ☐ planned → ⧗ in progress → ☑ shipped on make cut-criteria-render (auto, no manual edit).

Process

Each conversation lands as a PR that:

  1. Adds a row to docs/partner-outreach.md §Tracker (one row per person, not per org; one-line notes; no private contact info).
  2. Re-runs make cut-criteria-render if any §Tracker status crosses the gate threshold.
  3. References this issue in the PR body.

Why this is rc1-prep

Tier-2 items unblock the GA path; rc1 ships with Tier-2 B at ⧗ in progress (artifact ready, conversations not yet started). This issue is the operational lever between "artifact published" and "GA gate cleared."

Not in scope here

Metadata

Metadata

Assignees

No one assigned

    Labels

    external-clockBlocked on out-of-repo staterc1-prepv1.0-rc1 preparation tasks per docs/v1-rc1-operational-gaps.md

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions