Design system · monotykamary × linear × editorial web

Claim → geometry

Every figure is one argument rendered as geometry. Grayscale, hairline-framed, mono-captioned, with a single coral accent on the point. Hover the figures; they respond.

1. Write the claim in one sentence — it becomes the caption. 2. Name the claim's structure (spectrum? ranking? sequence? mutual causation? branch? transformation?). 3. That structure picks the geometry. 4. Put coral on the one element that is the point. 5. Motion only if it demonstrates the argument.

The six below are the method applied — not a fixed menu. The last two show it generalizing to new shapes.

Worked examples · the method applied

Structure: spectrum · Autonomy isn't binary; the useful position slides.

More oversightMore delegation
01CompleteHuman decides every move
02SuggestAI proposes local changes
03PairShared iteration loop
04DelegateAI executes bounded work
05RoamAI owns the trajectory
Throwaway prototypeMove deliberately, not permanently →Production system
The useful position is contextual: autonomy moves with blast radius, expertise, and feedback quality.

Structure: ranked magnitudes · Developers avoid high-stakes AI work; trust is low.

0 25 50 75 100 Avoid deployment / monitoring76% Reject professional vibe coding72% Avoid AI project planning69% Cite almost-right output66% Express high trust2.6%
Selected developer-survey figures cited in this analysis · share of respondents

Structure: sequence with a threshold · Nothing bills until work crosses the boundary.

01ComposeMeasured locally
02QueueStaged, not billed
03InvokeTokens + tool time
04DeliverOutcome lands
05CommitReceipt changes
Nothing becomes billable until the work crosses the delivery boundary.

Structure: mutual causation · Evidence sharpens judgment; judgment ranks evidence.

Technical loop
ContextActionTestsRepairEvidence
Human loop
ObserveQuestionReviewLearnJudgment
Calibration
Agent evidence sharpens human judgment; human judgment decides which evidence matters.

Structure: branch under uncertainty · Preserve inspectable conditions, not a transcript.

OBSERVED STATEVERIFIEDUNKNOWNRECOMPUTEREUSEQUERYDEFER
A recursive evaluation tree preserves inspectable conditions at every branch instead of an irreversible reasoning transcript.

Structure: transformation of form · Events become conditions become state.

01 · eventsRaw agent history
02 · observeCompressed conditions
03 · reconcileDeclarative state
READY
Event history becomes observable conditions, which controllers reconcile into state.

The method generalizes · shapes not in the original six

Structure: accumulation toward a target · Coverage is close, but one gate is unmet.

Unit tests
90
Integration
84
E2E flows
62
Lint / types
95
Coral tick = required threshold (80)Coral fill = target met
Three of four gates clear the bar; end-to-end coverage is the one that ships the risk.

Structure: boundary / inside-vs-outside · Trust is earned only by crossing review.

Unreviewed
agent output
Merged &
trusted
Human review
Output stays provisional until it crosses the one boundary that confers trust.

Reference

skill: .claude/skills/editorial-illustrations/

SKILL.md = the method · references/design-system.md = tokens + primitive CSS · references/worked-examples.md = the six with claim→geometry reasoning. Accent swaps in one token; toggle grayscale above to see the monotykamary-faithful mode.