DefendableOS · accountable AI rails and proof-of-value workflows.

DefendableOS is the honest public front door for the Defendable stack. The current field-tested wedge is AI Agent Operations, implemented and independently audited with limitations. The broader Proof of Value / AIOV direction is an active build track, not fully field-cleared.

Current status panel

  • AgentOps module chain — VERIFIED_AS_REPAIRED_WITH_LIMITATIONS
  • DefendableCloud — REPAIR_REQUIRED · browser demo only READY_WITH_LIMITATIONS
  • DefendableDocs field-release pages — VERIFIED_AS_DOCUMENTED_WITH_LIMITATIONS
  • DefendableRouter — FIELD INTEGRATION PENDING
  • Client pilot — HOLD
  • Production — NOT CLEARED FOR PRODUCTION
  • External SaaS enforcement — NOT CLEARED FOR EXTERNAL SAAS ENFORCEMENT

What works today

  • Four runtime module repos are public.
  • Codex audit and re-audit are published.
  • The AgentOps module chain is verified as repaired with limitations.
  • DefendableDocs field-release pages are verified with limitations.
  • A DefendableCloud browser demo exists with limitations.
  • Public repos and the Tribunal audit tape are available now.

What does not work yet

  • DefendableCloud server-side action POST API repair is required.
  • Broader DefendableDocs claim cleanup is required.
  • DefendableRouter public utility is not verified from public surface evidence.
  • Router-to-Cloud integration is not proven.
  • Production is not cleared.
  • External SaaS enforcement is not cleared.
  • Certification, insurance, and blockchain anchoring are not claimed.

Public surfaces

  • DefendableCloud — field utility surface · controlled synthetic demo under repair
  • DefendableDocs — client-use manual and owner record book · field-release pages aligned
  • DefendableRouter — router / receipt utility track · field integration pending
  • OpenDefendable — open-source truth surface for protocols, audits, wins/losses, utilities, and contribution lanes
  • Tribunal audit — public referee tape · not certification · not production clearance

Promotion protocol

Build → Public Safety Gate → Codex Audit → Repair → Re-audit → Field Release → Docs Update → Owner Promotion.

Builder receipt is submission. Codex audit is referee tape. Owner approval is promotion control.

Where to go next

  • View DefendableCloud
  • Read DefendableDocs field-release pages
  • Visit OpenDefendable
  • Review the Tribunal audit tape
  • View public repos
  • Request early-access review

Disclaimer

This public surface records audited status and open limitations. It does not claim production clearance, certification, insurance coverage, external SaaS enforcement, or blockchain anchoring. DefendableOS is a product of Swarm and Bee LLC (Florida limited liability company · D-U-N-S 138652395 · doing business as Swarm & Bee AI).