articulate-writing 0.1.0__tar.gz

articulate_writing-0.1.0/.gitattributes

@@ -0,0 +1,7 @@
+# Normalize line endings to LF in the repository, so a CRLF/LF checkout never
+# rewrites a file and never reads as a spurious change (the receipt text hash is
+# byte-exact). Matches the CLI's own line-ending canonicalization.
+* text=auto eol=lf
+*.png binary
+*.jpg binary
+*.gif binary

articulate_writing-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,48 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python: ["3.9", "3.10", "3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python }}
+      - run: pip install -e ".[dev]"
+      # The suite gates on the benchmark (recall/specificity), the dogfood check
+      # (our own prose passes our own standard), the mode/receipt/LSP contracts,
+      # and the ReDoS safety test.
+      - run: python -m pytest -q
+
+  articulate-self-check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install -e .
+      # Dogfood in CI: our shipped docs must pass our own gate.
+      - run: python -m articulate.cli check README.md docs/*.md --gate
+
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install build
+      - run: python -m build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/*

articulate_writing-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,41 @@
+name: Publish to PyPI
+
+# Publishes the package when a GitHub Release is published, or on a manual run.
+# Uses PyPI Trusted Publishing (OIDC): no API token is stored in the repository.
+# One-time setup on PyPI: add a pending publisher for project "articulate-writing"
+# pointing at this repository, the workflow file "publish.yml", and the environment
+# "pypi". See https://docs.pypi.org/trusted-publishers/.
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install build twine
+      - run: python -m build
+      - run: python -m twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write        # required for OIDC Trusted Publishing
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

articulate_writing-0.1.0/.gitignore

@@ -0,0 +1,34 @@
+# Secrets / env (standard workspace rule; the negation must follow .env.*)
+.env
+.env.*
+!.env.example
+.envrc
+.envrc.local
+CLAUDE.local.md
+
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.venv/
+venv/
+
+# Editor extension deps and build output (package.json/-lock.json stay tracked)
+node_modules/
+out/
+*.vsix
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Internal-only: strategy/scope with local paths and pricing, and the migration
+# checklist that references local tooling. Kept out of the public repo.
+project-docs/
+MIGRATION.md

articulate_writing-0.1.0/.pre-commit-hooks.yaml

@@ -0,0 +1,7 @@
+- id: articulate
+  name: Articulate writing check
+  description: Flag AI and prose tells; fail the commit on a blocked file.
+  entry: python -m articulate.cli check --gate
+  language: python
+  types_or: [markdown, plain-text]
+  require_serial: false

articulate_writing-0.1.0/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.

articulate_writing-0.1.0/PKG-INFO

@@ -0,0 +1,161 @@
+Metadata-Version: 2.5
+Name: articulate-writing
+Version: 0.1.0
+Summary: Local, re-derivable writing-quality and AI-tell detection and editing: register profiles, writing modes, a genre axis, and content-free audit receipts.
+Project-URL: Homepage, https://github.com/HarperZ9/articulate
+Project-URL: Repository, https://github.com/HarperZ9/articulate
+Project-URL: Documentation, https://github.com/HarperZ9/articulate/tree/main/docs
+Project-URL: Issues, https://github.com/HarperZ9/articulate/issues
+Author: Zain Dana Harper
+License-Expression: LicenseRef-FSL-1.1-MIT
+License-File: LICENSE
+Keywords: ai-detection,audit,editor,linter,prose,quality,receipt,writing
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Text Processing :: Linguistic
+Requires-Python: >=3.9
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == 'dev'
+Provides-Extra: mcp
+Requires-Dist: fastmcp>=3; extra == 'mcp'
+Description-Content-Type: text/markdown
+
+# Articulate
+
+A local writing-quality and AI-tell detection and editing tool. It flags the
+prose devices and machine-writing tells that make text read as generated, scores
+how machine-textured a passage is, and (with an LLM backend) rewrites prose to a
+plain, skilled standard. The core runs standard-library-only with no network
+call. Detection quality and writing quality are the goals; a detector score is a
+benchmark and a byproduct, never something the tool optimizes toward, and it is
+not an evasion tool.
+
+## Documentation
+
+Full docs are in [`docs/`](docs/): [getting started](docs/getting-started.md), a
+thorough [walkthrough](docs/walkthrough.md), the [feature reference](docs/features.md),
+the [CLI reference](docs/cli.md), and the [boundaries](docs/boundaries.md) that
+say what a verdict and a receipt mean and what they never claim.
+
+## What it does
+
+- **Detect.** Flags banned rhetorical devices (antithesis including keyword-free
+  parallel-negation contrast pairs, corrective negation, rule-of-three, em-dashes,
+  filler intensifiers, corporate verbs), current frontier-model register,
+  marketing, and email/blog tells, and Williams/Orwell signals (expletive openers,
+  nominalization density, passive voice, adverb density, cadence uniformity,
+  opener repetition). Emits a graded 0-100 texture score and a clean/flagged gate.
+- **Adapt by register.** A profile system (procedure, commit, research, readme,
+  essay, narrative, and more) sets which findings block. Fiction gates nothing;
+  procedures and essays gate strictly. Profiles resolve from `--profile`, an
+  in-file `writing-profile:` tag, or the file path.
+- **Choose a mode or a genre.** A writing mode crosses a domain register with an
+  articulation need, such as `memo/argue` or `technical-docs/explain`. The genre
+  axis reads narrative and expressive prose by its own convention: `literary-fiction`,
+  `genre-fiction`, `ya-fiction`, `memoir`, `screenplay`, `poetry`. Under a fiction
+  genre, quoted speech is masked out of the device passes so a character's line is
+  never scored as the author's prose; the craft devices report but never block; and
+  a report-only lexicon flags generation artifacts such as the somatic cliche or the
+  "could not help but" reflexive. Screenplay classifies Fountain roles first, so only
+  action lines face the device gate. Poetry reads by the line and drops the
+  craft-device categories from its report. Run `articulate modes` to list them.
+- **Edit.** `judge` reads the judgment-level failures a regex cannot see
+  (confident emptiness, vague abstraction, hedging with no position, weak verbs).
+  `fix` rewrites to the standard, self-checked against the detector. `polish`
+  loops until five qualities (concreteness, commitment, economy, rhythm, a
+  restatable fact per paragraph) clear a bar. Gated on writing quality, never a
+  detector score. Needs an LLM backend (local model or the `claude` CLI).
+
+## Use
+
+```bash
+# lint (exit 1 when blocked under the file's profile)
+python -m articulate.cli check path/to/doc.md --gate
+python -m articulate.cli check essay.md --profile essay --verbose
+echo "some prose" | python -m articulate.cli score
+
+# library
+python -c "import articulate; print(articulate.check_text('...', profile=articulate.profiles.load('research'))['gate'])"
+
+# receipt: a re-derivable verdict (Match / Drift / Unverifiable)
+python -m articulate.cli receipt doc.md --profile research > doc.receipt.json
+python -m articulate.cli verify doc.receipt.json doc.md   # replay; exit 0/1/2
+
+# content-free audit receipt: replayable, but stores no verbatim text (drop or hash
+# the matched substring). For a team that must retain a record without the source.
+python -m articulate.cli receipt doc.md --redact drop --reviewer alice > receipts/doc.json
+python -m articulate.cli check doc.md --content-free --sarif > doc.sarif  # no substrings
+
+# audit: query committed receipts locally (no server), and re-verify they still hold
+python -m articulate.cli audit receipts/                 # recorded verdicts, blocked rules
+python -m articulate.cli audit receipts/ --reverify --gate   # exit 1 if a source drifted
+
+# SARIF for CI (GitHub Code Scanning, Azure, reviewdog)
+python -m articulate.cli check src/**/*.md --sarif > articulate.sarif
+
+# LSP server (inline squiggles in VS Code, JetBrains via LSP4IJ, Neovim). Stdlib
+# only, no dependency. Point your editor's LSP client at:
+python -m articulate.lsp_server
+
+# benchmark (regression-gated corpus) and MCP server
+python -m articulate.bench
+python -m articulate.mcp_server
+```
+
+### Editor setup
+
+The LSP server speaks standard LSP over stdio, so any LSP client can drive it.
+A minimal Neovim registration:
+
+```lua
+vim.lsp.start({ name = "articulate", cmd = { "python", "-m", "articulate.lsp_server" },
+  filetypes = { "markdown", "text", "tex" } })
+```
+
+For VS Code, a thin client that launches the same command as a `LanguageClient`
+is all that is needed; no server code lives in the extension.
+
+### Scientific and mathematical writing
+
+`academic/prove` and `science-writing/explain` target hard technical exposition:
+stating the idea before the formalism, keeping a roadmap, defining each symbol
+once. The proof mode does not rewrite by default, because a wrong change to a
+quantifier order or an inequality direction changes a theorem; it routes to
+`--judge`, and `--fix` is opt-in. On a `.tex` file the editor masks every math
+span before a rewrite and splices it back byte for byte, so a formula is never
+altered.
+
+The boundary is fixed and load-bearing: a clean gate, a low texture score, or a
+Match receipt means the prose was screened under a named ruleset. It says nothing
+about whether the theorem is true. A clearly written proof can still be false, and
+Articulate never checks the mathematics. Correctness comes from referees and proof
+assistants (Lean, Coq, Isabelle), never from this tool.
+
+## Privacy
+
+The detector never touches the network. The editor layer defaults to a local
+model where configured, and an `--offline` mode is on the roadmap for air-gapped
+use. A content-free audit receipt keeps no verbatim text: it drops the matched
+substring and the exact offsets, keeping only which rule fired, its tier and
+category, and the line. A team can retain and replay a record without storing the
+sensitive source. Content-free is not zero-leakage: which rules fired and the line
+remain, which for a closed-vocabulary rule narrows the flagged word to that rule's
+small public candidate set. The `hash` mode keeps a sha256 for an equality check
+against a known string, so it is dictionary-reversible for those closed-vocabulary
+rules; use `drop` when the flagged word must stay secret. An auto-filled `reviewer`
+(from `$GITHUB_ACTOR`) records CI attribution, and a named human sign-off needs an
+explicit `--reviewer`. Committed receipts live as long as the repo, with no
+automatic expiry (bounded retention is a later self-hosted tier). The full
+[documentation](docs/) covers each surface and the boundaries in depth.
+
+## Status
+
+Pre-1.0. The core detector, profile system, writing modes (including the science
+modes for proofs and technical exposition), the genre axis (fiction, memoir,
+screenplay, poetry), the editor injection boundary, per-span mixed-authorship
+verdicts, a sub-threshold "unverifiable" calibration, binary fail-closed input
+guards, the benchmark, the editor layer, the CLI, the LSP and SARIF surfaces,
+receipts, the content-free audit receipt, and the MCP server are built into this
+one package. A local-model editor backend, a labeled non-native corpus for a
+fairness check, and PyPI packaging are on the roadmap.

articulate_writing-0.1.0/README.md

@@ -0,0 +1,138 @@
+# Articulate
+
+A local writing-quality and AI-tell detection and editing tool. It flags the
+prose devices and machine-writing tells that make text read as generated, scores
+how machine-textured a passage is, and (with an LLM backend) rewrites prose to a
+plain, skilled standard. The core runs standard-library-only with no network
+call. Detection quality and writing quality are the goals; a detector score is a
+benchmark and a byproduct, never something the tool optimizes toward, and it is
+not an evasion tool.
+
+## Documentation
+
+Full docs are in [`docs/`](docs/): [getting started](docs/getting-started.md), a
+thorough [walkthrough](docs/walkthrough.md), the [feature reference](docs/features.md),
+the [CLI reference](docs/cli.md), and the [boundaries](docs/boundaries.md) that
+say what a verdict and a receipt mean and what they never claim.
+
+## What it does
+
+- **Detect.** Flags banned rhetorical devices (antithesis including keyword-free
+  parallel-negation contrast pairs, corrective negation, rule-of-three, em-dashes,
+  filler intensifiers, corporate verbs), current frontier-model register,
+  marketing, and email/blog tells, and Williams/Orwell signals (expletive openers,
+  nominalization density, passive voice, adverb density, cadence uniformity,
+  opener repetition). Emits a graded 0-100 texture score and a clean/flagged gate.
+- **Adapt by register.** A profile system (procedure, commit, research, readme,
+  essay, narrative, and more) sets which findings block. Fiction gates nothing;
+  procedures and essays gate strictly. Profiles resolve from `--profile`, an
+  in-file `writing-profile:` tag, or the file path.
+- **Choose a mode or a genre.** A writing mode crosses a domain register with an
+  articulation need, such as `memo/argue` or `technical-docs/explain`. The genre
+  axis reads narrative and expressive prose by its own convention: `literary-fiction`,
+  `genre-fiction`, `ya-fiction`, `memoir`, `screenplay`, `poetry`. Under a fiction
+  genre, quoted speech is masked out of the device passes so a character's line is
+  never scored as the author's prose; the craft devices report but never block; and
+  a report-only lexicon flags generation artifacts such as the somatic cliche or the
+  "could not help but" reflexive. Screenplay classifies Fountain roles first, so only
+  action lines face the device gate. Poetry reads by the line and drops the
+  craft-device categories from its report. Run `articulate modes` to list them.
+- **Edit.** `judge` reads the judgment-level failures a regex cannot see
+  (confident emptiness, vague abstraction, hedging with no position, weak verbs).
+  `fix` rewrites to the standard, self-checked against the detector. `polish`
+  loops until five qualities (concreteness, commitment, economy, rhythm, a
+  restatable fact per paragraph) clear a bar. Gated on writing quality, never a
+  detector score. Needs an LLM backend (local model or the `claude` CLI).
+
+## Use
+
+```bash
+# lint (exit 1 when blocked under the file's profile)
+python -m articulate.cli check path/to/doc.md --gate
+python -m articulate.cli check essay.md --profile essay --verbose
+echo "some prose" | python -m articulate.cli score
+
+# library
+python -c "import articulate; print(articulate.check_text('...', profile=articulate.profiles.load('research'))['gate'])"
+
+# receipt: a re-derivable verdict (Match / Drift / Unverifiable)
+python -m articulate.cli receipt doc.md --profile research > doc.receipt.json
+python -m articulate.cli verify doc.receipt.json doc.md   # replay; exit 0/1/2
+
+# content-free audit receipt: replayable, but stores no verbatim text (drop or hash
+# the matched substring). For a team that must retain a record without the source.
+python -m articulate.cli receipt doc.md --redact drop --reviewer alice > receipts/doc.json
+python -m articulate.cli check doc.md --content-free --sarif > doc.sarif  # no substrings
+
+# audit: query committed receipts locally (no server), and re-verify they still hold
+python -m articulate.cli audit receipts/                 # recorded verdicts, blocked rules
+python -m articulate.cli audit receipts/ --reverify --gate   # exit 1 if a source drifted
+
+# SARIF for CI (GitHub Code Scanning, Azure, reviewdog)
+python -m articulate.cli check src/**/*.md --sarif > articulate.sarif
+
+# LSP server (inline squiggles in VS Code, JetBrains via LSP4IJ, Neovim). Stdlib
+# only, no dependency. Point your editor's LSP client at:
+python -m articulate.lsp_server
+
+# benchmark (regression-gated corpus) and MCP server
+python -m articulate.bench
+python -m articulate.mcp_server
+```
+
+### Editor setup
+
+The LSP server speaks standard LSP over stdio, so any LSP client can drive it.
+A minimal Neovim registration:
+
+```lua
+vim.lsp.start({ name = "articulate", cmd = { "python", "-m", "articulate.lsp_server" },
+  filetypes = { "markdown", "text", "tex" } })
+```
+
+For VS Code, a thin client that launches the same command as a `LanguageClient`
+is all that is needed; no server code lives in the extension.
+
+### Scientific and mathematical writing
+
+`academic/prove` and `science-writing/explain` target hard technical exposition:
+stating the idea before the formalism, keeping a roadmap, defining each symbol
+once. The proof mode does not rewrite by default, because a wrong change to a
+quantifier order or an inequality direction changes a theorem; it routes to
+`--judge`, and `--fix` is opt-in. On a `.tex` file the editor masks every math
+span before a rewrite and splices it back byte for byte, so a formula is never
+altered.
+
+The boundary is fixed and load-bearing: a clean gate, a low texture score, or a
+Match receipt means the prose was screened under a named ruleset. It says nothing
+about whether the theorem is true. A clearly written proof can still be false, and
+Articulate never checks the mathematics. Correctness comes from referees and proof
+assistants (Lean, Coq, Isabelle), never from this tool.
+
+## Privacy
+
+The detector never touches the network. The editor layer defaults to a local
+model where configured, and an `--offline` mode is on the roadmap for air-gapped
+use. A content-free audit receipt keeps no verbatim text: it drops the matched
+substring and the exact offsets, keeping only which rule fired, its tier and
+category, and the line. A team can retain and replay a record without storing the
+sensitive source. Content-free is not zero-leakage: which rules fired and the line
+remain, which for a closed-vocabulary rule narrows the flagged word to that rule's
+small public candidate set. The `hash` mode keeps a sha256 for an equality check
+against a known string, so it is dictionary-reversible for those closed-vocabulary
+rules; use `drop` when the flagged word must stay secret. An auto-filled `reviewer`
+(from `$GITHUB_ACTOR`) records CI attribution, and a named human sign-off needs an
+explicit `--reviewer`. Committed receipts live as long as the repo, with no
+automatic expiry (bounded retention is a later self-hosted tier). The full
+[documentation](docs/) covers each surface and the boundaries in depth.
+
+## Status
+
+Pre-1.0. The core detector, profile system, writing modes (including the science
+modes for proofs and technical exposition), the genre axis (fiction, memoir,
+screenplay, poetry), the editor injection boundary, per-span mixed-authorship
+verdicts, a sub-threshold "unverifiable" calibration, binary fail-closed input
+guards, the benchmark, the editor layer, the CLI, the LSP and SARIF surfaces,
+receipts, the content-free audit receipt, and the MCP server are built into this
+one package. A local-model editor backend, a labeled non-native corpus for a
+fairness check, and PyPI packaging are on the roadmap.

articulate_writing-0.1.0/action.yml

@@ -0,0 +1,48 @@
+name: "Articulate"
+description: "Writing-quality and AI-tell checks with SARIF output for inline PR annotations."
+branding:
+  icon: "edit-3"
+  color: "green"
+inputs:
+  files:
+    description: "Files or globs to check (space-separated)."
+    required: false
+    default: "**/*.md"
+  profile:
+    description: "Force a register profile (optional)."
+    required: false
+    default: ""
+  python-version:
+    description: "Python version to run under."
+    required: false
+    default: "3.12"
+  audit-path:
+    description: "Directory of committed receipts to re-verify; fails the build on any drift."
+    required: false
+    default: ""
+runs:
+  using: "composite"
+  steps:
+    - uses: actions/setup-python@v5
+      with:
+        python-version: ${{ inputs.python-version }}
+    # Installs the checked-out package. Swap for `pip install articulate-writing`
+    # once the package is published to PyPI.
+    - run: pip install "${{ github.action_path }}"
+      shell: bash
+    - run: |
+        PROFILE=""
+        if [ -n "${{ inputs.profile }}" ]; then PROFILE="--profile ${{ inputs.profile }}"; fi
+        python -m articulate.cli check ${{ inputs.files }} $PROFILE --sarif > articulate.sarif
+      shell: bash
+    - uses: github/codeql-action/upload-sarif@v3
+      with:
+        sarif_file: articulate.sarif
+        category: articulate
+    # Optional: re-verify committed receipts still hold against their source, and
+    # fail the build on any drift. Wire a receipts directory via the audit-path input.
+    - run: |
+        if [ -n "${{ inputs.audit-path }}" ]; then
+          python -m articulate.cli audit "${{ inputs.audit-path }}" --reverify --gate
+        fi
+      shell: bash

articulate_writing-0.1.0/corpus/ai/blog-intro.md

@@ -0,0 +1 @@
+In today's fast-paced digital world, staying ahead of the curve is more important than ever. As technology continues to evolve, businesses must adapt to remain competitive. Whether you're a seasoned professional or just starting out, this comprehensive guide will help you navigate the ever-changing landscape. Studies have shown that companies who embrace innovation consistently outperform their peers. Moreover, by fostering a culture of collaboration, organizations can unlock their full potential. Ultimately, the possibilities are endless, and the future is bright.

articulate_writing-0.1.0/corpus/ai/email-outreach.md

@@ -0,0 +1 @@
+I hope this email finds you well. I wanted to reach out to touch base regarding our upcoming collaboration. I'm thrilled to announce that we've made significant progress on the initiative. By leveraging our combined strengths, I'm confident we can unlock tremendous value and drive meaningful outcomes. Please don't hesitate to reach out if you have any questions. Circling back on the earlier thread, it's essential to ensure that we stay aligned. Looking forward to connecting further and delivering impactful results together.

articulate_writing-0.1.0/corpus/ai/flagship-clean.pangram

@@ -0,0 +1 @@
+AI 100%