Group: Zanswer Zpo

Sort by:Popular▼

✓Popular✓Newest

Shared zPo types and utilities: process context and metadata, the event vocabulary, merge semantics, template interpolation and the task definition schema readers.

Zanswer Zpo Connectors

Zanswer Zpo PDSL Deploy

Zanswer Zpo Providers

Zanswer Zpo Task Stubs

zPo tasking API: the task, payload and executor interfaces plus the lifecycle and gateway wire models that providers compile against.

The zPo authorization contract: the principal a gateway establishes, the role vocabulary and its capabilities, tenant selection and the ownership rule. Transport-neutral, so a gateway speaking any protocol enforces the same policy.

Kotlin task stub generation from JSON task definitions: the source emitter, its type mapper and the KotlinPoet dependency they need.

zPo messaging: NATS JetStream publishing and consumption, the outbox message model and the delivery guards that close the at-least-once seam.

The credential every zPo authoring tool obtains the same way: client credentials when the deployment states a client, a browser sign-in with PKCE when it states none, and one resolver that decides which.

The zPo process definition language: the authoring DSL, its expression and rule surface, and the Kotlin script host that compiles a definition.

Gradle plugin that deploys PDSL process definitions from a project's sources to a running zPo ops service.

Gradle plugin that generates type-safe Kotlin task stubs from the JSON task definitions a connector advertises, so definitions call tasks by name.

Editor-agnostic PDSL completion: context detection, the completion vocabulary, snippet grammar and workspace stub discovery, shared by every editor host.

The secret store every zPo process resolves credentials through: values stated in the environment, mounted files re-read when they rotate, and a mounted folder read one generation at a time, with one name served from one source.

Artifact signing and verification for packaged process definitions: the signer used when a definition is packaged and the verifier used when one is loaded.

Bill of materials pinning a compatible set of the zPo shared libraries: common, codegen, messaging, tasking-api, auth-contract, auth-client, http-contract and secrets.

Packaging and loading of compiled process definitions: the definition artifact and its manifest, the ABI descriptor, definition hashing and the artifact loader.

The zPo HTTP contract: the authentication seam, the RFC 9457 problem responder, input validation, the shared Ktor plugin stack, instrumentation routes and the await infrastructure every zPo HTTP service is built from.

The PDSL language server: an LSP process that serves diagnostics, hover and completion to any editor that speaks the protocol.