Skip to content
Promenaut

Promenaut joins forces with HSBC as strategic investor and design partner.Read More

Layer 8 · The foundation

SDK

What a module team builds with: the capability seam, the manifest, the toolchain, the test harness and the release path.

What it is not. Not an internal convenience. Promenaut's own modules are built on the same SDK and capability seam a client engineering team would use, and a new module may reach the platform no other way.

01Three to know

What it does.

01

Capability seam

The sanctioned way a module agent reaches the platform is a declared set of sixteen capability surfaces covering data, models, knowledge, artifacts, documents, files, workflow, events, notifications, service invocation, cost recording, decisions, autonomy policy, queues, secrets and logging, with the tenant it is bound to carried alongside them.

02

Module authoring SDK

A privately published SDK sets how an engineering team writes agents against the platform's capability seam: a base class with a fixed set of inherited helpers, versioned capability surfaces, a platform compatibility range checked when a module loads and when it installs, and a light manifest contract that resolves in both the backend and the frontend build.

03

A module states its own governance position

A module declares its purpose, intended use, data classes, human oversight controls, limitations and validation position in its manifest, and that block feeds the governance sections of the module's delivery pack.

02What it covers

The parts of SDK.

Capability seam

The declared surfaces a module agent reaches the platform through, and how they are versioned, scoped and measured

Agent contracts

What an agent declares it consumes, produces and touches, and how the platform holds it to that

Modules and manifests

How capability is packaged as modules, and what a module manifest declares and is checked for

Module interface

How a module draws its own screens and cards safely inside the product

Agent building blocks

Shared bases a module agent inherits for scoring, explaining results, answering questions and handling inputs

Authoring and testing

Writing, scaffolding, running and checking a module and its agents

Build and release

Building, signing, describing and releasing modules and the SDK itself

See it on a workflow you own.

Bring a real process. We'll show what your first agentic workflow looks like on the platform.