Files

Phillip Tarrant f5e6c59f2a docs(roadmap): add Ollama Cloud provider + backend switch as the next item

A laptop-dev enabler (planned, not specced): extend the proxy's M1 model-call
pipeline with an Ollama Cloud backend reachable via API key, plus a switch to
flip local-ollama <-> ollama-cloud, so AI works off the homelab.

Reconciles against §4: the API key and provider choice stay server-side in the
proxy (the client never holds a key, never picks the backend). The title
Settings-button "config file" splits — the client may hold only the proxy
base URL / profile (folds into M9); the provider/key switch is proxy config.

Filed under a renamed "Landed / planned out of band" section and pointed to
from the sequencing table as the next task before M5.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-15 05:27:04 -05:00

adr

docs: record editor-first UI-scene convention (ADR 0001)

2026-07-11 10:04:57 -05:00

schemas

refactor(contract)!: class_id -> calling_id, and the log gains race_id

2026-07-12 20:27:56 -05:00

superpowers

docs(m4c): implementation plan — title → creation → shell flow

2026-07-15 03:54:18 -05:00

canon-log.md

fix(creation-model): migrate stray class_id/allowed_classes copies

2026-07-12 20:58:49 -05:00

README.md

docs: traps.md — the bugs that passed a green suite

2026-07-12 21:07:39 -05:00

roadmap.md

docs(roadmap): add Ollama Cloud provider + backend switch as the next item

2026-07-15 05:27:04 -05:00

traps.md

fix(creation-screen): the white text, the badge on top of the roll, and a window too big for the laptop

2026-07-14 19:56:09 -05:00

README.md

/docs — cross-cutting docs

Anything affecting both client and api, plus planning and roadmap. Side-specific docs live in /api/docs and /client/docs.

Put here:

roadmap.md — phases, POC scope, what's next
traps.md — bugs we have already shipped, and the guards that catch them. Read before writing tests: every one of them passed a green suite.
adr/ — Architecture Decision Records
canon-log.md — the cross-boundary contract (§11)
Shared contracts — canon log schema, tag syntax, retry policy (§11, §12)
Anything spanning the HTTP boundary

The charter itself — CLAUDE.md — stays at the repo root. It is the source of truth; these docs elaborate, they do not override it.