Skip to content

Strategy

Strategy is the main reason AAAX exists. A strategy can stand alone as a Pydantic-modeled resource table with local handlers. When you want more of the PSI stack, LLLM owns tactic boundaries, SSSN owns channels and stores, and PsiHub owns package manifests. AAAX gathers those resources into one shell and exposes them as one command surface.

Describe
Write `psi.toml` resources.
Mount
Load the package into a shell.
Bind
Attach local tactic and channel handlers.
Serve
Expose the shell as Pydantic/FastAPI.

Resource Kinds

AAAX understands the package-facing resource kinds used by the PSI stack:

  • package
  • schema
  • tactic
  • channel
  • snapshot
  • service
  • run
  • config
  • doc
  • example
  • asset
  • custom

The built-in package bridge imports all of the PsiHub manifest sections that matter for launch context, not only executable tactics.

Strategy Rules

  • Local names must be path-segment friendly.
  • Prefix imported packages when names might collide.
  • Keep original psi:// refs in resource records.
  • Treat channels as resources with shell-facing handlers, not hidden runtime state.
  • Treat docs, examples, assets, package cards, and config as first-class context.

Next