Spec Design System — Orcha
Reference

Spec Design System

Living style guide for orcha specsUpdated 2026-05-09

Spec sections

  1. Header — title, status badge, date, owner
  2. Problem
  3. Goals & non-goals
  4. Approach
  5. Design
  6. Open questions
  7. References

Color

bg
#fafaf9
surface
#ffffff
rule
#e7e5e4
muted
#78716c
text
#1c1917
accent-light
#fef3c7
accent
#b45309
accent-tint
#fde6d8
accent-dark
#7c2d12

Typography

DisplayInbound email triageserif 32/1.18/700
SectionApproach comparisonsans 11/—/600
HeadingBypass for known sendersserif 19/1.35/700
BodyThe classifier rejects 4% of legitimate vendor invoices.sans 16/1.65/400
Meta2026-05-09 · Daniel · specsans 13/1.5/400
Code(known-sender? email)mono 13/1.55/400

Spacing

4
8
12
16
24
32
48
64

Status badges

Draft In review Approved Archived

Callouts

Note

Background information that's useful but optional.

Decision

A choice the author is making explicit. Searchable: future readers grep for "Decision".

Warning

Something that has bitten us before. Use sparingly — over-warning blunts the signal.

Tables

QueueConcurrencyMax retries
document-input43
document-ocr25
document-output83
 Plain reference table.
OptionEffortRiskReversible?
Retrain classifierHighMediumYes
Bypass for known sendersLowLowYes (flag)
Two-pass triageMediumMediumPartial
 Decision matrix — recommended row uses tr.recommended.

Code

Manual syntax tags inline: kw, str, num, fn, com, lang-tag.

clojure;; bypass check
(defn known-sender? [email]
  (contains? @trusted-domains
             (:from-domain email)))

Diagrams

Inline SVG only. Wrap in <figure> with a <figcaption>.

SES Triage worker Document queue raw email accepted
Figure caption sits below in muted italic.

Pros & cons

Pros

  • Lowest implementation cost
  • Reversible behind a flag
  • No model retraining

Cons

  • Doesn't fix unknown legitimate senders
  • Manual list maintenance