These documents define IDKMesh’s versioned data, evaluation, repository-graph, and project-configuration contracts. A status of experimental means the contract can gain a new version; it does not permit silently changing the meaning of an existing version.
Verification Provenance Integrity — binds WorkUnit, result, and verification objects with canonical digests.
idkmesh gate-audit CLI contract:
measures a verifier panel’s effective independent votes, correlation
structure, and seeded-probe breach rate from a verdict matrix; diagnostic
only, no acceptance authority.idkmesh gate-marginal diagnostic contract: measures what one additional
verifier changes for an already-selected panel under the exact same gate
rule, with explicit censoring/uncertainty and no routing authority.idkmesh gate-marginal-benchmark contract: freezes five design-only
verifier-selection rules and evaluates them on disjoint holdout rows without
emitting a production winner or routing decision.idkmesh gate-marginal-synthesis contract: aggregates a frozen set of
held-out benchmark reports descriptively across cohorts while refusing
duplicate evidence and emitting no strategy ranking or routing authority.EvaluatorPlan v0.4 Transition Semantics — requires both added and removed transition evidence.
schemas/idkmesh-api-error-v0.1.schema.json and schemas/idkmesh-list-v0.1.schema.json.Executor Admission v0.1 — readiness-checked atomic claims: the exact execution binding is derived and claimed in one operation, dispatch intent and submission revalidate the admission-time input snapshot, and changed upstream inputs fail closed. Local composition only; no dispatch, verification, acceptance or merge authority.
Coordination Preflight v0.1 — read-only exact-input prerequisite readiness, replay/descendant invalidation, declared-effort capability advice and critical-path estimates; reuses the connector resolver and grants no admission/dispatch authority.
Local Task Claims v0.1 — local SQLite atomic human/agent claims, immutable task limits, four deadlines, per-slot fencing and persistent unknown execution occupancy; no live provider or distributed ledger integration.
ScmRevisionBinding.verified=True only when the authorized repository/branch/revision matches independently observed SCM identity.When modifying a contract, update its schema, fixtures, implementation, and tests together. Introduce a new explicit version when behavior changes; keep old frozen evidence interpretable under its original meaning.