YUCLAW's lane

answers "what should I read, and what does it say?"

• Search — find filings, transcripts, and news relevant to a question
• Summarize — condense a document or a quarter into readable prose
• Monitor — watch tickers or topics and surface new items
• Converse — answer follow-up questions in context

The output is prose for a human reader, produced on demand. Its value is speed of understanding. Verifying it is the reader's job.

answers "what exactly was claimed, from what source, knowable when — and does it hold up?"

• Point-in-time extraction — every event carries available_as_of — what was knowable, when; replays filter on it, so nothing ingested later can leak into an earlier date
• Event classification — filings become typed events (a locked vocabulary) with magnitude, direction, and a SourceLock-verified excerpt that must locate verbatim in the filing
• Event-study validation — classified events are tested against subsequent abnormal returns and reported as measured — including where the result is adverse to the hypothesis
• Public replay — one command re-derives every published statistic from published derived data on anyone's machine — no account, no API key
• Ledger anchoring — each day's signal content-hashes roll into a daily root committed to a public git repository before pages update; edits after the fact are detectable
• Methodology boundaries — scoring universe and evidence tier are separated by positive gating with a standing negative check; coverage percentages are stated as measured
• Adverse-result disclosure — underpowered windows, outages, and results that go against the hypothesis are disclosed and never deleted — presentation may be compressed, substance may not