Skip to content

Restore exact user-visible invariance and start Cycle 8 carrier research - #97

Merged
byte271 merged 5 commits into
mainfrom
cursor/product-visible-invariance-2d93
Aug 26, 2026
Merged

byte271 merged 5 commits into
mainfrom
cursor/product-visible-invariance-2d93

Conversation

@byte271

@byte271 byte271 commented Aug 25, 2026 •

Copy link
Copy Markdown
Owner

Why

The public product path had drifted from the original contract. release_transform_registry() was the default contraction catalog, so FuckMark visibly rewrote user text (I do not agree. → I don't agree.). Semantic equivalence is not the product. Exact user-visible projection is Priority Zero.

Live GitHub at start of this work: main d7eeb0f (PR #96 merged), no open PRs, tag v0.2.0.

Contract repair

  • Contract specs/fuckmark-user-visible-invariance-v1.contract.json and docs/product-contract.md.
  • Visible projection v1 is insertion-only. Product hard gate fails with USER_VISIBLE_TEXT_CHANGED. Detector score cannot override it.
  • release_transform_registry() is the empty product registry. CLI release-cli-v4 fail-closes to the original text.
  • Historical contraction / Cycle 6 spacing / Cycle 7 durable catalogs remain replayable under explicit historical names.

GitHub CI's installed-CLI end-to-end still expected contraction output after the product path was emptied. That leftover assertion now expects unchanged visible text.

Historical reclassification (not rewritten)

  • Cycle 6 formal: NONZERO_RESIDUAL 7/192. PRODUCT_DISQUALIFIED (visible U+0020 runs).
  • Cycle 7 Stage A/B/C: INSUFFICIENT_EVIDENCE, PRODUCT_DISQUALIFIED.
  • U+200C: visibility-aligned diagnostic. REJECTED as durable (Cf-strip) and Chromium-pixel-REJECTED.

Cycle 8 research (not a release promotion)

U+034F is not product-authorized. The public CLI still authorizes zero carriers.

  • Ledger: exploratory 890000, replication 900000, validation 910000, secondary 920000. Confirmation reserves 830000/840000/850000 untouched. Cycle 7 880000 still unseen.
  • Fixture compare: visible-projection pass 20/20. Quote interiors stay protected spans.
  • Chromium pre screenshots: U+034F and U+FE00 VERIFIED pixel-equal; U+200C REJECTED (PNG bytes differ).
  • Detector-blind GPT-2 / Hugging Face SynthID Weighted Mean, frozen threshold 0.5570987654320988, 4 watermarked + 4 unwatermarked ASCII pairs per seed:
Seed Role Identity WM U+034F x1 WM U+034F Cf-strip WM UW (identity / U+034F)
890000 exploratory 3/4 0/4 0/4 0/4 / 0/4
900000 replication 4/4 0/4 0/4 0/4 / 0/4
910000 validation 3/4 0/4 0/4 0/4 / 0/4

U+200C also drops raw detections but Cf-strip restores identity detections (3/4, 4/4, 3/4). U+034F x8 can overflow GPT-2's 1024-token context; prefer x1.

This is PROMISING_DEVELOPMENT / HYPOTHESIS on tiny corpora. It is not Cycle 6-scale confirmation and is not a CLI promotion.

Codex P2 follow-up

Addressed the three Codex review comments on 12445a5 (originally reviewed 2ef9f8f):

  1. load_product_contract() returns the embedded v1 payload when specs/ is absent from an installed wheel. Checkout copies of the contract file must still match the embedded payload.
  2. Writers that replace pinned specs/cycle8 tokenizer JSON call require_gpt2_encoder() and fail closed. The detector harness (cycle8_hf) still scores when tiktoken is absent, writing encoder: unavailable into artifact fixture-compare instead of crashing GitHub Cycle8 Carrier Detector.
  3. Chromium HTML evidence encodes less-than and greater-than as JSON unicode escapes so an ASCII script terminator cannot close the inline script.

Tests

Full pytest passed locally after the Cycle8 CI fix. Cycle 8 evidence tests still pin the committed artifacts. The public CLI still leaves I do not agree. and We cannot continue. unchanged.

Open in Web Open in Cursor 

The public CLI no longer applies contractions or other visible edits.
release_transform_registry is now the empty product-visible-invariance
registry and fail-closes to the original text. Historical visible-edit
catalogs remain replayable under explicit names. Cycle 8 starts
invisible-carrier research; U+034F is a durable-track sanitizer
candidate, not a release promotion.

Co-authored-by: Byte271 <byte271@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Aug 25, 2026 •

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 87ad24f3-501a-49f0-a52b-84dc3d638109


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

The installed-CLI GitHub check still expected contraction output after
release-cli-v4 fail-closed. Align that assertion with unchanged text,
and instrument detector-blind U+034F space-carrier arms without
promoting any carrier to the product registry.

Co-authored-by: Byte271 <byte271@users.noreply.github.com>
@byte271
byte271 marked this pull request as ready for review August 25, 2026 22:56

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2ef9f8f891

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread fuckmark/product/contract.py
Comment thread fuckmark/cycle8/tokenizer_screen.py
Comment thread fuckmark/product/rendering.py
cursoragent and others added 3 commits August 25, 2026 23:10
Keep the product registry empty. Detector-blind space-carrier arms pass
visible projection on generated ASCII pairs. U+034F reduces watermarked
detections without unwatermarked inflation on these tiny corpora; U+200C
is undone by Cf-strip and fails Chromium pixel equality.

Co-authored-by: Byte271 <byte271@users.noreply.github.com>
load_product_contract uses the embedded v1 payload when specs/ is
absent from an installed wheel. Cycle 8 writers require a GPT-2
encoder before replacing verified tokenizer artifacts. Chromium HTML
evidence encodes less-than and greater-than so an ASCII script
terminator cannot close the inline script.

Co-authored-by: Byte271 <byte271@users.noreply.github.com>
Pinned specs/cycle8 writers still fail closed without a GPT-2 encoder.
The detector harness writes fixture-compare with encoder unavailable so
GitHub Cycle8 Carrier Detector can score seed 890000 without tiktoken.

Co-authored-by: Byte271 <byte271@users.noreply.github.com>
@byte271
byte271 merged commit 3ab6bd1 into main Aug 26, 2026
42 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants