Cratis AI profile reference

August 25, 2026 ยท View on GitHub

Profiles are generated views over approved capabilities. They do not create a second authored copy of a skill. Every package listed here remains planned until its profile and targets are explicitly approved.

The public- and engineering- prefixes identify the subscription channel and audience. They do not indicate repository or package confidentiality.

For a generated view with plain-language package descriptions, included skills, availability, trust, and evidence, browse the package and capability catalog.

Public product profiles

ProfileIntended packageCurrent state
public-fundamentals@cratis/ai-fundamentalsFirst preview source candidate
public-arc@cratis/ai-arcLegacy source migration planned
public-arc-ef-core@cratis/ai-arc-ef-coreEF Core migration source requires canonical Arc persistence authority
public-arc-react@cratis/ai-arc-reactLegacy source migration planned
public-components@cratis/ai-componentsPartial legacy sources; content gaps
public-chronicle@cratis/ai-chronicleLegacy source migration planned
public-cratis-cli@cratis/ai-cliContent gap
public-cratis-cli-terminal-workbench@cratis/ai-cli-workbenchTerminal Workbench content gap
public-chronicle-web-workbench@cratis/ai-chronicle-web-workbenchBrowser Workbench content gap
public-lens@cratis/ai-lensContent gap
public-screenplay@cratis/ai-screenplayContent gap
public-stage@cratis/ai-stageContent gap
public-studio@cratis/ai-studioClassification-only public-safe MCP source candidate; no implementation operation admitted
public-chronicle-mcp@cratis/ai-chronicle-mcpClassification-only passive source candidate; no tool or prompt admitted, executable server remains product-owned

Chronicle client profiles

ProfileIntended packageAuthority state
public-chronicle-client-dotnet@cratis/ai-chronicle-dotnetContent gap
public-chronicle-client-kotlin@cratis/ai-chronicle-kotlinChronicle.Kotlin authority required
public-chronicle-client-elixir@cratis/ai-chronicle-elixirChronicle.Elixir authority required
public-chronicle-client-typescript@cratis/ai-chronicle-typescriptChronicle.TypeScript authority required
public-chronicle-client-python@cratis/ai-chronicle-pythonChronicle.Python authority required
public-chronicle-client-java@cratis/ai-chronicle-javaAuthority gap; no verified Java client

Do not translate .NET guidance into another language and call it client support. Each client profile requires language-native API, toolchain, error, lifecycle, and host evidence from its owning repository.

Identity, compliance, and tenancy overlays

ProfileIntended packageScope
public-arc-identity@cratis/ai-arc-identityAuthentication providers, authorization, claims, frontend identity
public-chronicle-compliance@cratis/ai-chronicle-complianceSubjects, keys, erasure, retention, privacy, audit
public-chronicle-multi-tenancy@cratis/ai-chronicle-multi-tenancyChronicle namespace isolation and tenant resolution

These remain separate because identity has different meanings across Arc, Chronicle compliance, event-source identities, and product-specific roles.

Specification by Example profiles

ProfileIntended packageScope
public-specifications@cratis/ai-specificationsLanguage-agnostic philosophy, contexts, naming, observability
public-specifications-dotnet@cratis/ai-specifications-dotnetCratis.Specifications, C#, NSubstitute, scenario families
public-specifications-typescript@cratis/ai-specifications-typescriptTypeScript/React, Vitest, Chai, Sinon, view models

Language-specific profiles compose the shared philosophy rather than restating it independently.

Public composition profiles

ProfileIntended packageComposition
public-application-arc-only@cratis/ai-application-arcFundamentals + Arc + .NET specifications; no Chronicle assumptions
public-application-chronicle-dotnet@cratis/ai-application-chronicle-dotnetFundamentals + Chronicle + .NET client/specifications; no Arc assumptions
public-application-arc-chronicle@cratis/ai-application-arc-chronicleFundamentals + Arc + Chronicle backend
public-application-react@cratis/ai-application-reactFundamentals + Arc + Arc React + Components + specifications
public-application@cratis/ai-applicationFull Arc + Chronicle + React + Components application
public-modeling-screenplay-stage@cratis/ai-modeling-screenplay-stageScreenplay authoring through Stage runtime/specification handoff

Composition packages contain generated views of approved component skills, not separately authored copies.

Public-safe engineering profiles

All shared engineering packages are public-safe. Confidential facts remain in repository-local overlays.

ProfileIntended package
engineering-base@cratis/ai-engineering-base
engineering-application@cratis/ai-engineering-application
engineering-fundamentals@cratis/ai-engineering-fundamentals
engineering-arc@cratis/ai-engineering-arc
engineering-arc-ef-core@cratis/ai-engineering-arc-ef-core
engineering-arc-react@cratis/ai-engineering-arc-react
engineering-components@cratis/ai-engineering-components
engineering-chronicle@cratis/ai-engineering-chronicle
engineering-chronicle-clients@cratis/ai-engineering-chronicle-clients
engineering-cratis-cli@cratis/ai-engineering-cli
engineering-lens@cratis/ai-engineering-lens
engineering-screenplay@cratis/ai-engineering-screenplay
engineering-stage@cratis/ai-engineering-stage
engineering-studio@cratis/ai-engineering-studio
engineering-stagehand@cratis/ai-engineering-stagehand
engineering-chronicle-mcp@cratis/ai-engineering-chronicle-mcp
engineering-specifications@cratis/ai-engineering-specifications
engineering-documentation@cratis/ai-engineering-documentation
engineering-ai@cratis/ai-engineering-ai
engineering-workflows@cratis/ai-engineering-workflows

Every engineering profile composes engineering-base. Studio and Stagehand packages may contain only public-safe contribution behavior. Their private architecture, deployment, roadmap, infrastructure, support, and incident workflows stay local to their private repositories.

Trust and publication

A planned profile is not an installation or support claim. Approval requires:

  • named owner and reviewer;
  • immutable product/source authority;
  • exact skill revision and digest;
  • public-safe content and licensing review;
  • security, behavior, positive/negative trigger, collision, and portability evidence;
  • profile and artifact runtime approval;
  • real host and consumer lifecycle evidence.

Executable CLI, Lens, Studio MCP, and Chronicle MCP implementations remain owned and distributed by their product repositories. Cratis AI packages only passive selection, installation, safety, interpretation, and workflow guidance unless a separate executable package is explicitly reviewed.