Business Plan Migration to GitHub and Knowledge Syncing
Summary
This process documents the transition of the Sokrates business plan and core project documentation from manual file uploads to a version-controlled GitHub repository. It outlines the integration of the GitHub connector with the AI’s project environment and the specific indexing behaviors observed during the migration.
Details
The migration was initiated to ensure that the Sokrates business plan—previously managed as manual uploads—is subject to proper version control. The documentation was moved to the RationallyPrime/Sokrates-AI repository, specifically within the docs/business-plan/ directory.
Infrastructure and Access
Regardless of the source (manual upload or GitHub sync), project files are mounted within the AI’s environment at /mnt/project/ as read-only markdown files. The AI accesses this information using two primary tools:
project_knowledge_search: Used for semantic indexing and retrieval across the project corpus.view: Used for reading the specific content of individual files.
The AI environment treats synced files and manually uploaded files identically once they are mounted. The primary advantage of the GitHub integration is the elimination of “stale” documentation that occurs when local edits are not manually re-uploaded to the platform.
Syncing and Indexing Behavior
During the migration, a specific set of files was tracked to verify the success of the GitHub connector:
- Initial State: The environment contained seven files, including research reports, executive summaries, a cold pitch document, and
PROJECT-STATE-UPDATED.md. - Target State: The full business plan suite, including
01-core-deliverable-stack.md, individual files for Sections 1 through 6, and a combinedSections_7-10.md.
Observations during the sync process revealed that the GitHub connector requires an indexing period before files become available to the AI. The platform displays an “Indexing” status in the sidebar during this time. Furthermore, because project files are typically mounted at the initiation of a conversation session, a fresh chat session is often required to reflect the updated file list once indexing is complete. At the time of the migration, the business plan sections occupied approximately 9% of the project’s knowledge capacity.
File Structure
The business plan is organized into specific sections to facilitate modular updates:
docs/business-plan/01-core-deliverable-stack.mddocs/business-plan/Section_1.mdthroughSection_6.mddocs/business-plan/Sections_7-10.md