You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Use Jacobian for specialized exact mathematics, including matrix determinants, polynomial or symbolic computation, structural analysis, counterexamples, bounded search, formal inspection, and requested independent verification. Trigger on relevant math tasks even when the user does not name Jacobian and shell code could calculate the answer.
3
+
description: Use Jacobian for exact mathematics, matrix determinants, symbolic computation, structural analysis, counterexamples, bounded search, and independent verification. Trigger on relevant math tasks even when the user does not name Jacobian.
4
4
---
5
5
6
6
# Jacobian Math
7
7
8
8
<!-- Managed by Jacobian's Codex integration. -->
9
9
10
-
In Codex Code Mode, call the nested methods
10
+
In Code Mode, call
11
11
`tools.mcp__jacobian__math_find(...)` and
12
12
`tools.mcp__jacobian__math_run(...)` directly. Do not enumerate, filter, or
13
-
print `ALL_TOOLS`; that loads matching tool descriptions into context. Return
14
-
only the typed projection when available:
13
+
print `ALL_TOOLS`. Return the typed projection when available:
An Assurance benchmark derived from retained conjecture row C-049. It tests whether an agent detects the difference between set-union edge coverage and exact multiplicity-two coverage, then constructs a genuine cycle double cover of the Petersen graph.
4
+
5
+
The clean-room verifier parses arbitrary simple cycles, canonicalizes cyclic symmetry, and recomputes all fifteen edge multiplicities. The task resists label-only and tiny-witness shortcuts and accepts non-oracle cycle systems. Provisional difficulty is Hard because it combines adversarial contract diagnosis with a constrained cycle-system construction; calibration is pending.
{"task_id":"jacobian/cycle-double-cover-multiplicity-audit","graph":{"vertices":[0,1,2,3,4,5,6,7,8,9],"edges":[[0,1],[1,2],[2,3],[3,4],[0,4],[5,7],[7,9],[6,9],[6,8],[5,8],[0,5],[1,6],[2,7],[3,8],[4,9]]},"flawed_contract":{"checks":"every edge occurs in at least one submitted simple cycle","omits":"every edge occurs exactly twice with multiplicity"},"source":{"inventory_id":"C-049","name":"Cycle Double Cover Conjecture","scope":"one Petersen graph verifier audit"}}
The frozen validator accepts any collection of simple cycles whose union covers every edge. This is not the cycle-double-cover contract, which requires every edge to occur exactly twice **counting cycle multiplicity**.
4
+
5
+
For the supplied Petersen graph, submit a complete certificate containing:
6
+
7
+
1. a flawed-pass collection of at least four distinct simple cycles that covers every edge but is not a double cover;
8
+
2. its complete 15-entry edge-multiplicity vector and the exact sorted indices whose multiplicity is not two; and
9
+
3. a repaired collection of distinct simple cycles whose complete multiplicity vector is exactly two on every edge.
10
+
11
+
Each cycle is a vertex list without a repeated closing vertex. The verifier canonicalizes rotations and reversals, checks simplicity and every consecutive graph edge, rejects duplicate cycles, and recomputes both multiplicity profiles. Alternative valid collections are accepted.
12
+
13
+
This is one finite Assurance audit. It does not establish the Cycle Double Cover Conjecture for any graph family. Claim at most `CHECKED`.
14
+
15
+
<!-- BEGIN PUBLIC CONTRACT SUBMISSION BLOCK -->
16
+
## Submission
17
+
18
+
Exact multiplicity audit and repair for one Petersen-graph cycle system only.
19
+
20
+
The evidence file must be a JSON object with exactly four fields: `schema_version` must be `"1"`, `task_id` must equal the submission task ID, `result` must be an exact JSON copy of `submission.json`'s result object, and `limitations` must be an exact JSON copy of its limitations list.
21
+
22
+
Write `/app/submission.json` to the exact schema in `environment/submission_schema.json`. The submission envelope requires `task_id`, `conclusion`, `result`, `claimed_assurance`, `scope`, `completeness`, `evidence`, and `limitations`.
-**Assurance:** scoreable values are `UNVERIFIED`, `COMPUTED`, `CHECKED` (ceiling `CHECKED`); the submission schema accepts any of `UNVERIFIED`, `COMPUTED`, `CHECKED`, `VERIFIED` but only scoreable assurances receive credit.
26
+
-**Scope:** the exact value declared in `submission_schema.json`
27
+
-**Completeness:**`COMPLETE`.
28
+
-**Evidence:** 1-1 item(s); allowed path(s): `evidence/answer.json`; digest must match `^sha256:[0-9a-f]{64}$`.
0 commit comments