AFPS packs

A pack is the unit of agent-ready knowledge.

Every pack bundles six artifact classes — each with its own loading mode — plus activation metadata that tells an agent when the pack should fire.

docslazy pull

Reference material fetched only when an agent asks.

ruleseager push

Always-on constraints injected into the agent's working context.

workflowslazy push

Pushed when an activation trigger fires for the current task.

schemasvalidation time

Loaded by the validator/doorkeeper when an action is proposed.

testsevaluation time

Loaded by the eval runner to score baseline vs. AFPS-augmented behavior.

receiptsexecution time

Emitted as cryptographic evidence of what the agent actually did.

Pack lifecycle

01
Build
Author the pack: rules, workflows, schemas, tests, and activation metadata.
02
Evaluate
Run scenario evals comparing baseline vs. with-pack behavior. Fail the gate below threshold.
03
Distribute
Publish to a registry. Each version gets a scorecard, signature, and provenance.
04
Operate
Agents install, activate on triggers, emit receipts, and feed telemetry back.