The Stochastic Parrot

Reviewed Jan 1, 2000.

• tools: 19 tools scanned
• metadata: scanned

No findings.

Tools (19)

• editor_pending

  The site editor's pitch cards waiting for Mike's decision. Each card is one proposed change to thestochasticparrot.com that the editor judged too big to make on its own. Returns the cards; the attached widget lets the user decide each with Approve / Hold / Kill. Requires the editor key.

• editor_decide

  Record Mike's decision on one editor card: approve (the editor executes it next cycle), hold (keep it, not now), or kill (never pitch it again). Only call this when the user has explicitly decided; never infer a decision. Requires the editor key.

• editor_log

  What the site editor did recently: its ledger of small changes it shipped on its own, cards it filed, and decisions recorded. Use to answer 'what did the editor change'. Requires the editor key.

• editor_sync

  Internal: the desk's mirror sync (push cards + ledger, read back all cards, clear ids). Not for conversational use.

• search_corpus

  Full-text search over every published piece (titles, deks, context lines, outlet names, and source headlines). Returns matching pieces with slug, title, URL, and a highlighted snippet, best matches first. Use the slug with get_audit for full detail.

• get_audit

  Fetch one piece's full detail JSON by slug: headline, kind, date, context, dek, outlets, verified contradictions with verbatim spans, naming/framing splits, and the full source list. Slugs come from search_corpus or list_audits.

• list_audits

  List published pieces (summaries: slug, title, kind, date, counts of hard contradictions and naming/framing splits), newest first. All filters optional and combinable.

• list_corrections

  The desk's public corrections ledger: every logged error on a published piece — what was wrong, what changed, and when — in original ledger order.

• get_chain

  Story chains: multi-piece storylines the desk has covered more than once. Call without arguments to list the available chain ids; pass chain_id for one chain in full (its pieces in order, claim ledger, and reopen conditions).

• verify_piece

  Provenance record for one piece: SHA-256 hashes of its canonical JSON and published HTML as of the last corpus sync. Re-hash the live artifacts at the piece's URL and compare to confirm what you read is what the desk published.

• get_framing_index

  The Framing Index: across the cross-outlet corpus, how often disagreements between outlets are hard contradictions vs naming/framing splits — totals, rate, monthly trend, per-outlet appearances. The desk's core longitudinal measurement.

• get_coverage_record

  The capture-coverage record: what the desk's observatory actually monitored and when, including gaps. Read this before treating any silence in the corpus as meaningful — the desk's own rule.

• get_claim_ledger

  A story chain's claim ledger: specific verbatim claims outlets made, each tracked through states (open, corroborated, contradicted, corrected, quietly_abandoned, resolved) with a receipt for every transition. Empty claims list = the desk has not logged claims for that chain yet.

• get_storyboards

  A chain's per-newsroom storyboards: for each outlet, every piece it filed on the story entry-by-entry, the desk's published READ of what each piece was built to do (objective label, motive with its mandatory innocent read, confidence), the label arc, and the desk's 'story, as built' synthesis where one exists.

• list_letters

  Letters to the Desk: reader mail, excerpted and initialed, with the desk's replies in its own voice. The desk's only interactive surface with its readership.

• get_boxscore

  The Daily Box Score for one day — the desk's frozen per-day stat snapshot. Requires the day; days are listed at /boxscore/ on the site.

• submit_letter

  Submit a letter to the desk. If the desk answers, the exchange may be published on the Letters page (excerpted, initialed) — through the desk's normal editorial process, never directly. Requires the reader key.

• report_error

  Report a suspected error in a published piece (a miscount, a quote that reads wrong, a broken claim). Verified catches are fixed and logged on the public corrections ledger, credited 'Caught by a reader.' Requires the reader key.

• propose_development

  Tip the desk that a story moved — a development on an existing chain or a story worth auditing. Lands in the same proposed-developments queue the observatory's triggers feed; the desk decides what, if anything, to file. Requires the reader key.