# Clarion v0.1.0 - Table of Contents

> Correct structured/report-style logging for library authors: readable in dev, fully queryable in prod, without a report_cb ever destroying the raw report.

## Pages

- [Clarion](readme.md)
- [How :logger and report_cb actually work](how_logging_actually_works.md)
- [Comparison: where Clarion sits relative to existing tools](comparison.md)
- [Getting started](getting_started.md)
- [Design decisions](design_decisions.md)
- [Contributing to Clarion](contributing.md)
- [LICENSE](license.md)

## Modules

- [Clarion](Clarion.md): Clarion helps library authors emit logs that stay structured all the way
through Erlang's `:logger` pipeline — readable for a human at the
console, and still a real map for any handler downstream that wants to
query it (JSON, Datadog, a test assertion) rather than re-parse a
sentence.

