Known traps view

3 min readReferenceUpdated 2026-05-21

What you'll find here

The read-only operator display for craik.known_trap and craik.negative_knowledge records through craik operator traps: what the v0.7.0 operator surface formats, how state boundaries are preserved, and the review boundary.

Review aids, not policy.

Known traps and negative knowledge help agents avoid repeated mistakes. They do not override policy, resolve contradictions, or prove absence without the cited evidence.

Commands

craik operator traps
craik operator traps --project PROJECT_ID
craik operator traps --task-id TASK_ID
craik operator traps --json

craik operator traps prints the current known traps and negative knowledge review view. The JSON form emits the same timestamped snapshot for tooling, with optional project and task filters applied.

What it formats

Trap statement · kind · project · task · status

Avoidance guidance

Evidence · handoff · contradiction links

Expiry timestamps

Negative knowledge scope & trust class

State boundaries

State

Display

Notes

Active

current

Use as current guidance.

Expired

audit-only

Visible for audit. Don't treat as current guidance without review.

Contradicted

conflict

Visible so operators can inspect the conflict before relying on the trap or negative statement.

What's next

ReferenceKnown trapsThe underlying contract behavior.ReferenceOperator surfaceThe shared TUI boundary.ReferenceFreshnessHow expiry interacts with stale-risk warnings.