sheng 0.1.0

Register-resident refutation sieves for regex. Builds Hartmanis-Stearns SP-quotients of a pattern's automaton small enough to live in a SIMD register, and uses them to prove a document match-free before a real engine ever walks it. Sound by construction: a sieve may pass a non-matching document, never reject a matching one.
Documentation
# Code of Conduct

## Our Pledge

We pledge to make our community welcoming, safe, and equitable for all.

We are committed to fostering an environment that respects and promotes the
dignity, rights, and contributions of all individuals, regardless of
characteristics including race, ethnicity, caste, color, age, physical
characteristics, neurodiversity, disability, sex or gender, gender identity or
expression, sexual orientation, language, philosophy or religion, national or
social origin, socio-economic position, level of education, or other status.
The same privileges of participation are extended to everyone who participates
in good faith and in accordance with this Covenant.

## Encouraged Behaviors

While acknowledging differences in social norms, we all strive to meet our
community's expectations for positive behavior. We also understand that our
words and actions may be interpreted differently than we intend based on
culture, background, or native language.

With these considerations in mind, we agree to behave mindfully toward each
other and act in ways that center our shared values, including:

1. Respecting the purpose of our community, our activities, and our ways of
   gathering.
2. Engaging kindly and honestly with others.
3. Respecting different viewpoints and experiences.
4. Taking responsibility for our actions and contributions.
5. Gracefully giving and accepting constructive feedback.
6. Committing to repairing harm when it occurs.
7. Behaving in other ways that promote and sustain the well-being of our
   community.

## Restricted Behaviors

We agree to restrict the following behaviors in our community. Instances,
threats, and promotion of these behaviors are violations of this Code of
Conduct.

1. **Harassment.** Violating explicitly expressed boundaries or engaging in
   unnecessary personal attention after any clear request to stop.
2. **Character attacks.** Making insulting, demeaning, or pejorative comments
   directed at a community member or group of people.
3. **Stereotyping or discrimination.** Characterizing anyone's personality or
   behavior on the basis of immutable identities or traits.
4. **Sexualization.** Behaving in a way that would generally be considered
   inappropriately intimate in the context or purpose of the community.
5. **Violating confidentiality.** Sharing or acting on someone's personal or
   private information without their permission.
6. **Endangerment.** Causing, encouraging, or threatening violence or other
   harm toward any person or group.
7. Behaving in other ways that threaten the well-being of our community.

### Other Restrictions

1. **Misleading identity.** Impersonating someone else for any reason, or
   pretending to be someone else to evade enforcement actions.
2. **Failing to credit sources.** Not properly crediting the sources of content
   you contribute. This project is, of all of them, the one that should care
   most: `provenance` exists to answer "where did this text come from?", and a
   tool that attributes other people's writing for a living has no business
   being careless about attributing other people's work.
   [`NOTICE`]NOTICE records that nothing third-party is bundled here and
   points at the packages underneath, whose notices carry what they do bundle.
   A contribution that lifts someone else's work without saying so is a defect,
   not a shortcut.
3. **Promotional materials.** Sharing marketing or other commercial content in
   a way that is outside the norms of the community.
4. **Irresponsible communication.** Failing to responsibly present content
   which includes, links or describes any other restricted behaviors.

## Reporting an Issue

Tensions can occur between community members even when they are trying their
best to collaborate. Not every conflict represents a code of conduct violation,
and this Code of Conduct reinforces encouraged behaviors and norms that can help
avoid conflicts and minimize harm.

When an incident does occur, it is important to report it promptly. To report a
possible violation, email **<griffin@billylives.com>**, which reaches the
maintainer directly and privately. This project is small enough that the person
reading your report is the person who can act on it.

Include what happened, where (issue, pull request, discussion, or elsewhere),
and links if the exchange is public. You do not have to have decided whether it
"counts" before you write; deciding that is our job, not yours.

We take reports seriously and will respond as promptly as we can. We will
investigate, reviewing messages and logs or speaking with the people involved,
and we will keep investigation and enforcement as transparent as we can while
prioritizing safety and confidentiality. Enforcement actions are carried out in
private with the involved parties; communicating something to the whole project
may be part of a mutually agreed resolution.

A technical security vulnerability is a different channel with a different
clock. Do not report one here - see [`SECURITY.md`](SECURITY.md).

## Addressing and Repairing Harm

If an investigation finds that this Code of Conduct has been violated, the
following ladder guides how harm gets repaired, based on the incident's impact
on the people involved and on the project as a whole. Depending on the severity
of a violation, lower rungs may be skipped.

1. **Warning**
   - _Event:_ A violation involving a single incident or series of incidents.
   - _Consequence:_ A private, written warning from the maintainers.
   - _Repair:_ A private written apology, acknowledgement of responsibility, and
     seeking clarification on expectations.
2. **Temporarily limited activities**
   - _Event:_ A repeated incidence of a violation that previously resulted in a
     warning, or the first incidence of a more serious violation.
   - _Consequence:_ A private, written warning with a time-limited cooldown
     period, which may be limited to particular channels or to interactions with
     particular people.
   - _Repair:_ Making an apology, using the cooldown period to reflect on
     actions and impact, and being thoughtful about re-entering shared spaces
     after the period is over.
3. **Temporary suspension**
   - _Event:_ A pattern of repeated violation that warnings have failed to
     address, or a single serious violation.
   - _Consequence:_ A private written warning with conditions for return.
   - _Repair:_ Respecting the spirit of the suspension, meeting the specified
     conditions for return, and being thoughtful about reintegrating.
4. **Permanent ban**
   - _Event:_ A pattern of repeated violations that other steps on the ladder
     have failed to resolve, or a violation so serious that there is no way to
     keep the community safe with this person in it.
   - _Consequence:_ Access to all project spaces, tools, and communication
     channels is removed. Permanent bans should be rare, should have strong
     reasoning behind them, and should only be reached after other remedies have
     failed.
   - _Repair:_ There is no possible repair in cases of this severity.

This ladder is a guideline. It does not limit the maintainers' discretion and
judgment, in keeping with the best interests of the project.

## Scope

This Code of Conduct applies within all project spaces - the repository, its
issues, pull requests, discussions, and any chat or event held under the
project's name - and also applies when an individual is officially representing
the project in public or other spaces.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 3.0, permanently available at
<https://www.contributor-covenant.org/version/3/0/>.

Contributor Covenant is stewarded by the Organization for Ethical Source and
licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).

For answers to common questions, see the
[FAQ](https://www.contributor-covenant.org/faq); translations are available at
<https://www.contributor-covenant.org/translations>. The enforcement ladder was
inspired by the work of Mozilla's code of conduct team.

[homepage]: https://www.contributor-covenant.org