# Build Log

This file records chronological Atlas build and infrastructure milestones. Do not fabricate dates, command output, validation results, or operator names.

## Entries

### Date

2026-07-10

### Phase

Phase 2A.

### Objective

Create the shared installation framework, system-discovery tooling, and host-validation conventions used by later Atlas installation scripts.

### Changes

- Added shared Bash installer libraries under `install/lib/`.
- Added `install/bootstrap.sh` as a read-only Phase 2A scaffold.
- Added baseline command manifest under `install/manifests/`.
- Added system discovery tooling under `scripts/system/`.
- Added host validation tooling under `scripts/system/`.
- Documented runtime directories for logs, reports, and future state.
- Documented free-space validation thresholds for `/`, `/srv`, and `/sql`.
- No .NET, SQL Server, nginx, or Docker installation was started.

### Validation

- Bash syntax validation passed for all Phase 2A shell scripts.
- `install/bootstrap.sh --help`, `--version`, and `--dry-run` passed.
- `scripts/system/discover-system.sh` passed in human-readable and JSON modes.
- Discovery JSON parsed successfully with `jq`.
- `scripts/system/validate-host.sh` passed with no required failures.
- Controlled failure-path tests returned the expected validation and usage exit codes.
- Generated logs and reports were written outside the repository.

### Problems

- No unresolved Phase 2A implementation problems recorded.

### Decisions

- Installer logs use `/var/log/atlas/install/`.
- Generated reports use `/var/log/atlas/reports/`.
- Future persistent installer state and marker files use `/var/lib/atlas/`.
- Phase 2A does not create speculative future component installer scripts.

### Git Commit

Not yet committed.

### Operator

Codex.

### Date

Not recorded.

### Phase

Baseline server preparation before Phase 1 repository completion.

### Objective

Prepare Atlas as a dedicated AI development server with storage, network, SSH, Git, Gitea access, Codex CLI, and standard development utilities.

### Changes

- Ubuntu 26.04 LTS installed.
- Hostname set to `atlas`.
- Static IP configured as `192.168.10.10`.
- OS SSD configured with full-disk LVM.
- OS logical volume expanded to use available LVM capacity.
- SQL SSD mounted at `/sql`.
- Development SSD mounted at `/srv`.
- SSH access configured.
- Gitea SSH authentication configured.
- Git installed.
- Git LFS installed.
- Node.js installed.
- Standard development utilities installed.
- Codex CLI installed and authenticated.
- Codex full-access mode configured with no approval prompts.
- Passwordless sudo configured for the dedicated development user.
- Infrastructure repository created and cloned at `/srv/repos/AI-Development-Server`.

### Validation

- Server identity and storage were later inspected during Phase 1 planning.
- Repository remote was later inspected during Phase 1 planning.
- Original command output was not captured in this repository.

### Problems

- No baseline problems were recorded in this repository.

### Decisions

- Atlas will use this repository as the authoritative infrastructure and operations source.
- Atlas will be rebuilt over time through documented, version-controlled, idempotent automation.

### Git Commit

Not yet committed.

### Operator

TODO: Confirm during the relevant implementation phase.

## Entry Template

Copy this template for future entries.

```markdown
### Date

YYYY-MM-DD

### Phase

Phase name or number.

### Objective

What this work was intended to achieve.

### Changes

- Change made.

### Validation

- Validation performed.

### Problems

- Problem encountered, or `None recorded.`

### Decisions

- Decision made, or `None recorded.`

### Git Commit

Commit hash, or `Not yet committed.`

### Operator

Name or role.
```