IDKMesh · library

Everything, by category

204 documents and contracts, grouped by what kind of truth they are. Every entry links to the file in the repository — the canonical source. This page is a map, not a copy: nothing here restates a contract, so it cannot silently disagree with one.

Start here 8 Foundations, vision and principles 14 Architecture 26 Contracts and specifications 16 Schemas 33 Research programmes 32 Findings 20 Audits 12 Decisions and process 23 Community and the ACE stack 13 Interoperability and security 7
How to read a disagreement

When two documents appear to conflict, prefer the more specific current contract over an older plan or a historical record. A conversation, an old roadmap section, or a historical architecture sketch is evidence about how the project evolved — it does not override current schemas, current architecture, or a later accepted decision. The full hierarchy is in the documentation map.

Start here 8 documents

What a newcomer needs, in roughly the order it becomes useful. None of these assume you have read the others.

Foundations, vision and principles 14 documents

What the project is for, what it refuses to do, and the mathematical and scientific ground it stands on. These change slowly and deliberately.

Read the curated index for this section ↗ — it says which documents are current contracts and which are retained history.

Architecture 26 documents

The as-built system: subsystems, trust boundaries, compute fabric, evidence machinery, and the repository’s own self-observation. Retained historical designs are kept alongside the active ones and marked as such in the index.

Read the curated index for this section ↗ — it says which documents are current contracts and which are retained history.

Contracts and specifications 16 documents

The machine-readable truth. When a written document and a schema disagree, the schema is the contract. Versioning rules are in the schema index.

Read the curated index for this section ↗ — it says which documents are current contracts and which are retained history.

Schemas 33 documents

Every JSON Schema in the tree. These are what the harness validates against, and what an external implementation has to satisfy.

Read the curated index for this section ↗ — it says which documents are current contracts and which are retained history.

Research programmes 32 documents

Executable research plans, experiment interpretations, calibration evidence, and the preregistrations. Results are evidence for bounded claims — never automatic policy changes.

Read the curated index for this section ↗ — it says which documents are current contracts and which are retained history.

Findings 20 documents

Research and engineering findings, plus retained source notes. Some are historical support for a later decision rather than current implementation documentation; the index separates the two.

Read the curated index for this section ↗ — it says which documents are current contracts and which are retained history.

Audits 12 documents

Bounded review snapshots, each read against the baseline revision it declares. They stay useful after their findings are resolved because they preserve what was inspected and why a decision changed.

Read the curated index for this section ↗ — it says which documents are current contracts and which are retained history.

Decisions and process 23 documents

Durable decisions and the processes that produce them: architecture decision records, the improvement-proposal process, repository-wide operating rules, and the staged evidence gates.

Read the curated index for this section ↗ — it says which documents are current contracts and which are retained history.

Community and the ACE stack 13 documents

Growth strategy, capacity and metabolism models, and the layered ACE control stack with its bounded experiments — measured without Goodharting activity counts.

Read the curated index for this section ↗ — it says which documents are current contracts and which are retained history.

Interoperability and security 7 documents

The adapter boundary that lets external agent frameworks participate without redefining the WorkUnit semantic core — and the threat model for the privileged workflows.

Code, simulations and executable surfaces

The parts you run rather than read. Every experiment is deterministic given its seed, and every result artifact below was produced by a module in this list.

experiments/

Experiment definitions E011–E042, the contract harness, the two-attempt orchestrator, patch verifiers, and the evidence-report tooling.

sim/

Deterministic simulation and analysis modules — the code behind the matched-budget, goal-geometry and verifier-panel experiments.

randomness_lab/

The R1–R4 scheduling, scaling and dependence labs, runnable as python -m randomness_lab.

interop/

Protocol-neutral worker adapters, A2A/MCP bindings, identity binding, and SDK conformance helpers — with their own test suite.

idkmesh/

The installable package: the idkmesh CLI and its gate-audit command. The only part of the tree that ships.

tools/

IDKGraph repository modelling, link integrity, the observatory, the closing-keyword guard, branch-convergence auditing, and the evidence gates.

schemas/

The JSON Schemas themselves, versioned. Machine-readable protocol truth.

examples/

Worked inputs for every contract: work units, evaluator plans, compute offers, domain packs, gate-audit panels, routing replays.

tests/

The suite the PR gate runs, including the deliberately-broken fixtures that prove the guards actually fail closed.

results/ · benchmarks/

Committed result artifacts and benchmark cohorts, so a published number can be checked against the run that produced it.

config/ · state/

Policies and controller state, kept in the tree so a decision made by a controller is inspectable after the fact.

Project memory

Records kept as evidence about how the project evolved, rather than as navigation destinations. Category-level discoverability is deliberately sufficient here — the project does not manufacture an inbound link per archival record to reduce a warning counter.

Conversations

An append-only, curated index of substantive project conversations, required by PROJECT_RULES.md. Conclusions that matter are promoted out of here into architecture, decisions, research or governance.

Evidence artifacts

Retained evidence where a subsystem needs a durable evidence surface of its own.

Documentation map

The curated authority map: which source wins for which question, and the evidence ladder every artifact sits on.

Keep going

Run something in 15 minutes → How it works Experiment atlas Four pipelines