Skip to content

Repository files navigation

AI Sloppy Copy: Evidence-backed copy. Local rule enforcement.

Upstream copy and paid-ad guardrails used by Chief for ChatGPT Work and Codex.

CI status Latest release MIT license Chief upstream runtime Python standard library Local checker with no telemetry

Install | Example | Versions | Rules | CLI | Security

AI Sloppy Copy is the independently maintained source product for Chief's writing and evidence validator. Chief pins release 0.5.0 and loads it only when the request needs governed copy. Ordinary teammates do not install or select AI Sloppy Copy separately; they install Chief and ask for the work they need. This repository remains public for maintainers and direct development.

The deterministic local checker catches prohibited model-written patterns, applies evidence and voice controls, preserves paid-ad structure, and returns exact rule IDs for repair. The operator keeps final approval.

It does not identify who wrote text or promise AI-detector results. Rule compliance and authorship are different questions.

What changed in v0.5.0

  • The GitHub release, tag, ZIP, and both host manifests now use 0.5.0.
  • Windows PowerShell hook input may begin with a UTF-8 byte-order mark. The parser now accepts it instead of silently skipping the event.
  • The combined STYLE-001 and STYLE-008 failure shown during the 0.4.0 review is now a regression case. The test covers a partial repair plus a clean pass.
  • Repair feedback now requires another scan of the complete corrected answer. Checking only the named passages is not enough.
  • Paid-ad behavior remains unchanged. Standard 2.2.0 remains the active rules contract.

Versions explained

AI Sloppy Copy has one product version and one Standard version. Users install and cite the product version.

Layer Current version What it identifies When it changes
Product 0.5.0 The GitHub release and installable ZIP. Both host manifests carry the same number. Plugin code, hooks, packaging, or public documentation changes.
Standard 2.2.0 The rules contract used by the skill and local checker. A writing rule or its enforcement contract changes.

The product package contains the skill instructions and lifecycle hooks. It also carries the local checker with its compiled rules. Host manifests and visual assets are included.

Standard 2.2.0 defines 288 term rules plus 21 expression rules. It defines 41 style rules too. Evidence controls and approved-voice boundaries are part of the contract. Protected-text handling and paid-ad requirements are included.

A manifest is a small JSON file inside the upstream package. Chief's release builder imports the pinned runtime and records its version with its hashes. Only Chief is exposed to teammates. A manifest is not a separate release.

See it work

A generic draft is flagged and repaired with specific language.

Input
We can leverage this cutting-edge system to turbocharge production.

Hard failures
TERM-021  leverage
TERM-007  cutting-edge
TERM-211  turbocharge

Repair
Run the local checker before publishing. It flags blocked phrases and returns
rule IDs for repair.

The checker reports the problem. It does not perform reckless global replacement or silently change protected text.

What it enforces

Control Result
Evidence gates Unsupported recommendations, testimonials, case studies, and claims require a verified basis.
Paid-ad structure Complete ads preserve a Hook or Callout. They also preserve ordered Value plus one Direct CTA.
Campaign controls One CTA stays fixed while hooks and three to five Value blocks are tested.
Approved voice Named-person copy requires owner-approved voice samples.
Protected text Quotes, code, commands, paths, IDs, legal text, and required vendor wording stay exact.
Hard rules Banned terms and prohibited expressions block release.
Review rules Context-dependent style flags stay visible for human judgment.
Authorship boundary Compliance is never presented as proof of human authorship.
Included coverage Count
Term rules 288
Expression rules 21
Style rules 41
Regression cases 67
Paid-ad scenarios 9
Checker network calls 0

Install

Normal team use

Install Chief of Staff once. Do not install this repository separately. In ChatGPT Work, open Plugins, find Chief of Staff, click +, and start a new chat after OpenAI publishes the public listing. Until then, a workspace admin can install Chief from its GitHub-backed marketplace.

Ask Chief normally. For example:

Revise this landing page, preserve the approved voice, verify every claim, and return release-ready copy.

Chief routes the request through AI Sloppy Copy and reports what ran.

Direct Codex development only

Maintainers testing AI Sloppy Copy independently can install the upstream package directly:

codex plugin marketplace add plotdevice01/ai-sloppy-copy
codex plugin add ai-sloppy-copy@ai-sloppy-copy

If Codex says the marketplace already exists, update it:

codex plugin marketplace upgrade ai-sloppy-copy

If you still have a legacy 2.2.6 installation, reinstall once. Semantic-version updaters correctly but unhelpfully sort 0.5.0 below 2.2.6:

codex plugin remove ai-sloppy-copy
codex plugin marketplace upgrade ai-sloppy-copy
codex plugin add ai-sloppy-copy@ai-sloppy-copy

Restart Codex, open /hooks, review UserPromptSubmit and Stop, and start a fresh task. Confirm the plugin:

codex plugin list --json

Confirm ai-sloppy-copy@ai-sloppy-copy is installed and active. Then ask:

Use AI Sloppy Copy to revise this text: We can leverage this cutting-edge system to turbocharge production.

The response should replace the flagged phrases with specific wording. If the plugin is missing, repeat step 1 and restart Codex. Do not copy plugin files into application folders manually.

How it works

Verified sources and approved voice move through the local checker before human approval.

The shared skill applies the writing contract. Both host protocols use the same hooks and checker against the same 2.2.0 rule file. The Python checker handles repeatable file scans. Protected text and human approval remain explicit boundaries.

Use the checker directly

The checker uses only the Python standard library:

python plugins/ai-sloppy-copy/scripts/ai_sloppy_copy.py `
  --rules plugins/ai-sloppy-copy/scripts/AI-Sloppy-Copy-Rules.json `
  path/to/draft.docx

Supported inputs: TXT, Markdown, CSV, JSON, HTML, XML, and DOCX.

  • Exit code 0: no hard violations.
  • Exit code 1: one or more hard violations.

Update or remove a direct development install

Update:

codex plugin marketplace upgrade ai-sloppy-copy
codex plugin remove ai-sloppy-copy
codex plugin add ai-sloppy-copy@ai-sloppy-copy

Remove:

codex plugin remove ai-sloppy-copy
codex plugin marketplace remove ai-sloppy-copy

Chief of Staff stack

AI Sloppy Copy is bundled as a pinned internal runtime in Codex Chief of Staff and is not a separate team install or public-directory listing. The teammate makes one request to Chief. Chief handles the internal route without specialist negotiation.

Privacy and security

The checker runs locally. The plugin has no connectors, accounts, telemetry, or network calls. Its hooks receive host hook data and write only a temporary per-session retry counter.

Do not put secrets or private client text into custom rule datasets. Report a security issue through GitHub private vulnerability reporting.

See SECURITY.md for the support policy.

Development

python tests/test_runtime.py
python scripts/build_release.py

Every tagged release produces a deterministic portable ZIP. The release archive contains the same plugin, rules, documentation, and visual assets as this repository.

See CONTRIBUTING.md, CHANGELOG.md, and THIRD-PARTY-NOTICES.md.

License

MIT. Third-party source notices and licenses are listed in THIRD-PARTY-NOTICES.md.

About

Codex and Claude Code writing guardrails for evidence, approved voice, protected text, and local rule enforcement.

Topics

Resources

Contributing

Security policy

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages