Start here for quick project understanding. These files bridge business and technical domains.
.opencode/context/project-intelligence/
├── navigation.md # This file - quick overview
├── business-domain.md # Business context and problem statement
├── technical-domain.md # Stack, architecture, technical decisions
├── business-tech-bridge.md # How business needs map to solutions
├── decisions-log.md # Major decisions with rationale
└── living-notes.md # Active issues, debt, open questions
| What You Need | File | Description |
|---|---|---|
| Understand the "why" | business-domain.md |
Problem, users, value proposition |
| Understand the "how" | technical-domain.md |
Stack, architecture, integrations |
| See the connection | business-tech-bridge.md |
Business → technical mapping |
| Know the context | decisions-log.md |
Why decisions were made |
| Current state | living-notes.md |
Active issues and open questions |
| All of the above | Read all files in order | Full project intelligence |
New Team Member / Agent:
navigation.md (this file)Quick Reference:
business-domain.mdtechnical-domain.mddecisions-log.mdThis folder is referenced from:
.opencode/context/core/standards/project-intelligence.md (standards and patterns).opencode/context/core/system/context-guide.md (context loading)See .opencode/context/core/context-system.md for the broader context architecture.
Keep this folder current:
living-notes.md regularlyManagement Guide: See .opencode/context/core/standards/project-intelligence-management.md for complete lifecycle management including:
See .opencode/context/core/standards/project-intelligence.md for the standard itself.