Research tools / Implementation atlas

Inside the Mind Guild.

Explore the code behind our experiments. Follow an architecture, trace the perception pipeline, or find the file where an idea becomes an implementation.

Source snapshot13 Nov 2026a3bd514Mind-Guild / Mind_Guild
A map of the implementation

One repository. Distinct research tracks.

Select a module to see its purpose and source files.

BenchmarksS3Q Layer 1Supporting tools
MODULE DEPENDENCIESarrow = imports → dependency
Solid edges aggregate static Python imports. Dashed edges include explicit file loaders. Test edges appear when selected.
Also in the repository
01 / Separate execution paths

Benchmarks and reference runtime

The classic agent/environment experiments and the packaged Layer 1 runtime coexist in this repository. Their shared research goals do not imply an end-to-end integration.

Explore the implementation framework
02 / Scientific status

Implemented is a starting point

The recorded recipe has reproducibility evidence; full Layer 1 acceptance remains false. Allocation requirements and authoritative source verification remain open in the inspected snapshot.

Read the verification record
03 / Scope and method

A source-linked snapshot

Counts come from tracked files, excluding bytecode and editor metadata. Import links are static dependencies, including optional branches. The diagram maps code organization, not evidence of consciousness.

From a hypothesis to a protocol
About this map and its source links

The architecture and flow annotations were reviewed against the source at the displayed commit. Higher S3Q layers are outside this implementation map. GitHub source links require permission to the implementation repository. This page is a static snapshot; it does not poll GitHub or execute experiments.

Test-file counts describe inventory and do not report a test run. The file explorer includes tracked scratch experiments and retained evidence, labeled by module.