Information for contributors to the SPaDE project is at present somewhat disorganized and incomplete.

Initially the project is a collaboration between the repository owner (Roger Jones) and AI tools, primarily GitHub Copilot and Grok Build.

SPaDE is primarily philosophical and architectural in nature, and I therefore would expect that any humans who are persuaded by the rhetoric (or the technical content!) are likely to create their own projects buying in to the articulated SPaDE architecture, and hence contributing to a broader ecosystem. Nevertheless, in the event that others wished to contribute to SPaDE itself, it is recommended that in the first instance they clone the GitHub SPaDE repo and submit contributions through pull requests. In that case, they should acquaint themselves with the standards, procedures, methods and skills documented in the docs/admin directory.

Working practice is indexed from that directory. The following are a useful start:

• Roles, Responsibilities, Tasks
• Workflows
• Collaboration Guidelines
• Guidance for AI Contributions
• Working practice (Grok vs Copilot)
• Branches, worktrees, and sessions
• GitHub-scheduled Copilot; container tests
• Independent review of Grok-authored PRs
• Instructions for Copilot

I encourage anyone interested in contributing to consider starting their own related project developing agents to supply specialist services in the network of agents which is envisaged, but they may nevertheless wish to engage with SPaDE itself to influence the nature of that network. If there are no better guidelines and suggestions available by then a first contribution might be to offer some.