v2.7.0 — Ecosystem Trust and Compatibility Network¶

Purpose: Feature specification for Transparency, Advisories, and Revocation. Audience: product, architecture, engineering, security, operations, documentation, release, and AI coding agents Owner: Trust and Compatibility Maintainers Roadmap authority: docs/strategy/FORGEVENA_VERSIONED_PRODUCT_ROADMAP.md#v270--ecosystem-trust-and-compatibility-network Lifecycle: planned Review: before implementation and at every lifecycle promotion

Identity¶

Feature ID: transparency-advisory-revocation
Classification: committed
Owner: Trust and Compatibility Maintainers

Purpose and Problem¶

Record publisher identity, signatures, provenance, vulnerabilities, moderation, appeals, certification, expiry, and revocation.

Business and Developer Value¶

Users and organizations can make informed trust decisions and respond to incidents.

Architecture¶

Signed append-oriented transparency records feed policy and registry quarantine while preserving scoped confidentiality.

Dependencies¶

compatibility-evaluation-labs
v2.2 revocation

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¶

Revocation propagates predictably.
Appeals and corrections are auditable.
Trust and maturity remain distinct.

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¶

Transparency data may enable harassment.
False advisories can disrupt ecosystems.

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.