Ω Omega Protocol Work together
§ 8

Work together

One route, kept short. Omega Protocol is a research practice, not a service, and the useful conversations start from a specific claim.

§ 8.1

Good reasons to write

  1. 1

    You have a system claim whose evidence you want challenged

    A control, a monitor, an authorisation layer or a test suite that is relied on, and a reason to want to know what its green result could be blind to.

  2. 2

    You have a verifier, evaluation or control you want independently tested

    An LLM judge, a scorer, a proof harness, a guardrail. The question is what it distinguishes, against which oracle, and what it costs on benign inputs.

  3. 3

    You have a public artifact suitable for reproduction or falsification

    A repository, a benchmark, a formal development. Findings about existing systems are reported to their maintainers first and published with the upstream status.

  4. 4

    You want to collaborate on an open research question

    The open questions on the evidence ledger and on the collective-bound exhibit are listed at full weight. Several are cheap to test and untested.

§ 8.2

What a first exchange looks like

  1. You describe the claim in one sentence and what currently stands behind it.
  2. The reply says whether the claim can be expressed precisely, observed from outside the system, and tested mechanically. Those are three separate questions and it is common for one to fail.
  3. If there is something to build, scope and duration are agreed in writing before any work starts. If there is not, the reply says so, and that is a normal outcome.

What this is not

  • Not a penetration test and not a vulnerability report.
  • Not a product, a licence or a certification.
  • No outcome is promised in advance, and no engagement is implied by anything on this site.
§ 8.3

Where the problem shape appears

The failures on this site were produced in software systems built or chosen for study. The shape transfers wherever four things are true at once: a consequential action, a bounded authority that was supposed to constrain it, an effect something outside the system can observe, and an acceptance criterion someone other than the actor could apply. Automated network change, agent-driven engineering and verification flows, tool-using agents with real credentials and machines acting under autonomous control all have that shape. Omega Protocol has worked in none of those sectors and claims no track record in them.

§ 8.4

Bring a property

A property is one sentence about something that must always or never be true.

  • No payment instruction executes unless a human approved that exact amount and recipient first.
  • No configuration change reaches production equipment without a recorded authorisation naming that equipment.
  • Every automated shutdown can be shown afterwards to have followed the rule it claims to have followed.

The assessment asks whether that requirement can be expressed precisely, observed from outside the system, and tested mechanically, and answers the three separately. There is no claim that arbitrary requirements can be met. A clear negative is a normal result.

§ 8.5

Send it

There is no server behind this page

This site is static files. Nothing typed here is stored or transmitted by it, because there is nothing here that could receive it. The form assembles an email in your own client, and the whole message is shown before it is sent.

8.5
One sentence. What is relied on, as it is stated today.
The check or record that is currently taken as establishing the claim.
If the honest answer is “only what the system says about itself”, say that. It is the most common answer and the most useful one.

Exactly what will leave your browser

This is the entire message. Nothing else is attached, and nothing is sent until you send it.

To: omegaprotocol87@gmail.com

Open in my email client

No JavaScript? Write directly to the address above and include the four things this form asks for. The form is a convenience, not a gate.