An enterprise polyglot monorepo housing autonomous AI agent systems, AST knowledge graphs, real-time conversation observability, and engineering tools — governed by spec-driven development and navigable by both humans and AI companions.
Getting Started · Tool Catalog · Documentation · Roadmap · Contributing
PolyTuring is an enterprise monorepo for agentic engineering tools built with a first-principles approach to code quality, documentation, and lifecycle management:
- 🔧 Self-contained tools — Each tool lives in its own folder with everything it needs: source, tests, docs, spec, and lifecycle status
- 📋 Spec-driven development — No code without a specification. Every requirement is numbered, traced, and tested
- 🤖 Agent-native — Built for AI agents to autonomously navigate, build, test, and maintain tools using ReAct and Reflexion patterns
- 🌍 Polyglot — Rust, Go, Python, TypeScript, Node.js, Shell — whatever fits the problem
- 🔄 Full lifecycle — Every tool has an SDLC status: draft → spec-review → in-progress → testing → review → released
PolyTuring/
├── .agents/ 🧠 Agent rules, skills, and behavioral guidelines
├── .github/ ⚙️ CI/CD workflows, issue templates, CODEOWNERS
├── specs/ 📋 Specifications (SDD templates and active specs)
├── tools/ 🔧 The tools themselves (each is self-contained)
├── docs/ 📚 Documentation eBook, ADRs, how-to guides
├── sdlc/ 🔄 SDLC governance (roadmap, changelog, status board)
├── scripts/ 🛠️ Repo automation (scaffold, test, validate)
├── Makefile 🎯 Unified command interface
├── CONTRIBUTING.md 🤝 How to contribute
└── README.md 📍 You are here
# Clone
git clone https://github.com/vadde/PolyTuring.git
cd PolyTuring
# See what's available
make help
# Create your first tool
make new-tool NAME=my-awesome-tool
# Run all tests
make test
# View the SDLC dashboard
make statusSee the full catalog for details.
| Tool | Category | Language | Status | Description |
|---|---|---|---|---|
| omni-graph | GenAI & ML | Rust / React | in-progress v0.2.2 |
100% local semantic knowledge hub modeling codebases as AST graphs + vector embeddings with Ephemeral Branch Fabric and strict <1500 token Graph-RAG SLA. |
| session-explorer | GenAI & ML | Go / Bun | review v0.3.0 |
High-performance, single-binary conversation intelligence browser and real-time observability cockpit for agent coding transcripts. |
📖 Living Documentation Portal: https://vadde.github.io/PolyTuring/ · Or run make docs-serve locally.
The PolyTuring Book is a 9-chapter guide covering everything from getting started to advanced patterns:
| Chapter | Topic |
|---|---|
| 00 — Preface | Vision and design philosophy |
| 01 — Getting Started | Setup and first tool |
| 02 — Architecture | Repository structure |
| 03 — Tool Development | Building tools end-to-end |
| 04 — Spec-Driven Dev | SDD methodology |
| 05 — Agent Collaboration | AI agent workflows |
| 06 — CI/CD & Releases | Pipelines and releases |
| 07 — Advanced Patterns | GenAI, plugins, composition |
| 08 — Appendix | Glossary and references |
This repository is designed for autonomous AI agents. The Agent Intelligence Layer includes:
- 6 behavioral rules — ReAct protocol, code standards, commit conventions, SDD workflow, testing strategy, documentation standards
- 3 skills — New tool scaffolding, debugging, release preparation
- SDLC awareness — Agents check tool status before acting
- Divide & conquer — Complex problems decomposed into atomic sub-tasks
- Reflexion gates — Self-critique after every significant action
make help # Show all targets
make setup # Install pre-commit hooks
make new-tool NAME=x # Scaffold a new tool
make test # Test ALL tools
make test-tool T=name # Test a specific tool
make lint # Lint ALL tools
make lint-tool T=name # Lint a specific tool
make validate-specs # Validate all specs
make catalog # Regenerate tool catalog
make status # SDLC status dashboard
make clean # Clean artifacts1. Spec First → Write the spec before code
2. Scaffold → make new-tool NAME=my-tool
3. Implement → Write code in tools/my-tool/src/
4. Test → make test-tool T=my-tool
5. Document → Update README, examples, CHANGELOG
6. Review → Submit PR with SDD checklist
7. Release → Tag and publish
Key decisions are documented as Architecture Decision Records:
| ADR | Decision |
|---|---|
| ADR-001 | Monorepo over multi-repo |
We welcome contributions! See CONTRIBUTING.md for the full guide. Quick version:
- Fork and clone
- Create a feature branch:
feat/tool-name/description - Write a spec in
specs/catalog/ - Implement with tests
- Submit a PR with the SDD checklist
MIT — Use freely, build boldly.
Built with ❤️ and rigorous engineering discipline.