Earliest Preserved AI-Assisted DotTalk Work

Public history decision. Use August 2, 2025 as the earliest directly documented date of AI-assisted DotTalk development. Preserve July 21, 2025 as the earliest probable date, explicitly labeled as an inference.

Publication and evidence boundary

This page is the public web transcription of the supplied historical evidence record. That record was prepared from a preserved pyxbase.zip archive, archive-member metadata, cryptographic hashes, and connected mailbox records. The private messages and archive are not republished here.

The website build verifies this page's structure and publication safety. It does not independently authenticate private mailbox records or turn ZIP timestamps into forensic proof. The wording therefore remains deliberately narrow: earliest preserved evidence found, not the exact day the work began.

Executive finding

The formal conclusion is that AI-assisted work on the DotTalk lineage is evidenced by modernization artifacts dated July 21, 2025, with direct preserved project-specific AI material beginning August 2, 2025.

Evidence standard

Evidence chronology

Why July 21 remains probable

The earliest stored archive timestamps belong to these eight modernization artifacts:

• XBCMDS_modern.h
• XBINDEX_modern.h
• DOTTALK_modern.h
• XBASE_modern.c
• XBCMDS_modern.c
• XBINDEX_modern.c
• DOTTALK_modern.c
• TEST_modern.c

Their naming, coordinated scope, and 44-second production interval are consistent with automated or AI-assisted modernization. The files themselves do not name an AI system or prove the mechanism used. July 21 is therefore an important internal research date, but it is not the public single-date convention.

Why August 2 is direct

The 9:44:48 assistant record works directly with existing DotTalk/xBase architecture: AREA, SELECT, the global s[MAX_AREA] array, select_rec, and the continuing roles of initbase() and open_file(). It proposes a Python object model using DbfArea and DbfInstance.

At 10:00:52, gemini.txt continues the same work by assembling dbf_core.py, xbase_cli.py, and project documentation. Its filename provides the earliest preserved explicit model attribution found in the reviewed material.

Preservation record

Key artifact manifest

The timestamps below are the timezone-naive values stored in the ZIP central directory. Hashes are shown as recorded prefixes; the two directly discussed text artifacts retain their complete hashes below the table.

• new 1.txt SHA-256: ca07b351bb4fe50948049fbf786285da057af8a76b280c62f454840994628b7d
• gemini.txt SHA-256: 87c77ac42f2fa73c6215caae879a0797b78fd80f5eea8cd286d7bb79bef60035

Interpretation rules and limitations

1. ZIP timestamps preserve local wall-clock time with two-second precision, but they do not encode a timezone. The dates are more reliable than the timezone attribution.
2. File timestamps can survive copying or be changed. The mailbox evidence supplies an independent "existed no later than" bound, not cryptographic authentication of each internal timestamp.
3. The July 21 batch strongly suggests automation or AI assistance but does not identify a model or prove the mechanism.
4. new 1.txt is direct AI-style project output, but its model is unnamed. The later gemini.txt filename provides explicit model attribution.
5. This is the earliest evidence found in the reviewed material. An older archive, chat export, cloud revision, or message could move the documented date earlier.

Approved project-history wording

Full wording: AI-assisted work on the DotTalk lineage is evidenced by a rapid source-modernization batch dated July 21, 2025. Direct preserved AI transcript evidence begins August 2, 2025, when AI-generated material translated the existing AREA, SELECT, select_rec, and s[MAX_AREA] architecture into a Python object model; an explicitly named Gemini transcript followed minutes later.

Concise wording: Documented AI-assisted DotTalk development began by August 2, 2025, with probable modernization activity preserved from July 21, 2025.

Source register

Private message bodies and attachments remain outside this public page. The source register records their evidentiary role without exposing mailbox addresses or republishing private correspondence.