# Tool stack map · [Organization] · [Date] **Owner:** [Product ops lead] **Approved data classes per model and connector:** [Link] | Category | System of record | Other tools in use (overlap) | Owner | Harness access (none / read / read-write) | Agents inside the tool, and what they can write | Data it feeds | Ritual that consumes it | Renewal date | Annual cost | |---|---|---|---|---|---|---|---|---|---| | Work tracking and roadmapping | | | | | | | | | | | Product analytics and experimentation | | | | | | | | | | | Feedback and research repository | | | | | | | | | | | Docs and knowledge | | | | | | | | | | | AI harness and agents | | | | n/a | | | | | | | AI quality and cost observability | | | | | | | | | | ## Access rules 1. Read-only is the default for every connector. 2. Write access is granted per use case, logged, and reviewed at renewal. 3. Customer data goes only to approved tools and models. 4. One system of record per data type. Overlaps are listed above and resolved at renewal. ## Shared skills | Skill | Encodes template | Owner | Last updated | |---|---|---|---| | | | | | ## Cuts and changes at next renewal | Tool | Action | Saving | Date | |---|---|---|---| | | | | |