Skip to content

v2.4.0 — Publisher Platform and Ecosystem SDK

Purpose: Feature specification for Governed Publisher Lifecycle. Audience: product, architecture, engineering, security, operations, documentation, release, and AI coding agents Owner: Publisher Platform Maintainers Roadmap authority: docs/strategy/FORGEVENA_VERSIONED_PRODUCT_ROADMAP.md#v240--publisher-platform-and-ecosystem-sdk Lifecycle: planned Review: before implementation and at every lifecycle promotion

Identity

  • Feature ID: governed-publisher-lifecycle
  • Classification: committed
  • Owner: Publisher Platform Maintainers

Purpose and Problem

Support identity, staged publishing, ownership, recovery, disputes, vulnerabilities, deprecation, withdrawal, and revocation.

Business and Developer Value

The ecosystem can sustain trustworthy packages and publisher transitions.

Architecture

Publisher actions create signed transparency records and require policy, moderation, and recovery controls.

Dependencies

  • capability-studio-sdk

Configuration and User Flow

Configuration is schema-validated, secret-reference-only, previewable, exportable without secrets, and governed by scope. The user flow is inspect, preview, validate, approve, apply, verify, and roll back.

CLI, Dashboard, and API Flow

CLI, dashboard, SDK, and API surfaces call the same domain service. Structured responses include operation ID, status, warnings, planned changes, policy result, and evidence references. No interface may bypass consent or policy.

Security, Privacy, and Reliability

Permissions, data classes, trust roots, external effects, timeouts, retries, cancellation, audit, recovery, and rollback are explicit. Prompts, responses, tokens, credentials, and unapproved source content are excluded from logs and diagnostics.

Testing and Acceptance

  • Signed publication and promotion pass.
  • Ownership recovery resists account takeover.
  • Vulnerability and revocation workflows are tested.

Performance Targets

The feature must publish an approved baseline, remain within the platform's 20% regression budget, and define tighter latency, throughput, resource, and cost targets before preview.

Migration and Documentation

Migration is preview-first, versioned, reversible, and compatible with the previous two stable releases where applicable. CLI help, schemas, examples, troubleshooting, operations, security, and migration guidance ship with implementation.

Risks

  • Identity fraud.
  • Legal and moderation disputes.

Future Expansion

Expansion remains in the Evidence Funnel and requires a new feature ID or approved scope change; it cannot be inferred from this specification.