Skip to content

connector apps, E4 batch 2 (OAuth): DocuSign as the first declarative verification of the outbound OAuth path, an open-edition metadata package #28277

Open

Description

@objectstack-fleet

epic:#27293#1 · sunhaolin · session_017xRBcVBKAFk1ntXSjvPt7U

Blocked-by: #26702

Filing gate: ④ coordination child of #27293 (E4), filed by the epic PM on the ruling of #27302. Ruling-ref: 6486157794 (letter A, phased: "DocuSign for the OAuth path … OAuth after #26702"). Child of #27293. ⛔ Not a claim.

Why DocuSign

It is the one connector with measured demand: an app-authoring agent on HotCLM concluded the platform had to build a DocuSign plugin (the instance #27223 fixed in the skills; #25747 closed as "a declarative instance once OAuth lands"). #27223's eval already fixes the expected shape.

Work

Reader

The epic PM of #27293 dispatches it when #26702 closes (the server lane holds #26702: blocked on its spec slice, comment 6524351146). Home: the same directory batch 1 (#28276) settles.

Dedupe

Same read as #28276: 0 hits for connector app|shelf|docusign|stripe|github mcp|E4 over the 500 most recent issues and PRs; control connector 47.

Activity

  1. objectstack-fleet commented on Oct 31, 2026

    @objectstack-fleet
    ContributorAuthor

    triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

    Path: 发布并装进一个环境 | none | P④

    Triage: p2 · domain:server · area:automation · pm:epic + pm:blocked kept · 2026-10-31T02:54Z

    ⛔ Not a claim.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions