# Black-Box Opaqueness

> Shipping an agent with no traces, decision logs, or provenance — then debugging from user complaints.

- **Category**: Agentic AI
- **Subcategory**: Anti-Patterns
- **Canonical URL**: https://designpattern.fyi/patterns/black_box_opaqueness/

---

## Description
**Intent**: Skipping observability to ship faster — and discovering that debugging a black-box agent in production is archaeology.

**Context**: LLM frameworks emit no traces by default. Recording each model call, tool invocation, and decision path feels like something to add "later, once it proves itself." The agent ships naked: no run logs, no decision audit trail, no record of what input led to what output.

**Solution**: Add traces, decision logs, and provenance from day one — not after the first production incident. See provenance-ledger, decision-log, lineage-tracking.



## Use Cases
- Never. This is an anti-pattern documented to be avoided.
- It exists to warn against shipping agents without traces or decision logs.
- Reading this entry should redirect you to provenance-ledger, decision-log, and lineage-tracking.






## Trade-offs




### Considerations & Drawbacks

- Debugging stretches from hours to weeks when the only signal is an angry user report

- Compliance questions ("what did the agent do and why?") become unanswerable

- Stakeholder trust erodes the first time something goes wrong with no replay







---
**Reference**: [Original Source](https://www.agentpatternscatalog.org/patterns/black-box-opaqueness/)