ABOUT / CYONTHECT LAB

Independent by design.
Interdisciplinary by curiosity.

Cyonthect Lab is a personal software development and research initiative. It brings practical AI tools, psychology-oriented workflows and computational neuroscience experiments into one evolving body of work.

CYONTHECT / EXPLORATION FIELDFIG. 00
Conceptual diagram

THE INITIATIVE

A place for ideas
to meet implementation.

The name describes a way of working: follow a question across disciplines, translate it into a system and inspect what the system can actually do.

This is independently developed work, not an incorporated company, a funded institutional laboratory or an organization with a staff. The projects are presented with their current maturity and limitations.

The connection between them is methodological. Each asks how complex systems can become more understandable through tools, explicit workflows or carefully bounded experiments.

WORKING PRINCIPLES

Make the work legible.

Useful before impressive

Start with a concrete task or a research question. The interface and system should help explain it.

Boundaries are part of the design

Permissions, privacy and the limits of a scientific claim belong in the work from the beginning.

Progress without overstatement

Describe what exists today, keep goals separate and let evidence carry the claim.

DEVELOPMENT NOTES

A history with visible sources.

Selected records, with their evidence level stated. Dates describe development work, not legal incorporation.

  1. The first software work begins

    The owner dates the beginning of the first software project to June. This is development history, not a company incorporation date.

    Owner-provided history
  2. An available repository record

    The earliest available Pevrai commit in the inspected local history is dated 6 September. It does not establish when the earlier work began.

    Git history · commit 1d826c5
  3. Connectome provenance is documented

    The MaleCNS v1.0 pipeline document records source validation, identifier mapping and processing assumptions.

    Dated connectome pipeline documentation
  4. Desktop development priorities are reviewed

    Pevrai’s maintenance plan separates packaging acceptance, diagnostics and interface consistency from new features.

    Dated maintenance plan

No reliable dated milestone history was supplied for the psychology prototype. Its current capabilities are documented without assigning speculative completion dates.