Skip to content
AggregaAggrega
Select language: English

Error sentinels — canonical reference

Every fatal halt the compiler emits names a condition, and each condition carries three identifiers, because recognising a condition, recording it and quoting it are three different jobs. The sentinel is the Go value errors.Is matches, obtained by calling the accessor the declaring package exports: the identifier Go code recognises. The code is the string the condition is registered under: it names the condition itself in words, and it is what stays fixed as the Go packages around it evolve — the identifier a program records. The short code is the letter E and four digits, short enough to read out, type into a search or paste into a report: the identifier a person quotes. One condition, three identifiers — match the sentinel to recognise the condition from Go, read the code when you need to record or key on it, and resolve a short code against the table of every condition further down this page.

The user-facing diagnostic (the prefixed message catalogued in fatal-halts.md and error-translation.md) carries the developer-facing prose; the wrapped sentinel is what errors.Is matches against in programmatic consumers.

This page is the sentinel-keyed view of the catalogue. Programmers writing CI gates, IDE integrations, or build-orchestration code that needs to distinguish error kinds match against the sentinels listed here with the standard errors.Is predicate. Authors debugging a build by reading the emitted error text usually want the message-keyed views — fatal-halts.md for build-stopping errors, warnings.md for advisory output.

Each row in the tables below names an accessor — a function taking no arguments, exported from the package the table names, that returns the sentinel. Importing that package and calling the accessor is the supported integration surface, which is why the tables write each one with its parentheses — the call is what yields a value errors.Is can match, and the name without them is a function rather than an error:

import (
"errors"
"github.com/aggrega-ai/aggrega-cli/pkg/resolver"
)
if errors.Is(err, resolver.ErrParameterContractViolation()) {
// handle parameter contract violations
}

The three identifiers carry their stability separately, and that separation is the reason a condition has all three. The accessors listed below are stable across patch releases; renames or removals are announced in the changelog’s entry for the release that makes them, and adding a new accessor within a package is additive and does not break existing matchers. A code is fixed once its condition is published, so it is the identifier to record wherever a condition has to be named durably: renaming an accessor does not move the code its condition was registered under, and a code you have recorded outlives a refactor of the Go surface. A short code is the most durable of the three: a number is handed out once and then fixed, and a retired condition’s number stays retired rather than being handed to a different condition, so a short code recorded in an old report still names the condition it named when it was recorded. That is enforced rather than merely intended — a condition declared under a retired number is refused before the compiler reads any input, on every run — and every retired number is published beside the live ones in the table of every condition. The code column below carries the code, and it is the value a client of the structured diagnostic reads without linking these packages. It is published rather than inferred, because it need not restate the row it sits on — a re-exported name reports the code of the condition it forwards to, and a rule’s code names the rule rather than the accessor. The message column is the literal text the sentinel renders; the user-facing diagnostic puts a bracketed head and the source location ahead of that text. That head carries the condition’s short code, with the occurrence’s category beside it where the occurrence has one, as in [DEVELOPER_ERROR E0007] — so a reader can resolve either independently: the categories (DEVELOPER_ERROR / OPS_ERROR / CATALOG_ERROR / TRANSLATION_ERROR / FETCH_ERROR / POLICY_ERROR / TRUST_ERROR) are taught in error-translation.md, and the short codes resolve in the table of every condition on this page. Where a plugin raised the condition, the code token is qualified by the plugin that raised it — [TRANSLATION_ERROR provider/example:1.0.0/E0007] — and the short code is the final segment; error-translation.md carries why the qualifier is there and why the final segment is the one to resolve.

Reading the code of a condition

A code names the condition and nothing else, in kebab-case — parameter-contract-violation, lockfile-drift. It carries no prefix: not the package that declares it, not the stage that raises it, not a grouping of any kind. So a code stays the same when the compiler is reorganised around it, and a condition raised at more than one point in a compilation still has one name. Every condition’s name is distinct on its own, which is what makes the prefix unnecessary, and two conditions cannot be registered under one code. Read it off an error with CodeOf, from github.com/aggrega-ai/aggrega-cli/pkg/errors, which walks the wrap chain the way errors.Is does, so the code survives however many frames wrapped the error on its way back to you. That package is itself named errors, so an import alias keeps it apart from the standard library:

package release
import (
"log"
aggregaerrors "github.com/aggrega-ai/aggrega-cli/pkg/errors"
"github.com/aggrega-ai/aggrega-cli/pkg/resolver"
)
// Load reads a Release and reports the code of whatever condition halted it.
func Load(path string) error {
_, err := resolver.LoadRelease(path)
if err == nil {
return nil
}
if code, ok := aggregaerrors.CodeOf(err); ok {
// code names the condition in words, such as parameter-contract-violation.
log.Printf("%s halted: %s", path, code)
}
return err
}

CodeOf also reports whether any error in the chain carried a code at all; a chain carrying none is a fact about that chain rather than a failure. Where you would rather match the interface yourself, the same package exports it as CodedError, and errors.As finds it in the same walk.

A code travels one way. It is what a condition reports, never what identifies it to a matcher: writing the string into your own code gives you a string, and there is no path back from a string to the value errors.Is matches. Match the sentinel to recognise a condition; read the code to record one.

The code aggrega prints on a terminal is the short one, not this one. A halting diagnostic opens with a bracketed head carrying the condition’s short code, with the occurrence’s category beside it where the occurrence has one — [DEVELOPER_ERROR E0007], or [TRANSLATION_ERROR provider/example:1.0.0/E0007] where a plugin raised the condition and the code is qualified by the plugin that raised it, or [E0007] where the failure has no concern to route you to — and then the source location and the message text catalogued in fatal-halts.md. The descriptive code names the condition in words and is far too wide for that position: on the longest conditions it would fill a narrow terminal before the message began, which is the whole reason a second, compact identifier exists. So the token to work from when you have only printed output is the short code, and it resolves against the table of every condition further down this page: from a number you can read out over a phone you reach the condition, its accessor and its message text. aggrega explain <code> does that resolution at the terminal — it takes either of the condition’s codes and prints the condition together with the entry documenting the authoring fix, and it is described in aggrega explain. The message-keyed views in fatal-halts.md remain the way to work from wording rather than from an identifier.

Where a code does travel outside Go is the structured diagnostic the compiler-as-service daemon publishes, as a code field of its own on each entry rather than anything folded into the message text — so an editor extension, or any other client of that protocol, branches on what an entry reports without linking these packages and without parsing prose. That one key carries a machine-matchable code whoever assigned it, and the entry says which layer raised it. A code there has three origins, and the third is the reason a code you can look up on this page is not on its own a sign that anything failed:

  • The code of the condition a failure names, which is what this page catalogues.
  • The class code of an advisory about the rendered output — unsupported-field is one, and warnings.md describes it. It is assigned wherever the advisory was raised rather than registered as a condition, so it has no row here.
  • The registered code of an advisory about the authored documents — a name one edit from a declared one, a parameter nothing reads. Such a finding names a condition in the same form a failure does, so its code is registered and has a row on this page, and reading that row tells you what the finding is about.

So the same code you would read off a halt can also reach you from a build that finished, carried by a finding that changed nothing about the outcome. What separates the two is the outcome you were given and the layer the entry names — never the code’s own form, and never whether it resolves here. The field is omitted where nothing that produced the entry assigned a code: a failure naming no condition of Aggrega’s own, and an advisory whose raiser assigned none. aggrega serve documents the entry shape, the key that names the layer, and when the field is present.

A structured diagnostic carries both of a condition’s identifiers, and knowing which is which is the difference between an identifier you can act on and one you cannot. The code key above is for a program: hyphenated and naming the condition in words, so an extension branching on it reads as what it means, and it is the value CodeOf reports in Go. The shortCode key beside it is for a person — the letter E and four digits, the same token a halting diagnostic prints in its bracketed head. It is what you read out over a phone, type into a search box, or paste into an issue, and it is the token the table of every condition is keyed on.

Neither is short for the other, and neither is a fallback for the other. Match on the descriptive code; show a reader the short one. A surface that offered only the descriptive code would be handing an author an identifier meant for a matcher, and one that matched on the short code would be matching on a number that says nothing about the condition — which is why both travel rather than one being chosen.

A third key, codeDescription, carries where the condition is published, as a reference to open for more about the diagnostic. Its address resolves to the table of every condition on this page, so a reader following it from an editor arrives holding the short code the table is keyed on. An entry carries the short code and the reference together, or carries neither: both are present exactly where the entry names a registered condition — one with a row in that table — and both are absent where the code names a class of advisory or the identity of a conventions rule from a linter of your own that Aggrega does not declare, because there is no number to quote for those and nothing here that describes them.

Going the other way — from a code you are holding to the condition it names — the tables below are the published list. Each row carries the code beside the accessor that yields the same condition in Go, so a code read off a structured diagnostic resolves to a name you can match and to the text the condition renders. The tables cover the conditions whose accessor you can import, and two kinds of code sit outside them: a class code, which names a class of advisory rather than a condition and so has no accessor to put beside it, and a code whose condition is declared only in a package you cannot import and is re-exported nowhere, where there is no matchable name to put beside it. That second kind still names a condition, and that condition still has a short code — the table of every condition, further down this page, is keyed on the short code instead of on an importable name and so covers those as well.

The matchable surface, by declaring package

Every section below is one package you can import. Its heading is the package path relative to the module path github.com/aggrega-ai/aggrega-cli, so the section headed pkg/resolver is imported as github.com/aggrega-ai/aggrega-cli/pkg/resolver.

Entries are grouped by the package that declares the sentinel, because that is the package a matcher imports. Where in a build the condition is raised is a separate question, and one this page deliberately does not answer: a single sentinel is frequently raised from several places, and several are raised only from code the module does not export, so no per-entry answer would be true for every row. The message-keyed views answer the when-in-a-build question in terms you can observe — fatal-halts.md above all.

A few names appear in more than one package. Those are re-exports of one shared value rather than two conditions, so matching either name succeeds; the tables say so where both names are importable. Both rows carry the same code, which is the same fact stated on the identifier a client outside Go holds: one condition, one code, however many names reach it.

pkg/catalog

SentinelCodeMessage
ErrAllVersionsRetracted()all-versions-retractedevery published version this reference could select has been withdrawn
ErrAmbiguousImporterPlugin()ambiguous-importer-pluginformat is advertised by more than one importer plugin
ErrAmbiguousParserPlugin()ambiguous-parser-pluginformat is advertised by more than one parser plugin
ErrAmbiguousProviderPlugin()ambiguous-provider-plugincapability is served by more than one provider plugin; add a plugins.providers entry to select one
ErrAmbiguousTypeMapping()ambiguous-type-mappingmanifest maps multiple version-distinct keys to the same base type; the type-to-recipe lookup is ambiguous
ErrDuplicateEntityIdentity()duplicate-entity-identityduplicate entity identity within a single catalog directory
ErrImporterVersionUnsatisfiable()importer-version-unsatisfiableno importer plugin version satisfies the plugins.importer entry's version pin
ErrManifestImplementsMismatch()manifest-implements-mismatchmanifest mapping entry's recipe spec.implements does not match the mapped component-type / feature-type key
ErrNameMappingMatchedNothing()name-mapping-matched-nothinga Manifest name mapping's key names no component instance or attachment in this build, so the entry binds nothing
ErrNoImporterForFormat()no-importer-for-formatno importer plugin advertises the requested format
ErrNoParserForFormat()no-parser-for-formatno parser plugin advertises the requested format
ErrNoRecipeResolved()no-recipe-resolvedno recipe resolved for component/feature instance: add an explicit Manifest mapping for its type
ErrProviderBindingCapabilityUnserved()provider-binding-capability-unservedplugins.providers entry names a capability no provider-rendering plugin the build reads serves
ErrProviderBindingUnsatisfied()provider-binding-unsatisfiedplugins.providers entry names a plugin no provider-rendering plugin serving the capability matches
ErrProviderVersionUnsatisfiable()provider-version-unsatisfiableno provider-rendering plugin version satisfies the recipe's provider version pin
ErrQualifiedPluginReference()plugin-reference-must-not-be-registry-qualifiedwasm plugin reference must be the plugin coordinate identity (<pluginType>/<name>:<version>), not a registry-qualified or artifact path
ErrUnknownCatalogDocumentKind()unknown-catalog-document-kindcatalog document declares a kind a catalog does not hold
ErrUnsatisfiableEntityVersion()unsatisfiable-entity-versionno catalog version satisfies the referenced version constraint
ErrUnscopedPluginReference()plugin-reference-must-be-scopedwasm plugin reference must carry a pluginType scope (<pluginType>/<name>); an empty scope cannot bind to an OCI location
ErrUnscopedRecipeReference()recipe-reference-must-be-scopedrecipe reference must be provider-scoped (<provider>/<name>); an empty provider cannot bind to an OCI location
ErrUnusableSchemaImport()unusable-schema-importa schema `$import:` could not be applied
  • ErrManifestImplementsMismatch() is the same value as pkg/resolver.ErrManifestImplementsMismatch(), so a match against either name succeeds.

pkg/closure

SentinelCodeMessage
ErrInvalidLibraryRef()invalid-library-refresolve: invalid library reference URI
ErrMVSConflict()version-selection-conflictresolve: minimal version selection conflict — incompatible library version requirements
ErrNoAggregateLoader()catalog-cannot-load-sub-aggregate-bodiesresolve: catalog lookup cannot load resolved sub-aggregate bodies
ErrNoRecipeLoader()catalog-cannot-load-recipe-bodiesresolve: catalog lookup cannot load resolved recipe and plugin bodies
ErrSourceTemplateAtLockTime()source-template-at-lock-timeresolve: source-template evaluation failure at lock time
ErrSourceTemplateParse()source-template-not-parsableresolve: source-template parse error
ErrSourceTemplateProvidesRef()source-template-provides-refresolve: source-template references .provides (invalid reverse reference)
ErrSubAggregateDepth()sub-aggregate-depthresolve: sub-aggregate inclusion depth exceeded
ErrUnresolvableURI()unresolvable-uriresolve: no entity in the catalog matches this URI

pkg/compactform

SentinelCodeMessage
ErrAmbiguousDispatch()ambiguous-dispatchcompactform: ambiguous dispatch — $mode required
ErrCircularRef()reference-cyclecircular reference expansion
ErrConstraintTypeMismatch()constraint-type-mismatchcompactform: constraint not valid for declared type
ErrEscapeContentInvalid()escape-content-invalidcompactform: $jsonschema content invalid
ErrHostInLibraryRef()host-in-library-refcompactform: cross-document $ref carries a registry host; reference the library by identity
ErrReferenceUnresolvable()reference-unresolvablecompactform: $ref unresolvable
ErrUnknownKeyword()unknown-keywordcompactform: unknown keyword
ErrUnresolvedSchemaLibraryRef()unresolved-schema-library-refcompactform: cross-document $ref target not found
  • ErrCircularRef() is the same value as pkg/refcycle.ErrCycle(), so a match against either name succeeds.

pkg/deprecation

SentinelCodeMessage
ErrDeprecatedEntity()deprecated-entitydeprecation: build consumes a deprecated entity

pkg/docscache

SentinelCodeMessage
ErrFetchNotFound()fetch-not-foundoci: artifact not found at remote source
ErrNotDocsBundle()not-docs-bundledocscache: artifact is not a documentation bundle
ErrPageNotFound()page-not-founddocscache: page not found in documentation bundle
  • ErrFetchNotFound() is the same value as pkg/oci.ErrFetchNotFound(), so a match against either name succeeds.

pkg/egress

SentinelCodeMessage
ErrNoAnswerInTime()no-answer-in-timeegress: the server did not answer in time
ErrOfflineEgress()offline-egressegress: network access refused because the workspace is offline; remediation: pass `--offline=false` to allow the network for this one run, or clear the top-level `offline` key in the configuration file (or AGGREGA_OFFLINE) to allow it from now on; where the work is a build that needs content the machine does not have, run `aggrega pull --release <release>` from a connected environment first to populate the cache

pkg/externalinputs

SentinelCodeMessage
ErrAcquisitionDisabled()acquisition-disabledexternalinputs: acquisition is disabled for unpinned inputs
ErrDigestMismatch()digest-mismatchexternalinputs: fetched bytes mismatch the pinned digest
ErrSchemeNotAllowed()scheme-not-allowedexternalinputs: URL scheme is not allowed
ErrStoreCorrupt()store-corruptexternalinputs: store blob mismatches its pinned record

pkg/lockfile

SentinelCodeMessage
ErrLockfileDrift()lockfile-driftlockfile: out of date; it no longer matches what its Release resolves to
ErrLockfileInvalid()lockfile-invalidlockfile: file failed schema validation
ErrSignatureNotRecorded()signature-not-recordedsigning: no verified signature is recorded for an artifact that requires one

pkg/oci

SentinelCodeMessage
ErrAmbiguousContentLayer()ambiguous-content-layeroci: manifest has multiple layers of the expected content media type
ErrBundleAmbiguousEntityDocument()bundle-ambiguous-entity-documentoci: published bundle carries more than one entity document
ErrBundleNoEntityDocument()bundle-no-entity-documentoci: published bundle carries no entity document
ErrBundleUnreadable()bundle-unreadableoci: published bundle cannot be unpacked
ErrCacheLocationOutsideCache()cache-location-outside-cachea value a cache location is built from would place cached files outside the place it names in the cache
ErrCachedManifestIntegrity()cached-manifest-integrityoci: cached manifest digest mismatch
ErrFetchIntegrity()fetch-integrityoci: content digest mismatch
ErrFetchNetworkUnreachable()fetch-network-unreachableoci: network unreachable
ErrFetchNotFound()fetch-not-foundoci: artifact not found at remote source
ErrFetchUnauthorized()fetch-unauthorizedoci: authentication required or failed
ErrImmutableTagConflict()immutable-tag-conflictoci: tag already published with different content
ErrNoContentLayer()no-content-layeroci: manifest has no layer of the expected content media type
ErrOCILocationCollision()oci-location-collisionoci: distinct catalog identities map to the same OCI repository location
ErrPublishedArtifactNotAnEntity()published-artifact-not-an-entityoci: published artifact is not an entity document
ErrReferrerDiscoveryUnavailable()referrer-discovery-unavailableoci: referrer discovery could not be completed
ErrRegistryTooBusy()registry-too-busyoci: the registry kept asking to slow down
ErrRetiredMediaType()retired-media-typeoci: artifact carries a media type this compiler no longer reads
ErrSignatureBundleDigestMismatch()signature-bundle-digest-mismatchcached signature bundle does not match its recorded digest
ErrSignatureForAnotherArtifact()signature-for-another-artifactsigning: the recorded signature was made for a different artifact
ErrUnknownEntityKind()unknown-entity-kindoci: unknown entity kind for mediatype dispatch

pkg/pathscope

SentinelCodeMessage
ErrNameWindowsCannotHold()name-windows-cannot-holda name this operation writes holds a path segment Windows cannot hold as written

pkg/pluginpath

SentinelCodeMessage
ErrPluginArtifactNotFound()plugin-artifact-not-foundplugin artifact not found on this machine
ErrPluginEntityNotFound()plugin-entity-not-foundplugin reference is not a Plugin entity

pkg/pluginstrust

SentinelCodeMessage
ErrVerdictAttachmentNotConfigured()verdict-attachment-not-configureda plugin recorded as trusted for an accept-or-reject verdict is no longer attached at any verdict role

pkg/plugintest

SentinelCodeMessage
ErrCommandsMismatch()wasm-command-set-mismatchwasm: recorded command mirror does not match plugin describe()
ErrContractMismatch()wasm-contract-mismatchwasm: entity contract claim does not match plugin describe()
ErrHostFunctionsMismatch()wasm-host-function-set-mismatchwasm: stamped host-function record does not match .wasm imports
ErrRejected()wasm-manifest-rejectedwasm: plugin rejected by the sandbox
ErrTypeMismatch()wasm-plugin-type-mismatchwasm: declared plugin type does not match plugin describe()

pkg/readscope

SentinelCodeMessage
ErrReadLeadsOutOfWorkspace()read-leads-out-of-workspacea file this operation reads leads through a link out of the directory it must stay inside
ErrReferenceLeadsOutOfWorkspace()reference-leads-out-of-workspacea reference a document makes to another file leads out of the directory it must stay inside

pkg/recipepin

SentinelCodeMessage
ErrEntityNotPinned()entity-not-pinnedan input the entity reads has no pin recorded for it in the entity.lock beside it
ErrLocalSourceContentMismatch()local-source-content-mismatchthe files of the entity's local source do not match the pins recorded for them in entity.lock

pkg/refcycle

SentinelCodeMessage
ErrCycle()reference-cyclecircular reference expansion

pkg/registrytrust

SentinelCodeMessage
ErrMalformedTrust()malformed-trust-policyregistrytrust: advertised trust config is malformed
ErrNoTrustAdvertised()no-trust-advertisedregistrytrust: registry advertises no trust config
ErrOfflineRegistrationWithoutTrustPolicy()offline-registration-without-trust-policya registry other than the official hub is not registered offline without a trust policy supplied by hand, because the policy it advertises cannot be fetched; register it once while online, or pin its trust by hand with `aggrega registry add <host> --identity <identity>=<issuer>` or `--key <public-key-file>`

pkg/resolver

SentinelCodeMessage
ErrAnnotationBindingPillarOverlap()annotation-binding-pillar-overlapannotation binding declares one path in both pillar lists
ErrAnnotationBindingTargetUnresolved()annotation-binding-target-unresolvedannotation binding does not resolve against its target Feature
ErrAnnotationScalarNotRoutable()annotation-scalar-not-routablea scalar annotation value does not route to exactly one path of its binding
ErrAnnotationSidePillarMismatch()annotation-side-pillar-mismatchannotation routes through a pillar its authoring side may not use
ErrAnnotationSubkeyNotBound()annotation-subkey-not-boundannotation subkey is not routed by the annotation's binding
ErrAnnotationSubkeyNotConforming()annotation-subkey-not-conformingannotation subkey does not conform to the target Feature's schema at the routed pillar
ErrAttachmentInjectValue()attachment-inject-valueinject entry on an attachment carries `value:`; an attachment delivers the keys its FeatureRecipe publishes, each named with `from:`, and a literal belongs in the component's own inject block
ErrAttachmentSlotNearMiss()attachment-slot-near-missattachment name is a near miss for a declared slot
ErrAttachmentSlotShape()attachment-slot-shapeattachment does not conform to its declared slot shape
ErrConnectionAttachmentSlotUndeclared()connection-attachment-slot-undeclareda connection carries an attachment under a name its socket declares no slot for
ErrDuplicateBoundaryComponent()duplicate-boundary-componentcomponent declared in more than one boundary: declare each component in exactly one boundary
ErrDuplicateTriadIdentity()duplicate-triad-identityduplicate Aggregate/Manifest identity (metadata.name) in the Release directory
ErrFeatureMergeConflict()feature-merge-conflictfeature merge conflict: reconcile the Aggregate and Release declarations for the feature
ErrGuardEntityViewInconsistency()internal-catalog-view-disagreementthe compiler's own views of the catalog disagree
ErrInheritedBoundaryDirectoryIsLiteral()inherited-boundary-directory-is-literalinherited boundary directory carries no template variable, so it resolves to the path the extended Release writes to
ErrInjectDeliveryShape()inject-delivery-shapeinject delivery: shape must be a list of entries, each `in:` with exactly one of `from:` or `value:`
ErrInjectEntryAmbiguous()inject-entry-ambiguousinject entry carries both `value:` and `from:`; schema requires exactly one
ErrInjectKeyCollision()inject-key-collisionduplicate delivery key across inject sources
ErrInvalidInjectKey()invalid-inject-keyinvalid inject key: the from-key must name a provides key its source publishes
ErrInvalidParameterRef()invalid-parameter-refinvalid parameter reference: check the {{ .parameters.* }} expression names a declared parameter and parses as a Go template
ErrMalformedRecipeReference()malformed-recipe-referencemalformed recipe reference in a Manifest mapping value
ErrManifestCrossBindingPillarCollision()manifest-cross-binding-pillar-collisionmanifest annotation bindings collide on same Feature path+pillar
ErrManifestImplementsMismatch()manifest-implements-mismatchmanifest mapping entry's recipe spec.implements does not match the mapped component-type / feature-type key
ErrManifestReservedPrefix()manifest-reserved-prefixmanifest annotation binding uses reserved prefix
ErrMisnamedSlotFill()misnamed-slot-fillattachment written under a name no slot declares fits a slot its component leaves empty
ErrMissingRequiredFeature()missing-required-featuremissing required feature: attach a Feature of the required type to the component
ErrMissingRequiredSocket()missing-required-socketrequired uses socket not populated
ErrParameterContractViolation()parameter-contract-violationparameter contract violated
ErrParameterMissing()parameter-missingrequired parameter not supplied
ErrProvidesKeyNotDeclared()provides-key-not-declaredRecipe publishes a provides key its Component does not declare
ErrReleaseChainComposesBothRoutingKeys()release-chain-composes-both-routing-keysrelease extends chain composes both named boundaries and top-level components: declare one routing shape across the chain, never both
ErrSchemaConformance()schema-conformanceauthored pillar does not conform to its declared schema
ErrSchemaContractCompileFailure()schema-contract-compile-failuredeclared schema contract could not be compiled into a usable schema, so nothing was validated against it: correct the contract where it is declared, or remove it if the configuration it covers needs no validation
ErrSelfInjectForbidden()self-inject-forbiddenself-inject on component without spec.inject allowlist
ErrTriadRefUnresolvable()triad-ref-unresolvableaggregate/manifest reference unresolvable
ErrUnknownUsesSocket()unknown-uses-socketunknown uses socket: name a socket the entity declares in its usesSchema — only a component's own uses block may name one the catalog did not declare
ErrUnnormalizedRelease()release-not-in-canonical-formrelease reached resolve un-normalized (non-empty root components alongside a synthesized default boundary)
ErrUnreadParameter()unread-parameterdeclared parameter is read by no reference in the Aggregate
ErrUsesInjectValue()uses-inject-valueinject entry on a connection carries `value:`; a connection delivers the target's published keys, each named with `from:`
ErrUsesSocketNearMiss()uses-socket-near-missuses socket name is a near miss for a declared socket
ErrVerdictPluginTrustMismatch()verdict-plugin-trust-mismatchthe digest recorded as trusted for this plugin does not match the digest its cached manifest reports
ErrYAMLLoad()document-not-loadablefile load failed: the file could not be read, or its bytes did not parse

pkg/signing

SentinelCodeMessage
ErrKeylessLive()keyless-signing-requires-networksigning: keyless signing requires a live identity provider, Fulcio, and Rekor
ErrMixedSigningCredentials()mixed-signing-credentialssigning: the references named together need different signing credentials, so nothing was signed
ErrNoSignatureFound()no-signature-foundsigning: no signature found for an artifact that requires one
ErrNoTrustedIdentities()no-trusted-identitiessigning: keyless verification requires at least one trusted identity
ErrSignatureInvalid()signature-invalidsigning: signature does not verify
ErrSignatureVerificationFailed()signature-verification-failedsigning: signature bundle does not verify
ErrSigningPolicyRequiresSignature()signing-policy-requires-signaturesigning: signing policy requires a signature for this artifact kind; refusing to push unsigned content
ErrTrustRootLoad()trust-root-not-loadablesigning: cannot load pinned trust root
ErrUnsignedPushRefused()unsigned-push-refusedsigning: registry requires signatures; refusing to push unsigned content
ErrUnsupportedKey()unsupported-keysigning: unsupported held-key type
ErrUntrustedIdentity()untrusted-identitysigning: signature identity is not trusted for this registry

pkg/sourcecache

SentinelCodeMessage
ErrFetchIntegrity()fetch-integrityoci: content digest mismatch
ErrFetchNotFound()fetch-not-foundoci: artifact not found at remote source
  • ErrFetchIntegrity() is the same value as pkg/oci.ErrFetchIntegrity(), so a match against either name succeeds.
  • ErrFetchNotFound() is the same value as pkg/oci.ErrFetchNotFound(), so a match against either name succeeds.

pkg/sourcekind

SentinelCodeMessage
ErrUnknownKind()unknown-source-kindno source adapter serves the source kind

pkg/sourceresolver

SentinelCodeMessage
ErrFetchIntegrity()fetch-integrityoci: content digest mismatch
ErrFetchNetworkUnreachable()fetch-network-unreachableoci: network unreachable
ErrFetchNotFound()fetch-not-foundoci: artifact not found at remote source
ErrFetchUnauthorized()fetch-unauthorizedoci: authentication required or failed
ErrNoAdapterRegistered()source-adapter-not-registeredno source adapter is registered in this program for the source kind
  • ErrFetchIntegrity() is the same value as pkg/oci.ErrFetchIntegrity(), so a match against either name succeeds.
  • ErrFetchNetworkUnreachable() is the same value as pkg/oci.ErrFetchNetworkUnreachable(), so a match against either name succeeds.
  • ErrFetchNotFound() is the same value as pkg/oci.ErrFetchNotFound(), so a match against either name succeeds.
  • ErrFetchUnauthorized() is the same value as pkg/oci.ErrFetchUnauthorized(), so a match against either name succeeds.

pkg/sourceresolver/cacheslot

SentinelCodeMessage
ErrEmptyWorkspaceRoot()empty-workspace-rootcacheslot: empty workspaceRoot

pkg/sourceresolver/netrc

SentinelCodeMessage
ErrNetrcFileUnreadable()netrc-file-unreadablethe netrc file could not be read
ErrSourceURLCarriesCredential()source-url-carries-credentialthe source URL carries a credential

pkg/types

SentinelCodeMessage
ErrArtifactEntryShape()artifact-entry-shapeartifacts entry: shape must be a string scalar or {$import: <local-path>}
ErrArtifactLibraryEntryShape()artifact-library-entry-shapeartifactlibrary: entry must be a mapping of filename to a string body
ErrForbiddenKeyword()forbidden-keywordschemalibrary: forbidden JSON Schema keyword
ErrLibraryReferenceWhitespace()library-reference-whitespacelibrary reference: a reference to a library entry carries no whitespace or line break
ErrMalformedVersionPin()malformed-version-pinreference carries a malformed version pin
ErrMappingEntryNotScalar()mapping-entry-not-scalarmappinglibrary: entry body must be a string scalar
ErrOrderedMapDecodeDepthExceeded()document-nesting-depth-exceededa document nests too many levels deep
ErrParametersShape()parameters-shapeparameters: shape must be an inline object or {$import: <local-path>}
ErrTemplateNotFound()template-not-foundschemalibrary: template not found
ErrTemplateParamMissing()template-param-missingschemalibrary: template parameter missing
ErrTemplateParamTypeMismatch()template-param-type-mismatchschemalibrary: template parameter type mismatch
ErrValuesMappingShape()values-mapping-shapevaluesmapping: shape must be a string scalar or {$import: <path-or-library-identity>}
ErrWellKnownAnnotationScope()well-known-annotation-scopewellKnownAnnotations: a key is declared at a scope the provider's contract does not render
ErrWorkloadEntryNotScalar()workload-entry-not-scalarworkloadlibrary: entry body must be a string scalar
ErrWorkloadTemplateShape()workload-template-shapeworkload: shape must be a string scalar or {$import: <path-or-library-identity>}

pkg/usesedge

SentinelCodeMessage
ErrDanglingUsesTarget()dangling-uses-targetuses edge target does not exist
ErrReleaseEdgeRetarget()release-edge-retargetrelease edge retargets a developer-declared edge

pkg/validator

SentinelCodeMessage
ErrAssertionNameCollision()assertion-name-collisionassertion name declared twice across the extends chain
ErrCyclicExtension()cyclic-extensioncyclic extends chain
ErrDuplicateContainerEnvironmentVariable()duplicate-container-environment-variablea container declares one environment variable twice
ErrEmptySource()recipe-source-is-emptyrecipe source is an empty string, which names neither sourceless mode nor sourced mode
ErrExtendsChainTooDeep()extends-chain-too-deepextends chain exceeds maximum depth
ErrFeatureRecipeValuesMappingRequiresSource()feature-recipe-values-mapping-requires-sourceFeatureRecipe: valuesMapping requires source
ErrInheritanceMerge()extends-merge-failedinheritance merge failed
ErrRecipeFilenameCollisionAcrossInputKinds()recipe-filename-collision-across-input-kindsfilename collision across input kinds: two input-kind blocks produced a file under one output name
ErrRecipeNoInputKind()recipe-no-input-kindRecipe: at least one input kind required
ErrRecipeOutputComponentLabelCollision()recipe-output-component-label-collisionrecipe output-component-labels constraint: key is also declared in outputLabels
ErrRecipeOutputLabelReservedNamespace()recipe-output-label-reserved-namespacerecipe output-labels constraint: key uses a reserved namespace
ErrRecipeValuesMappingRequiresSource()recipe-values-mapping-requires-sourceRecipe: valuesMapping requires source
ErrSlotNotReferenceable()slot-not-referenceableworkload attachment slot is not referenceable
ErrUnknownSchemaPillar()unknown-schema-pillara schema block declares a key that names no data pillar
ErrWorkloadFeaturesSchema()workload-features-schemaworkload featuresSchema cross-check failed
ErrWorkloadValidation()workload-not-validworkload validation failed

pkg/validator/envelope

SentinelCodeMessage
ErrDuplicatePipelineStepID()duplicate-pipeline-step-ida pipeline declares one step id twice
ErrEntityEnvelope()entity-envelope-invaliddocument envelope validation failed
ErrRetiredABIVersion()retired-abi-versiona plugin declares a plugin ABI version this compiler no longer speaks
ErrRetiredAPIVersion()retired-api-versiona document declares an API version this compiler no longer reads

pkg/validator/jsonschema

SentinelCodeMessage
ErrExtensionEval()schema-extension-evaluation-failedvalidator/jsonschema: x-aggrega extension evaluation failed
ErrSchemaResolve()schema-not-resolvablevalidator/jsonschema: schema resolution failed

pkg/validator/merger

SentinelCodeMessage
ErrMergeInvalid()schema-merge-input-invalidmerger: invalid merge input

pkg/workspaceconfig

SentinelCodeMessage
ErrAmbiguousRegistryAlias()ambiguous-registry-aliasregistry alias matches more than one host
ErrCapabilityOnCrossCuttingSocket()capability-on-cross-cutting-socketa cross-cutting socket is bound by capability but attaches by uri
ErrColonInProviderBindingCapability()colon-in-provider-binding-capabilitya provider socket binding names a capability containing a colon, which no Recipe can select
ErrConfigInvalid()workspace-config-invalidworkspace configuration is invalid
ErrDuplicateImporterAttachment()duplicate-importer-attachmentimporter is attached by more than one plugins.importer entry
ErrDuplicateProviderTarget()duplicate-provider-targetcapability is bound to more than one provider plugin
ErrDuplicateRegistryAlias()duplicate-registry-aliasregistry alias is already used by another host
ErrGovernanceRoleInvalid()governance-role-invalida governance attachment declares no role or an unknown role
ErrInertFieldOnProviderSocket()inert-field-on-provider-socketa provider socket binding sets a field with no referent on that socket

pkg/writescope

SentinelCodeMessage
ErrWriteLeadsOutOfWorkspace()write-leads-out-of-workspacea path this operation writes or deletes leads through a link out of the directory it must stay inside

pkg/yamlpos

SentinelCodeMessage
ErrPositionOutOfRange()position-out-of-rangeposition out of range

Sentinels that carry another sentinel

ErrCacheMetadataInvalid (pkg/sourceresolver/metadata) reports a corrupt source-artifact cache slot. It is declared as a wrapper around ErrFetchIntegrity() rather than as an identity of its own, so it does not appear in the tables above and a match against ErrFetchIntegrity() succeeds for it as well. Because it wraps a sentinel instead of declaring one, it is exported as a value rather than as a function: match it as ErrCacheMetadataInvalid, with no parentheses. Match the wrapper when you want that specific condition, and the wrapped sentinel when you want the whole integrity class.

Sentinels reachable under a second name in one package

Where a package exports two accessors for one condition — the second declared as a forward to the first — the tables above carry the declaring accessor and leave the forwarding name out. Both names are exported from the same package, so an import that reaches either already reaches the other, and a second row would list one condition twice under a name that matches nothing new. Matching either name succeeds: the forward returns the same value the declaring accessor returns.

This is not the cross-package case. A sentinel re-exported from another package carries a row in each package’s table, because a matcher importing one of those packages cannot reach the other’s name without importing that package too; a forward inside a single package needs no second row, because one import reaches both names.

ErrDuplicateRecipeIdentity() in pkg/catalog is such a forward: it returns ErrDuplicateEntityIdentity(), which is the name the table for that package carries.

Conditions with no matchable sentinel

Some compilation stages declare their sentinels in packages the compiler does not export, so there is nothing for errors.Is to reference and no matcher can be written against them. They are described here rather than tabulated, because a table on this page is a promise that the left-hand column can be dereferenced.

Their diagnostics reach you in full through the emitted error text and through the message-keyed views — fatal-halts.md in particular — which is the supported way to recognise them:

  • Topology construction (graph construction and sub-aggregate flattening) reports a sub-Aggregate that could not be loaded, naming the unreachable Aggregate URI; a uses: declaration whose structural shape does not match the schema; nesting depth exceeded; and a flattened node-ID collision, where two sub-Aggregates compile to the same node ID and one instance name has to be renamed to disambiguate.
  • Graph finalization (Feature merging across the Aggregate and Release surfaces) reports a Feature type declared inconsistently between the two.
  • Static analysis (selector evaluation and cross-node type-safety checks) reports a selector: violation; a catalog-resolution miss it cannot proceed past, naming the unreachable entity; and a policy rejection, where a plugin attached at a governance verdict role rejected the assembled build. A policy rejection carries the POLICY_ERROR category, the rejecting plugin’s name, and the rule message the plugin supplied.
  • Rendering (provider dispatch and per-provider rendering) reports an unknown provider.
  • The embedded Wasm host loader emits its own guardrail sentinels — a manifest-rejected guardrail (a plugin requested a runtime-access capability the AOT-purity firewall denies), a guest-panic recovery, and a deterministic plugin-exit trap. These surface in the user-facing diagnostic when running a plugin (for example through aggrega lint). Plugin authors testing a guest against the host reach the same conditions by importable name through pkg/plugintest, listed above.

To gate a pipeline on a policy rejection specifically, match the POLICY_ERROR category prefix in the diagnostic rather than a sentinel; the category is a documented part of the error surface, described in error-translation.md.

Every condition, by short code

The table below runs the lookup the other way round: a short code in the left-hand column, and beside it the condition that code names and the text that condition renders. It covers every condition aggrega can report, the ones the sections above cannot list included.

That wider coverage is the point of this table rather than an accident of it. The sections above are keyed on a name you can import, so a condition declared only in a package you cannot import — and re-exported nowhere you can import either — has nothing to put in their left-hand column. This table is keyed on the short code, and every condition has one, so no reportable condition falls outside it. A short code you are holding resolves here whether or not the condition behind it also has an accessor you can match.

What earns a place in this table is that the compiler can actually report the condition. The rows are derived from the code rather than transcribed into it: a condition appears here because something in the compiler raises it, so every code in the left-hand column is one aggrega can print. That is the promise the table makes, and it is what lets you read a row as a check that really runs.

The deliberate exception is a condition declared before the code that reports it exists, so that the code and the wording are fixed in advance and never change under a reader who has already quoted them. Such a condition says so in a note directly beneath the table. It is listed rather than hidden — a code you are holding should always resolve — and the note beside it tells you plainly that no build raises it yet, and what would have to exist before one did.

A retired number is listed too, in its own set of notes beneath the table, and it stays listed permanently. A condition is occasionally withdrawn — it is replaced by one covering more ground, or nothing ever reported it — and from that moment its number is retired: it is never handed to a different condition, so a short code you quote off an old report can only ever name what it named when the report was written. That promise is mechanical rather than editorial. A condition declared under a retired number is refused before the compiler reads any input, on every run, so no release can carry one — the same class of refusal a number two live conditions tried to share would meet, worded so you can tell which of the two you hit. The note for a retired code tells you, where the retirement recorded it, what the code named and, where the condition was replaced, which code reports that ground now.

Never reusing a number is also what gives the sequence its permanent gaps, and the notes are what make those gaps readable. A missing number is not on its own evidence of anything: it may be retired, and it may equally be one nothing has reached yet. The notes are the record of which numbers are retired and, where it was recorded, what each of them named, so a code resolving to neither a row nor a note is one this compiler has never issued.

A short code is deliberately opaque: four digits say nothing about a condition on their own, which is the price of an identifier short enough to read out, type into a search, or paste into a report. The correspondence below is what makes it usable. A number is handed out once, from a single ascending sequence, and is fixed from then on; it says nothing about the condition it names. So a short code is an identifier and nothing more — its value is not a classification, and neither it nor any grouping you may notice in the table is a guide to where a condition lives or to what it is about.

The table carries no category column, and that is not an omission: a category is a property of a particular failure rather than of the condition behind it. Some conditions belong to one category by construction. For others the category follows from the kind of entity the failure is about, so one such condition reported once against an Aggregate and once against a Release carries a different category each time — and a single value written beside the condition here would be wrong for every condition of that second kind.

Where the categories are taught is error-translation.md — each one, what it means, and where the fix for it lives. A category and a short code answer different questions about the same failure: the category identifies the surface the fix belongs on, and the short code identifies which condition halted the build. Neither is derivable from the other, which is why each has its own published list — and why a failure with no authoring surface to name still carries a code you can look up here.

CodeConditionMessage
E0001no-plugin-resolution-configuredcliplugin: no plugin resolver configured
E0003malformed-attachment-requirementmalformed attachment requirement
E0004overridden-annotationannotation contribution overridden by an explicit value
E0005policy-violationpolicy violation
E0006required-slot-unfilledrequired attachment slot unfilled
E0007selector-violationselector violation
E0008slot-selector-unsatisfiedattachment slot selector unsatisfied
E0009pipeline-contract-violationpipeline step typed-I/O contract violation
E0010pipeline-step-failedpipeline step failed
E0011pipeline-target-absentpipeline patch targets a document not present in the set
E0012pipeline-target-opaquepipeline patch targets an opaque (non-structured) unit
E0013feature-type-mismatchfeature type mismatch between Aggregate and Release
E0014inject-entry-ambiguousinject entry carries both `value:` and `from:`; schema requires exactly one
E0015uses-inject-forbiddenuses-edge inject dictates a delivery mechanism the socket does not permit
E0016patch-test-operation-failedjsonpatch: test operation failed
E0017annotation-injection-rejectedannotation-transform plugin output was rejected: an injection targets a component coordinate the host did not supply, or carries a value that is not a string or an object of subkeys
E0018policy-settings-invalidpolicy attachment settings do not satisfy the plugin's declared settings schema
E0019endpoint-requires-reference-formendpoint requires form: reference
E0020invalid-cron-scheduleschedule is not a valid cron expression
E0021persistent-template-requires-stateful-formpersistentTemplate volume requires form: stateful
E0022pipeline-patch-target-not-structuredpipeline PATCH target is not parseable structured YAML/JSON
E0023reference-form-requires-endpointform: reference requires an endpoint
E0024schedule-requires-scheduled-formschedule requires form: scheduled
E0025scheduled-form-requires-scheduleform: scheduled requires a schedule
E0026artifact-content-mismatchimported artifact content does not match the digest recorded for it in entity.lock
E0027artifact-import-shapeartifacts $import: is not a bare-name artifact-library reference (<Library>#/artifacts/<entry>)
E0028artifact-output-collisionartifacts output filename collision: two artifact outputs carry the same filename
E0029artifact-pillar-not-declaredartifact template references a pillar the Recipe does not declare
E0030artifact-library-entry-not-foundartifact-library import references a bundle not present in the ArtifactLibrary
E0031artifact-library-not-foundartifact-library import references an ArtifactLibrary not present in the catalog
E0032assembled-output-collisionassembled output collision: two contributors write the same output path
E0033authored-assertion-failedassertion failed
E0034attachment-inject-key-collisionduplicate delivery key across attachment-inject and another inject source
E0035boundary-assembly-not-providedprovider expected to assemble its dispatch group provides no boundary assembler
E0036chart-name-mismatchmerged-path assembly has conflicting assembly-name annotation values
E0037cross-provider-link-unsupportedcross-boundary link between endpoints rendered by different providers is not supported
E0038derived-key-collisionderived name collision: one name is derived more than once in one key space
E0039featurerecipe-template-invalid-fieldFeatureRecipe template references a per-component-only field with executionScope: boundary
E0040host-in-library-importlibrary $import: carries a registry host; reference the library by bare-name identity
E0041instance-id-collisionmultiple contributors share an instance ID at the same dispatch path
E0042locals-forward-referencelocals entry references a sibling defined later in the same block
E0043locals-unknown-referencetemplate references a key the locals block does not declare
E0044mapping-entry-not-foundmapping-library import references an entry not present in the MappingLibrary
E0045mapping-import-shapevaluesMapping $import: is not a bare-name mapping-library reference (<Library>#/mappings/<entry>)
E0046mapping-library-not-foundmapping-library import references a MappingLibrary not present in the catalog
E0047orphan-cross-boundary-link-placeholderassembled output retains an unresolved cross-boundary link placeholder
E0048path-collisiondispatch path produced multiple provider outputs
E0049path-template-invalid-fieldpath template references a field not in the documented allowlist
E0050pipeline-host-scope-unavailablepipeline /host operation from a step with no host component
E0051pipeline-patch-targets-unassembled-fragmentspipeline PATCH targets an assembler provider's pre-assembly fragments
E0052pipeline-target-not-emittedpipeline PATCH targets a document the node did not emit
E0053plugin-provider-incompatiblepipeline plugin is not compatible with the rendering provider
E0054provider-node-input-invalidprovider rejected node input
E0055provides-contract-unfulfilledRecipe or FeatureRecipe does not publish a provides key its abstract entity's schema.provides contract declares
E0056provides-evaluation-failedprovides template evaluation failed
E0057provides-self-containmentprovides block references a root outside the self-contained set
E0058render-nondeterministicprovider render is not deterministic
E0059self-inject-key-collisionduplicate delivery key across self-inject and uses-inject
E0060template-unknown-roottemplate references a root the render context does not define
E0061unknown-providerunknown provider
E0062custom-mechanism-has-no-mappingcustom inject mechanism has no matching key in injectMapping output; add the mechanism's key to the Recipe injectMapping
E0063workload-entry-not-foundworkload-library import references an entry not present in the WorkloadLibrary
E0064workload-import-shapeworkload $import: is not a bare-name workload-library reference (<Library>#/workloads/<entry>)
E0065workload-library-not-foundworkload-library import references a WorkloadLibrary not present in the catalog
E0066dangling-uses-targetuses edge target does not exist
E0067active-toggle-not-a-booleanactive toggle did not resolve to a boolean
E0068sub-aggregate-nesting-depth-exceededmax sub-aggregate nesting depth exceeded
E0069mutator-patch-rejectedmutator patch rejected
E0070reexport-cyclere-exported component alias forms a cycle
E0071release-edge-retargetrelease edge retargets a developer-declared edge
E0072sub-aggregate-not-loadablesub-aggregate load failed
E0073sub-aggregate-name-collisionflattened node ID collision: rename one of the colliding instances so their flattened IDs differ
E0074unbound-release-edge-configrelease per-edge configuration has no edge to apply to
E0075aggregate-not-in-canonical-formaggregate reached topology un-normalized (non-empty root components alongside a synthesized default subsystem)
E0076unplaced-sub-modulesub-module placed in no boundary: route it into a boundary under `aggregates`, or name its components there under `components`
E0077uses-target-not-activeuses edge target was pruned because its active toggle resolved to false
E0078wasm-nested-producer-consumption-deniedproducer-consumption re-entry denied: a producer reached through the host may not issue a further producer-consumption call
E0079wasm-command-set-mismatchwasm: recorded command mirror does not match plugin describe()
E0080wasm-contract-mismatchwasm: entity contract claim does not match plugin describe()
E0081wasm-diagnostic-severity-invalidwasm: guest plugin returned a diagnostic whose severity the contract does not declare
E0082wasm-guest-errorwasm: guest plugin reported an error
E0083wasm-guest-panicwasm: guest plugin panicked during call
E0084wasm-host-function-set-mismatchwasm: stamped host-function record does not match .wasm imports
E0085wasm-manifest-rejectedwasm: plugin rejected by the sandbox
E0086wasm-plugin-exitedwasm: plugin invoked proc_exit
E0087wasm-plugin-type-mismatchwasm: declared plugin type does not match plugin describe()
E0088wasm-plugin-version-mismatchwasm: entity metadata.version does not match plugin describe()
E0089all-versions-retractedevery published version this reference could select has been withdrawn
E0090ambiguous-importer-pluginformat is advertised by more than one importer plugin
E0091ambiguous-parser-pluginformat is advertised by more than one parser plugin
E0092ambiguous-provider-plugincapability is served by more than one provider plugin; add a plugins.providers entry to select one
E0093ambiguous-type-mappingmanifest maps multiple version-distinct keys to the same base type; the type-to-recipe lookup is ambiguous
E0094duplicate-entity-identityduplicate entity identity within a single catalog directory
E0095malformed-recipe-referencemalformed recipe reference in a Manifest mapping value
E0096manifest-implements-mismatchmanifest mapping entry's recipe spec.implements does not match the mapped component-type / feature-type key
E0097no-importer-for-formatno importer plugin advertises the requested format
E0098no-parser-for-formatno parser plugin advertises the requested format
E0099no-recipe-resolvedno recipe resolved for component/feature instance: add an explicit Manifest mapping for its type
E0100provider-binding-unsatisfiedplugins.providers entry names a plugin no provider-rendering plugin serving the capability matches
E0101provider-version-unsatisfiableno provider-rendering plugin version satisfies the recipe's provider version pin
E0102plugin-reference-must-not-be-registry-qualifiedwasm plugin reference must be the plugin coordinate identity (<pluginType>/<name>:<version>), not a registry-qualified or artifact path
E0103unsatisfiable-entity-versionno catalog version satisfies the referenced version constraint
E0104plugin-reference-must-be-scopedwasm plugin reference must carry a pluginType scope (<pluginType>/<name>); an empty scope cannot bind to an OCI location
E0105recipe-reference-must-be-scopedrecipe reference must be provider-scoped (<provider>/<name>); an empty provider cannot bind to an OCI location
E0106invalid-library-refresolve: invalid library reference URI
E0107version-selection-conflictresolve: minimal version selection conflict — incompatible library version requirements
E0108catalog-cannot-load-sub-aggregate-bodiesresolve: catalog lookup cannot load resolved sub-aggregate bodies
E0109catalog-cannot-load-recipe-bodiesresolve: catalog lookup cannot load resolved recipe and plugin bodies
E0110source-template-at-lock-timeresolve: source-template evaluation failure at lock time
E0111source-template-not-parsableresolve: source-template parse error
E0112source-template-provides-refresolve: source-template references .provides (invalid reverse reference)
E0113sub-aggregate-depthresolve: sub-aggregate inclusion depth exceeded
E0114unresolvable-uriresolve: no entity in the catalog matches this URI
E0115ambiguous-dispatchcompactform: ambiguous dispatch — $mode required
E0116constraint-type-mismatchcompactform: constraint not valid for declared type
E0117escape-content-invalidcompactform: $jsonschema content invalid
E0118host-in-library-refcompactform: cross-document $ref carries a registry host; reference the library by identity
E0119reference-unresolvablecompactform: $ref unresolvable
E0120unknown-keywordcompactform: unknown keyword
E0121unresolved-schema-library-refcompactform: cross-document $ref target not found
E0122deprecated-entitydeprecation: build consumes a deprecated entity
E0123not-docs-bundledocscache: artifact is not a documentation bundle
E0124page-not-founddocscache: page not found in documentation bundle
E0125offline-egressegress: network access refused because the workspace is offline; remediation: pass `--offline=false` to allow the network for this one run, or clear the top-level `offline` key in the configuration file (or AGGREGA_OFFLINE) to allow it from now on; where the work is a build that needs content the machine does not have, run `aggrega pull --release <release>` from a connected environment first to populate the cache
E0126acquisition-disabledexternalinputs: acquisition is disabled for unpinned inputs
E0127digest-mismatchexternalinputs: fetched bytes mismatch the pinned digest
E0128scheme-not-allowedexternalinputs: URL scheme is not allowed
E0129store-corruptexternalinputs: store blob mismatches its pinned record
E0130lockfile-driftlockfile: out of date; it no longer matches what its Release resolves to
E0131lockfile-invalidlockfile: file failed schema validation
E0132ambiguous-content-layeroci: manifest has multiple layers of the expected content media type
E0133cached-manifest-integrityoci: cached manifest digest mismatch
E0135fetch-integrityoci: content digest mismatch
E0136fetch-network-unreachableoci: network unreachable
E0137fetch-not-foundoci: artifact not found at remote source
E0138fetch-unauthorizedoci: authentication required or failed
E0139immutable-tag-conflictoci: tag already published with different content
E0140no-content-layeroci: manifest has no layer of the expected content media type
E0141oci-location-collisionoci: distinct catalog identities map to the same OCI repository location
E0142referrer-discovery-unavailableoci: referrer discovery could not be completed
E0143unknown-entity-kindoci: unknown entity kind for mediatype dispatch
E0144signature-bundle-digest-mismatchcached signature bundle does not match its recorded digest
E0145plugin-entity-not-foundplugin reference is not a Plugin entity
E0146reference-cyclecircular reference expansion
E0147malformed-trust-policyregistrytrust: advertised trust config is malformed
E0148no-trust-advertisedregistrytrust: registry advertises no trust config
E0149attachment-slot-near-missattachment name is a near miss for a declared slot
E0150attachment-slot-shapeattachment does not conform to its declared slot shape
E0151duplicate-boundary-componentcomponent declared in more than one boundary: declare each component in exactly one boundary
E0152duplicate-triad-identityduplicate Aggregate/Manifest identity (metadata.name) in the Release directory
E0153feature-merge-conflictfeature merge conflict: reconcile the Aggregate and Release declarations for the feature
E0154internal-catalog-view-disagreementthe compiler's own views of the catalog disagree
E0155inject-key-collisionduplicate delivery key across inject sources
E0156invalid-inject-keyinvalid inject key: the from-key must name a provides key its source publishes
E0158invalid-parameter-refinvalid parameter reference: check the {{ .parameters.* }} expression names a declared parameter and parses as a Go template
E0160manifest-cross-binding-pillar-collisionmanifest annotation bindings collide on same Feature path+pillar
E0161manifest-reserved-prefixmanifest annotation binding uses reserved prefix
E0162missing-required-featuremissing required feature: attach a Feature of the required type to the component
E0163missing-required-socketrequired uses socket not populated
E0164parameter-contract-violationparameter contract violated
E0165parameter-missingrequired parameter not supplied
E0167provides-key-not-declaredRecipe publishes a provides key its Component does not declare
E0168schema-conformanceauthored pillar does not conform to its declared schema
E0169self-inject-forbiddenself-inject on component without spec.inject allowlist
E0170triad-ref-unresolvableaggregate/manifest reference unresolvable
E0171unknown-uses-socketunknown uses socket: name a socket the entity declares in its usesSchema — only a component's own uses block may name one the catalog did not declare
E0172release-not-in-canonical-formrelease reached resolve un-normalized (non-empty root components alongside a synthesized default boundary)
E0173unread-parameterdeclared parameter is read by no reference in the Aggregate
E0174uses-socket-near-missuses socket name is a near miss for a declared socket
E0175document-not-loadablefile load failed: the file could not be read, or its bytes did not parse
E0176keyless-signing-requires-networksigning: keyless signing requires a live identity provider, Fulcio, and Rekor
E0177no-signature-foundsigning: no signature found for an artifact that requires one
E0178no-trusted-identitiessigning: keyless verification requires at least one trusted identity
E0179signature-invalidsigning: signature does not verify
E0180signature-verification-failedsigning: signature bundle does not verify
E0181signing-policy-requires-signaturesigning: signing policy requires a signature for this artifact kind; refusing to push unsigned content
E0182trust-root-not-loadablesigning: cannot load pinned trust root
E0183unsigned-push-refusedsigning: registry requires signatures; refusing to push unsigned content
E0184unsupported-keysigning: unsupported held-key type
E0185untrusted-identitysigning: signature identity is not trusted for this registry
E0186unknown-source-kindno source adapter serves the source kind
E0187empty-workspace-rootcacheslot: empty workspaceRoot
E0188artifact-entry-shapeartifacts entry: shape must be a string scalar or {$import: <local-path>}
E0189artifact-library-entry-shapeartifactlibrary: entry must be a mapping of filename to a string body
E0190forbidden-keywordschemalibrary: forbidden JSON Schema keyword
E0191mapping-entry-not-scalarmappinglibrary: entry body must be a string scalar
E0192document-nesting-depth-exceededa document nests too many levels deep
E0193parameters-shapeparameters: shape must be an inline object or {$import: <local-path>}
E0194template-not-foundschemalibrary: template not found
E0195template-param-missingschemalibrary: template parameter missing
E0196template-param-type-mismatchschemalibrary: template parameter type mismatch
E0197values-mapping-shapevaluesmapping: shape must be a string scalar or {$import: <path-or-library-identity>}
E0198well-known-annotation-scopewellKnownAnnotations: a key is declared at a scope the provider's contract does not render
E0199workload-entry-not-scalarworkloadlibrary: entry body must be a string scalar
E0200workload-template-shapeworkload: shape must be a string scalar or {$import: <path-or-library-identity>}
E0201assertion-name-collisionassertion name declared twice across the extends chain
E0202cyclic-extensioncyclic extends chain
E0204feature-recipe-values-mapping-requires-sourceFeatureRecipe: valuesMapping requires source
E0205extends-merge-failedinheritance merge failed
E0207recipe-output-component-label-collisionrecipe output-component-labels constraint: key is also declared in outputLabels
E0208recipe-output-label-reserved-namespacerecipe output-labels constraint: key uses a reserved namespace
E0209recipe-values-mapping-requires-sourceRecipe: valuesMapping requires source
E0210recipe-no-input-kindRecipe: at least one input kind required
E0211recipe-filename-collision-across-input-kindsfilename collision across input kinds: two input-kind blocks produced a file under one output name
E0212slot-not-referenceableworkload attachment slot is not referenceable
E0213workload-features-schemaworkload featuresSchema cross-check failed
E0214workload-not-validworkload validation failed
E0215entity-envelope-invaliddocument envelope validation failed
E0216schema-extension-evaluation-failedvalidator/jsonschema: x-aggrega extension evaluation failed
E0218schema-not-resolvablevalidator/jsonschema: schema resolution failed
E0220extends-chain-too-deepextends chain exceeds maximum depth
E0221schema-merge-input-invalidmerger: invalid merge input
E0222ambiguous-registry-aliasregistry alias matches more than one host
E0223capability-on-cross-cutting-socketa cross-cutting socket is bound by capability but attaches by uri
E0224workspace-config-invalidworkspace configuration is invalid
E0225duplicate-provider-targetcapability is bound to more than one provider plugin
E0226duplicate-registry-aliasregistry alias is already used by another host
E0227governance-role-invalida governance attachment declares no role or an unknown role
E0228inert-field-on-provider-socketa provider socket binding sets a field with no referent on that socket
E0229position-out-of-rangeposition out of range
E0246verdict-plugin-trust-mismatchthe digest recorded as trusted for this plugin does not match the digest its cached manifest reports
E0247verdict-attachment-not-configureda plugin recorded as trusted for an accept-or-reject verdict is no longer attached at any verdict role
E0248wasm-output-shapewasm: guest plugin returned an output that is not the shape the socket reads
E0250nest-segment-not-one-directoryprovider named a directory for each contributor's own sub-directory that is not a single directory name
E0251recipe-source-is-emptyrecipe source is an empty string, which names neither sourceless mode nor sourced mode
E0252artifact-library-file-escapes-keyartifact-library bundle file name does not name a file of its own beneath the artifacts key its output is nested under
E0253annotation-binding-target-unresolvedannotation binding does not resolve against its target Feature
E0254annotation-subkey-not-conformingannotation subkey does not conform to the target Feature's schema at the routed pillar
E0255annotation-side-pillar-mismatchannotation routes through a pillar its authoring side may not use
E0256annotation-binding-pillar-overlapannotation binding declares one path in both pillar lists
E0257schema-contract-compile-failuredeclared schema contract could not be compiled into a usable schema, so nothing was validated against it: correct the contract where it is declared, or remove it if the configuration it covers needs no validation
E0259boundary-scope-attachment-not-declared-at-a-boundaryattachment binds a FeatureRecipe with executionScope: boundary and no boundary holding the component declares it
E0260unplaced-componentcomponent placed in no boundary: name it under a boundary's `components`, or place the sub-module that contributes it under `aggregates`
E0261unresolved-boundary-componentboundary names a component the composition does not hold: correct the name, or remove the entry
E0262unusable-component-identitycomponent identity cannot be the name its emitted resources are stamped with: rename the component
E0263component-identity-target-refusesthe target will not accept a name derived from this component's authored identity: rename the component
E0264provider-refused-every-component-identityprovider guest never accepted a component identity the compiler composed for it
E0265unsupported-input-kindprovider does not support the node's input kind
E0266unusable-schema-importa schema `$import:` could not be applied
E0267unknown-schema-pillara schema block declares a key that names no data pillar
E0268pipeline-patch-unit-not-carvedreassemble names a patched unit token the carve did not produce; a conforming codec carves and reassembles a file under the same tokens
E0269provider-render-duplicate-pathprovider guest returned two output files under one path; a conforming guest returns each output path at most once
E0270link-patch-file-not-emittedlink patch names an output file the dispatch group did not emit; a conforming link patch names a file the group's own render returned
E0271pipeline-emit-file-absentemit_file side effect carries no file; a conforming emit_file side effect carries a file with its path and content
E0272pipeline-side-effect-kind-undefinedside effect declares a kind the plugin contract does not define; a conforming side effect declares emit_file or emit_crd
E0273rendered-name-unavailabletemplate reads the name the target gives the resources it renders for the node, and this node's provider reports no such name; a conforming template reads a value the node's own provider supplies
E0274verdict-plugin-identity-changedthe plugin identity recorded as trusted no longer matches what this resolution reports
E0275edit-refused-invalid-resultthe edit was refused because the resulting document would not be valid, and nothing was written
E0276schema-evolutionthe version being published changes the published predecessor in a way the documented evolution rubric objects to
E0277annotation-prefixan annotation key on the entity uses a prefix the platform reserves
E0278name-shapethe entity's name does not follow the documented name shape for its kind
E0279dynamic-refsa schema in the entity uses a dynamic reference construct that cross-document reference resolution cannot follow
E0280id-overridesa schema in the entity declares an identifier of its own, where the platform owns that schema's identity
E0281category-matches-directorythe entity's category label does not match the category directory the entity is filed under
E0282x-aggrega-discouragementthe entity writes an Aggrega schema extension directly into schema content instead of declaring it under usesSchema or featuresSchema
E0283plugin-default-limitsthe Plugin entity declares no runtime resource cap of its own, so the platform defaults apply
E0284secret-slot-declares-sensitivean attachment slot admits only secret material and does not declare that it handles it
E0285provides-declared-by-componentthe Recipe publishes a provides key the Component it implements does not declare, so a consumer wiring that key is refused
E0286publish-bump-below-classificationthe version bump being published is smaller than the evolution check's classification of the change requires
E0287import-halting-diagnosticthe importer reported a diagnostic that stops the import, so the source was not fully turned into draft authoring files
E0288plugin-cannot-express-inputa plugin has no expression for a construct this build declares
E0289plugin-required-input-unresolveda plugin could not resolve something it requires to exactly one value
E0290plugin-output-name-collisiontwo things a plugin produced occupy one name in its output
E0291plugin-value-not-representablea plugin has no representation for a value it was given
E0292plugin-failure-unclassifieda plugin reported a failure that none of the declared kinds names
E0293wasm-guest-condition-undeclaredwasm: guest plugin named a condition the socket does not declare
E0294subsystem-component-identity-collisioncomponents in different subsystems take the same identity: rename one of them, since a subsystem contributes nothing to a component's identity
E0295library-reference-whitespacelibrary reference: a reference to a library entry carries no whitespace or line break
E0296release-chain-composes-both-routing-keysrelease extends chain composes both named boundaries and top-level components: declare one routing shape across the chain, never both
E0297inherited-boundary-directory-is-literalinherited boundary directory carries no template variable, so it resolves to the path the extended Release writes to
E0298bundle-no-entity-documentoci: published bundle carries no entity document
E0299bundle-ambiguous-entity-documentoci: published bundle carries more than one entity document
E0300bundle-unreadableoci: published bundle cannot be unpacked
E0301published-artifact-not-an-entityoci: published artifact is not an entity document
E0302entity-not-pinnedan input the entity reads has no pin recorded for it in the entity.lock beside it
E0303entity-shares-its-directorythe entity shares its directory with another entity, and an entity of its kind has a directory of its own
E0304content-outside-entity-directorya path names content outside the entity's own directory
E0305local-source-content-mismatchthe files of the entity's local source do not match the pins recorded for them in entity.lock
E0306plugin-artifact-not-foundplugin artifact not found on this machine
E0307cache-location-outside-cachea value a cache location is built from would place cached files outside the place it names in the cache
E0308conflicting-features-reach-one-componenta Feature reaches a component alongside a Feature it declares a conflict with
E0309symbolic-link-in-entity-filesa symbolic link sits among the files an entity carries
E0310offline-registration-without-trust-policya registry other than the official hub is not registered offline without a trust policy supplied by hand, because the policy it advertises cannot be fetched; register it once while online, or pin its trust by hand with `aggrega registry add <host> --identity <identity>=<issuer>` or `--key <public-key-file>`
E0311malformed-version-pinreference carries a malformed version pin
E0312colon-in-provider-binding-capabilitya provider socket binding names a capability containing a colon, which no Recipe can select
E0313provider-binding-capability-unservedplugins.providers entry names a capability no provider-rendering plugin the build reads serves
E0314plugin-built-from-uncommitted-changesplugin was built from a working tree with uncommitted changes, so no commit reproduces the version it reports
E0315connection-attachment-slot-undeclareda connection carries an attachment under a name its socket declares no slot for
E0316connection-attachment-written-off-its-connectiona Release attachment takes the name of an attachment one of a component's connections carries
E0317release-connection-attachment-untypeda Release connection attachment names no Feature type, and the type is required for an attachment only the Release makes
E0318attachment-inject-mapping-key-collisionduplicate delivery key across two attachments: an attachment's FeatureRecipe writes a delivery key another attachment already delivered
E0319duplicate-connection-aliasconnection alias is already used by another connection of the same component
E0320write-leads-out-of-workspacea path this operation writes or deletes leads through a link out of the directory it must stay inside
E0321read-leads-out-of-workspacea file this operation reads leads through a link out of the directory it must stay inside
E0323caller-render-facts-not-declaredtemplate reads its callers' render facts, but the FeatureRecipe does not set readsCallerRenderFacts
E0324reference-leads-out-of-workspacea reference a document makes to another file leads out of the directory it must stay inside
E0325provider-render-fact-not-listprovider guest reported a render fact whose value is not a list; a conforming guest reports every render fact's value as a JSON array, even with one entry
E0326pipeline-step-reads-caller-render-factspipeline step reads its callers' render facts, but a pipeline step does not read the components connecting to its host; it reads only the host's own render facts
E0327index-of-absent-map-keytemplate indexes a map with a key the map does not hold
E0328misnamed-slot-fillattachment written under a name no slot declares fits a slot its component leaves empty
E0329connection-credential-matches-target-keya connection and the target it reaches do not name one key: they write different locators for it, or only one of them names one
E0330mixed-signing-credentialssigning: the references named together need different signing credentials, so nothing was signed
E0331signature-not-recordedsigning: no verified signature is recorded for an artifact that requires one
E0332signature-for-another-artifactsigning: the recorded signature was made for a different artifact
E0333recorded-signature-out-of-datesigning: a recorded signature is not the one a pull would record
E0334omit-matched-nothingan omits entry left out nothing the source rendered
E0335unsupported-omitsprovider does not support omits
E0336omit-report-mismatcha provider's omitted counts do not match the omits entries it was handed
E0337importer-version-unsatisfiableno importer plugin version satisfies the plugins.importer entry's version pin
E0338duplicate-importer-attachmentimporter is attached by more than one plugins.importer entry
E0339ambiguous-import-formatmore than one importer recognises the source
E0340name-windows-cannot-holda name this operation writes holds a path segment Windows cannot hold as written
E0341importer-declares-no-file-patternsthe importer serving the source's format declares no file patterns, so it reads one file and cannot read a directory
E0342import-directory-matched-nothingno file in the directory matches the file patterns the importer serving the source's format declares
E0343import-source-name-collisiona file read from the directory and a file named in the importer's `with.sources` have the same name
E0344windows-unusable-entryan entry this publication carries cannot be used on Windows
E0345duplicate-container-environment-variablea container declares one environment variable twice
E0346metrics-credential-annotation-matches-providesa Component's annotation stating how its metrics authenticate disagrees with whether it declares the provides key saying an instance's metrics need a credential
E0347target-render-facts-not-declaredtemplate reads the render facts of a component its host is wired to, but the FeatureRecipe does not set readsTargetRenderFacts
E0348pipeline-step-reads-target-render-factspipeline step reads the render facts of a component its host is wired to, but a pipeline step reads only the host's own render facts
E0349import-target-unboundno Recipe in the workspace's catalog binds to the capability the import's target names
E0350unrecognised-import-formatno importer recognises the source
E0351unsupported-boundary-artifactsprovider does not support boundary artifacts
E0352boundary-directory-not-beneath-output-rootboundary output directory does not name a directory beneath the output root
E0353boundary-feature-name-not-a-directoryboundary-level Feature instance name is not a directory name
E0354cross-boundary-link-value-not-copieda template does more than copy a value it reads off a cross-boundary link
E0355inject-delivery-shapeinject delivery: shape must be a list of entries, each `in:` with exactly one of `from:` or `value:`
E0356suspend-requires-scheduled-formsuspend requires form: scheduled
E0357name-mapping-matched-nothinga Manifest name mapping's key names no component instance or attachment in this build, so the entry binds nothing
E0358uses-target-not-exporteduses edge target names a component its module does not export
E0359source-adapter-not-registeredno source adapter is registered in this program for the source kind
E0360netrc-file-unreadablethe netrc file could not be read
E0361source-url-carries-credentialthe source URL carries a credential
E0362uses-inject-valueinject entry on a connection carries `value:`; a connection delivers the target's published keys, each named with `from:`
E0363annotation-subkey-not-boundannotation subkey is not routed by the annotation's binding
E0364value-template-execution-faileda value template failed while it ran
E0365boundary-contribution-not-assembledboundary-level Feature's output is routed to a dispatch path nothing assembles
E0366inject-mapping-output-not-parsableFeatureRecipe injectMapping output could not be read as a dictionary of deliveries
E0367annotation-scalar-not-routablea scalar annotation value does not route to exactly one path of its binding
E0368inject-mapping-output-key-not-deliveredFeatureRecipe injectMapping output writes a key no delivery mechanism of the host reads
E0369absent-path-read-and-iteratedtemplate reads a path as a value and iterates it, and the data holds nothing at that path
E0370duplicate-pipeline-step-ida pipeline declares one step id twice
E0371unknown-catalog-document-kindcatalog document declares a kind a catalog does not hold
E0372attachment-inject-valueinject entry on an attachment carries `value:`; an attachment delivers the keys its FeatureRecipe publishes, each named with `from:`, and a literal belongs in the component's own inject block
E0373retired-api-versiona document declares an API version this compiler no longer reads
E0374retired-abi-versiona plugin declares a plugin ABI version this compiler no longer speaks
E0375retired-media-typeoci: artifact carries a media type this compiler no longer reads
E0376no-answer-in-timeegress: the server did not answer in time
E0377repository-listing-too-longregistry: the repository listing did not end in time
E0378registry-too-busyoci: the registry kept asking to slow down
  • E0002 is retired: nothing reports it now, and the number is never handed to a different condition. It named a catalog lookup that fails while the graph’s static contracts are checked — a fault in the compiler rather than in an authored document — and the condition raised when a build resolves a component type the catalog it reads then holds no entry for reports that state now, and its code is E0154.
  • E0134 is retired: nothing reports it now, and the number is never handed to a different condition. It named a publishable entity whose directory was not named after the version the entity declares; a publication does not judge a directory’s name, and the condition raised when an entity shares its directory with another entity where its kind has a directory of its own is E0303.
  • E0157 is retired: nothing reports it now, and the number is never handed to a different condition. It named an Aggregate key — a component, feature, subsystem or nested-module instance name — that did not match the authored-name pattern. Every one of those key surfaces is constrained to that same spelling by the Aggregate schema, which refuses the document while validating its envelope and reports the offending key with a line and column; that condition’s code is E0215.
  • E0159 is retired: nothing reports it now, and the number is never handed to a different condition. It named a target reference whose dot-separated segments did not all match the instance-name pattern, and no build reported it before the condition was withdrawn.
  • E0166 is retired: nothing reports it now, and the number is never handed to a different condition. It named the file a Release’s parameters: { $import: … } points at when that file could not be read or its bytes did not parse; a file that yields no document is one condition wherever the path was written, and its code is E0175.
  • E0203 is retired: nothing reports it now, and the number is never handed to a different condition. It named a FeatureRecipe on the eval capability that declared a source, a values overlay, a workload or artifacts; that capability was withdrawn, and nothing reports this state now.
  • E0206 is retired: nothing reports it now, and the number is never handed to a different condition. It named a Recipe on the eval capability that declared a source, a workload, artifacts or a values overlay; that capability was withdrawn, and a Recipe declaring none of those is refused on every capability under E0210.
  • E0217 is retired: nothing reports it now, and the number is never handed to a different condition. It named a schema-validation failure that could not be reported against a particular field, and no build reported it before the condition was withdrawn.
  • E0219 is retired: nothing reports it now, and the number is never handed to a different condition. It named a cyclic extends chain, reported by a chain walk separate from the schema merge’s combining step; a single chain walk reports every cyclic chain, and its code is E0202.
  • E0230 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0231 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0232 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0233 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0234 is retired: nothing reports it now, and the number is never handed to a different condition. It named a Recipe source that is an empty string, reported while rendering through the compose provider; one condition covering every provider reports that now, and its code is E0251.
  • E0235 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0236 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0237 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0238 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0239 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0240 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0241 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0242 is retired: nothing reports it now, and the number is never handed to a different condition. It named a Recipe source that is an empty string, reported while rendering through the Helm provider; one condition covering every provider reports that now, and its code is E0251.
  • E0243 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0244 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0245 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0249 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0258 is retired: nothing reports it now, and the number is never handed to a different condition. The condition this number named was withdrawn, and no build reports it.
  • E0322 is retired: nothing reports it now, and the number is never handed to a different condition. It named a value a Feature attached to a boundary computed for a component’s environment under a key another attachment had already delivered. A Feature attached to a boundary delivers into a component only through its FeatureRecipe’s injectMapping, and a mapping writing a key another attachment delivered is reported under E0318.

Matching guidance

The errors.Is predicate walks the wrap chain, so a sentinel match works even when the error is wrapped several times on its way back to you. Match against the error an exported function returned:

package release
import (
"errors"
"fmt"
"github.com/aggrega-ai/aggrega-cli/pkg/resolver"
"github.com/aggrega-ai/aggrega-cli/pkg/validator/envelope"
)
// Load reads a Release and reports the distinct failures a caller handles
// differently.
func Load(path string) error {
_, err := resolver.LoadRelease(path)
switch {
case errors.Is(err, envelope.ErrEntityEnvelope()):
return fmt.Errorf("%s is not a Release: %w", path, err)
case errors.Is(err, resolver.ErrYAMLLoad()):
return fmt.Errorf("%s could not be read as YAML: %w", path, err)
case err != nil:
return err
}
return nil
}

There is no exported entry point that runs a whole build, so errors.Is matching applies to code calling these packages directly. To gate CI on a build, run aggrega build and read its exit status and its diagnostics: their message text is catalogued in fatal-halts.md, their category in error-translation.md, and the short code in their bracketed head resolves in the table of every condition on this page.

The two gating paths exist because the three identifiers reach different distances. A gate written in Go links these packages, matches sentinels, and can read either code off any error it holds. A gate written around the command has the exit status and the printed text — and the printed text names the condition, because the short code sits in the bracketed head. So such a gate keys on that short code rather than on message wording, and the message-keyed views stay the way to work back from wording it already has. Match the sentinel from Go; key on the short code around the command; read the descriptive code off the structured diagnostic where a client speaks that protocol.

Sentinels declared in different packages with the same short name are distinct conditions, not two spellings of one: errors.Is distinguishes them by identity, so a match against one does not match the other. The re-exports called out in the tables are the exception, and they are called out precisely because they are the case where two names do match. Match against the name in the package the tables list it under, and treat a short name on its own as ambiguous.

For the user-facing diagnostic catalogue (the messages developers see in their terminal when a build halts), see fatal-halts.md. For the advisory-warning catalogue (the non-halting warning:, lint: and notice: output), see warnings.md. For the category-prefix taxonomy ([DEVELOPER_ERROR] / [OPS_ERROR] / [CATALOG_ERROR] / [TRANSLATION_ERROR] / [FETCH_ERROR] / [POLICY_ERROR] / [TRUST_ERROR]), see error-translation.md.