Architecture Decision Records — frontend-core¶
ADRs recorded in this spoke, in MADR v4.0 format. The hub
(nickpclarke/AgentArmy) owns the canonical ARC-ADR-### registry; the records here are
spoke-authored drafts that either (a) capture a frontend-core-specific decision, or
(b) mirror a hub ADR ID referenced by the CopilotKit epic (#12) but not yet published, so the
issue links resolve. They are pending hub ratification.
| ID | Title | Status | Scope |
|---|---|---|---|
| ARC-ADR-002 | JWT-forwarding auth contract (FE → MC → BE) | Proposed | Mirrors hub ID (ref. #13) |
| ARC-ADR-003 | No LLM key in browser — Empty adapter boundary | Proposed | Mirrors hub ID (ref. #13) |
| ARC-ADR-006 | HITL confirmation for destructive operations | Proposed | Mirrors hub ID (ref. #17) |
| ARC-ADR-007 | Migrate frontend-core from Vite+Svelte to Next.js | Proposed | frontend-core decision |
Context¶
These records back the CopilotKit generative-UI epic (#12). ARC-ADR-007 is the anchor: it makes explicit the epic's unstated prerequisite — frontend-core is Vite+Svelte today, but the epic assumes a Next.js App Router app. The other three record the cross-cutting contracts the migrated app must implement (JWT forwarding, no-LLM-key boundary, destructive-op HITL).
Hub references: - Published example: ARC-ADR-001 — HITL decision-point pattern - Hub plan: CopilotKit generative UI
Numbering caveat.
007is chosen as the next ID after the highest referenced (006);004/005may exist in the hub registry and were not verifiable from this spoke. Confirm against the hub before upstreaming.