docs(core): refine project intelligence system and deprecate legacy context (#93 )

* feat(context): Add project intelligence system

- Add project-intelligence.md standard (what & why)
- Add project-intelligence-management.md guide (how to manage)
- Add project-intelligence/ folder with 6 context files:
  - navigation.md (quick overview & routes)
  - business-domain.md (business context, users, value)
  - technical-domain.md (stack, architecture, decisions)
  - business-tech-bridge.md (business → technical mapping)
  - decisions-log.md (decision history with context)
  - living-notes.md (active issues, debt, questions)
- Update standards navigation with new entries
- Register all new contexts in registry.json

This enables projects to document and maintain business + technical
context for quick onboarding and lasting project understanding.

* fix(registry): Add project-intelligence to profiles

- Add context:project-intelligence/* to developer, business, full, and advanced profiles
- Ensures project intelligence contexts are included when these profiles are selected

This complements commit c731328 which added the context entries.

* docs(core): refine project intelligence system and deprecate legacy context

2026-01-13 11:25:18 +00:00

3.1 KiB

Raw Blame History

Project Intelligence

What: Living documentation that bridges business domain and technical implementation. Why: Quick project understanding and onboarding for developers, agents, and stakeholders. Where: .opencode/context/project-intelligence/ (dedicated folder)

Quick Reference

What You Need	File	Description
Understand the "why"	`business-domain.md`	Problem, users, value
Understand the "how"	`technical-domain.md`	Stack, architecture
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, debt, questions

Why This Exists

Projects fail when:

Business intent is lost in code
Technical decisions aren't documented with context
New members spend weeks instead of hours understanding the project
Context lives only in people's heads (who leave)

This ensures business and technical domains speak the same language.

Structure

.opencode/context/
├── project-intelligence/              # Project-specific context
│   ├── navigation.md                  # Quick overview & routes
│   ├── business-domain.md             # Business context, problems solved
│   ├── technical-domain.md            # Stack, architecture, decisions
│   ├── business-tech-bridge.md        # How business needs → solutions
│   ├── decisions-log.md               # Decisions with rationale
│   └── living-notes.md                # Active issues, technical debt
└── core/                              # Universal standards

Onboarding Checklist

For new team members or agents:

Read navigation.md (this file)
Read business-domain.md to understand the "why"
Read technical-domain.md to understand the "how"
Review business-tech-bridge.md to see the connection
Check decisions-log.md for context on key choices
Review living-notes.md for current state
Explore codebase with this context loaded

How to Keep This Alive

Trigger	Action
Business direction shifts	Update `business-domain.md`
New technical decision	Add to `decisions-log.md`
New issues or debt	Update `living-notes.md`
Feature launch	Update `business-tech-bridge.md`
Stack changes	Update `technical-domain.md`

Full Management Guide: See .opencode/context/core/standards/project-intelligence-management.md

Integration with Context System

Lazy Loading: Load project intelligence first when joining a project
Layering: Then load standards and specific context as needed
Reference: See .opencode/context/core/context-system.md for system overview

Management Guide: .opencode/context/core/standards/project-intelligence-management.md
Context System: .opencode/context/core/context-system.md
Standards Index: .opencode/context/core/standards/navigation.md

3.1 KiB Raw Blame History