AGBoss Examples — Executable Architecture & Reliability Proofs

Independent, runnable AGBoss applications that demonstrate and verify the framework's core engineering guarantees against real distributable npm packages (@agboss/core and @agboss/cli).

AGBoss is an open-source TypeScript framework with static verification for complex multi-agent workflows.

Pre-release status (v0.1.0-rc): @agboss/[email protected] and @agboss/[email protected] are currently in release-candidate preparation (npm currently hosts the initial 0.0.1 placeholders). Each example's package.json declares standard public registry ranges ("^0.1.0"). Until 0.1.0 is published to npm, run npm run pack:framework && npm run verify:package && npm run install:packed from the repository root to pack and install the local release-candidate tarballs into each example's node_modules without dirtying git-tracked manifests.

---

1. Purpose & Central Principle

This repository serves three goals:

1. Developer onboarding: Help a new developer understand, install, and run AGBoss without familiarity with its internal source tree.
2. Executable architectural proofs: Demonstrate concrete failure classes, inject/reproduce them deterministically, and prove with executable assertions how AGBoss detects, prevents, compensates, or recovers from them.
3. External release validation: Validate the actual packed .tgz / published npm artifacts in clean consumer projects outside the agboss monorepo.

Central Principle: Promise → Failure Injection → Reproducible Proof

Every project in this repository answers six engineering questions with executable assertions:

1. Promise: What engineering property does AGBoss claim to provide?
2. Threat: What concrete error or failure threatens that property?
3. Failure Injection: How is that failure deterministically reproduced?
4. Mechanism: What does AGBoss detect, prevent, compensate, or recover?
5. Proof: What observable state, diagnostic code, or ledger invariant proves the expected behavior?
6. Guarantee Boundary: Where does the framework guarantee end, and what remains the application's or external system's responsibility?

---

This is the beginning of the README. Read the rest at the original. Read the full README ↗