fable-agent/docs/competition.md

2.2 KiB

Competition: FableCodex / pi-fable / fable-agent

Positioning

FableCodex and pi-fable add Fable-style workflow discipline.
fable-agent adds the missing verification substrate: typed attestations, security scanners, risk gates, and guarded deploy receipts.

Market map

Project Layer Strength fable-agent wedge
FableCodex Codex workflow skill Inspect-first, goal ledger, evidence before done Runtime-independent attestations and security checks
pi-fable Pi package / subagent workflow Pi-native routing, findings gate, verifier agents Factory-aware verification, deploy route evidence, typed receipts
fable-agent Verification/control plane Receipts, AST/glyph/content safety, verify-cycle, guarded deploy Proves agent work instead of only guiding it

Product category

Agentic attestation infrastructure.

Not an AI factory. Not an orchestrator marketplace. Not a model unlocker.

fable-agent verifies agent work with:

  • typed attestation schema: fable.verification.attestation.v1
  • verified vs unverified claim separation
  • AST structural capability scanner
  • glyph/covert-channel scanner
  • content safety and adaptive reframing gate
  • build/test/docs checks
  • risk-based human review gate
  • guarded deploy route recording

Strategic contrast

FableCodex says

Make Codex behave more carefully.

pi-fable says

Make Pi subagents behave more carefully.

fable-agent says

Prove what agent work did, what verified it, what risk remains, and whether guarded deploy is allowed.

Deploy fact discipline

For fable-agent guarded deploy decisions:

  • current route: 8099/deploy via git-proxy
  • legacy/stale direct deploy service: 8098 deploy-webhook
  • memory is not proof; receipts are proof

Default command

fable-agent verify . --out .fable/attestations/latest.json

or:

fable-agent factory verify . --out .fable/attestations/factory-latest.json

Do not copy

Do not copy competitor ceremony unless it creates proof. Avoid:

  • bigger ledgers for their own sake
  • dashboard before receipts are boring green
  • marketplace before typed objects are stable
  • generic self-healing claims without degraded-repair receipts
  • direct legacy 8098 deploy assumptions