@agimon-ai/po-core

Po runtime systems and reusable core services.

Packages

Package details

package

Install @agimon-ai/po-core from npm and Pi will load the resources declared by the package manifest.

$ pi install npm:@agimon-ai/po-core
Package
@agimon-ai/po-core
Version
0.0.0-alpha.183
Published
Nov 22, 2026
Downloads
85.6K/mo · 16.2K/wk
Author
agiflow-ai
License
BUSL-1.1
Types
package
Size
11.3 MB
Dependencies
24 dependencies · 3 peers

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

Po core

Shared runtime systems and contracts for Po hosts and extensions. The distribution composes them; feature packages own policy. Importing a contract must not activate its provider.

Main/child systems own agent lifetimes, the kernel owns contribution selection, server adapters own APIs/transports, and browser contracts live under web. Public src/exports files forward symbols from their owners. The retained Pi compatibility host supports third-party packages/providers; it is not a Po terminal-UI authoring surface.

Extension and host contracts

Use Plugin lifecycle for the low-level generated-host contract and Architecture for normal routed authoring.

Hosts supply explicit platform, environment, home, storage, and scope capabilities. Feature runtime code uses injected po/* services rather than ambient process configuration or host-only filesystem APIs. A service provider owns initialization and cleanup; consumers declare their dependencies rather than importing a selectable implementation.

Workspace registry

@agimon-ai/po-core/workspaceRegistry exports the read-only po/workspace-registry contract. A host binds it before serving plugins. readPoWorkspaceRegistry(context) returns undefined when absent; required consumers must declare that dependency.

  • list() returns detached records.
  • resolve() accepts exactly one nonempty { id }, { name }, { path }, or { alias } selector.
  • Results are found, missing, or ambiguous; duplicate selectors never silently choose the first match.

IDs are local to one host. Cross-host UI identity remains host-qualified. Free-form metadata belongs to the consuming package, which decides whether it supplies defaults or enforced scope; the registry does not choose credentials or expose sibling services.

Node composition associates .po/workspaces.yaml declarations by saved name. Aliases/metadata refresh at composition boundaries and are not duplicated in membership storage. Invalid declarations are reported and omitted without blocking unrelated roots. Renaming a declaration unlinks its previous metadata association. Sandbox records expose identity without reading their folders; edge admission has its own available inventory.

See Po Config for declaration syntax.

Workflow allocation

@agimon-ai/po-core/workflow defines role assignments, effective-graph requirements, profile candidates, versioned allocation evidence, and expected provider identity. Validation checks exact role coverage and same-profile groups; parsing detaches saved evidence. Neither step authorizes execution or proves remote freshness.

Allocation-aware launches require the workspace-bound identity provider's discovery, allocation, and revalidation capabilities. Missing capabilities must block that launch rather than substitute teams, mailboxes, or the launcher's profile. Runtime enforcement belongs to the composition using these contracts.

Federation destination boundary

The portable packageApi entry supplies verified caller stamps and SQLite-backed replay/feed, workspace-sharing, provider-consent, and calling-host grant stores. Inject SQLite through po/sqlite. Preserve live nonces and durable pause state; refreshing refused work requires renewed authority, not an automatic fallback.

The Node remote runtime composes pinned issuer/host/device authority and sealed transport. Enrollment and claim bind account keys separately from host-scoped reconnect/biometric keys. Dispatch uses verified principal, org, device, and calling-host/grant stamps, never caller-provided headers. Workspace authorization, roster trust, current revocation, and durable replay admission remain destination responsibilities.

A contract or successful signature check alone does not prove a host composed the required authorization boundary. See Security.