chorus-discourse 0.3.1__tar.gz

chorus_discourse-0.3.1/CHANGELOG.md

@@ -0,0 +1,46 @@
+# Changelog
+
+## 0.3.1 - 2026-09-22
+
+- Fixes the gather-to-chorus wiring gap. `normalize()` mapped only `feed_item`,
+  so feed entries from a real gather corpus were dropped without a diagnostic and
+  only YouTube comments reached the discourse surface. `feed-entry` now maps to
+  the `feed` source, and `feed_item` is kept for back-compat.
+- Adds an OIDC trusted-publishing release workflow with tag/version, artifact
+  digest, clean-venv entry-point resolution, and sdist-rebuild gates.
+- Publishes to PyPI as `chorus-discourse`. The console script stays `chorus`.
+
+## 0.3.0 - 2026-09-07
+
+- Adds `chorus decision` and MCP `chorus.decision`, a source-change review gate
+  that compares current and reference gather-style source packs, reports
+  added/removed/changed/unchanged item ids, verifies both deterministic Chorus
+  digests, and returns typed `UNVERIFIABLE` failure states for missing, malformed,
+  empty, or ambiguous source inputs.
+- Adds a safe public projection for the review-gate result. It keeps counts,
+  hashes, receipts, and limitations by default; human-readable public ids, source
+  names, refs, and URLs require an operator-authored projection policy rather
+  than source-row metadata. It excludes raw source text, author names, local paths,
+  private sessions, and bulk comments.
+- Hardens false-success controls for source packs: missing or malformed text,
+  invalid, missing, mismatched, or non-UTF-8 Gather objects, duplicate ids, and
+  absent, null, blank, or non-string ids return typed `UNVERIFIABLE` instead of
+  being compared as unchanged.
+
+This release does not decide whether a source claim is true, complete, or ready
+for publication. `MATCH` means the compared source observations and fingerprints
+are unchanged; `DRIFT` means a reviewer should inspect the changed source rows;
+`UNVERIFIABLE` means source capture or identity must be repaired before reuse.
+
+## 0.2.0 - 2026-09-07
+
+- Adds deterministic corpus-salience theme labels with `label_quality` support metadata so weak and singleton labels are visible in the digest.
+- Writes new receipts as `chorus-lens/3`, binding label terms and `label_quality` into the re-checkable digest body.
+- Preserves historical `chorus-lens/2` verification through an explicit legacy verifier. v2 receipts verify against the v2 body shape and do not bind the current v3-only `terms` and `label_quality` fields.
+- Fixes receipt verification so the submitted digest body must match its receipt before the verifier accepts a re-derived body.
+
+This release does not claim better semantic insight from comment corpora. It reduces generic-label false success on the included controls and labels weak support, while lexical clustering remains a known limitation.
+
+## 0.1.0
+
+- Initial discourse synthesis package with CLI, MCP stdio surface, daemon, deterministic sentiment, lexical clustering, contested aspects, and re-checkable receipts.

chorus_discourse-0.3.1/LICENSE

@@ -0,0 +1,110 @@
+# Functional Source License, Version 1.1, MIT Future License
+
+## Abbreviation
+
+FSL-1.1-MIT
+
+## Notice
+
+Copyright 2026 Zain Dana Harper
+
+## Terms and Conditions
+
+### Licensor ("We")
+
+The party offering the Software under these Terms and Conditions.
+
+### The Software
+
+The "Software" is each version of the software that we make available under
+these Terms and Conditions, as indicated by our inclusion of these Terms and
+Conditions with the Software.
+
+### License Grant
+
+Subject to your compliance with this License Grant and the Patents,
+Redistribution and Trademark clauses below, we hereby grant you the right to
+use, copy, modify, create derivative works, publicly perform, publicly display
+and redistribute the Software for any Permitted Purpose identified below.
+
+### Permitted Purpose
+
+A Permitted Purpose is any purpose other than a Competing Use. A Competing Use
+means making the Software available to others in a commercial product or
+service that:
+
+1. substitutes for the Software;
+
+2. substitutes for any other product or service we offer using the Software
+   that exists as of the date we make the Software available; or
+
+3. offers the same or substantially similar functionality as the Software.
+
+Permitted Purposes specifically include using the Software:
+
+1. for your internal use and access;
+
+2. for non-commercial education;
+
+3. for non-commercial research; and
+
+4. in connection with professional services that you provide to a licensee
+   using the Software in accordance with these Terms and Conditions.
+
+### Patents
+
+To the extent your use for a Permitted Purpose would necessarily infringe our
+patents, the license grant above includes a license under our patents. If you
+make a claim against any party that the Software infringes or contributes to
+the infringement of any patent, then your patent license to the Software ends
+immediately.
+
+### Redistribution
+
+The Terms and Conditions apply to all copies, modifications and derivatives of
+the Software.
+
+If you redistribute any copies, modifications or derivatives of the Software,
+you must include a copy of or a link to these Terms and Conditions and not
+remove any copyright notices provided in or with the Software.
+
+### Disclaimer
+
+THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR
+PURPOSE, MERCHANTABILITY, TITLE OR NON-INFRINGEMENT.
+
+IN NO EVENT WILL WE HAVE ANY LIABILITY TO YOU ARISING OUT OF OR RELATED TO THE
+SOFTWARE, INCLUDING INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES,
+EVEN IF WE HAVE BEEN INFORMED OF THEIR POSSIBILITY IN ADVANCE.
+
+### Trademarks
+
+Except for displaying the License Details and identifying us as the origin of
+the Software, you have no right under these Terms and Conditions to use our
+trademarks, trade names, service marks or product names.
+
+## Grant of Future License
+
+We hereby irrevocably grant you an additional license to use the Software under
+the MIT license that is effective on the second anniversary of the date we make
+the Software available. On or after that date, you may use the Software under
+the MIT license, in which case the following will apply:
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

chorus_discourse-0.3.1/MANIFEST.in

@@ -0,0 +1,2 @@
+include CHANGELOG.md
+recursive-include docs/releases *.md

chorus_discourse-0.3.1/PKG-INFO

@@ -0,0 +1,135 @@
+Metadata-Version: 2.4
+Name: chorus-discourse
+Version: 0.3.1
+Summary: A discourse-synthesis satellite for gather: weighted, clustered, re-checkable readings of comment corpora.
+License-Expression: LicenseRef-FSL-1.1-MIT
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# chorus
+
+![chorus](docs/art/chorus-header.svg)
+
+Read a comment section the way you wish you could: not scrolled, but **synthesized**.
+
+chorus takes a corpus of comments or threads and returns a weighted, clustered,
+re-checkable reading of the discourse. It tells you the themes people are actually
+voicing, ranks them by how much the crowd engaged and how strongly they felt,
+surfaces the sharpest dissent instead of hiding it behind an average, and names the
+topics the crowd is genuinely **split** on. Every digest carries a receipt a
+stranger can re-run to get the same answer. Zero third-party runtime dependencies.
+
+It orbits [gather](https://github.com/HarperZ9/gather): gather captures the corpus
+with provenance, chorus synthesizes the discourse on top of it.
+
+![Eight stages of turning a corpus of comments into a discourse digest: normalize, engagement, score, weight, cluster, themes, contested, and receipt. Gathered rows become discourse items, and rows that are not discourse are skipped. Engagement is read from the source when it is present; when a source genuinely has no signal, engagement is zero and the absence is recorded, so a missing vote is never counted as a real zero-weight one. Sentiment comes from a thirty word lexicon with negation, intensifier, capitalization and punctuation rules, and the same text always scores the same. Weight is the natural log of one plus engagement, multiplied by one plus half the sentiment intensity, so a loud comment nobody engaged with stays small. Clustering is a hashed TF-IDF cosine against the nearest leader across five hundred and twelve dimensions, seeded most-engaged first. Each theme carries its size, its sentiment split, its controversy, and the single highest-weight voice that disagrees with the majority. Contested aspects are measured separately across every comment that mentions a term, so a topic the corpus is split on survives the clustering that would file praise and complaint about it under different themes. The receipt hashes the inputs, the parameters and the digest body. Three outcomes: re-derived, rejected, and advisory only.](docs/art/synthesis-lane.svg)
+
+## What you get
+
+- **Themes, ranked.** Comments cluster into themes by what they say; each theme
+  carries a corpus-salience label, label-support metadata, its size, an
+  engagement-and-sentiment weight, a sentiment split, a *controversy* score (how
+  divided and how strongly felt), and the single highest-weight voice that
+  disagrees with the majority. Singleton and weak-support labels are named as
+  such in the digest instead of being presented as broad crowd themes. Theme item
+  IDs stay in the output so callers can resolve labels back to the source links
+  and provenance in their corpus.
+- **The contested topics, named.** A separate lens reports the aspects the corpus
+  is genuinely split on, measured across *every* comment that mentions a topic. It
+  is immune to the lexical clustering that would otherwise file "the battery is
+  amazing" and "the battery is terrible" under different themes and hide the fight.
+  One-sided praise and neutral chatter are excluded; only real two-sided
+  disagreement is surfaced.
+- **A receipt, not a vibe.** `--verify` re-derives the whole digest from the inputs
+  and confirms it. A tampered digest fails even if its own hash was recomputed to
+  match. Sentiment is a *weight*, never a verdict.
+- **Honest nulls.** A missing engagement signal is recorded as absent, never
+  counted as a zero. A too-thin corpus says so. The lexicon's limits (English-only,
+  literal, no sarcasm) are stated in the digest itself.
+- **A daemon.** Point it at a watchlist and it re-synthesizes only when a corpus
+  actually changes, storing each receipted digest by its own hash.
+- **A source-change review gate.** Compare a current gather corpus against a
+  reference corpus before reusing a prior synthesis or release note. The result
+  reports added, removed, changed, unchanged, digest verification, a local digest
+  outline, and typed source failure states. The optional public projection is
+  safe by default as hashes and counts. Human-readable public ids, source names,
+  refs, and URLs require an operator-authored `--public-policy` sidecar; raw
+  source row metadata cannot authorize public output. The projection omits raw
+  source text, author names, local paths, private session content, and bulk
+  comments. Source URLs appear there only through that public-policy sidecar.
+- **An MCP surface.** Drive it from any MCP host: `chorus.run`, `chorus.corpora`,
+  `chorus.digests`, `chorus.decision`, `chorus.status`, `chorus.doctor`.
+
+## Release notes
+
+See [CHANGELOG.md](CHANGELOG.md). Version 0.3.0 adds `chorus decision` and MCP `chorus.decision` as a source-change review gate for deciding whether a prior synthesis or release note can reuse the same source observations, needs source review, or must hold for source repair. It does not decide whether a source claim is true, complete, or ready for publication. Version 0.2.0 writes `chorus-lens/3` receipts with label-support metadata while preserving historical `chorus-lens/2` verification through an explicit legacy path. v2 receipts do not bind the current v3-only label terms or `label_quality` fields.
+
+## Run it
+
+```bash
+pip install -e .
+
+chorus run examples/discourse-sample.json --verify   # try it on the bundled sample
+chorus run <corpus> --verify        # a corpus -> a verified discourse digest
+chorus decision <current> --reference <reference> --task "Check whether sources changed"
+chorus decision <current> --reference <reference> --public --public-policy public-policy.json
+chorus corpora <root>               # discover gather corpora as discourse sources
+chorus watch add <corpus>           # add a corpus to the daemon watchlist
+chorus daemon --interval 300        # poll the watchlist, synthesize on change
+chorus digests <store>              # what the daemon has synthesized
+chorus mcp                          # the MCP stdio server
+```
+
+`<corpus>` is a gather corpus directory (a folder holding `catalog.jsonl`) or a
+JSON list of rows. Add `--model "<command>"` to `run` to overlay a model's read on
+the comments the lexicon is least sure about; the overlay is provenance-tagged and
+never enters the re-checkable core.
+
+No service key or provider account is needed for the deterministic path. The
+bundled sample is the quickest local check:
+
+```bash
+chorus run examples/discourse-sample.json --verify
+python -m pytest
+```
+
+If `chorus` is not on `PATH`, reinstall from the checkout with
+`python -m pip install -e .` and open a new shell. `chorus.status` and
+`chorus.doctor` are MCP tools exposed through `chorus mcp`; they are not separate
+CLI subcommands. Public source-change projections need an operator-authored
+`--public-policy` sidecar before source names, ids, refs, or URLs appear.
+
+![Eight stages of verifying a discourse digest: receipt, version, vocabulary, inputs, rescore, recluster, rehash, and verdict. The receipt supplies the parameters and hashes the original run recorded. The method version selects the verifier for that pipeline; unsupported versions fail instead of being guessed. The lexicon is hashed into the receipt, so editing the word list invalidates every digest that was built with the old one. The corpus hash is checked before any work is done. Then the stored sentiment is thrown away and every comment is re-scored from its own text, which is why fabricated sentiment cannot verify. Clustering and weighting re-run from the parameters the receipt recorded, not from the live defaults, so raising a default cannot silently break an already-versioned receipt. The digest body is rebuilt from that re-derivation and hashed. The verdict is one boolean with nothing taken on trust: a digest whose themes, weights or sentiment distribution do not follow from the inputs fails, even when its own stored hash was recomputed to match its tampered body. Three outcomes: verified, tampered, and no receipt.](docs/art/verify-lane.svg)
+
+## The receipt
+
+The digest's `receipt` binds the inputs, the method, and the result. `verify`
+first checks that the submitted digest body still matches its own receipt, then
+re-runs the deterministic pipeline (score, cluster, weight) from the same corpus
+through the method-version verifier recorded in the receipt. Current runs write
+`chorus-lens/3`; historical `chorus-lens/2` receipts remain checkable through
+their legacy label body. Unsupported method versions fail closed. Any model
+overlay is listed separately with its own provenance and is excluded from that
+check: the parts a stranger can re-derive and the parts that are model opinion
+are kept distinct, on the record.
+
+![Twelve rows covering every number a digest reports and where it comes from. The lexicon is thirty words, fifteen positive and fifteen negative, each carrying a valence between minus three and plus three, and the whole list is hashed into every receipt. Ten intensifiers are looked for up to three tokens back, widening or narrowing a valence. Nine negators flip a valence and keep about three quarters of its size, so a negation weakens a claim rather than erasing it. The compound score runs from minus one to one, the summed valence divided by the root of itself squared plus fifteen, so no single loud comment runs away with a theme. Two emphases apply: an all-caps valence word of more than one letter counts a quarter more, and up to four exclamation marks add five percent each. Weight is the log of one plus engagement, times one plus half the sentiment intensity. Clustering runs a hashed TF-IDF cosine over five hundred and twelve dimensions against the nearest leader, joining above eighteen hundredths, seeded most-engaged first. Controversy is the population standard deviation of a theme's sentiment, zero at consensus and near one at a hard split. Twelve contested aspects are surfaced, each needing three mentioning voices and real disagreement on both sides. The receipt carries seven fields. The accented row is the model overlay, which is advisory opinion on the items the lexicon is least sure of and is deliberately kept outside the digest hash. The last row is engagement coverage, which reports how many items actually carried a signal, because an absent signal is recorded absent rather than counted as a zero.](docs/art/method-table.svg)
+
+## Design
+
+The design and its two exposed defects-caught-in-review live in
+[docs/superpowers/specs](docs/superpowers/specs). Sentiment is coarse by
+construction and the digest says so; clustering is lexical, not semantic. chorus
+tells you what it did and hands you the means to check it.
+
+## License
+
+Source-available under the Functional Source License (FSL-1.1-MIT) (see [LICENSE](LICENSE)):
+read it, run it, build on it; commercial use that competes with the project is
+reserved.
+
+---
+
+**[Zentropy Labs](https://github.com/ZentropyLabs-ai)** · order out of entropy. An independent lab building evidence-first tools that leave a re-checkable artifact behind. Built by Zain Dana Harper in Seattle. The full workbench is at [Project Telos](https://harperz9.github.io).

chorus_discourse-0.3.1/README.md

@@ -0,0 +1,125 @@
+# chorus
+
+![chorus](docs/art/chorus-header.svg)
+
+Read a comment section the way you wish you could: not scrolled, but **synthesized**.
+
+chorus takes a corpus of comments or threads and returns a weighted, clustered,
+re-checkable reading of the discourse. It tells you the themes people are actually
+voicing, ranks them by how much the crowd engaged and how strongly they felt,
+surfaces the sharpest dissent instead of hiding it behind an average, and names the
+topics the crowd is genuinely **split** on. Every digest carries a receipt a
+stranger can re-run to get the same answer. Zero third-party runtime dependencies.
+
+It orbits [gather](https://github.com/HarperZ9/gather): gather captures the corpus
+with provenance, chorus synthesizes the discourse on top of it.
+
+![Eight stages of turning a corpus of comments into a discourse digest: normalize, engagement, score, weight, cluster, themes, contested, and receipt. Gathered rows become discourse items, and rows that are not discourse are skipped. Engagement is read from the source when it is present; when a source genuinely has no signal, engagement is zero and the absence is recorded, so a missing vote is never counted as a real zero-weight one. Sentiment comes from a thirty word lexicon with negation, intensifier, capitalization and punctuation rules, and the same text always scores the same. Weight is the natural log of one plus engagement, multiplied by one plus half the sentiment intensity, so a loud comment nobody engaged with stays small. Clustering is a hashed TF-IDF cosine against the nearest leader across five hundred and twelve dimensions, seeded most-engaged first. Each theme carries its size, its sentiment split, its controversy, and the single highest-weight voice that disagrees with the majority. Contested aspects are measured separately across every comment that mentions a term, so a topic the corpus is split on survives the clustering that would file praise and complaint about it under different themes. The receipt hashes the inputs, the parameters and the digest body. Three outcomes: re-derived, rejected, and advisory only.](docs/art/synthesis-lane.svg)
+
+## What you get
+
+- **Themes, ranked.** Comments cluster into themes by what they say; each theme
+  carries a corpus-salience label, label-support metadata, its size, an
+  engagement-and-sentiment weight, a sentiment split, a *controversy* score (how
+  divided and how strongly felt), and the single highest-weight voice that
+  disagrees with the majority. Singleton and weak-support labels are named as
+  such in the digest instead of being presented as broad crowd themes. Theme item
+  IDs stay in the output so callers can resolve labels back to the source links
+  and provenance in their corpus.
+- **The contested topics, named.** A separate lens reports the aspects the corpus
+  is genuinely split on, measured across *every* comment that mentions a topic. It
+  is immune to the lexical clustering that would otherwise file "the battery is
+  amazing" and "the battery is terrible" under different themes and hide the fight.
+  One-sided praise and neutral chatter are excluded; only real two-sided
+  disagreement is surfaced.
+- **A receipt, not a vibe.** `--verify` re-derives the whole digest from the inputs
+  and confirms it. A tampered digest fails even if its own hash was recomputed to
+  match. Sentiment is a *weight*, never a verdict.
+- **Honest nulls.** A missing engagement signal is recorded as absent, never
+  counted as a zero. A too-thin corpus says so. The lexicon's limits (English-only,
+  literal, no sarcasm) are stated in the digest itself.
+- **A daemon.** Point it at a watchlist and it re-synthesizes only when a corpus
+  actually changes, storing each receipted digest by its own hash.
+- **A source-change review gate.** Compare a current gather corpus against a
+  reference corpus before reusing a prior synthesis or release note. The result
+  reports added, removed, changed, unchanged, digest verification, a local digest
+  outline, and typed source failure states. The optional public projection is
+  safe by default as hashes and counts. Human-readable public ids, source names,
+  refs, and URLs require an operator-authored `--public-policy` sidecar; raw
+  source row metadata cannot authorize public output. The projection omits raw
+  source text, author names, local paths, private session content, and bulk
+  comments. Source URLs appear there only through that public-policy sidecar.
+- **An MCP surface.** Drive it from any MCP host: `chorus.run`, `chorus.corpora`,
+  `chorus.digests`, `chorus.decision`, `chorus.status`, `chorus.doctor`.
+
+## Release notes
+
+See [CHANGELOG.md](CHANGELOG.md). Version 0.3.0 adds `chorus decision` and MCP `chorus.decision` as a source-change review gate for deciding whether a prior synthesis or release note can reuse the same source observations, needs source review, or must hold for source repair. It does not decide whether a source claim is true, complete, or ready for publication. Version 0.2.0 writes `chorus-lens/3` receipts with label-support metadata while preserving historical `chorus-lens/2` verification through an explicit legacy path. v2 receipts do not bind the current v3-only label terms or `label_quality` fields.
+
+## Run it
+
+```bash
+pip install -e .
+
+chorus run examples/discourse-sample.json --verify   # try it on the bundled sample
+chorus run <corpus> --verify        # a corpus -> a verified discourse digest
+chorus decision <current> --reference <reference> --task "Check whether sources changed"
+chorus decision <current> --reference <reference> --public --public-policy public-policy.json
+chorus corpora <root>               # discover gather corpora as discourse sources
+chorus watch add <corpus>           # add a corpus to the daemon watchlist
+chorus daemon --interval 300        # poll the watchlist, synthesize on change
+chorus digests <store>              # what the daemon has synthesized
+chorus mcp                          # the MCP stdio server
+```
+
+`<corpus>` is a gather corpus directory (a folder holding `catalog.jsonl`) or a
+JSON list of rows. Add `--model "<command>"` to `run` to overlay a model's read on
+the comments the lexicon is least sure about; the overlay is provenance-tagged and
+never enters the re-checkable core.
+
+No service key or provider account is needed for the deterministic path. The
+bundled sample is the quickest local check:
+
+```bash
+chorus run examples/discourse-sample.json --verify
+python -m pytest
+```
+
+If `chorus` is not on `PATH`, reinstall from the checkout with
+`python -m pip install -e .` and open a new shell. `chorus.status` and
+`chorus.doctor` are MCP tools exposed through `chorus mcp`; they are not separate
+CLI subcommands. Public source-change projections need an operator-authored
+`--public-policy` sidecar before source names, ids, refs, or URLs appear.
+
+![Eight stages of verifying a discourse digest: receipt, version, vocabulary, inputs, rescore, recluster, rehash, and verdict. The receipt supplies the parameters and hashes the original run recorded. The method version selects the verifier for that pipeline; unsupported versions fail instead of being guessed. The lexicon is hashed into the receipt, so editing the word list invalidates every digest that was built with the old one. The corpus hash is checked before any work is done. Then the stored sentiment is thrown away and every comment is re-scored from its own text, which is why fabricated sentiment cannot verify. Clustering and weighting re-run from the parameters the receipt recorded, not from the live defaults, so raising a default cannot silently break an already-versioned receipt. The digest body is rebuilt from that re-derivation and hashed. The verdict is one boolean with nothing taken on trust: a digest whose themes, weights or sentiment distribution do not follow from the inputs fails, even when its own stored hash was recomputed to match its tampered body. Three outcomes: verified, tampered, and no receipt.](docs/art/verify-lane.svg)
+
+## The receipt
+
+The digest's `receipt` binds the inputs, the method, and the result. `verify`
+first checks that the submitted digest body still matches its own receipt, then
+re-runs the deterministic pipeline (score, cluster, weight) from the same corpus
+through the method-version verifier recorded in the receipt. Current runs write
+`chorus-lens/3`; historical `chorus-lens/2` receipts remain checkable through
+their legacy label body. Unsupported method versions fail closed. Any model
+overlay is listed separately with its own provenance and is excluded from that
+check: the parts a stranger can re-derive and the parts that are model opinion
+are kept distinct, on the record.
+
+![Twelve rows covering every number a digest reports and where it comes from. The lexicon is thirty words, fifteen positive and fifteen negative, each carrying a valence between minus three and plus three, and the whole list is hashed into every receipt. Ten intensifiers are looked for up to three tokens back, widening or narrowing a valence. Nine negators flip a valence and keep about three quarters of its size, so a negation weakens a claim rather than erasing it. The compound score runs from minus one to one, the summed valence divided by the root of itself squared plus fifteen, so no single loud comment runs away with a theme. Two emphases apply: an all-caps valence word of more than one letter counts a quarter more, and up to four exclamation marks add five percent each. Weight is the log of one plus engagement, times one plus half the sentiment intensity. Clustering runs a hashed TF-IDF cosine over five hundred and twelve dimensions against the nearest leader, joining above eighteen hundredths, seeded most-engaged first. Controversy is the population standard deviation of a theme's sentiment, zero at consensus and near one at a hard split. Twelve contested aspects are surfaced, each needing three mentioning voices and real disagreement on both sides. The receipt carries seven fields. The accented row is the model overlay, which is advisory opinion on the items the lexicon is least sure of and is deliberately kept outside the digest hash. The last row is engagement coverage, which reports how many items actually carried a signal, because an absent signal is recorded absent rather than counted as a zero.](docs/art/method-table.svg)
+
+## Design
+
+The design and its two exposed defects-caught-in-review live in
+[docs/superpowers/specs](docs/superpowers/specs). Sentiment is coarse by
+construction and the digest says so; clustering is lexical, not semantic. chorus
+tells you what it did and hands you the means to check it.
+
+## License
+
+Source-available under the Functional Source License (FSL-1.1-MIT) (see [LICENSE](LICENSE)):
+read it, run it, build on it; commercial use that competes with the project is
+reserved.
+
+---
+
+**[Zentropy Labs](https://github.com/ZentropyLabs-ai)** · order out of entropy. An independent lab building evidence-first tools that leave a re-checkable artifact behind. Built by Zain Dana Harper in Seattle. The full workbench is at [Project Telos](https://harperz9.github.io).

chorus_discourse-0.3.1/docs/releases/0.3.0.md

@@ -0,0 +1,64 @@
+# Chorus 0.3.0
+
+Date: 2026-09-07
+
+## Useful benefit
+
+Chorus 0.3.0 adds a source-change review gate through the CLI command
+`chorus decision` and the MCP tool `chorus.decision`. A reviewer can compare a
+current Gather-style source pack against the reference pack used for a prior
+synthesis or release note and get a machine-readable result:
+
+- `MATCH`: the compared source observations and fingerprints are unchanged.
+- `DRIFT`: one or more source rows were added, removed, or changed, so the prior
+  synthesis or release note needs source review before reuse.
+- `UNVERIFIABLE`: the source pack is missing, malformed, internally inconsistent,
+  or has invalid identities, so reuse should hold until source capture is
+  repaired.
+
+The public projection is safe by default as hashes, counts, checks, limitations,
+and policy provenance. Human-readable public ids, source names, refs, and URLs
+require an operator-authored public projection policy. Raw source row metadata
+cannot publish those fields.
+
+## Semantic limits
+
+This release does not decide whether a source claim is true, complete, or ready
+for publication. A `MATCH` result means the compared rows and fingerprints did not
+change. It does not prove that the source set is representative, that no relevant
+source exists elsewhere, that the implementation using the source is correct, or
+that a publication should proceed. `DRIFT` is a review trigger. `UNVERIFIABLE` is
+a source-repair trigger.
+
+## False-success controls
+
+Regression checks cover the observed failure modes:
+
+- missing paths and malformed JSON return typed `UNVERIFIABLE` results;
+- missing, blank, non-string, or null source text returns typed `UNVERIFIABLE`;
+- invalid, missing, mismatched, or non-UTF-8 Gather content objects return typed
+  `UNVERIFIABLE`;
+- duplicate ids and absent, null, blank, bool, numeric, list, or dict ids return
+  typed `UNVERIFIABLE` before normalization can coerce them;
+- source-controlled row metadata cannot authorize public ids, source names,
+  refs, or URLs;
+- operator public projection policy can publish safe human-readable fields when
+  supplied deliberately by the caller.
+
+## Install and use
+
+Download the wheel and checksums from the GitHub release. With Python 3.10 or
+later, install the downloaded file and inspect the command's input options:
+
+```sh
+python -m pip install ./chorus_discourse-0.3.0-py3-none-any.whl
+chorus decision --help
+```
+
+The package has no runtime dependencies. Existing MCP hosts can call
+`chorus.decision` through `chorus mcp`. Keep input packs private unless they were
+deliberately prepared for publication. A public policy authorizes only its
+selected metadata; it does not authorize publishing raw source corpora.
+
+GitHub downloads, host installation, and third-party marketplace approval are
+separate distribution states. This release makes no marketplace approval claim.

chorus_discourse-0.3.1/pyproject.toml

@@ -0,0 +1,29 @@
+[build-system]
+requires = ["setuptools>=61"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "chorus-discourse"
+version = "0.3.1"
+description = "A discourse-synthesis satellite for gather: weighted, clustered, re-checkable readings of comment corpora."
+readme = "README.md"
+requires-python = ">=3.10"
+license = "LicenseRef-FSL-1.1-MIT"
+license-files = ["LICENSE"]
+dependencies = []
+
+[project.scripts]
+chorus = "chorus.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.pytest.ini_options]
+# Without this, pytest imports whatever copy of the package happens to be
+# installed in the environment instead of this repo's src/. That is not a
+# style preference: chorus was resolving to a stale editable install pointing
+# at an old worktree, and plexus to a copy in site-packages, so both suites
+# were green while testing source that was not this checkout.
+pythonpath = ["src"]
+testpaths = ["tests"]
+addopts = "-q"

chorus_discourse-0.3.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

chorus_discourse-0.3.1/src/chorus/__init__.py

@@ -0,0 +1,10 @@
+"""chorus — a discourse-synthesis satellite for gather.
+
+Turns a corpus of comments and threads into a weighted, clustered, re-checkable
+reading of the discourse. Sentiment is a weight and a signal here, never an
+accept gate. Stdlib only; deterministic; every digest carries a receipt.
+"""
+from chorus.item import DiscourseItem, normalize
+
+__version__ = "0.3.1"
+__all__ = ["DiscourseItem", "normalize"]

chorus_discourse-0.3.1/src/chorus/__main__.py

@@ -0,0 +1,5 @@
+import sys
+from chorus.cli import main
+
+if __name__ == "__main__":
+    sys.exit(main(sys.argv[1:]))