Hand Weles one bound request with your own authority.

Skarbiec asks Weles's credential admission in process at the route Stado's resolver names, submits one bound request, and retains the actual refusal or provider result.

No bridge program runs#

Skarbiec talks to Weles's credential admission in process: no bridge program is started and the release packages no Weles client. The route is the one this host's Stado resolver answers for the credential-operations family (Weles's weles-admission today) asked as consumer skarbiec-weles-credential-client — `stado capabilities resolve credential-operations --consumer skarbiec-weles-credential-client` shows it.

Skarbiec hands its bearer only to a loopback adapter. A route that is not a loopback address this host reaches is refused as weles-endpoint-not-loopback and nothing is sent; no answer from the resolver is weles-endpoint-unresolved, and the operation is not handed over. Either way nothing at the provider changes.

Three separate grants#

The canonical Skarbiec service calls Weles as skarbiec-weles-credential-client. That consumer requires audience weles and call:weles#credential-operations. The bearer is WELES_TOKEN when it is set, else the owner-only file WELES_TOKEN_FILE names, else ~/.stado/skarbiec-weles-credential-client-token.

Weles verifies each caller through Skarbiec using its separate weles-credential-admission consumer, introspect:tokens grant, and weles-credential-admission-skarbiec-token file. Revocation takes effect on the next call without restarting Weles.

The provider writer has only the exact stage:item#field capability required for acquisition. For a generic winston item this is winston-writer with stage:winston#api_key. The acquisition's --consumer names that writer, not the eventual application reader. A stage grant does not grant read access or prove that the provider interaction succeeded.

Discovery belongs to Stado#

The address comes from this host's Stado resolver; Skarbiec appends the fixed /api/v1/credential-operations route. There is no environment URL, forward file or guessed service port.

POST /api/v1/credential-operations accepts the exact skarbiec.credential-operation.v4 request for submit and status; it names the role the credential plays, which alone selects the credential's contract. The self-hosted route is separate from organization-authenticated hosted tasks and the Spis browser-task service. Their bearers cannot substitute for its credential-operation grant.

Managed password items are deployment-owned, case-sensitive identifiers, not account names compiled into Skarbiec. Skarbiec supplies the sealed directory identity and rejects a missing or conflicting Entra directory and an Entra field other than password before contacting Weles. The worker separately checks its WELES_MANAGED_PASSWORD_CONTRACTS_FILE declaration and exact writer and reader grants; a client-shaped request does not grant access.

Shell
skarbiec credential acquire winston \
  --consumer winston-writer \
  --purpose 'Qualify the requested writing styles within the free API allowance' \
  --signup-origin https://dev.gowinston.ai \
  --as skryba-detector-onboarding \
  --token-file ~/.stado/skryba-detector-onboarding-token

skarbiec credential status winston \
  --as skryba-detector-onboarding \
  --token-file ~/.stado/skryba-detector-onboarding-token

Status names observed work#

Weles binds a request ID to the authenticated caller and the exact provider, item, field, writer, origin, operation and baseline. A changed request cannot reuse that ID. Status reads its persisted record and exact action log. A missing forward or authority is never represented as a queued operation.

An interrupted executor is not replayed after restart. Uncertain transport or provider effects remain unknown rather than being marked unchanged. For generic acquisition, Weles requires the matching acknowledgement written after Skarbiec accepted capture. A child process exit code alone is not proof. Skarbiec separately verifies the managed write against its active operation journal before settling acquisition.

The self-hosted transport accepts submit and status. It explicitly refuses resume with WELES_CREDENTIAL_MODE_REFUSED; the hosted task bridge has a separate approval continuation contract. A refused or unverified provider flow is not a completed acquisition.

Admission diagnostics
CodeMeaning
WELES_ENDPOINT_UNRESOLVEDThis host's Stado resolver answered no credential-operations alternative for skarbiec-weles-credential-client. No provider operation was submitted.
WELES_ENDPOINT_NOT_LOOPBACKThe resolver's route is not a loopback address this host reaches, so no bearer was sent.
WELES_BEARER_VARIABLE_MALFORMED / WELES_BEARER_VARIABLE_UNREADABLEWELES_TOKEN is set but cannot be presented as the bearer.
ENTRA_IDENTITY_CONTRACT_MISMATCHThe request's provider, directory presence or Entra password field disagrees; no provider work was submitted.
WELES_CREDENTIAL_AUTH_UNCONFIGUREDWeles cannot load its separate introspection authority.
WELES_CREDENTIAL_SCOPE_REFUSEDThe caller lacks the exact audience or credential-operation capability.
WELES_CREDENTIAL_REQUEST_CONFLICTA request ID is already bound to another caller or request.
WELES_CREDENTIAL_EXECUTION_INTERRUPTEDNo durable final executor result exists; Weles did not replay the operation.
WELES_CREDENTIAL_RESULT_UNCONFIRMEDThe run did not establish a matching capture acknowledgement.

Real release qualification#

Packaging does not qualify credential admission. Real qualification must invoke the compiled Skarbiec CLI, retain the actual command and exit status, and inspect persisted credential status. A host with no resolver answer must record needs_configuration and WELES_ENDPOINT_UNRESOLVED without creating a provider credential (`tests/credential/admission_in_process.mjs`).

The Weles deployed admission journey checks real caller authentication, exact-writer refusal, persisted unsupported-operation status and request-ID conflict. These refusal results are not proof of successful provider acquisition. A live acquisition and the consuming application's real flow still have to pass.

The Weles client also provides tests/credentials/journey.mjs for both real providers through both bridges. Its fixture must select an actual isolated vault served to the dedicated worker, separate caller authorities and the expected worker revision. It checks persisted verification and matching provider capture, not a copied vault or canned response. See the Weles client guide at https://weles.wisent.com/docs/client for the fixture, retained evidence and continuation contract.