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.

Armed, wired, muted

A cascade viewer is only worth what its producers put in it, so this package never shows the switch on its own. Every source reports in one of three states, and the middle one is the point:

Between 0.1.x and 0.2.0 every source in this package printed a green on while nothing in the whole stack called emit at all. That is the failure mode a viewer must not have: a quiet system and an unwired viewer looked identical, and the instrument reported the wish instead of the wire. doctor, list, watch and logger status now all say which of the two you are looking at.

Two consequences worth knowing:

• Recording is the default. An absent loggers.json means every source records, and an unknown source records. The file holds deliberate mutes, not permissions.
• A muted source refuses out loud. tibet-cascade emit into a muted source prints why and exits 2; it never silently swallows what you asked it to record.

Emitting from your own code

import tibet_cascade

tibet_cascade.emit(
    "device-link", "pairing.challenge", "challenge minted",
    subject="jasper2.aint", cascade_id=fork_id, refs={"fork_id": fork_id},
)

emit() never raises and honours the mute switch — a full disk or a read-only home returns None. Observability that can break the thing it observes is worse than none. Pass the same cascade_id through a chain of events to make them one causal thread, and parent_id to say which event came from which.

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