---
schema_version: 1
id: RAC-KTQ63DYWAWNW
type: roadmap
---
# RAC v0.9.0 — Explorer Foundation

## Problem

RAC Core now exposes repository intelligence through stable services and repository models.

The CLI provides powerful automation, but users still need to understand:

- Which commands exist
- Which artifact to inspect
- How repository information connects
- Which areas require attention

A terminal-native workspace is required to make repository knowledge discoverable.

---

## Outcomes

Introduce RAC Explorer:

```bash
rac explorer
```

Explorer shall provide:

- Repository overview
- Artifact navigation
- Artifact inspection
- Relationship exploration
- Search-driven workflows

while remaining a consumer of RAC Core.

Explorer shall feel closer to:

- Claude Code
- Amp
- Lazygit
- k9s

than a traditional dashboard.

---

## Initiatives

## Initiative 1 — Textual Application Foundation

Introduce a Textual-based TUI.

Architecture:

```text
RAC Core

↓

Explorer Adapter

↓

Textual UI
```

---

## Initiative 2 — Explorer Adapter Layer

Introduce a dedicated boundary between RAC Core and Textual.

The adapter shall:

- Invoke RAC services
- Translate Core models into UI state
- Own no repository intelligence
- Prevent widgets directly depending on Core internals

---

## Initiative 3 — Non-Blocking Execution Model

Explorer shall never execute expensive Core operations directly in UI handlers.

Operations such as:

- Repository loading
- Validation
- Relationship analysis
- Portfolio calculation

shall execute through Textual workers.

---

## Initiative 4 — Repository Home

Provide a landing experience.

Example:

```text
RAC Explorer

Health 92%

Attention

2 broken relationships
1 incomplete artifact
```

---

## Initiative 5 — Artifact Browser

Support browsing:

- Requirements
- Decisions
- Roadmaps
- Prompts
- Designs

---

## Initiative 6 — Artifact Context View

Display:

- Metadata
- Validation state
- Completeness
- Relationships
- Diagnostics

---

## Initiative 7 — Relationship Navigation

Allow users to navigate connected artifacts.

---

## Initiative 8 — Slash Command Surface

Introduce:

```text
/
```

as the universal interaction model.

Examples:

```text
/open req-001

/find payments

/health
```

All actions shall use a single command registry.

---

## Initiative 9 — Error Handling

Core failures shall surface as recoverable Explorer states.

Failures shall not crash the interface.

---

## Requirements

### REQ-001 — Consumer Architecture

Explorer shall consume Core services only.

---

### REQ-002 — Terminal Native

Explorer shall operate entirely within a terminal.

---

### REQ-003 — Keyboard First

All functionality shall work without mouse input.

---

### REQ-004 — Responsive

Explorer shall support repositories containing at least:

```text
1000 artifacts
```

---

### REQ-005 — Terminal Compatibility

Explorer shall support:

- Common terminals
- Limited colour environments
- Remote sessions

Meaning shall never depend on colour alone.

---

### REQ-006 — Tested Interface

Explorer shall include:

- Adapter tests
- Screen tests
- Core isolation tests

---

## Non Goals

- Artifact editing
- AI assistant
- Repository hosting

---

## Success Measures

- Users can browse, inspect, and navigate relationships across a repository entirely within the terminal.
- Explorer remains responsive on repositories of at least 1000 artifacts.

---

## Related Artifacts

- ADR-015 Explorer as Core Consumer
- ADR-016 Explorer Adapter Boundary
- Design: Explorer Terminal Experience
- Design: Explorer Visual System