Testosterone docs

Design notes for Testosterone (testo-core, CLI testo). New here? Getting Started adds it to your project in about five minutes. For the design, start with ARCHITECTURE.md and README.md.

The notes are plain markdown. They open as an Obsidian vault, and are published as a searchable site at https://taltal-beep.github.io/testosterone/docs/. Dated plans, audits and phase checklists from earlier development are in the Archive.

Architecture

• System Diagram: the architecture picture, what each part does, and where every other diagram lives
• Architecture Overview: component flowchart, modules, engine, adapters, artifact layout, persistence
• Deep Dive - Execution Logic: session init, the subprocess loop, teardown

Using the CLI

• Getting Started: install, write testosterone.yaml, run a cycle, see what changed, run it in GitHub Actions
• Setup Prompts: copy-paste prompts for an AI assistant to install Testosterone in your project, write testosterone.yaml, add CI and open the UI
• Command Reference: every testo command, flag and exit code, and the testosterone.yaml schema
• Troubleshooting and Error Codes: exit codes, NDJSON errors, debugging playbook

Testing and CI

• QA Strategies: how runs are defined, triggered, logged, and how the orchestrator tests itself
• CI-CD Pipeline Setup: GitHub Action, GitLab template, runner image, test tiers
• E2E Harness Operations Guide: the external E2E harness
• GitLab Pages Demo: the GitHub and GitLab Pages demo pipeline

Releasing

• Publishing to PyPI · Publishing Docker Images · Publishing to Artifactory
• Changelog policy

Decisions and direction

• Specs & ADRs: design decisions that still describe the code
• Product Roadmap: current state and next steps
• Technical Debt Tracker: open backlog
• Agent Context Guide: which note to read before changing what (for AI coding agents)

The vault itself

• Vault schema: frontmatter, linking and the ingest / query / lint rules for these notes
• Vault log: record of changes to the vault's structure