Skip to content

Record H14/H15 sanitizer research without product authorization - #104

Closed
byte271 wants to merge 12 commits into
mainfrom
cursor/sanitizer-robust-mechanism-e145
Closed

byte271 wants to merge 12 commits into
mainfrom
cursor/sanitizer-robust-mechanism-e145

Conversation

@byte271

@byte271 byte271 commented Aug 27, 2026 •

Copy link
Copy Markdown
Owner

Follow-up sanitizer research starting from live PR #103 (715bf10). This branch is #103 plus H14 and H15. It does not reopen mix freeze, does not retune spent confirmation corpora, and does not product-authorize a carrier.

Confirmation 0/192 is unchanged. product_approved_carriers_v1() remains empty. release_transform_registry() remains empty. process_text("I do not agree.") is unchanged. Mix sanitizer robustness stays FAIL.

Why H13/H14 were not the stopping point

H9 closed assigned width-0 insertions at Mn / Me / Cf. H12 found Cc sanitizer survivors that are Chromium host-dependent and not ordinary text. H13 classified those families and found no conjunction survivor. H14 extended that negative result to Mc, Lm, designed blanks, Hangul fillers, and font-metric empty glyphs.

H15 goes to sequence-level / representation-level transforms instead of another single-codepoint sweep.

H15 measurements

Required sanitizers remain Mn-strip, default-ignorable-strip, Cf-strip, NFC, NFKC, NFKD, and combinations. They were not weakened.

Class Sanitizers Chromium pre Ordinary text Product
Grapheme prepend plus Latin base (13 survivors) PASS REJECTED FAIL FAIL
Joining connectors (tatweel / nirugu / Nko) PASS REJECTED FAIL FAIL
Hangul L plus V composition FAIL (NFC or NFKD) REJECTED FAIL FAIL
Bidi LRI/FSI wrap around LTR English FAIL (Cf-strip) VERIFIED on this host FAIL FAIL
ISO-6429 ESC CSI sequences PASS (Cc plus ASCII) REJECTED (parameters visible) FAIL FAIL
Mix plus DEL remainder FAIL as a pair VERIFIED here FAIL FAIL
DejaVu Latin GSUB extra ligature FAIL (NFKC / no extra glyph) n/a FAIL FAIL

ASCII plus sanitizer-surviving Mc does not NFC-compose. DejaVu Sans Mono has no sanitizer-surviving zero-advance mapped glyph, including composites.

Partial sanitizer remainders collapse to a previously classified class (H12 Cc, or visible Mc/Me). That is not a new Priority-Zero mechanism.

Boundary

Sequence-level transforms do not escape the H13/H14 sanitizer boundary. After Mn-strip, default-ignorable-strip, Cf-strip, NFC, and NFKC, a surviving difference must still be a non-Mn, non-default-ignorable, non-Cf graphic. Measured sequence graphics change Chromium pixels. Renderer-neutral wraps and joiners that were pixel-equal here are Cf or default-ignorable and die to those strips.

No measured class is simultaneously sanitizer-surviving, Chromium-portable, ordinary plain text, and Priority-Zero safe.

This does not rewrite mix sanitizer FAIL. H14 spec hash b1ca728142a217887ad327ddb226869b4343c898452240d731ab4c7d07f6f918. H15 spec hash a0fcdd2dfd7a05575592a2dec095c54513869deeb9bfdfbca4d7301ef478906c.

What this does not do

  • It does not mark mix sanitizer robustness PASS.
  • It does not put any carrier in release_transform_registry().
  • It does not inspect or rerun spent confirmation seeds 830000 / 840000 / 850000.
  • It does not generate 950000.
  • It does not retag v0.3.0.
Open in Web Open in Cursor 

cursoragent and others added 8 commits August 26, 2026 23:26
…ion.

Five gates after the merged mix freeze: reproducibility and visibility pass;
Latin-1/literal-search, Mn/default-ignorable sanitizers, and single-detector
confirmation fail. Mix stays out of the public CLI. Do not retag v0.3.0.

Co-authored-by: Byte271 <byte271@users.noreply.github.com>
UTF-8 is the only product encoding; latin-1, ascii, and cp1252 are rejected.
Visible-projection search is the product search API. Assigned Unicode has no
stronger Priority-Zero invisible mechanism. Mean versus Weighted Mean on the
same GPT-2 adapter is HYPOTHESIS 0/192, not a second model. Mix stays out of
the public CLI.

Co-authored-by: Byte271 <byte271@users.noreply.github.com>
Cross-detector PASSes on Hugging Face nine-key GPT-2 Weighted Mean plus
Google synthid-text 30-key GPT-2. DistilGPT2 n=16 is HYPOTHESIS
second-model transfer, not confirmation-scale. Sanitizer still FAILs:
width-0 assigned insertions are Mn, Me, or Cf, and all 13 enclosing
marks change Chromium pre pixels. Mix stays out of the public CLI.

Co-authored-by: Byte271 <byte271@users.noreply.github.com>
Frozen H9 and closed-set hashes stay the CPython 3.12 snapshot. Live
scans on 3.11 and 3.13 still must find no stronger Priority-Zero
mechanism. Mix stays out of the public CLI.

Co-authored-by: Byte271 <byte271@users.noreply.github.com>
DEL and C1 except NEXT LINE survive the required sanitizers and keep
Chromium pre/textarea/contenteditable pixels. Independent seed 1100000
n=16 is control-mix 0/16 WM with identity 15/16. Mix sanitizer stays
FAIL. The public CLI stays empty.

Co-authored-by: Byte271 <byte271@users.noreply.github.com>
GitHub Actions Chromium rejected the full control-mix apply while one
research host matched. Do not treat that as a product visibility PASS.
Mix sanitizer stays FAIL. The public CLI stays empty.

Co-authored-by: Byte271 <byte271@users.noreply.github.com>
No measured Unicode-string family is simultaneously sanitizer-surviving,
Chromium-portable, ordinary plain text, and Priority-Zero safe. This is
a classification, not a Unicode re-scan. Mix sanitizer stays FAIL. The
public CLI stays empty.

Co-authored-by: Byte271 <byte271@users.noreply.github.com>
Mc, NFKC-stable Lm, designed blanks, Hangul filler sequences, and
font-metric empty glyphs were measured. None are simultaneously
sanitizer-surviving, Chromium-portable, ordinary plain text, and
Priority-Zero safe. Mix sanitizer stays FAIL. The public CLI stays empty.

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

coderabbitai Bot commented Aug 27, 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: 7000a2fa-78bf-4f7d-a4d8-ba1aaa922768


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.

@cursor
cursor Bot changed the base branch from cursor/cycle8-publishability-gates-2d93 to main August 27, 2026 02:58
cursoragent and others added 2 commits August 27, 2026 02:59
Co-authored-by: Byte271 <byte271@users.noreply.github.com>
Repository hygiene forbids comments and docstrings in Python files.

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

@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: 191422e0fd

ℹ️ 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".

"glyph": glyph_name,
"contours": contours,
"advance": int(advance),
"lsb": int(lsb),

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Distinguish composite glyphs from empty glyphs

When the font contains a composite TrueType glyph, numberOfContours is negative (normally -1), so this condition labels ordinary visible composite glyphs as empty. Those glyphs are then included in dejavu_empty_survivor_labels and the empty-glyph Chromium candidate buckets, corrupting the mechanism scan's font-metric results; classify only non-composite glyphs with exactly zero contours as empty.

Useful? React with 👍 / 👎.

Comment thread tools/h14_mechanism_scan.py Outdated
from collections import Counter
from pathlib import Path

from fontTools.ttLib import TTFont

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Declare FontTools for the mechanism scan

In a standard installation using either pip install -e . or pip install -e ".[dev]", this runner exits immediately with ModuleNotFoundError: No module named 'fontTools' because pyproject.toml declares no runtime dependencies and the dev extra contains only pytest. Add FontTools to an appropriate project/research extra or otherwise document and enforce the prerequisite so the committed H14 scan can be reproduced.

Useful? React with 👍 / 👎.

cursoragent and others added 2 commits August 27, 2026 03:09
Composite glyphs have numberOfContours == -1 and must not be labeled empty. FontTools stays a research extra, not a runtime dependency.

Co-authored-by: Byte271 <byte271@users.noreply.github.com>
Grapheme prepend and joining connectors survive the required sanitizers and change Chromium pixels. Hangul L plus V dies to NFC or NFKD. Bidi wraps and partial remainders collapse to Cf or H12. Mix sanitizer stays FAIL.

Co-authored-by: Byte271 <byte271@users.noreply.github.com>
@cursor cursor Bot changed the title Record H14 extended sanitizer classes without product authorization Record H14/H15 sanitizer research without product authorization Aug 27, 2026
@cursor

cursor Bot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Superseded by #106, which already contains this branch plus H16 and the Gate v2 preregistration. Closing so this experimental stack is not landed in numerical order.

@byte271 byte271 closed this Aug 27, 2026
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