Skip to content
Promenaut

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

For engineering

Can our engineers build on it?

The questions a review asks of Promenaut, with what answers each on the platform, and everything built for them.

01Your review

The questions, in the order they come.

  • Domain module systemCapability ships as versioned domain modules.
  • Per-tenant module profilesEach environment ships a declared set of modules resolved at build time, so two tenants can run different capability sets from one codebase without branching.
  • A mistyped top-level manifest key is an errorA module manifest is checked by one validator that the platform loader and the SDK share.
We take you through the answer: talk to our engineers →

  • Capability seamThe sanctioned way a module agent reaches the platform is a declared set of twenty-one capability surfaces covering data, models, knowledge, artifacts, documents, files, workflow, events, notifications, service invocation, cost recording, decisions, questions that pause the run until the person who launched it answers, the settings a run launched with, autonomy policy, read tools on outside MCP servers, tool calls a model selects, skills granted to the agent, queues, secrets and logging, with the tenant it is bound to carried alongside them.
  • Capability surfaces are versioned one by oneEach capability surface carries its own semantic version, and an agent can name the surfaces and versions it needs.
  • A module agent cannot write into another organisationIn production a module agent that names an organisation other than its own on a knowledge, artifact, queue, cost, decisions or input-request call, or on a read of the run's settings, is refused, a cost record it writes is booked only on its own run's work item, and a notification addressed to someone outside its organisation is refused.
We take you through the answer: talk to our engineers →

02Everything built for it

What the platform does for you, layer by layer.

Capability seam

  • Capability seam
  • A module Agent reads the settings its run launched with
  • Declared data access
  • One parser version, owned by the platform
  • A knowledge read that cannot be scoped returns nothing
  • Seam use is measured per module
  • Capability surfaces are versioned one by one
  • A module reads only its own secrets, for the organisation it runs for

Agent contracts

  • Declared I/O contracts
  • Declared side effects
  • Each agent is handed the earlier work it declares

Modules and manifests

  • Domain module system
  • Atomic module add and remove
  • Module-owned agents are read-only at the API
  • A module states the platform it needs
  • A mistyped top-level manifest key is an error
  • A deliverable is declared in the manifest
  • A module states its own governance position
  • What is inside each installed module
  • Agents, teams and workflows declared in the manifest
  • A module's own API routes, gated and kept off the raw database

Module interface

  • A descriptor card cannot express anything unsafe
  • A module installed after the build still draws its own interface
  • Interface registries are generated per profile
  • Module UI contract

Agent building blocks

  • Shared weighted scoring and conformance scorer base
  • Shared base for agents that explain a computed result
  • Modules inherit the platform's result, scoping and input methods
  • A conversational answerer is a provider on a shared loop
  • Reports are composed as a typed model

Authoring and testing

  • Module authoring SDK
  • Module scaffolding
  • Module test harness
  • Any agent, shown as SDK code and by source
  • Run one agent or one workflow from the command line
  • A module validates on its own
  • The whole platform on a module author's own machine
  • A module design is checked against what the SDK can build
  • A design is checked for completeness, reuse and how each agent will be proven
  • A module design pack for review
  • A design becomes a module scaffold and an engineering handoff

Build and release

  • Per-tenant module profiles
  • A module builds against the published SDK alone
  • promenaut-build CLI
  • A bill of materials for what is inside a module
  • Module artifacts are signed and verified
  • SDK packages released in dependency order
  • A partner submits a module to intake and follows its review from the command line
  • Release of a first-party module from its own repository
More on SDK →

Weighing us against the tools you already know? See how we compare, with sources →

03The pack

The full answers, written for you.

The Promenaut SDK at a GlanceAbout 10 minutes

Get the SDK overview

Bring your engineers.

See what a module is, how its agents are written and tested, and how it ships.

Talk to our engineers