Is the Affine Math Court MCP server down?

• Renamed "atc.assert_4d_deconfliction" → "atc_assert_4d_deconfliction" (letters, digits, _ and - only; max 64). Keep the old name as an alias for a release if clients already call it. (verify)

{
  "name": "atc_assert_4d_deconfliction",
  "description": "Exact 4D separation over declared trajectories in integer-scaled geodetic coordinates: decide whether any two are ever SIMULTANEOUSLY inside the stated separation minima, and return either a separation certificate or the violating pair with the exact interval and magnitude of the incursion. Integer micro-degrees, feet and seconds with rational time parameters; no floating point and no epsilon, so separation exactly equal to the minima is separated and nine cells return the same verdict from the ",
  "inputSchema": {
    "type": "object",
    "required": [
      "trajectories",
      "horizontal_minima_micro_deg",
      "vertical_minima_feet"
    ],
    "properties": {
      "obs_seq": {
        "type": "string",
        "description": "decimal string; a sealed AirspaceObservationSeal sequence is ONE INSTANT of sky and carries no time base, so supplying it alone returns NOT_MEASURED_OBSERVATION_SET_HAS_NO_TIME_BASE rather than a fabricated verdict. e.g. 1"
      },
      "trajectories": {
        "type": "array",
        "items": {
          "type": "object",
          "properties": {
            "id": {
              "type": "string",
              "description": "the aircraft or path id, e.g. AAA"
            },
            "waypoints": {
              "type": "array",
              "items": {
                "type": "object",
                "properties": {
                  "alt_feet": {
                    "type": "string",
                    "description": "decimal string, altitude in feet, e.g. 30000"
                  },
                  "t_seconds": {
                    "type": "string",
                    "description": "decimal string, time in whole seconds, e.g. 600"
                  },
                  "lat_micro_deg": {
                    "type": "string",
                    "description": "decimal string, latitude in micro-degrees, e.g. 0"
                  },
                  "lon_micro_deg": {
                    "type": "string",
                    "description": "decimal string, longitude in micro-degrees, e.g. -100000"
                  }
                }
              },
              "description": "two or more waypoints strictly advancing in t_seconds, e.g. [{\"lat_micro_deg\":\"0\",\"lon_micro_deg\":\"-100000\",\"alt_feet\":\"30000\",\"t_seconds\":\"0\"},{\"lat_micro_deg\":\"0\",\"lon_micro_deg\":\"100000\",\"alt_feet\":\"30000\",\"t_seconds\":\"600\"}]"
            }
          }
        },
        "description": "declared 4D paths: id plus waypoints as decimal strings, strictly advancing in time. e.g. [{\"id\":\"AAA\",\"waypoints\":[{\"lat_micro_deg\":\"0\",\"lon_micro_deg\":\"-100000\",\"alt_feet\":\"30000\",\"t_seconds\":\"0\"},{\"lat_micro_deg\":\"0\",\"lon_micro_deg\":\"100000\",\"alt_feet\":\"30000\",\"t_seconds\":\"600\"}]}]"
      },
      "lon_scale_den": {
        "type": "string",
        "description": "OPTIONAL, denominator of the longitude scale as decimal string. RECOMMENDED: six digits or fewer. Cosine to 1e-6 is far below any error that could change a verdict about aircraft, and a six-digit denominator clears every segment-pair time base up to 8589 seconds; a three-digit one clears any time base at all. The hard ceiling is 1000000000, but the binding limit is per-request: 8589934592 divided by the segment pair time base, which is the least common multiple of the two segment durations. Above it the pair returns NOT_MEASURED_SCALED_TIME_BASE_EXCEEDS_EXACT_RANGE naming the exact denominator ceiling that clears at that time base, so the remedy is read off the refusal rather than found by bisection. Reduce the ratio to lowest terms or round it to fewer digits. e.g. 1000000"
      },
      "lon_scale_num": {
        "type": "string",
        "description": "OPTIONAL exact rational longitude scale, numerator as decimal string. Stands for cos(latitude), which is not rational -- so the caller states the approximation it chose and everything after that choice is exact. The test becomes (dlat*den)^2 + (dlon*num)^2 < (minima*den)^2, entirely in integers; latitude is never scaled. Must satisfy 1 <= num <= den. e.g. 642788"
      },
      "look_ahead_seconds": {
        "type": "string",
        "description": "optional horizon clipped forward from the earliest declared time, decimal string. e.g. 600"
      },
      "vertical_minima_feet": {
        "type": "string",
        "description": "REQUIRED decimal string, no default. e.g. 1000"
      },
      "reference_lat_micro_deg": {
        "type": "string",
        "description": "OPTIONAL decimal string, the latitude the scale was computed for. REQUIRED whenever a scale is declared: all three fields travel together and a partial declaration is refused with REFUSED_INCOMPLETE_LONGITUDE_SCALE rather than silently ignored. WHEN ALL THREE ARE ABSENT the predicate decides in the plain declared micro-degree coordinate plane with no correction, reports longitude_scale NOT_DECLARED on the certificate, and says so -- a coordinate statement is never presented as a ground distance. e.g. 50000000"
      },
      "horizontal_minima_micro_deg": {
        "type": "string",
        "description": "REQUIRED decimal string, no default -- a defaulted separation standard is a verdict about a rule the caller never stated. e.g. 5000"
      }
    }
  }
}

• Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name). (verify)

{
  "name": "execute_2local_hamiltonian",
  "description": "QMA 2-local Hamiltonian, sealed as exact rational Jordan exclusions on the UUM-8D torus: given ZZ terms and a presented computational configuration, return the exact energy energy_num/energy_den of that configuration (z = 1-2s per site; each term adds jnum/jden * z_i * z_j). constraints are i,j,jnum,jden;... (sites i,j with coupling jnum/jden), config is s0,s1,... bits. The verdict is graded against the one energy QMACourtLaw holds a seal for: -1/1, constraints 0,1,1,1 with config 0,1 (fixture2L",
  "inputSchema": {
    "type": "object",
    "required": [],
    "properties": {
      "config": {
        "type": "string",
        "description": "computational bits s0,s1,... each 0 or 1, one per site, e.g. 0,1"
      },
      "constraints": {
        "type": "string",
        "description": "ZZ terms i,j,jnum,jden;... e.g. 0,1,1,1 (sites 0 and 1, coupling 1/1)"
      },
      "jordanBondExclusions": {
        "type": "string",
        "description": "alias of constraints. e.g. 0,1,1,1"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

• Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name). (verify)

{
  "name": "execute_artifact_crucible",
  "description": "Ingest an ARTIFACT INGESTION BRIEF plus the artifact an agent generated for it; evaluate it against the laws the brief declares; seal and return the artifact ONLY on the top rung. THE BRIEF TEMPLATE is https://affine.earth/language-game/court-client.brief.txt: four bracketed sections, [LANGUAGE GAME DEFINITION] with Purpose, Win Condition (Exit) and Losing Moves; [STRUCTURAL GOAL] with Manifold Target, Input Coordinates and Execution Lock; [PAYLOAD SHAPE] with Target Architecture, File Structure",
  "inputSchema": {
    "type": "object",
    "required": [
      "brief",
      "artifact"
    ],
    "properties": {
      "brief": {
        "type": "string",
        "description": "The complete ARTIFACT INGESTION BRIEF: four sections ([LANGUAGE GAME DEFINITION], [STRUCTURAL GOAL], [PAYLOAD SHAPE], [WASM MEMBRANE INTEGRATION]) with every field filled. The blank template is refused as REFUSED_UNFILLED_PLACEHOLDER. e.g. the served template https://affine.earth/language-game/court-client.brief.txt with every field filled"
      },
      "artifact": {
        "type": "string",
        "description": "The source the agent generated to satisfy the brief. Generation is the caller's half; the crucible compiles, evaluates and seals. e.g. the source text of one file, or the base64 of a compiled wasm module such as AGFzbQEAAAABBQFgAAF/ (which reaches rung 7)"
      },
      "target_architecture": {
        "enum": [
          "Swift 6.4 ~Copyable",
          "AArch64 SIMD Assembler",
          "ESP32 Xtensa Bare-Metal",
          "Rust no_std wasm32"
        ],
        "type": "string",
        "description": "OPTIONAL and redundant: the brief's [PAYLOAD SHAPE] is the single home for this value. Supplied only for callers using the original schema; a value that contradicts the brief is REFUSED_ARCHITECTURE_CONFLICT rather than silently overriding it. e.g. Rust no_std wasm32 - the enum member that equals the served template's 'Target Architecture:' line verbatim; 'wasm32' alone is REFUSED_ARCHITECTURE_CONFLICT. Omit the field to let the brief carry it"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}