Administrative Documentation
There is at the moment considerable overlap and conflict among these documents as my tentative steps in seeking working methods in a rapidly changing environment are recorded.
I therefore hope for this to be greatly simplified, and many of these documents to be retired, but do not expect this to happen quickly because establishing working methods takes time!
Meanwhile the documentation falls into the following categories:
Methods and standards
- amms001.md Project Structure and Documentation Policy (including: subsystem-specific architecture/design/implementation in the subsystem directory;
docs/ only for whole-system or cross-subsystem material)
amms002.md Roles, Responsibilities, Tasks
- amms003.md Workflows
- amms004.md Collaborative Guidelines
- amms005.md Guidance for AI Contributions
- amms006.md Glossary Link Maintenance
- amms007.md Glossary Augmentation Procedure (historic, pro-tem)
amms008.md LLM Wiki, in progress and not authoritative
amms009.md Agentic development team: roles and where work is written
- amms010.md DGX Spark software baseline
amms011.md First local role cards: project manager, architect, philosopher
- amms012.md Method for Writing ProofPower HOL Specifications
- amms013.md Proposal: Structured Project Data for SPaDE Repositories
Process or procedure descriptions
- ampd001.md GitHub-scheduled Copilot agent; tests in the SPaDE container
- ampd002.md Process for Copilot completing code and test assignments
ampd003.md Conversational Documentation Development Procedure
- ampd004.md Task branches, worktrees, and sessions
- ampd005.md Independent review of pull requests into
main; later LLM-evaluation questions
- ampd007.md Glossary Augmentation Procedure
- ampd008.md Copilot Delegation Procedure with Task Documents
- ampd009.md Commissioning work on the Spark: local agents, cloud models, review, GitHub Issues
- ampd010.md Local agent task execution
- ampd011.md Task Assignment Procedure for Local LLMs
- ampd012.md Procedure for Writing Specifications in ProofPower HOL
Plans and strategies
Testing and evaluation
Not yet a method. Questions about evaluating SPaDE as a tool for LLMs (MCP clients, frozen prompts, independence from the authoring agent) are listed at the end of ampd005.md.
Task Descriptions
- amtd000.md Admin Meta-Task-Description
- amtd001.md Task Description for Review of Hyperlinks in Project Documentation
- amtd002.md Task Description for Linking Project Documentation to the SPaDE Glossary
- amtd003.md Task Description for Augmentation of the SPaDE Glossary
- amtd004.md Task Description for Implementation of Glossary Automation Scripts
- amtd005.md Task Description — Execute Glossary Augmentation Process
- amtd006.md - Task Description for an interactive ProofPower session (
pp-step)
Chat Logs
amcl001.md Chat Log: Conversational Documentation Development Procedure
- amcl002.md Grok web discussion links formerly listed under
drafts/
- amcl003.md Session record: agentic team on the DGX Spark
Code and Scripts
- amcd001.py - Script for adding glossary links to documentation
- Dynamically loads terms from glossary
- Supports incremental operation with
--since parameter
- Generates review reports
- Handles file filtering and dry-run mode
- amcd002.py - Script for extracting terms from glossary
- Parses glossary file to extract all terms and anchors
- Outputs in multiple formats (python, json, text)
- Handles term variations and compound terms
- Used by amcd001.py for dynamic term loading
- amcd003.py - Script for discovering potential glossary terms
- Scans documentation for technical terminology
- Filters by frequency and importance
- Outputs candidate terms with usage contexts
- Supports glossary augmentation workflow
- amcd004.py - Python interface to an interactive theorem prover (e.g., ProofPower) (coded by Gemini 3 Pro)