---
schema_version: 1
id: RAC-KTQ63DY90TXR
type: roadmap
---
# RAC v0.7.5 — Repository Index

## Context

Previous v0.7 releases introduced repository-level intelligence:

- Relationship metadata
- Relationship inspection
- Relationship validation
- Repository summaries

However, RAC capabilities still operate primarily as command executions over files and directories.

Future consumers such as:

- Explorer
- IDE integrations
- AI tools
- CI systems

require a consistent representation of repository contents.

Repository discovery should exist once in RAC Core rather than being recreated by every consumer.

---

## Outcomes

Introduce a repository index model that represents all known artifacts within a repository.

The repository index answers:

```text
What artifacts exist?

Where are they?

What type are they?

What metadata describes them?
```

---

## Initiatives

## Initiative 1 — Repository Index Model

Introduce:

```text
RepositoryIndex

ArtifactSummary
```

Example:

```json
{
  "artifacts": [
    {
      "id": "REQ-041",
      "type": "requirement",
      "title": "Payment Retry Logic",
      "path": "requirements/payment.md"
    }
  ]
}
```

---

## Initiative 2 — Artifact Discovery

Provide deterministic repository scanning.

Support:

- Requirements
- Decisions
- Roadmaps
- Prompts
- Designs

The index should provide artifact inventory without requiring full inspection.

---

## Initiative 3 — Metadata Extraction

Expose lightweight metadata:

- ID
- Artifact type
- Title
- Path
- Status
- Created date if available
- Updated date if available

---

## Initiative 4 — Machine Output

Expose through:

```bash
rac index
```

Support:

```bash
rac index --json
```

for consumers.

---

## Initiative 5 — Performance Foundation

Repository indexing should support future interactive usage.

Target:

```text
1000+ artifacts
```

without noticeable delay.

---

## Requirements

## REQ-001 — Core Ownership

Repository discovery shall belong to RAC Core.

Consumers shall not independently scan repositories.

---

## REQ-002 — Stable Artifact Identity

Every indexed artifact shall expose a stable identifier.

---

## REQ-003 — All Artifact Types

Indexing shall support:

- Requirement
- Decision
- Roadmap
- Prompt
- Design

---

## REQ-004 — Read Only

Indexing shall never modify repositories.

---

## Non Goals

- Relationship traversal
- Health scoring
- Validation
- Search ranking
- UI features

---

## Success Measures

Future consumers can build navigation experiences entirely from RAC Core.

Explorer can render a repository tree without parsing files itself.

CLI users can inspect repository structure directly.
