Skip to content

docs(decisions): record ADR-100 desktop capture product; corpus setup guidance intent#320

Merged
tcballard merged 2 commits into
mainfrom
claude/rac-core-delivery-roadmap-k97szy
Jul 5, 2026
Merged

docs(decisions): record ADR-100 desktop capture product; corpus setup guidance intent#320
tcballard merged 2 commits into
mainfrom
claude/rac-core-delivery-roadmap-k97szy

Conversation

@tcballard

@tcballard tcballard commented Jul 5, 2026

Copy link
Copy Markdown
Collaborator

Summary

Two corpus artifacts, no engine change:

  1. ADR-100: Start the Desktop Capture Product — Cross-Platform Tauri Overlay (rac/decisions/adr-100-desktop-capture-product.md, Proposed / Product). Ratifies the gate recorded in rac/roadmaps/future/lore-overlay.md ("gated on the decision to start a desktop product"): the desktop capture host is a committed product direction, aimed at non-technical knowledge owners who will not author through MCP servers, harnesses, or agents in Slack.
  2. Corpus Setup and Structuring Guidance (rac/roadmaps/future/corpus-setup-guidance.md, Planned, unscheduled). Records the adoption gap observed at large-organisation scale: inconsistent corpus setup and the mega-doc-of-decisions anti-pattern, with two initiatives — an opinionated setup/structuring guide, and a documented mega-doc split path via rac ingest (ADR-006).

Key choices in ADR-100 (for review)

  • Tauri v2, cross-platform from the outset — macOS + Windows both first-class in the initial release cycle (not macOS-first-then-Windows); Linux stays deferred per the roadmap's non-goals.
  • Admin-provisioned deployment — an administrator configures gateway, GitHub App, and target repo once (ADR-088 profile pattern); the author-facing surface is hotkey → interview → fidelity confirmation only.
  • Own repository, slug rac-overlay per ADR-092 naming; Lore brand at org/marketplace level; "overlay" stays a working title.
  • Two-gate model unchanged — the app proposes draft PRs only, never approves/merges (ADR-077, ADR-065); engine stays AI-free (ADR-002).

The corpus-setup-guidance item deliberately commits documentation only; the candidate doctor advisory (mega-doc detection) is named but fenced behind its own future decision.

Verification

  • rac validate rac/ — 389 artifacts, 0 invalid, exit 0
  • rac relationships rac/ --validate — 2,308 checked, 0 issues, exit 0
  • rac review rac/ — no priority 1–2 findings

After merge

tcballard added 2 commits July 5, 2026 09:26
…e-overlay]

Ratifies the gate recorded in rac/roadmaps/future/lore-overlay.md: the
desktop capture host is a committed product direction. Tauri v2,
cross-platform from the outset (macOS + Windows first-class, Linux
deferred); admin-provisioned deployment for non-technical authors;
own repository (rac-overlay per ADR-092); two-gate write model
unchanged (ADR-077, ADR-065).
…tup-guidance]

Implements rac/roadmaps/future/corpus-setup-guidance.md.

Records the observed adoption gap: inconsistent corpus setup at
organisation scale and the mega-doc-of-decisions anti-pattern, with
two initiatives — an opinionated setup/structuring guide and a
documented mega-doc split path via rac ingest (ADR-006).
@tcballard
tcballard merged commit 6f8de33 into main Jul 5, 2026
9 checks passed
@tcballard
tcballard deleted the claude/rac-core-delivery-roadmap-k97szy branch July 5, 2026 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant