Skip to content

Overview

Psi is a fractal connective grammar. It connects systems, composes them, and exposes the composite in the same shape it consumed, so the whole becomes a part and the loop recurs.

SSSN Connect with Channel: how systems reach one another.

LLLM Compose with Tactic: typed units of work that combine.

AAAX Expose with Strategy: orchestration as a Pydantic/FastAPI surface another system can connect to.

PsiHub Describe, validate, discover, and download package metadata.

PsiCLI Prepare credentials, inspect packages, and launch resources locally.

PsiSDK Install the full PSI station; detailed component docs stay in their own places.

Connect, Compose, Expose

The essence is: connect, compose, expose, then again. What gets exposed has the shape of what was connected, so composition can repeat at any level.

SSSN, LLLM, and AAAX are independent frameworks, not a required pipeline. Use any one alone, pair them in whatever way fits the system, or stack all three when you want the recursive loop.

flowchart LR S["SSSN: Channel"] --> L["LLLM: Tactic"] L --> A["AAAX: Strategy"] A --> S P["PsiHub + PsiCLI"] -. "package grammar" .- S P -. "describe, validate, discover, launch" .- A

PsiSDK

psi-sdk is the thin umbrella package for projects that want SSSN, LLLM, AAAX, PsiHub, and PsiCLI in one install. It re-exports the real component modules as psi.sssn, psi.lllm, psi.aaax, and psi.hub, installs the user-facing psi command, then adds a few local workflow helpers. Detailed docs for channels, tactics, strategies, package metadata, and CLI workflows stay with the component docs.

Use PsiSDK for the umbrella import and one-install workflow.

Developer Quick Start

Install the station when a project wants the whole PSI ecology:

python -m pip install psi-sdk

import psi

channel = psi.sssn.Channel(name="signals")
tactic_type = psi.lllm.Tactic
strategy_type = psi.aaax.Strategy

psi.init_package("demo", org="local", kind="mixed")
report = psi.validate_package("demo")

psi.hub.publish(...) is the local package-sharing shortcut. The same install also provides PsiCLI's psi command for humans and scripts:

psi --help

Separate Adoption

Each component remains independently adoptable:

python -m pip install sssn
python -m pip install lllm-core
python -m pip install aaax
python -m pip install psihub
python -m pip install prosi-psi-cli

import sssn
import lllm
import aaax
import psihub

Use the component docs for deep API details: SSSN, LLLM, AAAX, and PsiHub.

One Shape

The docs are arranged as four switchable sets: Psi, LLLM, SSSN, and AAAX. The framework docs share the same public shape: one center abstraction, one thin implementation layer, and one service-ready surface.

The connective layer owns only the seam: no owned execution, no privileged coordinator. Thinness is what keeps the exposed composite self-similar to the connected part.

Where To Go

  • Use SSSN when systems need to meet through channels, events, artifacts, snapshots, stores, or HTTP backends.
  • Use LLLM when typed tactics need to compose work across runtimes.
  • Use AAAX when composed package resources need to be exposed as CLI, FastAPI, agentic context, or a service surface another system can connect to.
  • Use PsiCLI when a human or local script needs to initialize credentials, inspect a package, or launch a package resource.
  • Use PsiSDK when a Python project wants the whole PSI ecology from one install.
  • Use PsiHub when Python code needs package metadata, validation, local publish/download, cards, config templates, or local hub APIs.
  • Use Tutorial for the shortest package lifecycle.
  • Use Reference for the surface map across Psi, LLLM, SSSN, and AAAX.