tibet-cascade

Cascade Logging for TIBET.

tibet-cascade is the observability layer for causal logging across the stack:

JIS claim/bind/FIR-A
-> TIBET token
-> cap-bus event
-> gateway verdict
-> ping/overlay/network state
-> continuityd arrival/resume
-> Phantom fork/resume
-> audit/evidence/report

It does not replace tibet-tail, tibet-trail, tibet-ping, or tibet-pol. It correlates them.

Install

pip install tibet-cascade

Bootstrap-or-die dependencies are mandatory:

• tibet-core>=0.5.0
• jis-core>=0.4.0

Commands

tibet-cascade doctor
tibet-cascade watch
tibet-cascade trace --id <cascade-or-token-id>
tibet-cascade logger on jis-core
tibet-cascade logger off tibet-core
tibet-cascade logger status
tibet-cascade ping --instance phone
tibet-cascade caps --read
tibet-cascade token --trace <token-id>

Default event file:

~/.tibet/cascade/events.jsonl

Override with:

TIBET_CASCADE_JSONL=/path/to/events.jsonl tibet-cascade watch

Event Shape

{
  "ts": "2026-06-07T21:55:00Z",
  "cascade_id": "cas_...",
  "event_id": "evt_...",
  "parent_id": "evt_...",
  "source": "jis-core",
  "kind": "identity.claim",
  "subject": "jis:...",
  "level": "INFO",
  "summary": "claim accepted",
  "refs": {
    "tibet_token": "...",
    "cap_event": "...",
    "trace": "..."
  },
  "data": {}
}

Stack Area

observability

Related packages:

• tibet-tail: live event stream
• tibet-trail: provenance trail reader
• tibet-ping: liveness and network probe
• tibet-pol: process and posture observer
• tibet-cascade: causal correlation cockpit