# trenches

> A cross-chain crypto trenches digest: what changed since the last report, which narratives are moving, which tokens belong to them, and what the evidence actually shows.

This file is a resource map for scripts and agents. It does not make any claim about who reads it.

## Where the latest report lives

- https://trenches.party/            HTML (latest report)
- https://trenches.party/latest.json  structured JSON (same report)
- https://trenches.party/latest.md    Markdown (same report)
- https://trenches.party/latest.txt   plain text (same report)

No report has been published yet; the latest aliases return 404 until the first report exists.
All four latest routes always refer to the same report. They are aliases and change on every publication; do not cite them.

## Structured data and schema

- https://trenches.party/schema/report.json   JSON Schema (draft 2020-12) that every report validates against (schema_version 1.0)
- https://trenches.party/reports/<report_id>/index.json   canonical JSON of one report
- JSON responses carry Link: </schema/report.json>; rel="describedby".

## Discovering archived reports

- https://trenches.party/feed.json   JSON Feed 1.1; one item per report, newest first. item.id and item.url are the permanent report URLs; item._trenches carries report_id, revision, revises, superseded_by, previous_report_id, observation_window and the JSON/Markdown/text URLs.
- https://trenches.party/archive/    human-readable list of every report.
- Each report JSON has previous_report_id, so the chain of reports can be walked backwards from the latest one.

## Publication time versus observation time

- published_at is when the report was published.
- observation_window.start / observation_window.end bound the period the observations cover.
- Every metric has its own observed_at and an optional measurement window (null means a point-in-time snapshot). Treat metric values as valid at observed_at, not at publication time.

## Confidence and missing data

- Confidence levels are the strings high, moderate, low, unknown. They apply to narratives, inferred statements, actor activity and relative-strength statements.
- Observed facts (observed, evidence, metrics, checks) are separate from interpretation (inferred, relative_strength).
- Missing or unavailable values are JSON null, rendered as "unknown". A value is never zero as a stand-in for missing.
- A metric only carries a change when a baseline object is present; otherwise no change is claimed.
- Tokens are identified by chain (CAIP-2 style id) plus contract or mint address, never by ticker alone.

## Report identity, revisions and citation

- report_id looks like 2026-09-09T1200Z (publication minute, UTC). Several reports per day are possible.
- Corrections are new reports with ids like 2026-09-09T1200Z-r2, with revises and revision_note set. Originals stay online and the feed marks them superseded_by.
- Cite the permanent URL https://trenches.party/reports/<report_id>/ (or index.json / index.md next to it). Evidence items have stable fragments: https://trenches.party/reports/<report_id>/#evidence-<evidence_id>; narratives: #narrative-<narrative_id>; tokens: #token-<token_id with non-alphanumerics replaced by ->.

## Examples

curl -s https://trenches.party/latest.json | jq '.report_id, .published_at, .observation_window'
curl -s https://trenches.party/feed.json | jq '.items[] | {id, date_published, superseded_by: ._trenches.superseded_by}'
curl -s https://trenches.party/reports/<report_id>/index.json | jq '.narratives[] | {id, lifecycle, confidence}'
curl -s https://trenches.party/schema/report.json | jq '.required'
curl -sI https://trenches.party/latest.json   # inspect ETag and Cache-Control; conditional requests with If-None-Match are honoured

## Other

- https://trenches.party/methodology/   how reports are produced and what the labels mean
- Content is plain HTML with inline CSS. No JavaScript is required to read any page.