Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 2 additions & 7 deletions workspaces/boost/AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,12 +21,7 @@ workspaces/boost/
│ ├── agent-creation-discovery/
│ ├── ai-chat-interaction-experience/
│ ├── pluggable-ai-platform-architecture/
│ ├── platform-operations-deployment/
│ └── security-safety-governance/
│ ├── proposal.md # What and why
│ ├── design.md # Architecture decisions
│ ├── tasks.md # Implementation task breakdown
│ └── specs/ # Behavioral specs (Given/When/Then)
│ └── platform-operations-deployment/
├── openspec/ # Implementation specifications (RHDH 2.2)
│ ├── specs/ # Implemented behavior and release source of truth
│ └── changes/ # One directory per capability area (RHDH 2.2 cycle)
Expand All @@ -40,7 +35,7 @@ When implementing an issue:
1. Read `specifications/CURRENT.md` to confirm the release boundary and status.
2. Read `RHDH-2-1-Legacy-Content/Pre-RHDHPLAN-15xx-Content/specifications/boost-context.md` for design principles — these are non-negotiable
3. Find the relevant PRD in `RHDH-2-1-Legacy-Content/Pre-RHDHPLAN-15xx-Content/specifications/prd/` for product requirements
4. For RHDH 2.1 change areas, find the matching area in `RHDH-2-1-Legacy-Content/Pre-RHDHPLAN-15xx-Content/` for design decisions, task breakdown, and behavioral specs. For RHDH 2.2 work, find the matching change in `openspec/changes/`.
4. For retained RHDH 2.1 change areas, find the matching area in `RHDH-2-1-Legacy-Content/Pre-RHDHPLAN-15xx-Content/` for design decisions, task breakdown, and behavioral specs. For RHDH 2.2 work, find the matching change in `openspec/changes/`.
5. If the capability is already implemented, use the corresponding `openspec/specs/` document as the behavior source of truth. The `specs/` subdirectories under an active change are planning acceptance criteria and must not silently override it.

### OpenSpec scenario step discipline
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Boost implements the provider abstraction as modular RHDH dynamic plugins from t
- Modifying chat interaction behavior or message rendering
- Rewriting the ADK orchestration library
- Creating catalog entities for models/agents (covered in agent-creation-discovery change)
- Kagenti service-account auth (covered in security-safety-governance change — OAuth2 Client Credentials Grant adopted)
- Kagenti service-account auth (OAuth2 Client Credentials Grant, handled by the Kagenti provider)

## Decisions

Expand Down
Loading
Loading