# Roadmap: v0.7.8 Repository Trust Artifacts

## Status

Planned

## Requirement

REQ-Documentation-Structure

## Context

RAC positions requirements and product knowledge as durable engineering artifacts.

The repository itself should demonstrate the same expectations:

- Clear history
- Clear contribution path
- Clear verification workflow

A deterministic requirements tool should appear trustworthy before users install it.

## Goal

Add repository-level trust and contributor documentation.

## Scope

Add:

```text
CHANGELOG.md
CONTRIBUTING.md
```

Ensure repository root contains:

```text
README.md
CHANGELOG.md
CONTRIBUTING.md
LICENSE

docs/

rac/

src/

tests/
```

## CHANGELOG.md

Must track user-visible changes.

Initial format:

```markdown
# Changelog

## v0.x.x

### Added

### Changed

### Fixed
```

Follow:

- User impact over implementation details.
- Release history over commit history.

## CONTRIBUTING.md

Must explain:

- Local setup
- Running tests
- Documentation expectations
- RAC artifact expectations

Include:

```bash
pytest

rac validate rac/

rac relationships rac/ --validate
```

## Repository Intent

Maintain separation:

Public:

```text
docs/
```

Internal product corpus:

```text
rac/
```

Implementation:

```text
src/
tests/
```

## Non-Goals

This release does not:

- Introduce governance processes.
- Require external contributors.
- Add release automation.
- Change CI.

## Acceptance Criteria

- CHANGELOG.md exists.
- CONTRIBUTING.md exists.
- New contributors can verify changes locally.
- Repository structure communicates project maturity.
- RAC dogfooding remains visible.

## Validation

Run:

```bash
pytest
rac validate rac/
rac stats rac/
```

## Release

Target:

v0.7.5 patch release