✦ Primitive library

How DAC talks back.

Every coaching response from DAC is prose plus a typed primitive. Off-the-shelf chart libs don't carry the framework vocabulary, so we built our own. This page is the kit.

15 primitives · sample data · no LLM call · designer audit surface

Composite scenes

What a chat turn looks like

Three real envelopes from the seeded narrative. Each is what DAC streams back when asked the question above it: prose, blocks, followups, in that order. The homepage hero renders the first scene.

Read me the state of the team this morning.
Onboarding completion dropped 12% last cycle. This isn't an onboarding bug. It's a coherence gap between two functions: you're learning what users do, but you haven't closed the loop on why they leave. Three moves score, in order.
Pattern observed across last 3 cycles
Coherence gap
Feedback loop quality is one stage ahead of experience design. Signals arrive, but the design response lags the data. The 12% drop is the symptom; the gap is the cause.
Measures
  • Onboarding completion
  • Step drop-off rate
  • Activation rate
Observed in
  • Cycle 14
  • Cycle 15
  • Cycle 16
Connects to
  • Feedback loop quality
  • Experience design
  • Design / dev handoff
Break outWatch the next 4 checkout events in PostHog this week. Re-segment the drop-off pattern before the next ship.
Ranked by projected lift on onboarding completion
Three moves, in order
  1. 1
    Review last 4 checkout events in PostHog
    You already have the data. The pattern is one query away.
    S4 · Leadmeasured42 sig
  2. 2
    Spin off a Reduce drop-off cycle
    Dedicated cycle so the fix lands in one ship, not three.
    S3 · Orchestrateprojected11 sig
  3. 3
    Pull in a design review before re-ship
    The handoff is where the data and the design diverge.
    S3 · Orchestrateprojected6 sig
Push these to LinearShow me the PostHog eventsWhy is #2 only projected?
Why does the same gap keep showing up?
I keep seeing the same shape across the last four cycles. It has a name. Here's the diagnosis and the move that breaks it.
Pattern recurring across 4 cycles
Translation Gap
Build is in the top decile. GTM is two stages behind. The widening gap suggests you are shipping into a market that has not been re-segmented since Q1.
Measures
  • Cycle time
  • Lead-to-MQL ratio
  • Activation rate
Observed in
  • C14
  • C15
  • C16
  • C17
Connects to
  • Build · Operations
  • GTM · Positioning
Break outRe-segment the top three accounts this sprint and re-run the qualifying motion against the new ICP.
Show me the four cyclesWhat if we ignore it?
If we ship Cycle 18, where does composite land by Q3?
Here's the trajectory if you ship Cycle 18's commitment on time. The band is the 95% interval. Stage threshold falls inside the interval at C20.
Composite trajectory · composite
C17C20C12C16C20
Targetby C20: Composite reaches the Lead → Compound threshold·75composite
What if we slip a cycle?Show me the C20 break-down

Primitive kit · 15 blocks

Every primitive, with sample data

One card per Block type. The prose above each card is what DAC would stream around it inside a chat. If a card here looks wrong, the LLM emitting that block in production looks the same wrong.

ScoreCard

1 block

Here's the composite read for this cycle. The bar moved a point on the back of two shipped moves last sprint.
Composite
71Stage 4 · Lead↑ +1.2
95% CI: 68.4, 73.6
Up from 69.8 last cycle. The lift came from feedback loop quality.
NextLock in the weekly signal-review ritual this sprint to hold the gain.
Show me what moved itWhat would push us past 75?

RankedList

1 block

These are the three highest-leverage moves I see this cycle, ordered by projected impact on composite.
Ranked by projected lift
Top moves this cycle
  1. 1
    Close the Intercom-to-roadmap loop
    Customer signals are arriving but not moving decisions.
    S2 · Augmentmeasured47 sig+2.4
  2. 2
    Pair PM with eng on weekly spec review
    Spec quality is bottlenecking cycle time.
    S3 · Orchestrateprojected18 sig+1.6
  3. 3
    Pull design review forward of dev handoff
    Late design changes are causing rework on auth.
    S3 · Orchestrateprojected9 sig+0.9
Push #1 to LinearWhy is #2 only projected?

NamedPatternCard

1 block

I keep seeing the same shape across the last four cycles. It has a name. It's not unique to your team. It's how Build-strong, GTM-light orgs stall.
Pattern recurring across 4 cycles
Translation Gap
Build is in the top decile. GTM is two stages behind. The widening gap suggests you are shipping into a market that has not been re-segmented since Q1.
Measures
  • Cycle time
  • Lead-to-MQL ratio
  • Activation rate
Observed in
  • Cycle 14
  • Cycle 15
  • Cycle 16
  • Cycle 17
Connects to
  • Build · Operations
  • GTM · Positioning
  • GTM · Pricing
Break outRe-segment the top three accounts this sprint and re-run the qualifying motion against the new ICP.
Show me the cyclesWhat breaks this pattern?

GapIndicator

1 block

Here's the stage gap on Stakeholder Alignment. You are one stage off the next band; the criterion you are missing is the cross-functional decision log.
Gap · Stakeholder Alignment
NowS3 · Orchestrate→NextS4 · Leadhigh confidence
You are running aligned cycles but the decisions inside them are not durable. Add a decision log read by GTM.
What does the next stage look like?Show me the criteria

ComparisonPanel

1 block

Side-by-side of where you are versus the criterion for the next band. The right column is the bar to clear.
NOW
Today
S3 · Orchestrate
Decisions get made in cycle reviews but are not written down. New joiners re-litigate them.
NEXT
Next band
S4 · Lead
Every cycle review ends with a written decision log linked from the cycle artifact, read by GTM within 48 hours.
Help me draft the log templateWho owns this?

TrajectoryChart

1 block

Composite trajectory for the last six cycles plus a six-cycle projection. The band is the 95% interval. Here is the milestone we are aiming at.
Composite trajectory · composite
C17C23C12C18C23
Targetby C20: Composite reaches the Lead → Compound threshold·75composite
What drives the projected lift?What if we miss the milestone?

DocumentTemplate

1 block

Here's a board-ready one-pager you can take into Friday's review. Three sections: state, the named pattern, the move you are making.
Cycle 17 board read
For the May board meeting
State
Composite
71Stage 4 · Lead↑ +1.2
NextLock in the weekly signal-review ritual this sprint.
Team73S4 · Lead
Operation71S4 · Lead
Product68S3 · Orchestrate
Pattern
Translation Gap is closing
GTM caught up half a stage in the last two cycles after the Intercom-to-roadmap loop opened.
Cycle 18 commitment
Re-segment top three accounts
Re-run the qualifying motion against the post-Q1 ICP.
Projection · +1.4 composite by C20Spillover · Lifts GTM · Positioning by ~2 stage points
Next stepSend to board by Friday ahead of the May review meeting.
Send toPDFSlackSlides
Send to SlackExport as PDF

FunctionCard

1 block

Here's the Operations function in detail. It's the strongest of the three.
Operations
73S4 · Lead
142 signals
Cycle ritual quality + decision durability are both in the top quartile.
LiftPair the cycle review with a written decision log this sprint to push into the Compound band.
Compare to BuildShow the underlying dimensions

ShippingLandingBarPair

1 block

Here's the shipping vs landing read on the auth refactor. You shipped four; one landed. That's the gap.
Auth refactor · Cycle 173 shipped without a measured landing signal
Shipped
4
Landed
1
Why did three not land?Add a landing signal to Cycle 18

TriadTriangle

1 block

Here's the triad shape this cycle. Team and Operation are aligned; Product is the trailing edge.
✦ Triad · Team · Operation · Product
✦ Team73
S4 · Lead
✦ Operation71
S4 · Lead
✦ Product68
S3 · Orchestrate

✦ Trailing edge: Operation → Product

Why is Product trailing?What lifts the operation→product edge?

CompoundLoop

1 block

Here's where you are in the loop. You scored, I coached, you pushed to Linear, the team executed. Now we re-score this cycle.
Compound loop
  1. ScoreCycle 17 ran Monday.
    →
  2. CoachThree moves emitted.
    →
  3. Linear2 of 3 pushed.
    →
  4. Execute1 landed, 1 in progress.
    →
  5. Re-scoreCycle 18 starts Monday.
AdvanceRun the signal-review ritual this Thursday so Cycle 18 starts with a clean read.
What if we skip a cycle?Show me last cycle's loop

EvidenceLedger

1 block

Here's the ledger of moves we shipped against Feedback Loop Quality and what each one moved.
Evidence ledger · Feedback loop quality · last 12 weeks
CycleMoveSignal shiftΔ
C15
Open the Intercom-to-roadmap loop
4w window · measured C17 read
Customer signals cited in decisions: 4/wk → 11/wk+1.4
C16
Add NPS to the cycle review
4w window · measured C17 read
Cycle reviews citing NPS: 0/4 → 3/4+0.7
C16
Tag PRs with the signal that prompted them
6w window · measured C17 read
Tagged PRs: 0% → 12%+0.2
Next cycle
Push tagged-PR adoption to 50% this sprint by adding it to the PR template.
The weak delta is a tooling problem, not a value problem; remove the friction and it lands.
What else did C15 move?Show me a weak-delta move

MaturityJourneyTrack

1 block

Here's the maturity track for Decision Quality. You are at Lead; the Compound band needs a written decision log read across functions within 48 hours.
Maturity journey
Decision Quality
S1React
S2Augment
S3Orchestrate
S4Leadyou are hereDecisions logged + linked.
S5CompoundDecisions read cross-function in 48h.
next: S5
BreakoutPilot a 48-hour cross-function decision-read with one squad next sprint to earn the Compound criterion.
Who runs the pilot?What blocks the cross-function read?

TeamCompositeHeader

1 block

Here's the header you'd put on the team page. Composite + the triad in one read.
Team
Acme.ai · Product
71Stage 4 · Lead
Team73
Operation71
Product68
Drill into the teamCompare with last cycle

OneMovePromptCard

1 block

If you only do one thing this sprint, do this. It carries the highest projected lift and the spillover is real.
Highest leverage this sprint
Close the Intercom-to-roadmap loop
Customer signals are arriving but not moving decisions. Closing this loop is the single biggest unlock on Translation Gap.
whenthis sprint·watchcount of cycle decisions citing customer signals / week
+2.4 projectedcomposite by C19
Feedback loop quality +1.6Decision quality +0.7
Push to LinearShow me the evidence