Automate

Apps

Packaging components into something a non-technical user can run.

Availability note — these docs describe both working and planned product areas. Account authentication, administrator-managed AIHK/AICA tenant regions and keys, signed-in Composer runs and public Guard scans are connected. Skills, Memory, Agents, Workflows, Apps, billing, the public SDK/CLI and the unified API are previews unless a section explicitly says otherwise.

Roadmap and package-contract reference: this page describes the intended GenCMS runtime. The current deployment persists workspace records and drafts but does not execute marketplace Skills, index Memory for retrieval, publish packages, or run Agents, Workflows or Apps. See the deployed API reference for the routes available today.

An App is the finished experience: a form, a run, a result. The Skills, Memory grants and model mode underneath are configuration, not something the user has to understand.

Tender Assistant App
├── Skill: Tender Analyzer
├── Skill: Compliance Matrix
├── Skill: Proposal Reviewer
├── Memory: Company Knowledge (read)
└── Model: Claude-class

What an App page must show before a run

  • What it does, in one sentence
  • The Skills it uses and their versions
  • Its model mode
  • Which Memory collections it can read or write
  • Its Guard status
  • An estimated credit cost per run
← PreviousWorkflowsNext →GenCMS Guard