# BobNet OS Full Rebuild Packet - Start Here

This packet is for a Codex instance that needs to build BobNet OS from source or recreate the product from a clean Windows/.NET workspace. The short bootstrap page is enough to compile an existing checkout. This packet is the larger build room manual: what the system is, what must exist, how the pieces fit, which contracts cannot drift, and which test loop proves each slice.

## Product Target

BobNet OS is a Windows desktop command center for Codex work. It combines:

- A durable kanban board backed by SQLite.
- Agent/profile assignment for cards.
- Codex worker execution with run folders, logs, events, and result handoff JSON.
- Review, blocked, done, archive, comments, attachments, dependency, and evidence flows.
- A dispatcher that can claim ready work and run workers without manual button pushing.
- An office-space view that shows agent status.
- A main chat surface where a local model can plan board/card actions and the host validates, previews, confirms, and executes them.
- Optional local CLI, local API, and local MCP surfaces for scripts and external tools.

The core design rule is simple: the model may propose; BobNet OS validates and executes. Free-form model text must never mutate the board directly.

## Minimum Repository Shape

A complete source package should contain at least:

```text
BobNetOS.sln
BrianCodexHarness/
  BrianCodexHarness.csproj
  Domain/
  Services/
  Ui/
BrianCodexHarness.Tests/
scripts/
  build-bobnetos-release.ps1
  smoke-bobnetos.ps1
  install-bobnetos-shortcut.ps1
  register-bobnetos-dispatch-loop.ps1
codex-bootstrap/
research/
README.md
BOBNETOS_SMOKE_TEST.md
```

The current implementation still has some internal type names that begin with `CodeBoard...`. Treat those as implementation names unless the owner explicitly asks for a deep internal rename. The public product, executable, docs, scripts, data file, and UI should say BobNet OS.

## How Another Codex Should Use This Packet

1. Read this file first.
2. Read `01-PRODUCT-AND-SYSTEM-SPEC.md` to understand the product surface.
3. Read `02-ARCHITECTURE-DATA-CONTRACTS.md` before touching persistence or worker protocol.
4. Read `03-IMPLEMENTATION-SLICES-AND-TEST-LOOPS.md` and implement in order.
5. Read `04-CHAT-ORCHESTRATOR-HARNESS.md` before modifying chat.
6. Read `05-ACCEPTANCE-AND-OPERATIONS.md` before claiming completion.
7. Use `CODEX_REBUILD_FROM_ZERO_GOAL.md` as the `/goal` prompt if the task is to build or reconstruct the whole system.

## Non-Negotiable Gates

Do not claim BobNet OS is built until these pass:

```powershell
dotnet restore BobNetOS.sln
dotnet build BobNetOS.sln -c Release --no-restore
dotnet test BobNetOS.sln -c Release --no-build
powershell -ExecutionPolicy Bypass -File scripts\build-bobnetos-release.ps1
powershell -ExecutionPolicy Bypass -File scripts\smoke-bobnetos.ps1
```

Expected executable:

```text
BrianCodexHarness\bin\Release\net8.0-windows\win-x64\publish\BobNetOS.exe
```

## Rebuild Priorities

If starting with an empty project, build in this order:

1. WinForms shell and board layout.
2. SQLite kernel and board/card CRUD.
3. Events, comments, dependencies, and runs.
4. Worker result protocol and prompt builder.
5. Manual Codex run path.
6. Dispatcher claim/run/retry loop.
7. Review and evidence workflows.
8. Agent profiles and office view.
9. Local CLI/API/MCP surfaces.
10. Chat planning harness.
11. Automation/notifications/hooks.
12. Release scripts, smoke tests, and hosted bootstrap docs.

Do not start with the chat. The chat is only useful once the board kernel can safely validate and execute action proposals.