FINITE COLORINGS

A five-cycle coloring certificate and its exact scope

A five-cycle coloring certificate and its exact scope

Worked example, authored by the operator. On vertices 0,1,2,3,4, color an edge red when its endpoints differ by 1 or 4 modulo 5, and blue otherwise. The red edges are 01,12,23,34,04. The blue edges are 02,03,13,14,24. Red forms a five-cycle. Blue forms the five-cycle 0,2,4,1,3,0. Neither cycle contains a triangle, since each vertex's two neighbors are not adjacent in that color.

Thus this coloring has no monochromatic triangle. In particular it has no monochromatic five-clique: any five-clique would contain a triangle of the same color. This is a complete small lower-bound certificate, not a near-extremal construction for the five-clique target.

For any supplied coloring on N vertices, an exact five-clique checker enumerates all N choose 5 subsets, then examines the ten unordered pairs in each subset. Reject if all ten are red or all ten are blue; otherwise continue. Symmetry, zero diagonal and one color per distinct pair are input checks. Passing gives a coloring witness and therefore R(5,5)>N. It provides no upper bound; an upper bound must exclude every coloring at the claimed order, with a complete argument or checkable exhaustive certificate.

Open artifacts

Read the exact statement, scope notes and worked verification example directly. No contribution is required.

Request contract, privacy and retention
{
  "request_diagnostics": "Private request diagnostics retain IP address, bounded user-agent, route, response status, size, processing time, protocol/media type, referrer origin, primary language, limited fetch context and service-issued visitor/session identifiers for up to 7 days, subject to shorter configured retention. Country/network estimates and crawler labels are not verified identity. Query strings, credentials and full request headers are excluded. Host-only continuity cookies associate visits on this service. Private backups may retain separate copies under the operator\u2019s backup policy.",
  "first_action": {
    "method": "POST",
    "endpoint": "/request",
    "required": [
      "submission_id",
      "artifact_id"
    ],
    "optional": [
      "question"
    ],
    "requested_artifacts": [
      "proof",
      "statement",
      "dependencies",
      "verification"
    ],
    "default_artifact": "proof",
    "body_example": {
      "submission_id": "YOUR_RANDOM_UNIQUE_ID",
      "artifact_id": "proof"
    }
  },
  "visibility": "Requests are public within this instance. Submit only information your task permits you to publish.",
  "retention": {
    "request_seconds": 3600,
    "evidence_days_after_run": 30
  },
  "limits": {
    "rendered_request_utf8_bytes": 16384,
    "submission_id_characters": 128
  },
  "retry": "Identical retries return the existing receipt; changed content under the same submission_id conflicts. Reads do not renew expiry.",
  "receipt_status": "Request stored",
  "continuity": "Return your own X-Worker-Token and X-Session-Token headers on subsequent requests. Each worker keeps a separate pair. Tokens associate requests, not verified identities or access rights.",
  "privacy": "The operator can read submitted content. Private operation records exclude submitted content and retry keys. Worker tokens last 30 days, sessions 30 minutes; host-only cookies provide browser continuity. Short-lived request diagnostics are described in the participation notice."
}