{
  "format": "palo-agentic-capability-matrix",
  "schemaVersion": "1.0.0",
  "release": "2.5.0",
  "releaseStatus": "developer-preview",
  "updatedAt": "2026-07-19",
  "statusVocabulary": [
    "specified",
    "prototype",
    "implemented",
    "production-ready"
  ],
  "disclaimer": "PALO-AI v2.5.0 is a developer preview and reference implementation. It is not a production authorization service, security boundary, compliance certification, or substitute for organization-owned identity, access control, key management, monitoring, backup, retention, legal review, and security assurance.",
  "capabilities": [
    { "id": "mcp-stdio", "status": "implemented", "note": "Official SDK reference transport covered by protocol tests; deployment hardening remains the adopter's responsibility." },
    { "id": "mcp-streamable-http-auth", "status": "prototype", "note": "Bearer-token developer transport; no principal-level RBAC, workload identity, TLS termination, rotation, or rate limiting is provided." },
    { "id": "trusted-registry", "status": "prototype", "note": "Versioned SQLite records exist, but administrative authorization, publisher signatures, backup, and recovery are not implemented." },
    { "id": "canonical-action-claim", "status": "implemented", "note": "Action Claim 1.1 remains compatible; Action Claim 1.2 immutably binds a declared Effect Contract to the proposed action." },
    { "id": "effect-contract", "status": "implemented", "note": "A closed JSON-Pointer predicate DSL represents preconditions, expected effects, forbidden effects and inconclusive handling without arbitrary executable expressions." },
    { "id": "rego-default-deny", "status": "implemented", "note": "Rego v1 reference policy and tests are included; production policy distribution and bundle attestation are not provided." },
    { "id": "hmac-signatures", "status": "prototype", "note": "Reference HMAC signing is implemented with environment-supplied keys; KMS/HSM integration, rotation, and external anchoring remain under development." },
    { "id": "replay-protection", "status": "prototype", "note": "Nonce, idempotency-key, and sequence checks exist, but the reference executor does not provide production-grade exactly-once execution." },
    { "id": "transactional-ledger", "status": "prototype", "note": "SQLite WAL, append-only triggers, capability consumption, execution intent and hash-chain verification are implemented; external tools cannot participate in the local transaction and production durability remains incomplete." },
    { "id": "single-instance-execution-recovery", "status": "prototype", "note": "Startup recovery converts stale pending outbox entries into signed unknown receipts, inconclusive attestations, incidents and resource holds; distributed leasing and exactly-once execution are not provided." },
    { "id": "one-time-execution-capability", "status": "prototype", "note": "Signed, short-lived capabilities bind claim, decision, tenant, resource, executor and verifier and are consumed once inside the reference runtime." },
    { "id": "trusted-execution-receipt", "status": "prototype", "note": "Operator-provisioned in-process executors generate signed receipts inside the runtime; workload attestation, connector isolation and distributed recovery remain under development." },
    { "id": "authoritative-outcome-verification", "status": "prototype", "note": "Separately registered verifiers compare authoritative pre/post state with the Effect Contract and emit verified, mismatch or inconclusive attestations." },
    { "id": "assurance-incident-lifecycle", "status": "prototype", "note": "Mismatch and inconclusive outcomes open a resource hold and incident that can be acknowledged or resolved; automatic rollback is intentionally excluded." },
    { "id": "web-mobile-approval", "status": "prototype", "note": "The Web client demonstrates the approval contract. Android integration is referenced by release artifacts outside this repository's tested source tree; authenticated reviewer identity, meaningful action presentation, notification delivery, traceable mobile build evidence, and production workflow assurance remain under development." },
    { "id": "palo-am-exchange", "status": "prototype", "note": "Local profile and decision import/export is available for evaluation; owner validation and enterprise synchronization are not provided." },
    { "id": "vibe-pre-tool-gate", "status": "prototype", "note": "The current gate demonstrates claim metadata and policy checks; it is not a trusted attestation or an unavoidable tool-execution proxy." },
    { "id": "hierarchical-subagents", "status": "prototype", "note": "Individual profiles, delegation limits, and parent metadata exist; trusted spawning, lineage verification, and evidence handback are incomplete." },
    { "id": "collaborative-agent-teams", "status": "specified", "note": "Team registry, shared task claims, peer assignment, leases, conflict handling, and team-level evidence are not implemented." },
    { "id": "dify-connector", "status": "prototype", "note": "A non-production example demonstrates authenticated claim submission; production credentials, distributed retry semantics, packaging and connector certification are not included." },
    { "id": "n8n-visual-decision-gate", "status": "prototype", "note": "The compatibility decision node remains available in the installable 0.2.0 package and routes a live fail-closed gateway decision. It remains optional, unpublished, unverified and not an unavoidable execution boundary." },
    { "id": "n8n-governed-executor", "status": "prototype", "note": "Package 0.2 adds a PALO Governed Action node with Verified, Review Required, Denied and Execution Failed outputs backed by the v2.5 runtime; it is unpublished and not n8n-verified." },
    { "id": "n8n-secure-approval-resume", "status": "specified", "note": "The exact-claim approval contract is prototyped; authenticated reviewer delivery and one-time backend-controlled n8n resume are not implemented." },
    { "id": "n8n-workflow-admission", "status": "specified", "note": "Workflow assessment, digest registration and activation/pre-execution enforcement hooks are architected but not implemented." },
    { "id": "governance-e2e", "status": "prototype", "note": "Automated tests cover authorize, approval, one-time execution, signed receipt, verified effect, stale-state prevention, mismatch incident, inconclusive verification and ledger integrity; distributed production staging remains incomplete." },
    { "id": "governance-hub-gui", "status": "prototype", "note": "A white role-adaptive Executive and Technical interface demonstrates guided authority setup, portfolio signals, decision queues, execution traces, approvals and incidents with realistic evaluation data. It is not yet connected to production identity, tenant authorization, managed keys or an independently assessed runtime boundary." }
  ]
}