Skip to content

AIFACTORY-FEAT-007: AgentRegistryService: complete delivery

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.

A design artefact, not a tracker

This backlog is generated from model/backlog/ and validated against the architecture model. No work item exists in any tracker, and no item carries a date, an estimate or an assignee (ADR-0029).

Epic Control Plane (PF-01) · Increment I4 Trust and accountability · State elaborated · Route backend-developer · Build order 124 of 185 (Factory code)

AgentRegistryService is the service of bounded context BC-04 (Asset Publication). Publishes immutable releases of agents, skills, tools, workflows, policies and model profiles with their full dependency closure, hashes and evaluation evidence; serves release resolution to Run Control and release loading to the runtime (BC-04). This feature completes the service after its thin delivery in I1: every aggregate, operation, event and worker of the model. Repository ConnectSoft.AI.SoftwareFactory.AgentRegistryService.

Delivers AgentRegistryService (complete)
Stubs —
Realizes adrs: ADR-0002, ADR-0021, ADR-0022, ADR-0023
Requirements FR-02, FR-11, FUX-02, FUX-10, NFR-02, NFR-11, NFR-13, XL-02, XL-08, XL-15
Depends on AIFACTORY-FEAT-001 AgentRegistryService: thin delivery for the first outcome
AIFACTORY-FEAT-189 AgentRegistryService: the publication path of releases from I2
Sources model/services/control-plane/AgentRegistryService.yaml

Scenarios to trace (15, catalog): SCN-AgentRegistryService-001 ✓, SCN-AgentRegistryService-002 ✓, SCN-AgentRegistryService-003 ✓, SCN-AgentRegistryService-004 ✓, SCN-AgentRegistryService-014 ✓, SCN-AgentRegistryService-005 ✓, SCN-AgentRegistryService-006 ✓, SCN-AgentRegistryService-007 ✓, SCN-AgentRegistryService-008 ✓, SCN-AgentRegistryService-009 ✓, SCN-AgentRegistryService-010 ✓, SCN-AgentRegistryService-011 ✓, SCN-AgentRegistryService-012 ✓, SCN-AgentRegistryService-013 ✓, SCN-AgentRegistryService-015 ✓

AIFACTORY-US-042: A published release is immutable, carries its whole closure and, from I4, its evaluation evidence wherever a suite exists

behavior · persona asset-maintainer As an asset maintainer, I want my releases published with their evaluation evidence where a suite exists and taken out of use only with a stated policy, so that a run that pins a release always executes exactly what was evaluated and approved.

This is the integration PBI of the complete delivery. The publication path, from a commit in Git to a Published release with its whole closure approved by someone who is not its author, is delivered in I2 by feature agent-registry-service-publication (D140); this feature completes the service on the same contract, so that a run that pins a release always executes exactly what was evaluated wherever evaluation can exist. This PBI proves on a deployed estate that the parts of the complete delivery work together. With the complete QualityScoreService of I4, a candidate of an asset kind that has an evaluation suite carries a passed evaluation record or a recorded waiver before it is published, and Publication:Gates:RequireEvaluation takes effect (ADR-0021, D117, D140, AIFACTORY-US-1562). The twenty-six seeded Draft releases of the thin delivery are published through that gate and the seed is retired, and a release published before I4 without an evaluation record, of a kind for which a suite exists, is resubmitted through the gate as a new version while the earlier release stays immutable and loadable by its id (AIFACTORY-US-421, D140). A Published release is deprecated, and a Published or a Deprecated release is revoked, by a Platform admin with a required reason and an in-flight policy for the runs that pinned it (AIFACTORY-US-417 for the deprecation and the revocation of the aggregate, AIFACTORY-US-536 for the REST command RevokeRelease); a revoked release is in the state Revoked and is never pinned, aliased or published again (D119). An alias that points at a release when it is revoked stays in place and visible, and a resolution through it, or by the id of the Revoked release, answers FAILED_PRECONDITION naming the revoked release until an administrator moves the alias (D121, D123). RunControlService refuses new runs on a Deprecated or a Revoked release and applies the stated in-flight policy to every run that is not terminal and whose pinned release closure holds the revoked release, child runs included: finish lets the runs continue to their end, drain lets the step that is running finish, dispatches no further step and ends the run Cancelled with the reason release-revoked, and revoke cancels the run at once with the same reason while the runtime interrupts its attempt (D123, AIFACTORY-US-736). The service opens the Draft release of an accepted learning proposal and announces it with LearningReleaseOpened (AIFACTORY-US-1493, D131), and handles what other services announce about releases (AIFACTORY-US-420). A deprecation and a revocation each leave an audit-evidence-v1 record that is written to the outbox in the transaction of the command, on the topic audit.evidence.v1.evidence-submitted under the run event envelope, from which AuditService appends it with its command SubmitEvidence (D115, D117). The two REST commands of the Platform admin are reached through ControlPlaneApi under factory.assets.publish; a release of another tenant is answered 404, and a caller with the scope but without the Platform admin role 403 (ADR-0015). Manifests never contain secrets.

Acceptance criteria

AC1 Given an agent candidate of a kind with an evaluation suite submitted through AgentRegistryService/SubmitRelease on the deployed estate, when QualityScoreService announces QualityScoreService/EvaluationCompleted with the verdict passed and a Reviewer who is not the submitter grants the publication approval, then the AgentRegistryService/AssetRelease is Published with its evaluation record reference and its approval; given a second candidate of that kind whose verdict is failed, when AgentRegistryService/PublishRelease is called, then the answer is 412 with the failing gate named and nothing is published (ADR-0021, D140).
AC2 Given a release Published before I4 without an evaluation record, of a kind for which a suite exists, when any operation tries to change its content, then the change is refused and its manifest is unchanged, and when it is resubmitted through the gate as a new version, then a new release id is Published with its evaluation record and the earlier release is still streamed by its id through AgentRegistryService/AssetPublication.LoadRelease (FR-02, D140).
AC3 Given a Published release that a non-terminal run pinned and a second Published release, when a Platform admin deprecates the second through AgentRegistryService/DeprecateRelease and revokes the first through AgentRegistryService/RevokeRelease with the in-flight policy revoke, then AgentRegistryService/AssetReleaseDeprecated and AgentRegistryService/AssetReleaseRevoked are published under the run event envelope with an audit-evidence-v1 record each, the pinned run ends Cancelled with the reason release-revoked, RunControlService/SubmitRun answers 409 for both releases, and AgentRegistryService/AssetPublication.ResolveRelease answers FAILED_PRECONDITION naming the revoked release, by its id and through its alias (D119, D121, D123).
AC4 Given FeedbackService/LearningProposalDecided with the state Accepted for an asset of the tenant, when the service handles it, then one Draft AgentRegistryService/AssetRelease keeps the proposal id, AgentRegistryService/LearningReleaseOpened announces its release id with the proposal id, and that release reaches Published only through AgentRegistryService/SubmitRelease and the gate (D131, ADR-0021).
AC5 Given the service descriptor of the repository and an empty store, when the contract test compares it with the hosted surface and the service starts, then the eight REST operations and the two gRPC methods of model/services/control-plane/AgentRegistryService.yaml are hosted with their scope, side-effect class, idempotency and response codes, the outbox holds only the five event types of the aggregate and the audit-evidence-v1 records of a publication, a deprecation and a revocation, and the service registers no release by itself (ADR-0014, ADR-0028).
Traces: services AgentRegistryService, RunControlService, QualityScoreService, FeedbackService
Traces: aggregates AgentRegistryService/AssetRelease
Traces: apis AgentRegistryService/SubmitRelease, AgentRegistryService/PublishRelease, AgentRegistryService/DeprecateRelease, AgentRegistryService/RevokeRelease, AgentRegistryService/AssetPublication.ResolveRelease, AgentRegistryService/AssetPublication.LoadRelease, RunControlService/SubmitRun
Traces: events QualityScoreService/EvaluationCompleted, AgentRegistryService/AssetReleaseDeprecated, AgentRegistryService/AssetReleaseRevoked, FeedbackService/LearningProposalDecided, AgentRegistryService/LearningReleaseOpened
Traces: descriptors release-manifest-v1, audit-evidence-v1, run-event-envelope-v1
Traces: adrs ADR-0014, ADR-0015, ADR-0021, ADR-0028
Traces: requirements FR-02
Depends on AIFACTORY-US-1562, AIFACTORY-US-1493, AIFACTORY-US-417, AIFACTORY-US-420, AIFACTORY-US-421, AIFACTORY-US-536, AIFACTORY-US-736, feature:agent-registry-service-publication, feature:run-control-service, feature:quality-score-service-complete, feature:feedback-service, feature:component-base-template-factory-profile, feature:component-audit-factory-evidence, feature:contracts-package
Sources model/services/control-plane/AgentRegistryService.yaml, docs/planes/control/services/agent-registry-service/index.md#context-and-boundaries, docs/planes/control/registries.md, docs/architecture/adr/0021-quality-gates.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-696 Verify immutable-release-with-closure by running the declared command on the deployed estate verification Run dotnet test -c Release --filter "Category=Acceptance&Feature=CompleteDelivery" in the pipeline of the repository against the deployed QualityScoreService, RunControlService and FeedbackService; a zero-match filter counts as a failure; the run passes and proves AC1 to AC5 of AIFACTORY-US-042, that is a release published with its evaluation record and a failed candidate refused with 412, a release published before I4 left unchanged and resubmitted as a new version, a deprecation and a revocation with their events, their evidence, the cancelled pinned run and the refused submissions and resolutions, the Draft release of an accepted learning proposal published through the gate, and the hosted surface of the complete service against the service descriptor with no release registered on an empty store. ConnectSoft.AI.SoftwareFactory.AgentRegistryService

AIFACTORY-US-1562: Attach the evaluation evidence to a candidate and publish a release of a kind with a suite only with a passed verdict or a recorded waiver

behavior · persona reviewer As a reviewer, I want a candidate of an asset kind that has an evaluation suite to reach my approval only with its verdict attached and to be published only with its evidence, so that from I4 Published means evidenced wherever evidence can exist.

The publication path of I2, feature agent-registry-service-publication, publishes a release on its closure and its approval, because no evaluation suite exists before the complete QualityScoreService of I4 (D140). This PBI adds the evaluation gate of ADR-0021 with the complete delivery, and with it the option Publication:Gates:RequireEvaluation takes effect (D140). The evidence rule holds only where an evaluation suite exists for the asset kind: an agent, skill or workflow release needs a passed evaluation record or a recorded waiver (ADR-0021 decision 2) and a ModelProfile release its capability scorecard (ADR-0021 decision 1), while a release of a kind for which no suite exists keeps the path of I2 and is published on its closure and its approval alone (D117). After a submission, QualityScoreService evaluates a candidate with the suite of its kind, where one exists, and announces QualityScoreService/EvaluationCompleted with the target release, the verdict, the evidence reference and its kind. The inbox handler RecordEvaluationEvidence attaches the verdict and evaluationRecordRef to the InReview release the event names, idempotently on the event id, when the kind is release-gate or, for a ModelProfile release, capability-suite, whose record is the scorecard. A failed or inconclusive verdict is attached and requests no approval, and an event of another kind, for a release that is not InReview or for a release outside the tenant of the envelope is acknowledged without effect, because a Published release is immutable. From this delivery a candidate of a kind with a suite no longer has its publication approval requested when its closure is resolved: the request of the publication path, through RunControl.RequestApproval of RunControlService with the subject kind asset-release and the release id (D135, D140), is made when the verdict is passed or waived, the closure is resolved and no blocking finding is open, as the sequence on the service page shows (D21). How the registry learns that no suite exists for a kind is not stated by the model and is reported to the owner; the fixture of the acceptance suite states it per kind. The rule GatesPassedAndApproved of PublishRelease and of PublishOnApproval gains the evidence check: where a suite exists for the asset kind, its evidence exists while Publication:Gates:RequireEvaluation is true, and otherwise PublishRelease answers 412 naming the evidence gate, PublishOnApproval does not publish and connectsoft.factory.releases.blocked is incremented with the reason. The gate checks only the evidence this service recorded itself through RecordEvaluationEvidence; PublishRelease and PublishOnApproval make no synchronous call to QualityScoreService, whose Evaluation.GetVerdict is not read at the gate (D141). A release published before I4 without an evaluation record for a kind with a suite stays Published and immutable; it is resubmitted through this gate as a new version by AIFACTORY-US-421 (D140).

Acceptance criteria

AC1 Given an InReview release of a kind with a suite whose closure is resolved without a blocking finding, when QualityScoreService/EvaluationCompleted of kind release-gate with the verdict passed arrives for it, then RecordEvaluationEvidence attaches the verdict and evaluationRecordRef once per event id and only then the publication approval is requested through RunControlService/RunControl.RequestApproval with the subject kind asset-release and the release id (D135, D140); given a ModelProfile release, then the event of kind capability-suite attaches its scorecard the same way (ADR-0021).
AC2 Given a failed or inconclusive verdict, an event of another kind, an event for a release that is not InReview, or one for a release outside the tenant of the envelope, when QualityScoreService/EvaluationCompleted is handled, then the failed or inconclusive verdict is attached and requests no approval and the other three are acknowledged without effect; given a candidate of a kind for which the fixture holds no suite, then its approval is requested as soon as its closure is resolved, as in the publication path (D117, ADR-0021).
AC3 Given Publication:Gates:RequireEvaluation true and an approved InReview release of a kind with a suite without a passed evaluation record or a recorded waiver, when AgentRegistryService/PublishRelease is called or RunControlService/ApprovalDecided grants its approval, then the answer is 412 naming the evidence gate, decided on the evidence recorded by RecordEvaluationEvidence with no synchronous call to QualityScoreService (D141), PublishOnApproval does not publish, the release stays InReview and connectsoft.factory.releases.blocked is incremented with the reason; given the same release with a passed record or a recorded waiver, then it is Published with its evaluationRecordRef (ADR-0021, model/services/control-plane/AgentRegistryService.yaml).
AC4 Given the service started with Publication:Gates:RequireEvaluation false, when the release of AC3 without evidence is published, then it is Published on its closure and its approval; given a release Published before I4 without an evaluation record, when AgentRegistryService/GetRelease is called after the gate is active, then it is returned unchanged with no evaluation record (D140, FR-02).
Traces: services AgentRegistryService, QualityScoreService, RunControlService
Traces: aggregates AgentRegistryService/AssetRelease
Traces: apis AgentRegistryService/PublishRelease, AgentRegistryService/GetRelease, RunControlService/RunControl.RequestApproval
Traces: events QualityScoreService/EvaluationCompleted, RunControlService/ApprovalDecided
Traces: descriptors release-manifest-v1, run-event-envelope-v1
Traces: adrs ADR-0014, ADR-0015, ADR-0021
Traces: requirements FR-02, NFR-11, XL-08
Depends on feature:agent-registry-service-publication, feature:quality-score-service-complete, feature:run-control-service, feature:contracts-package
Sources model/services/control-plane/AgentRegistryService.yaml, model/services/observability/QualityScoreService.yaml, docs/architecture/quality-gates.md, docs/architecture/adr/0021-quality-gates.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-6341 Inbox handler RecordEvaluationEvidence and the approval request on a passed or waived verdict implementation RecordEvaluationEvidence, subscribed to EvaluationCompleted of QualityScoreService in the messaging profile, attaches the verdict and the evidence reference to the InReview release the event names, once per event id, for the kind release-gate and, for a ModelProfile release, capability-suite; it acknowledges without effect an event of another kind, for a release that is not InReview or for a release outside the tenant of the envelope; for a candidate of a kind with a suite the publication approval request of AIFACTORY-TASK-1687, with the subject kind asset-release and the release id (D135, D140), is made on a passed or waived verdict of a candidate with a resolved closure and no blocking finding instead of on the resolution of its closure, a failed or inconclusive verdict requests none, and a candidate of a kind without a suite keeps the request on the resolution of its closure (D117). ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-6342 Evidence check of GatesPassedAndApproved under the option Publication:Gates:RequireEvaluation implementation The option Publication:Gates:RequireEvaluation is bound with its default true and read at start (D140); the domain model of AIFACTORY-TASK-364 gains the invariant that a release of a kind with a suite is Published only with a passed evaluation record or a recorded waiver while the option is true (ADR-0021 decisions 1 and 2), checked on the evidence RecordEvaluationEvidence recorded and with no synchronous call to QualityScoreService (D141); PublishRelease answers 412 naming the evidence gate and PublishOnApproval does not publish when the evidence is missing, both increment connectsoft.factory.releases.blocked with the reason, and a Published release keeps the evaluationRecordRef it was published with. ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-6343 Verify the evaluation evidence and its gate through the acceptance suite verification Run dotnet test -c Release --filter "Category=Acceptance&Feature=EvaluationGate"; a zero-match filter counts as a failure; the tests prove AC1 to AC4 of AIFACTORY-US-1562 with contract fixtures of QualityScoreService/EvaluationCompleted and a fake of RunControl.RequestApproval: the verdict attached once per event id and the approval requested only after a passed verdict, the scorecard of a ModelProfile release, the failed verdict and the three events acknowledged without effect, the kind without a suite requested on its closure, the 412 of the evidence gate and the refusal of PublishOnApproval with the counter, the publication with a record or a waiver, the option set to false and a release published before I4 read unchanged. ConnectSoft.AI.SoftwareFactory.AgentRegistryService

AIFACTORY-US-417: Deprecate a Published release with a reason and an in-flight policy and revoke one for a security or policy reason, as a Platform admin

behavior · persona platform-admin As a platform admin, I want to take a release out of use with a stated reason and a stated policy for the runs that already pinned it, so that no new run pins it and no running run is silently moved to another release.

A Published release leaves use in two ways, and neither repoints a run silently. Both are commands of the Platform admin with a required reason (D117). A caller whose scope carries factory.assets.publish and who holds the Platform admin role deprecates a Published release through AgentRegistryService/DeprecateRelease with a reason and an in-flight policy, which says what happens to runs that already pinned the release: finish, drain or revoke, as the service page names them. These are the values of the model and of the event, as model/services/agent-mesh/AgentRuntimeService.yaml lists them, and release-manifest-v1 names the same three for revocation.inFlightPolicy (D121). The release moves from Published to Deprecated through Deprecate and keeps the reason in withdrawalReason and the policy in inFlightPolicy, and two outbox records are written in the transaction of the command: AssetReleaseDeprecated with releaseId, tenantId and inFlightPolicy, and, because the command is audited, an audit-evidence-v1 record that names the Platform admin as actor, the release as subject with its manifestHash, the reason and the outcome, on the topic audit.evidence.v1.evidence-submitted under the run event envelope (D115); the response is 200. The action values of audit-evidence-v1 name release-published and release-revoked and none for a deprecation, which is reported to the owner as a correction of the descriptor; the acceptance test fixes the other members of the record. Deprecation keeps the manifest readable: the release can still be read and loaded by its id for the runs that pinned it, and it is immutable as before, so the stored manifest is not changed by a deprecation or a revocation. On the event RunControlService refuses new runs that would pin the release with 409 while runs already pinned continue, AgentRuntimeService applies the in-flight policy to running attempts and AgentCardService withdraws the card, each in its own PBI. A revocation is the security or policy action: a Platform admin withdraws a Published or a Deprecated release for a stated reason with the in-flight policy for the runs pinned to it, the release moves to the state Revoked through the transition Revoke, from Published or from Deprecated, and keeps the reason and the policy the revocation states (D119). No transition leaves Revoked, and a revoked release is never pinned, aliased or published again: ResolveRelease resolves no alias and no release id to it for a new pin (AIFACTORY-US-421), MoveAlias refuses it (AIFACTORY-US-419) and PublishRelease answers 409 (AIFACTORY-US-416). The revocation moves and removes no alias: an alias that points at the release stays in place and visible, and a resolution through it answers FAILED_PRECONDITION naming the revoked release until an administrator moves the alias (D121, AIFACTORY-US-421). With the revocation two outbox records are written in the transaction of the command: AssetReleaseRevoked with releaseId, tenantId, reason and inFlightPolicy, and an audit-evidence-v1 record of action release-revoked that names the actor, the release as subject with its manifestHash, the reason and the outcome, on the topic audit.evidence.v1.evidence-submitted under the run event envelope (D115); a command that rolls back leaves no evidence. On that event RunControlService applies the stated in-flight policy to every run that is not terminal and whose pinned release closure holds the revoked release, child runs included, where finish lets the runs continue to their end, drain lets the step that is running finish, dispatches no further step and ends the run Cancelled with the reason release-revoked, and revoke cancels the run at once with the same reason (D123, AIFACTORY-US-736); AgentRuntimeService interrupts the running attempts of those runs under revoke, lets them finish under drain and does nothing under finish, AgentCardService withdraws the card and AuditService records the evidence. This PBI delivers the revocation of the aggregate with its event and its evidence and proves it at the level of the domain and the outbox; the REST command RevokeRelease that performs it, with its request, its refusals and its repeat, is delivered and proven by AIFACTORY-US-536. For DeprecateRelease a body without a reason or with an in-flight policy other than finish, drain or revoke is answered 400, a caller without the scope or with the scope and without the Platform admin role 403, a release of another tenant or an unknown one 404 and a release that is Draft, InReview or Revoked 409, and a repeated call for a release already Deprecated returns 200 and writes no second event and no second evidence. Both events are published under the run event envelope of the contracts package by the dispatcher of the agent-registry messaging profile, which retries a transport outage with backoff.

Acceptance criteria

AC1 Given a Published release and a Platform admin whose scope carries factory.assets.publish, when AgentRegistryService/DeprecateRelease is called with a reason and an in-flight policy, then the response is 200, the AgentRegistryService/AssetRelease is Deprecated and keeps the reason in withdrawalReason and the policy in inFlightPolicy, its manifest stays readable and unchanged, and the AgentRegistryService/AssetReleaseDeprecated outbox record with releaseId, tenantId and inFlightPolicy and an audit-evidence-v1 record that names the actor, the release as subject with its manifestHash, the reason and the outcome are written in the same transaction; a command that rolls back leaves neither (SCN-AgentRegistryService-004, ADR-0014).
AC2 Given a body without a reason or with an in-flight policy other than finish, drain or revoke, a caller without the scope or with the scope and without the Platform admin role, a release of another tenant or an unknown one, or a release that is Draft, InReview or Revoked, when AgentRegistryService/DeprecateRelease is called, then the answer is 400, 403, 404 or 409 respectively and nothing changes; given a release already Deprecated, when the call is repeated, then it returns 200 and writes no second event and no second evidence (SCN-AgentRegistryService-004, ADR-0015).
AC3 Given a committed deprecation, when the dispatcher publishes AgentRegistryService/AssetReleaseDeprecated on asset-publication.releases.v1.asset-release-deprecated, then the event is sent under the run event envelope with releaseId, tenantId and inFlightPolicy, and a transport outage is retried with backoff so the event is neither lost nor published twice under its event id (SCN-AgentRegistryService-012, ADR-0012).
AC4 Given a Published release, and likewise a Deprecated one, revoked by a Platform admin with a reason and an in-flight policy, when the revocation commits, then the release is in the state Revoked through Revoke, which no transition leaves (D119), and keeps the reason in withdrawalReason and the policy in inFlightPolicy, the AgentRegistryService/AssetReleaseRevoked outbox record with releaseId, tenantId, reason and inFlightPolicy is written, and an audit-evidence-v1 record of action release-revoked that names the actor, the release as subject with its manifestHash, the reason and the outcome is written to the outbox in the transaction of the command, on the topic audit.evidence.v1.evidence-submitted under the run event envelope; a command that rolls back leaves no evidence (D115); the stored manifest is unchanged, and an alias that pointed at the release still points at it, since a revocation changes and removes no row of ReleaseAliases (D121); the dispatcher publishes the event on asset-publication.releases.v1.asset-release-revoked under the run event envelope and retries a transport outage without loss or duplicate (SCN-AgentRegistryService-013, ADR-0012, ADR-0014).
AC5 Given a Deprecated release that a run pinned earlier, when it is read through AgentRegistryService/GetRelease or loaded by its release id through AgentRegistryService/AssetPublication.LoadRelease, then the same manifest and closure are returned as before the deprecation, because the registry never repoints a pinned run (FR-02, docs/planes/control/registries.md).
Traces: services AgentRegistryService
Traces: aggregates AgentRegistryService/AssetRelease
Traces: apis AgentRegistryService/DeprecateRelease, AgentRegistryService/GetRelease, AgentRegistryService/AssetPublication.LoadRelease
Traces: events AgentRegistryService/AssetReleaseDeprecated, AgentRegistryService/AssetReleaseRevoked
Traces: descriptors audit-evidence-v1, run-event-envelope-v1
Traces: adrs ADR-0012, ADR-0014, ADR-0015
Traces: requirements FR-02, NFR-02
Traces: scenarios SCN-AgentRegistryService-004, SCN-AgentRegistryService-012, SCN-AgentRegistryService-013
Depends on feature:agent-registry-service-publication, feature:component-audit-factory-evidence, feature:contracts-package
Sources model/services/control-plane/AgentRegistryService.yaml, model/services/control-plane/RunControlService.yaml, docs/planes/control/services/agent-registry-service/index.md#context-and-boundaries, docs/planes/control/registries.md, docs/architecture/quality-gates.md, model/services/agent-mesh/AgentRuntimeService.yaml, docs/reference/schemas/release-manifest.schema.json, docs/reference/schemas/audit-evidence.schema.json

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-541 Immutability, deprecation and revocation of a Published release implementation The transitions Deprecate and Revoke are added to the domain model of AIFACTORY-TASK-364 with the invariant that a deprecation and a revocation keep a reason and the revocation also its in-flight policy, and DeprecateRelease is hosted on POST /factory/asset-releases/{releaseId}/deprecate under factory.assets.publish and listed in the service descriptor file with the codes 200, 400, 403, 404 and 409, beside the publication path of I2 (D140); Published content cannot change; DeprecateRelease admits only a caller with the Platform admin role, requires a reason and an in-flight policy, applies the Deprecate transition, keeps the reason in withdrawalReason and the policy in inFlightPolicy and writes, in the same transaction, AssetReleaseDeprecated and, through the Factory sink of the audit library pinned from feature component-audit-factory-evidence, an audit-evidence-v1 record with the actor, the release as subject with its manifestHash, the reason and the outcome (D115, D117), whose action value follows the correction of the descriptor the PBI reports; it returns 200 without a second event or evidence on a repeat and answers 400, 403, 404 (also for a release of another tenant, ADR-0015) and 409 as modelled, the 409 also for a Revoked release; the revocation of the aggregate moves a Published or a Deprecated release to the state Revoked through Revoke with a reason and an in-flight policy (D119), keeps both on the release, allows no transition out of Revoked and writes, in the transaction of the command, AssetReleaseRevoked and, through the same sink, an audit-evidence-v1 record of action release-revoked with the actor, the release as subject with its manifestHash, the reason and the outcome, on the topic audit.evidence.v1.evidence-submitted under the run event envelope (D115); the REST command RevokeRelease over it is delivered by AIFACTORY-US-536; the in-flight policy takes the values finish, drain and revoke of model/services/agent-mesh/AgentRuntimeService.yaml, the stored manifest is not changed by a deprecation or a revocation, and a revocation changes and removes no alias row, so an alias that points at the revoked release stays in place (D121). ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-1690 Contract of AssetReleaseDeprecated and AssetReleaseRevoked against the run event envelope of the contracts package contract Beside the golden files of AssetReleaseSubmitted and AssetReleasePublished of the publication path (AIFACTORY-TASK-6347, D140), golden files fix AssetReleaseDeprecated and AssetReleaseRevoked on their topics under run-event-envelope-v1 with the payload fields of model/services/control-plane/AgentRegistryService.yaml and the tenant in the envelope; a contract test fails when a serialised event differs from its file or from docs/reference/schemas/run-event-envelope.schema.json, and the envelope type comes from the pinned contracts package. ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-1691 Verify deprecate-and-revoke-a-release through the acceptance suite verification Run dotnet test -c Release --filter "Category=Acceptance&(Scenario=SCN-AgentRegistryService-004\|Scenario=SCN-AgentRegistryService-012\|Scenario=SCN-AgentRegistryService-013)"; a zero-match filter counts as a failure; the tests prove AC1 to AC5 of AIFACTORY-US-417, including a deprecation by a Platform admin with its reason and policy kept on the release, the 400 of a missing reason and the 403 of a caller that holds the scope without the Platform admin role, the publication and payload of both events, a revocation from Published and one from Deprecated that both end in the state Revoked, an alias that still points at the release after its revocation, the 409 of a deprecation of a Revoked release, the evidence record of a deprecation and of a revocation on the topic audit.evidence.v1.evidence-submitted and none after a rollback; consumer handling is proven by the suites of the consumers. ConnectSoft.AI.SoftwareFactory.AgentRegistryService

AIFACTORY-US-420: AgentRegistryService handles once and inside the tenant what other services announce about releases

behavior · persona platform-admin As a platform admin, I want every event another service announces about releases handled once and inside its tenant, so that a blueprint, a marketplace installation, an entitlement and a retention rule reach the registry once.

Besides the two events of the publication gate, the model lists eight consumed events of AgentRegistryService. BlueprintService announces BlueprintSubmitted, for which the handler OpenReleaseCandidate opens a release candidate for the submitted blueprint version. FeedbackService announces LearningProposalDecided, for which the same handler opens the Draft release of an accepted learning proposal through the command OpenLearningRelease and announces it with LearningReleaseOpened; that path is delivered by AIFACTORY-US-1493 (D131). MarketplaceCatalogService announces ListingInstalled and ListingRemoved: RegisterInstalledRelease makes the releases of the installed listing available to the tenant, and WithdrawInstalledRelease withdraws the releases of the removed installation from the tenant so that no new run may pin them. LicenseService announces EntitlementStateChanged, for which ApplyEntitlementState suspends or restores the use by the tenant of the releases that come from a marketplace listing. RetentionResidencyService announces RetentionRuleChanged, for which ApplyRetentionRule applies the effective retention period to the records the service owns in the store class of the rule. RetentionResidencyService also announces DeletionOrderIssued and LegalHoldChanged; the owner decided that their handlers ExecuteDeletionOrder and ApplyLegalHold, with the deletion of an ordered scope, its receipt through AcknowledgeOrderTask and the suspension of deletion and expiry for a held scope, are built in this repository in I4 by feature retention-residency-service, one PBI per group of owning services, and proven by its deletion and hold scenarios (D137); this PBI delivers neither handler. The service registers the six subscriptions of this PBI, beside those of ApprovalDecided and EvaluationCompleted, in the OrleansMessaging section of its own messaging profile with the service name agent-registry, and the two retention subscriptions join the same section with their handlers. Its inbox deduplicates each delivery on the event id, and each handler reads the tenant from the envelope and never from the payload, so a message without a tenant is not handled and is poisoned with its reason. A candidate opened by OpenReleaseCandidate enters the same lifecycle as a submitted one and is published only through the gate of AIFACTORY-US-416; a handler never publishes a release, and a release of another tenant is never touched. The publishers of the retention and blueprint events are delivered in this increment or an earlier one; MarketplaceCatalogService and LicenseService arrive in a later increment, so their three handlers are proven against contract fixtures built from the model and the publishers prove their side in their own features. The model has no table or field for the availability of an installed release to a tenant or for its suspension, so where the three marketplace and entitlement handlers keep it is an open point this PBI does not decide: it delivers their subscriptions, the idempotent inbox and the tenant guard, and the handlers follow the model once it names the fields. The gateway consumes none of these events (ADR-0028 amendment on gateways and events).

Acceptance criteria

AC1 Given the messaging profile, when the service starts, then the OrleansMessaging section declares one subscription with its handler for each of the ten consumed events of model/services/control-plane/AgentRegistryService.yaml other than RetentionResidencyService/DeletionOrderIssued and RetentionResidencyService/LegalHoldChanged, whose handlers feature retention-residency-service builds in this repository (D137), and the five published events with their topics, AgentRegistryService/LearningReleaseOpened among them (D131); startup fails when a consumed event listed in the service descriptor file of the repository has no subscription, and ControlPlaneApi subscribes to none of them (ADR-0028).
AC2 Given a BlueprintService/BlueprintSubmitted event, when OpenReleaseCandidate handles it, then one AgentRegistryService/AssetRelease candidate exists per event id in a state before Published, a second delivery of the same event opens no second candidate, and no release is Published by a handler (ADR-0014, ADR-0021).
AC3 Given a RetentionResidencyService/RetentionRuleChanged for the store class of the records the service owns in one tenant, when ApplyRetentionRule handles it, then the effective retention period of the rule applies to those records of that tenant, no record of another tenant is touched and a second delivery of the same event changes nothing (ADR-0015, model/services/control-plane/AgentRegistryService.yaml).
AC4 Given a delivery without a tenant in the envelope, a duplicate delivery and a handler that throws, when they arrive, then the first is poisoned with its reason, the second is acknowledged without effect, and the third is retried with backoff and poisoned at the attempt limit of the profile while the other subscriptions keep delivering (ADR-0012, ADR-0014).
Traces: services AgentRegistryService
Traces: aggregates AgentRegistryService/AssetRelease
Traces: events RetentionResidencyService/RetentionRuleChanged, RetentionResidencyService/DeletionOrderIssued, RetentionResidencyService/LegalHoldChanged, BlueprintService/BlueprintSubmitted, AgentRegistryService/LearningReleaseOpened
Traces: adrs ADR-0012, ADR-0014, ADR-0015, ADR-0021, ADR-0028
Depends on AIFACTORY-US-1562, feature:agent-registry-service-publication, feature:contracts-package, feature:retention-residency-service, feature:blueprint-service
Sources model/services/control-plane/AgentRegistryService.yaml, model/services/data-event/RetentionResidencyService.yaml, docs/planes/control/services/agent-registry-service/index.md#messages, docs/architecture/adr/0028-one-repository-and-deployable-per-service.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-367 Messaging wiring of the agent-registry profile: outbox for 5 published events and inbox subscriptions for 8 of the 10 consumed events implementation On the OrleansMessaging section that the publication path wired in I2 with AssetReleaseSubmitted, AssetReleasePublished and the subscription of ApprovalDecided (AIFACTORY-TASK-6346, D140), the section declares the service name agent-registry, the five published events AssetReleaseSubmitted, AssetReleasePublished, AssetReleaseDeprecated, AssetReleaseRevoked and LearningReleaseOpened with their topics (D131) and the subscriptions of the model with their handlers other than those of DeletionOrderIssued and LegalHoldChanged, which feature retention-residency-service adds in this repository (D137); the outbox writer enlists in the unit of work of each command, the inbox deduplicates on the event id and each handler reads the tenant from the run event envelope and refuses a message without one. ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-1696 Contract fixtures of the consumed events of the marketplace, licence, retention, learning and blueprint publishers fixture The acceptance suite holds one fixture per consumed event of model/services/control-plane/AgentRegistryService.yaml under run-event-envelope-v1 with the payload fields its producer declares in the model, a duplicate of each with the same event id and a variant without a tenant in the envelope. ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-1697 Handlers OpenReleaseCandidate for a submitted blueprint and ApplyRetentionRule implementation OpenReleaseCandidate opens one release candidate per submitted blueprint version, idempotently on the event id and never past the gate, and passes an accepted learning proposal to the command OpenLearningRelease of AIFACTORY-US-1493; ApplyRetentionRule applies the effective retention period of the rule to the rows and manifest references the service owns in the store class of the rule, inside the tenant of the envelope; the deletion and hold handlers are not part of this task (D137). ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-1698 Verify the inbox handlers against the contract fixtures verification Run dotnet test -c Release --filter "Category=Acceptance&Feature=InboxHandlers"; a zero-match filter counts as a failure; the tests prove AC1 to AC4 of AIFACTORY-US-420: the subscriptions of model/services/control-plane/AgentRegistryService.yaml other than those of DeletionOrderIssued and LegalHoldChanged and the five published events, the blueprint candidate opened once, the retention rule applied inside its tenant once, the message without a tenant and the poisoned delivery. ConnectSoft.AI.SoftwareFactory.AgentRegistryService

AIFACTORY-US-421: Resolution and loading serve releases that passed the gate, the seeded Draft releases are published through it and the releases published before I4 without evaluation are resubmitted

behavior · persona platform-admin As a platform admin, I want the seeded Draft releases of the first outcome and the releases published before I4 without an evaluation record taken through the gate, and the seed removed, so that every release a run can pin was evaluated where a suite exists and approved, with no exception left in the registry.

The thin delivery of the first outcome resolved and loaded seeded Draft releases, under the amendment of ADR-0021 that lets a Draft workflow or agent release run only in the acceptance environment and in internal projects until the evaluation gate exists, and that removes the rule when the gate is delivered. This PBI makes the registry side of that removal true. The twenty-six seeded releases of the six chain definitions, their nine agents and the eleven model profiles of model/model-profiles.yaml that the thin delivery seeds (D121, D123) pass the gate like any candidate: each is submitted from its Draft row, which moves that row to InReview without a second row as AIFACTORY-US-415 states for a version that exists as a Draft release, its closure is resolved, it is evaluated, approved by someone who is not the author, a Reviewer for a workflow or an agent release and a Platform admin for a model profile release, and published, and its alias is moved to the Published release. The owner decided that the publication path is delivered in I2 (D140), so the releases of the workflow features of I2, I3 and I4 were published before this delivery on their closure and their approval, without an evaluation verdict. A release published before I4 without an evaluation record, of an asset kind for which an evaluation suite exists from this delivery, is resubmitted through the evaluation gate as a new version with a new release id, and the gate checks the evidence the registry recorded itself from EvaluationCompleted through RecordEvaluationEvidence of AIFACTORY-US-1562, with no synchronous call to QualityScoreService (D141): the Published release itself stays immutable and loadable by its id for the runs that pinned it, the new version is evaluated, approved and published like any candidate, and the aliases that pointed at the earlier release are moved to it (D140). A release of a kind without a suite keeps its publication of I2. For the eleven model profile releases, which were loadable by alias as Draft releases in the thin delivery, the approval by a Platform admin who is not the author becomes required with this delivery (D121). After that the seed loader, the fakes and the static answers of the first outcome are deleted from the service, and the service registers no release by itself. From then on AgentRegistryService/AssetPublication.ResolveRelease resolves an alias to a Published release, since an alias can only be moved to one, and AgentRegistryService/AssetPublication.LoadRelease streams the manifest and the closure content references of the release a run pinned, also when that release was deprecated meanwhile, because deprecation keeps the manifest readable. The contract of the two methods does not change: the request messages and the reply message that the contract test of the thin delivery fixes are kept, a Published release now carries the publication fields publishedAt, publishedBy, evaluation and approval and validates against release-manifest-v1 in full, the statuses for a missing workload identity, a missing service scope, an invalid request and a release of another tenant are those of the thin delivery, and the callers RunControlService, WorkflowEngineService and AgentRuntimeService are not rebuilt. Whether a new run may pin a Deprecated release is not decided by the registry: RunControlService refuses it on AssetReleaseDeprecated. A Revoked release is different (D119): the registry itself never resolves it for a new pin, by its release id or through an alias. The owner decided what happens to an alias that points at a release when it is revoked (D121): the revocation neither moves nor removes it, so the alias stays in place and visible, and AssetPublication.ResolveRelease through that alias resolves nothing and answers FAILED_PRECONDITION with a status message that names the revoked release, until an administrator moves the alias to a Published release through MoveAlias (AIFACTORY-US-419). The answer tells the caller that the alias exists and that its release was withdrawn, which NOT_FOUND would hide; RunControlService accepts no run on it and answers SubmitRun with 409 naming the gate for as long as the alias points there. A resolution by the release id of a Revoked release answers the same way, FAILED_PRECONDITION with a status message that names the revoked release, as the owner decided (D123). AssetPublication.LoadRelease keeps streaming the unchanged manifest of a Revoked release by release id for the runs that pinned it before the revocation, to which RunControlService applies the stated in-flight policy (AIFACTORY-US-736, D123). The policy rule that waived Draft releases is removed by the feature that owns policy; this PBI guarantees that no alias points at a Draft release once it is gone.

Acceptance criteria

AC1 Given the twenty-six seeded Draft releases of the thin delivery, the eleven model profile releases among them (D121, D123), when each has been submitted from its Draft row, which moves that row to InReview without a second row as AC2 of AIFACTORY-US-415 states, and has been evaluated, approved by someone who is not its author, a Platform admin for each model profile release and a Reviewer for every other one, and published through the gate and its alias moved, then AgentRegistryService/AssetPublication.ResolveRelease resolves each alias to a Published release with an evaluation record reference, recorded by RecordEvaluationEvidence and checked at the gate without a synchronous call (D141), and an approval, and no alias points at a Draft release; given a release Published before I4 without an evaluation record, of a kind for which a suite exists, when it is resubmitted through the gate as a new version, then the new version is Published with an evaluation record reference, its aliases resolve to it, and the earlier release is unchanged and still loadable by its id (D140, ADR-0021, model/backlog/features/control-plane.yaml).
AC2 Given the seed loader, the fakes and the static answers of the first outcome are deleted, when the service starts on an empty store, then it registers no release by itself, and the contract test shows AgentRegistryService/AssetPublication.ResolveRelease and AgentRegistryService/AssetPublication.LoadRelease with their request and reply messages unchanged, and the reply for a Published release validates against release-manifest-v1 in full (model/services/control-plane/AgentRegistryService.yaml).
AC3 Given a run that pinned a release which is now Deprecated, when the runtime loads it by release id through AgentRegistryService/AssetPublication.LoadRelease, then the stream delivers the same manifest and closure content references as before the deprecation (FR-02, docs/planes/control/registries.md).
AC4 Given the callers RunControlService, WorkflowEngineService and AgentRuntimeService built against the thin delivery, when they run against the complete service, then resolution and loading succeed without a rebuild of the callers and a release of another tenant is still answered NOT_FOUND (ADR-0015, XL-15).
AC5 Given a Revoked release and an alias that pointed at it when it was revoked, when AgentRegistryService/AssetPublication.ResolveRelease is called with that alias, then the call answers FAILED_PRECONDITION with a status message that names the revoked release, no release is returned for a new pin, nothing is written and the alias still points at the revoked release in ReleaseAliases (D121); when it is called with the release id of the Revoked release, then it answers FAILED_PRECONDITION with a status message that names the revoked release as well and no release is returned (D123); when the alias has been moved to a Published release, then the same call resolves it to that release; when a run that pinned the release before its revocation loads it by release id through AgentRegistryService/AssetPublication.LoadRelease, then the stream delivers the same manifest and closure content references as before the revocation (FR-02, model/services/control-plane/AgentRegistryService.yaml).
Traces: services AgentRegistryService
Traces: aggregates AgentRegistryService/AssetRelease
Traces: apis AgentRegistryService/AssetPublication.ResolveRelease, AgentRegistryService/AssetPublication.LoadRelease
Traces: descriptors release-manifest-v1
Traces: adrs ADR-0015, ADR-0021
Traces: requirements FR-02, XL-15
Depends on AIFACTORY-US-1562, feature:agent-registry-service-publication, feature:agent-registry-service-thin
Sources model/services/control-plane/AgentRegistryService.yaml, model/backlog/features/control-plane.yaml, docs/architecture/adr/0021-quality-gates.md, docs/planes/control/registries.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-370 Retire the thin scope and the stubs of AgentRegistryService implementation Callers run against the complete service; the seed loader with its configuration key Publication:Seed:Path and its readiness check, the fakes and the static answers of the first outcome are deleted, the service registers no release by itself, and the contract test of the request and reply messages of AssetPublication.ResolveRelease and AssetPublication.LoadRelease passes unchanged, with the reply of a Published release validating against release-manifest-v1 in full. ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-1699 Publish the twenty-six seeded releases through the gate and move their aliases migration A migration runbook and its script submit the releases of the six chain definitions, their nine agents and the eleven model profiles from their source commits, each onto its seeded Draft row (AC2 of AIFACTORY-US-415), wait for closure and evaluation, leave the publication approval to a Reviewer who is not the author and, for the eleven model profile releases, to a Platform admin who is not the author (D121, D123), move each alias to the Published release and report every release with its evaluation record reference and approval; a release that fails a gate is listed with the gate and keeps its Draft seed until it passes. ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-6344 Resubmit as new versions through the gate the releases published before I4 without an evaluation record migration A migration runbook and its script list every Published release of the tenants and of the platform tenant that carries no evaluation record and whose asset kind has an evaluation suite from this delivery, submit for each a new version from its source commit through SubmitRelease, wait for closure, evaluation and the approval of a Reviewer who is not the author, or of a Platform admin for a ModelProfile release, move each alias that pointed at the earlier release to the new Published version and report every pair of releases with the evaluation record reference of the new one; the earlier release stays Published, immutable and loadable by its id for the runs that pinned it (D140); a new version that fails a gate is listed with the gate and the alias keeps pointing at the earlier release until it passes. ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-2654 ResolveRelease never resolving a Revoked release for a new pin implementation AssetPublication.ResolveRelease returns no release when the release id it is given, or the release an alias points at, is in the state Revoked, so that RunControlService accepts no run on a revoked release (D119); a resolution through an alias that points at a Revoked release answers FAILED_PRECONDITION with a status message that names the revoked release and leaves the alias in place, until the alias is moved to a Published release (D121); a resolution by the release id of a Revoked release answers the same way, FAILED_PRECONDITION with a status message that names the revoked release (D123); the refusal writes nothing, a release of another tenant is still answered NOT_FOUND, and AssetPublication.LoadRelease keeps streaming a Revoked release by its release id. ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-1700 Verify resolution and loading after the gate verification Run dotnet test -c Release --filter "Category=Acceptance&Feature=ResolveAndLoadAfterTheGate"; a zero-match filter counts as a failure; the tests prove AC1 to AC5 of AIFACTORY-US-421: every alias on a Published release, a release published before I4 without an evaluation record resubmitted as a new version whose aliases move to it while the earlier release stays loadable by its id (D140), an empty store after start, a Deprecated release still loadable by its id, an alias of a Revoked release that stays in place and whose resolution answers FAILED_PRECONDITION naming the release until the alias is moved to a Published one, a Revoked release whose resolution by its id answers FAILED_PRECONDITION naming it and that is still loadable by its id, and the unchanged contract of the two gRPC methods against release-manifest-v1. ConnectSoft.AI.SoftwareFactory.AgentRegistryService

AIFACTORY-US-536: Revoke a release as a Platform admin with a required reason and the in-flight policy for the runs pinned to it

behavior · persona platform-admin As a platform admin, I want to revoke a release for a security or policy reason and to state what happens to the runs that already pinned it, so that a compromised or forbidden release stops being used at once and the act is on record with its reason.

A revocation is the security or policy action on a release, and D117 makes it a REST command of the Platform admin. A caller whose scope carries factory.assets.publish and who holds the Platform admin role revokes a release through the gateway route of AgentRegistryService/RevokeRelease, addressed by releaseId. The body carries two required members: the reason, a security or policy reason, and the inFlightPolicy for the runs that already pinned the release, one of finish, drain or revoke, the values model/services/agent-mesh/AgentRuntimeService.yaml lists. The command applies the revocation of the aggregate that AIFACTORY-US-417 delivers. A Published release and a Deprecated release move to the state Revoked through the transition Revoke and keep the reason in withdrawalReason and the policy in inFlightPolicy, those the revocation states (D119). No transition leaves Revoked, and a revoked release is never pinned, aliased or published again. Two outbox records are written in the transaction of the command: AssetReleaseRevoked with releaseId, tenantId, reason and inFlightPolicy, and an audit-evidence-v1 record of action release-revoked that names the Platform admin as actor, the release as subject with its manifestHash, the reason and the outcome, on the topic audit.evidence.v1.evidence-submitted under the run event envelope (D115). The response is 200 with the release. The stored manifest is not changed, so the release stays readable and loadable by its id, and the registry repoints no run and moves no alias: an alias that points at the release stays in place and visible, and a resolution through it answers FAILED_PRECONDITION naming the revoked release until an administrator moves the alias (D121, AIFACTORY-US-421). On the event RunControlService applies the stated policy to every run that is not terminal and whose pinned release closure holds the release, child runs included: under finish the runs continue to their end, under drain the step that is running finishes, no further step is dispatched and the run ends Cancelled with the reason release-revoked, and under revoke the run is cancelled at once with the same reason (D123, AIFACTORY-US-736). AgentRuntimeService interrupts the running attempts of those runs under revoke, lets them finish under drain and does nothing under finish, AgentCardService withdraws the card and AuditService records the evidence, each in its own PBI. The operation is naturally idempotent: a repeated call that names the reason and the policy the release already keeps returns 200, changes nothing and writes no second event and no second evidence. A body without a reason, without an in-flight policy or with a policy outside the three values is refused with 400. A caller without the scope, or with the scope and without the Platform admin role, such as a Reviewer or an asset maintainer, is refused with 403. A release that does not exist in the tenant of the caller is answered 404, which is also the answer for a release of another tenant (ADR-0015). A release that is Draft or InReview is answered 409, because the model holds the transition Revoke from Published and from Deprecated only (D119). A release that is already Revoked and is named with another reason or another policy is answered 409 too, because no transition leaves Revoked and the reason and the policy of a revocation are not rewritten. A refused call changes nothing and publishes nothing, and a command that rolls back leaves no state change, no event and no evidence. The route of the command is generated from the fronts file of ControlPlaneApi under the publication route class; the gateway forwards the user token and decides nothing about the revocation.

Acceptance criteria

AC1 Given a Published release, and likewise a Deprecated one, and a Platform admin whose scope carries factory.assets.publish, when AgentRegistryService/RevokeRelease is called with a reason and an inFlightPolicy of finish, drain or revoke, then the response is 200, the AgentRegistryService/AssetRelease is in the state Revoked through Revoke (D119) and keeps the reason in withdrawalReason and the policy in inFlightPolicy, its stored manifest is unchanged, and the AgentRegistryService/AssetReleaseRevoked outbox record with releaseId, tenantId, reason and inFlightPolicy and an audit-evidence-v1 record of action release-revoked that names the actor, the release as subject with its manifestHash, the reason and the outcome are written in the transaction of the command (SCN-AgentRegistryService-014, ADR-0014).
AC2 Given a body without a reason, without an inFlightPolicy or with a policy other than finish, drain or revoke, when AgentRegistryService/RevokeRelease is called, then the answer is 400 with a problem response that names the member; given a caller without factory.assets.publish, or with the scope and without the Platform admin role, then the answer is 403; given a releaseId of another tenant or one that does not exist, then the answer is 404 for both alike; in each case the release keeps its state and no event and no evidence is written (SCN-AgentRegistryService-014, ADR-0015).
AC3 Given a Draft or an InReview release, when AgentRegistryService/RevokeRelease is called, then the answer is 409; given a release this command already revoked, when the call is repeated with the same reason and policy, then it returns 200, changes nothing and writes no second outbox record and no second evidence; given a Revoked release named with another reason or another policy, then the answer is 409, because model/services/control-plane/AgentRegistryService.yaml holds the transition Revoke from Published and from Deprecated and none out of Revoked (SCN-AgentRegistryService-014, D119).
AC4 Given a revocation whose transaction rolls back after the transition, when the store and the outbox are read, then the release is still in the state it had, Published or Deprecated, and neither AgentRegistryService/AssetReleaseRevoked nor an evidence record exists; given a committed revocation, when the release is read from the store by its id, then its manifest and closure are the ones it had before, so a run that pinned it is repointed by nobody (SCN-AgentRegistryService-014, ADR-0014).
Traces: services AgentRegistryService
Traces: aggregates AgentRegistryService/AssetRelease
Traces: apis AgentRegistryService/RevokeRelease
Traces: events AgentRegistryService/AssetReleaseRevoked
Traces: descriptors audit-evidence-v1, run-event-envelope-v1
Traces: adrs ADR-0014, ADR-0015
Traces: requirements FR-02, NFR-02
Traces: scenarios SCN-AgentRegistryService-014
Depends on AIFACTORY-US-417, feature:component-audit-factory-evidence, feature:contracts-package
Sources model/services/control-plane/AgentRegistryService.yaml, model/services/agent-mesh/AgentRuntimeService.yaml, docs/planes/control/registries.md, docs/architecture/adr/0015-factory-tenancy-under-canonical-adr-0100.md, docs/reference/schemas/audit-evidence.schema.json

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-2151 RevokeRelease as a REST command of the Platform admin with the required reason, the in-flight policy and the natural repeat implementation RevokeRelease is hosted on POST /factory/asset-releases/{releaseId}/revoke under factory.assets.publish with the side-effect class publication and natural idempotency and is listed in the service descriptor file with the codes 200, 400, 403, 404 and 409; it admits only a caller with the Platform admin role, validates the reason and the inFlightPolicy (finish, drain or revoke), applies the revocation of the aggregate of AIFACTORY-TASK-541 to a Published or a Deprecated release, which ends in the state Revoked (D119), so that the release keeps the reason and the policy and AssetReleaseRevoked and the audit-evidence-v1 record of action release-revoked are written in the transaction of the command (D115), returns 200 without a second event or evidence on a repeat with the same reason and policy, and answers 400, 403, 404 (also for a release of another tenant, ADR-0015) and 409 as AIFACTORY-US-536 states. ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-2152 Verify revoke-a-release-as-platform-admin through the acceptance suite verification Run dotnet test -c Release --filter "Category=Acceptance&Scenario=SCN-AgentRegistryService-014"; a zero-match filter counts as a failure; the tests prove AC1 to AC4 of AIFACTORY-US-536: a revocation by a Platform admin with its reason and policy kept on the release, the event and the evidence record in one transaction and none after a rollback, the 400 of a missing reason and of a missing or unknown policy, the 403 of a Reviewer and of an asset maintainer who hold the scope, the 404 of a foreign and of an unknown release, the revocation of a Deprecated release that ends in the state Revoked, the 409 of a Draft, an InReview and a differently named Revoked release, and the repeat without a second event. ConnectSoft.AI.SoftwareFactory.AgentRegistryService

AIFACTORY-US-736: RunControlService applies the in-flight policy of a revocation to the runs that already pinned the revoked release

behavior · persona platform-admin As a platform admin, I want the in-flight policy I state with a revocation applied to the runs that already pinned the release, so that a revoked release stops being used in the way the revocation says and no run is silently moved to another release.

A revocation states an in-flight policy for the runs that already pinned the release, one of finish, drain or revoke (AIFACTORY-US-536), and AssetReleaseRevoked carries it with releaseId, tenantId, reason and inFlightPolicy. The registry repoints no run and stops none: the service that owns the runs acts on the event. This PBI delivers that act, the part of the inbox handler ApplyRevocationPolicy of RunControlService that concerns the runs already pinned, in the repository ConnectSoft.AI.SoftwareFactory.RunControlService. It belongs to this feature because the event is first published by the complete registry; before it the handler has no publisher. The other part of the same handler is delivered with feature run-control-service: it keeps the state Revoked of the release in GateStates, so that SubmitRun refuses a run that would pin it with 409 (AIFACTORY-TASK-1491), and that answer also holds while the alias of a submission points at the revoked release, until an administrator moves the alias (D121). The owner decided what each of the three values does to a run (D123), the model of RunControlService states it with its transitions and triggers, and this PBI delivers exactly that. The handler consumes AssetReleaseRevoked in the inbox of the service, once per event id and inside the tenant of the envelope. The policy covers every run of that tenant that is not terminal, that is neither Completed nor Failed nor Cancelled, and whose pinned release closure holds the revoked release. That is a run whose releaseId is the revoked release, a run whose pinned release only has the revoked release in its closure, and a child run, which inherits the pinned release closure of its parent (D119) and is selected in its own right. Under finish nothing changes: the selected runs continue to their end, no cancellation intent is recorded and nothing is published for them. Under drain the step that is running finishes, no further step is dispatched, and the run then follows the cancellation path and ends Cancelled with the reason release-revoked: a Running run moves to Cancelling through the trigger ReleaseRevokedAfterRunningStepSettled once its running step has settled and to Cancelled through AllAttemptsSettled, while a run in which no step is running, Accepted or Held, has nothing to finish and takes the cancellation path at once, by the transitions the model holds from Accepted and from Held to Cancelled. Under revoke the run follows the cancellation path at once and ends Cancelled with the same reason: an Accepted run moves to Cancelled through ReleaseRevokedBeforeDispatch, a Held run through ReleaseRevokedWhileHeld, and a Running or a WaitingForApproval run moves to Cancelling through ReleaseRevoked and to Cancelled once all its attempts have settled, and an attempt that is open is interrupted as for CancelRun. For drain and for revoke the handler records a cancellation intent with the reason release-revoked and the actor system, as for a stop on BudgetExceeded, and RunCancelled carries that reason; the run is Cancelled and never Failed. A run that is already Cancelling keeps the intent and the reason it has, because the model holds no revocation transition out of Cancelling. The work on a running attempt is divided with AgentRuntimeService, whose handler ApplyInFlightPolicy consumes the same event and is delivered by feature agent-runtime-service: under revoke the runtime interrupts the running attempt, which ends Cancelled with the failure class cancellation, under drain it lets the attempt finish, under finish it does nothing, and in every case it keeps the manifest the attempt already loaded. RunControlService owns the run, which means the selection, the cancellation intent, the transitions, the stop of dispatch under drain and the settlement of the attempts. Whatever the policy, no run is repointed: the pinned releaseId, the policy revision and the snapshot of a run never change, the manifest of the revoked release stays loadable by its release id for as long as a pinned run needs it (AIFACTORY-US-421), and every state change of a run is committed in the same transaction as its outbox record. A run whose pinned closure does not hold the revoked release, a terminal run and a run of another tenant are not touched, and a redelivered event applies nothing twice. The selection reads the table RunPinnedReleases, in which RunControlService keeps, at acceptance, one row per release of the pinned closure of a run, the release id of every closure member that resolved-execution-snapshot-v1 names, and a child run its own rows (D125, AIFACTORY-US-005 and AIFACTORY-US-656 of feature run-control-service); the handler finds the runs of the revoked release by that table under the tenant row filter. A run that waits in WaitingForApproval under drain has no step running and takes the transition ReleaseRevoked to Cancelling at once, and a run already Cancelling keeps the reason it has, as the owner decided (D125). The handling is proven in the suite of RunControlService with events built from the pinned contracts package, and once against the publishing registry.

Acceptance criteria

AC1 Given, in one tenant, a non-terminal run whose releaseId is a release, a non-terminal run whose pinned release closure holds that release without pinning it, an open child run that inherited that closure from its parent, a run whose pinned closure does not hold the release and a Completed run pinned to the release, and a run of another tenant pinned to it, when AgentRegistryService/AssetReleaseRevoked for that release and tenant is handled by ApplyRevocationPolicy, then exactly the first three RunControlService/Run rows are selected and the inFlightPolicy of the event is applied to each of them, the other three runs are unchanged, and a redelivery of the event under the same event id selects and applies nothing again (D123, model/services/control-plane/RunControlService.yaml).
AC2 Given each of the three policies finish, drain and revoke, when the handler has applied it to a pinned run, then the releaseId, the policyRevision and the snapshotId of the run are the ones it pinned at acceptance, the revoked release is still streamed by its release id through AgentRegistryService/AssetPublication.LoadRelease, and every state change of a run was committed with its outbox record in one transaction, so that no run is repointed and no transition is announced without being committed (model/services/control-plane/RunControlService.yaml, FR-02).
AC3 Given the policy finish, when the event is handled, then every selected RunControlService/Run keeps its state and continues to its end, no cancellation intent is recorded and nothing is written to the outbox for it; given the policy drain and a Running run with a step that is running, then that step finishes, no further step is dispatched, a cancellation intent with the reason release-revoked and the actor system is recorded, the run moves to Cancelling through ReleaseRevokedAfterRunningStepSettled once the step has settled and ends Cancelled, and RunControlService/RunCancelled carries the reason release-revoked; given the policy drain and an Accepted or a Held run, then the run is Cancelled at once with the same intent and reason and no attempt is dispatched for it; no drained run ends Failed (D123, model/services/control-plane/RunControlService.yaml).
AC4 Given the policy revoke, when the event is handled, then a cancellation intent with the reason release-revoked and the actor system is recorded for every selected run, an Accepted run moves to Cancelled through ReleaseRevokedBeforeDispatch, a Held run through ReleaseRevokedWhileHeld, and a Running or a WaitingForApproval run moves to Cancelling through ReleaseRevoked, its open attempt is interrupted as for RunControlService/CancelRun, and it ends Cancelled once all its attempts have settled; RunControlService/RunCancelled is written once per run with the reason release-revoked, a parent run and its child run that were both selected each end Cancelled with that reason, a run that was already Cancelling gets no second intent, and no revoked run ends Failed (D123, model/services/control-plane/RunControlService.yaml).
AC5 Given a Published release that a non-terminal run pinned, when a Platform admin revokes it through AgentRegistryService/RevokeRelease with the in-flight policy revoke, then AgentRegistryService/AssetReleaseRevoked reaches ApplyRevocationPolicy of RunControlService once, that run ends Cancelled with the reason release-revoked, and RunControlService/SubmitRun for that release, by its release id or through an alias that still points at it, answers 409 with a problem body that names the gate (D119, D121, D123, model/services/control-plane/RunControlService.yaml).
Traces: services AgentRegistryService, RunControlService
Traces: aggregates AgentRegistryService/AssetRelease, RunControlService/Run
Traces: apis AgentRegistryService/RevokeRelease, AgentRegistryService/AssetPublication.LoadRelease, RunControlService/SubmitRun, RunControlService/CancelRun
Traces: events AgentRegistryService/AssetReleaseRevoked, RunControlService/RunCancelled
Traces: descriptors run-event-envelope-v1
Traces: adrs ADR-0014, ADR-0015
Traces: requirements FR-02, NFR-02
Depends on AIFACTORY-US-421, AIFACTORY-US-536, feature:run-control-service, feature:contracts-package
Sources model/services/control-plane/RunControlService.yaml, model/services/control-plane/AgentRegistryService.yaml, model/services/agent-mesh/AgentRuntimeService.yaml, docs/planes/control/registries.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-2971 Selection of the runs whose pinned closure holds the revoked release and policy dispatch of the inbox handler ApplyRevocationPolicy implementation In ConnectSoft.AI.SoftwareFactory.RunControlService the handler of AssetReleaseRevoked, beside the GateStates row it keeps (AIFACTORY-TASK-1491), selects the runs of the tenant of the envelope that are not terminal and whose pinned release closure holds the revoked release, which are the runs that pinned it, the runs whose pinned release has it in its closure and the child runs that inherited such a closure, each selected in its own right (D123), and hands each of them to one policy component with a branch for each of finish, drain and revoke, whose effects AIFACTORY-TASK-3551 delivers; the runs are found through the table RunPinnedReleases under the tenant row filter, by the release id the event names (D125); the handler is idempotent on the event id, touches no run of another tenant, no terminal run and no run whose pinned closure does not hold the release, never changes the releaseId, the policyRevision or the snapshotId of a run, and commits every state change of a run with its outbox record in one transaction. ConnectSoft.AI.SoftwareFactory.RunControlService
AIFACTORY-TASK-3551 Branches finish, drain and revoke of the in-flight policy: the cancellation intent with the reason release-revoked, the revocation transitions of the run and the stop of dispatch under drain implementation The policy component applies to a selected run the effect model/services/control-plane/RunControlService.yaml states for each value (D123): finish changes nothing and the run continues to its end; drain records a cancellation intent with the reason release-revoked and the actor system, lets the step that is running finish, makes the dispatcher dispatch no further step of the run, moves a Running run to Cancelling through ReleaseRevokedAfterRunningStepSettled once that step has settled and cancels an Accepted or a Held run at once; revoke records the same intent and moves an Accepted run to Cancelled through ReleaseRevokedBeforeDispatch, a Held run through ReleaseRevokedWhileHeld and a Running or a WaitingForApproval run to Cancelling through ReleaseRevoked, requesting the interruption of an open attempt as CancelRun does; Cancelling ends in Cancelled through AllAttemptsSettled, RunCancelled is written once per run with the reason release-revoked, no stopped run ends Failed, a run that is already Cancelling gets no second intent, a run in WaitingForApproval under drain takes the transition ReleaseRevoked at once and a run already Cancelling keeps its reason (D125), and every transition is committed with its outbox record in one transaction. ConnectSoft.AI.SoftwareFactory.RunControlService
AIFACTORY-TASK-2972 Fixture publisher of AssetReleaseRevoked and runs whose pinned closure holds the release in every non-terminal state fixture The acceptance suite of ConnectSoft.AI.SoftwareFactory.RunControlService holds a fixture publisher that sends AssetReleaseRevoked under run-event-envelope-v1 from the pinned contracts package with a stated releaseId, tenantId, reason and inFlightPolicy of finish, drain or revoke, and a fixture that creates runs in the states Accepted, Running, WaitingForApproval, Held and Cancelling that pinned that release, a run whose pinned release has it in its closure only, a parent run with an open child run that inherited the closure, a Completed run pinned to it, a run whose pinned closure does not hold it and a run of another tenant; the fixture lets the running step of a run settle and an open attempt report its outcome on demand, so that the drain and the interruption are reproducible without AgentRuntimeService. ConnectSoft.AI.SoftwareFactory.RunControlService
AIFACTORY-TASK-2973 Verify the application of the in-flight policy to pinned runs through the acceptance suite of RunControlService verification Run dotnet test -c Release --filter "Category=Acceptance&Feature=RevocationInFlightPolicy" in ConnectSoft.AI.SoftwareFactory.RunControlService; a zero-match filter counts as a failure; the tests prove AC1 to AC5 of AIFACTORY-US-736: the selection of exactly the non-terminal runs whose pinned closure holds the revoked release, child runs included, the redelivery that applies nothing twice, the pinned releaseId, policyRevision and snapshotId unchanged under each of the three policies, runs that continue to their end under finish, a Running run that finishes its running step, dispatches no further step and ends Cancelled under drain, Accepted and Held runs cancelled at once, the transitions of revoke from Accepted, Held, Running and WaitingForApproval with the open attempt interrupted, RunCancelled with the reason release-revoked and no stopped run ended Failed, and, against a registry that publishes AgentRegistryService/AssetReleaseRevoked after RevokeRelease, the handler reached once, the pinned run ended Cancelled and SubmitRun answered 409 for the release id and for an alias that still points at the revoked release. ConnectSoft.AI.SoftwareFactory.RunControlService

AIFACTORY-US-1493: Open the Draft release of an accepted learning proposal and announce its release id to FeedbackService

behavior · persona asset-maintainer As an asset maintainer, I want an accepted learning proposal to become a Draft release of its target asset in the registry, so that I review and submit the change it proposes through the same gate as every other release, and the proposal knows which release came out of it.

An asset maintainer accepts a learning proposal in FeedbackService, which announces LearningProposalDecided with the proposal id, the state, the target asset, the version the proposal starts from and the reference of the proposal text and diff. The owner decided that AgentRegistryService, the owner of releases, opens the Draft release of an accepted proposal itself when it consumes that event and announces the release id, and that FeedbackService records the resulting release from that announcement and no longer calls the registry to open a release (D131). The handler OpenReleaseCandidate passes an event with the state Accepted to the command OpenLearningRelease of the AssetRelease aggregate inside the tenant of the envelope. The command opens one Draft release of the target asset that keeps the proposal id in learningProposalId and the reference of the proposal text and diff, and writes in the same transaction the outbox record LearningReleaseOpened with releaseId, tenantId, proposalId, assetKind, assetId and version. The asset kind is that of the releases of the target asset the tenant can read. The model does not state which version the Draft release takes after the version the proposal starts from; that is reported to the owner, and the acceptance suite fixes it in its fixture. The command is idempotent on the proposal id: the unique index UX_Releases_Tenant_LearningProposal on tenant and proposal keeps one Draft release per proposal, and a repeated event opens none and announces the same release id again, so FeedbackService, which records it once per proposal, can rely on a redelivery. A rejected proposal opens nothing and announces nothing. An accepted proposal without a target asset, or whose target asset has no release the tenant can read, opens nothing and is poisoned with its reason. The Draft release enters the lifecycle of every candidate: the maintainer submits it from Draft as AIFACTORY-US-415 states for a version that exists as a Draft release, and it is published only through the gate of AIFACTORY-US-416; no handler publishes it. A release of another tenant is never touched. The dispatcher of the agent-registry messaging profile publishes LearningReleaseOpened on asset-publication.releases.v1.learning-release-opened under the run event envelope of the contracts package and retries a transport outage with backoff.

Acceptance criteria

AC1 Given a FeedbackService/LearningProposalDecided event with the state Accepted for a target asset whose releases the tenant can read, when OpenReleaseCandidate handles it, then one Draft AgentRegistryService/AssetRelease of that asset exists in the tenant of the envelope with the proposal id in learningProposalId, and the AgentRegistryService/LearningReleaseOpened outbox record with releaseId, tenantId, proposalId, assetKind, assetId and version is written in the same transaction (SCN-AgentRegistryService-015, D131, ADR-0014).
AC2 Given the event of AC1 delivered again, or another event for the same proposal, when it is handled, then no second release exists for the proposal under UX_Releases_Tenant_LearningProposal and the same release id is announced again; given a FeedbackService/LearningProposalDecided with the state Rejected, then no release is opened and nothing is announced; given an accepted proposal without a target asset or whose target asset has no release the tenant can read, then nothing is opened and the delivery is poisoned with its reason (SCN-AgentRegistryService-015, D131).
AC3 Given the Draft release of AC1, when the asset maintainer submits it through AgentRegistryService/SubmitRelease, then it moves to InReview without a second row as AIFACTORY-US-415 states and is published only through the gate of AIFACTORY-US-416; no handler publishes it, and no release of another tenant changes (ADR-0015, ADR-0021).
AC4 Given a committed opening, when the dispatcher of the agent-registry messaging profile publishes AgentRegistryService/LearningReleaseOpened on asset-publication.releases.v1.learning-release-opened, then the event is sent under the run event envelope with its six payload fields and the tenant of the release in the envelope, and a transport outage is retried with backoff so the event is neither lost nor published twice under its event id (SCN-AgentRegistryService-015, ADR-0012).
Traces: services AgentRegistryService, FeedbackService
Traces: aggregates AgentRegistryService/AssetRelease
Traces: apis AgentRegistryService/SubmitRelease
Traces: events FeedbackService/LearningProposalDecided, AgentRegistryService/LearningReleaseOpened
Traces: descriptors run-event-envelope-v1
Traces: adrs ADR-0012, ADR-0014, ADR-0015, ADR-0021
Traces: requirements FR-02
Traces: scenarios SCN-AgentRegistryService-015
Depends on feature:agent-registry-service-publication, feature:feedback-service, feature:contracts-package
Sources model/services/control-plane/AgentRegistryService.yaml, model/services/observability/FeedbackService.yaml, docs/reference/schemas/run-event-envelope.schema.json

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-6069 OpenLearningRelease with the learningProposalId column and its unique index implementation The command OpenLearningRelease of the AssetRelease aggregate opens one Draft release of the target asset of an accepted proposal inside the tenant of the envelope, keeps the proposal id in LearningProposalId and the reference of the proposal text and diff, takes the asset kind of the releases of the target asset the tenant can read and writes LearningReleaseOpened in the same transaction; the column LearningProposalId and the filtered unique index UX_Releases_Tenant_LearningProposal are added to AssetReleases; a repeat for the same proposal opens nothing and writes LearningReleaseOpened again with the same release id (D131). ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-6070 OpenReleaseCandidate passing an accepted learning proposal to OpenLearningRelease implementation The handler of LearningProposalDecided reads the tenant from the envelope, passes an event with the state Accepted to OpenLearningRelease, acknowledges a Rejected proposal without effect and poisons with its reason an accepted proposal without a target asset or whose target asset has no release the tenant can read; it never publishes a release. ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-6071 Contract of LearningReleaseOpened against the run event envelope of the contracts package contract A golden file fixes LearningReleaseOpened on asset-publication.releases.v1.learning-release-opened under run-event-envelope-v1 with releaseId, tenantId, proposalId, assetKind, assetId and version and the tenant in the envelope; a contract test fails when a serialised event differs from its file or from docs/reference/schemas/run-event-envelope.schema.json. ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-6072 Verify open-the-draft-release-of-an-accepted-learning-proposal through the acceptance suite verification Run dotnet test -c Release --filter "Category=Acceptance&Scenario=SCN-AgentRegistryService-015"; a zero-match filter counts as a failure; the tests prove AC1 to AC4 of AIFACTORY-US-1493 with contract fixtures of LearningProposalDecided: the Draft release opened once with its proposal id and the event in the same transaction, the redelivery that opens nothing and announces the same release id, the rejected proposal, the poisoned proposal without a readable target asset, the submission from Draft through the gate, and the publication and payload of LearningReleaseOpened; the recording of the resulting release is proven by the suite of FeedbackService. ConnectSoft.AI.SoftwareFactory.AgentRegistryService