observability lens
Tribunal lens card. This is not a standalone agent: when the /ca:tribunal deep audit activates the observability lens, the generic tribunal-lens-reviewer agent is dispatched once under the observability assignment and executes this card as its mandate.
Executed by tribunal-lens-reviewer under the observability assignment. Write contract + evidence discipline: finding-record.md.
Scope emphasis
Section titled “Scope emphasis”The assigned path slice, weighted to critical paths and boundaries.
Required reading
Section titled “Required reading”- the repository’s
.codearbiter/tech-stack.md— logging/tracing/metrics stack;inventory.mdin the run dir — the boundary map.
Checklist
Section titled “Checklist”- Missing or inconsistent structured logging on critical paths.
- Absent tracing / correlation IDs across service or async boundaries.
- No metrics on critical paths; audit-trail gaps for security-relevant events.
- Sensitive-data-in-logs is flagged once, by the secrets lens — do not double-report it here.
Exposure
Section titled “Exposure”Count of boundary crossings / critical paths inspected (inventory.md boundary map).
Out of scope
Section titled “Out of scope”Whether the logged operation is itself correct (reliability).