TLAH Studio Documentation
July 27, 2026 ยท View on GitHub
This directory separates current operational guidance from historical design records. The code, automated tests, and current release metadata take precedence when an older plan conflicts with the product.
Current Guides
| Guide | Scope | Verified against |
|---|---|---|
| Architecture | Runtime, persistence, tool selection, research/artifacts, permissions, MCP, and updates | 4.15.0 |
| Development | Environment, commands, conventions, tool/workbench testing, and CI | 4.16.0 |
| Release and signing | Version sync, CI, Authenticode, manifest signing, and deployment | 4.16.0 |
| Privacy and data flows | Local storage, research endpoints, quality metrics, permissions, export, and deletion | 4.15.0 |
| 4.16 product surface identity | Empty states, presets, onboarding, installer/download art, asset pipeline | 4.16.0 |
| 4.14 tool intelligence | Release contract and acceptance gates for dynamic tools and the professional workbench | 4.14.0 |
| 4.15 immersive aquarium | Layered aquarium rendering, motion, accessibility, lifecycle, performance, and search reliability | 4.15.0 |
| Security policy | Supported versions and private reporting | Current stable |
| Contributing | Contribution workflow and quality gates | Current stable |
Roadmap
The following documents describe planned directions, not committed release dates or current capabilities:
Historical Design Records
These files explain how major systems evolved. They may contain completed checklists, old baselines, or implementation sketches and should not be used as current setup instructions.
| Record | Historical topic |
|---|---|
TLAH_3_0_AGENT_DEVELOPMENT_PLAN.md | Agent runtime extraction and initial GA plan |
TLAH_3_3_STABILITY_AND_TOOL_LIFECYCLE_PLAN.md | Tool lifecycle and safety pipeline |
TLAH_4_0_AGENT_PLATFORM_PLAN.md | Persistent tasks and platform services |
TLAH_4_1_1_TOOL_CAPABILITY_PLAN.md | File, code, and web tool expansion |
TLAH_4_8_PHASE0_FOUNDATION.md | 4.8 foundation work |
TLAH_4_9_PHASE1_AUTONOMY.md | Autonomy and permission model |
TLAH_4_9_4_UI_OVERHAUL.md | Earlier UI overhaul design |
TLAH_4_9_7_RELEASE_AUDIT.md | 4.9.7 release audit |
TLAH_4_9_8_RELEASE_AUDIT.md | 4.9.8 release audit |
Documentation Rules
- Use repository-relative paths and replace personal machine paths with placeholders.
- Put current behavior in the guides above; keep milestone narratives in historical records.
- State the version or commit used to verify technical claims.
- Update English and Chinese READMEs together when changing public product facts.
- Never place credentials, private keys, production SSH details, or user data in documentation.