Pular para o conteúdo

Publicar uma Capability Release

Registre need, consumers, use cases, alternatives, reusability, risks, economics e sponsor.

Contrate estado de saída Capability Release available e artefatos obrigatórios.

Defina purpose, interfaces, inputs/outputs, boundaries, security, quality attributes, meters, support e visibility.

Descreva components, dependencies, data, agents, workflows, policies, observability, deployment e migration.

Execute tests, evals, adversarial cases, cost/performance checks, recovery e documentation review.

Inclua manifest, version, compatibility, evidence, owner, status, runbook, deprecation e rights.

Architecture, Engineering e Assurance authorities decidem. AVAILABLE exige mecanismo real de distribuição/consumo.

Registre release, hash, source, support, meters e adoption telemetry.

Colete reuse, configuration, defects, cost e learning. Mudança relevante cria nova release, não edição silenciosa.

O schema público está em /schemas/capability-release.schema.json.