Progressive Disclosure

Gildea uses progressive disclosure to keep responses efficient by default while allowing you to request more detail when needed.

Three levels of detail

The lightest view — metadata and a text preview:

GET /v1/signals?entity=NVIDIA

Returns decomposition_text (thesis or summary text), tags, entities, and verified_text_unit_count. No individual text units.

The complete verified breakdown with all text units:

GET /v1/signals/sig_01JABCDEF123456789

Returns the full decomposition tree — every verified sentence and claim with compact verification metadata.

Full decomposition plus source evidence snippets:

GET /v1/signals/sig_01JABCDEF123456789?include=evidence

Each text unit includes its evidence block with preview snippets and character counts.

Orthogonal to the include parameter, verification_detail controls how much verification metadata is returned:

Value	Verification fields
(default)	verdict, path, human_reviewed, scoring_mode, primary_score
`full`	+ scoring_method, components_ran, all scores, thresholds, reason_codes

Combine them:

GET /v1/signals/sig_01J...?include=evidence&verification_detail=full

Bandwidth — signal cards are ~500 bytes; full decomposition with evidence can be 10KB+
Cost — fewer bytes transferred = faster responses
Clarity — most use cases only need the signal card for browsing