lucix — The Slack seam

In the flow

Ask arrival, nudge, and check-in — in a DM

The same T7/T11 interactions, native to Slack. Note: the verb buttons don't commit — they open a modal (no one-click commit); the nudge is delivered "R. Delgado via lucix", and defer completes right here.

llucix· App

lucixAPP9:02 AM

APAC Launch · run by Maya Chen · you own Data migration

Can Data migration commit to finishing by Mar 31?

Heads up — Platform v2, which this depends on, is still open. If a date isn't real yet, the honest move is a condition.

This is a copy of the ask — your answer lives on the record at lucix.

R. Delgadovia lucix10:14 AM

You'd said Thursday — is that still good? No rush, whenever works.

carrying: "Can you commit to a Mar 31 date?" · written by R. Delgado, delivered by lucix

lucixAPPMar 31

Platform v2 was due to land. Did your condition hold?

the condition you set on APAC Launch · one answer reaches every place it's bound

No answer is an answer — nothing here chases you.

No one-click commit

The verb fork opens a modal — the authorship confirm is the only primary action

Why a modal? A verb button that committed on one tap would let a slip of the thumb put words on the record. So in Slack — exactly as in the app — the verbs open a compose step, and the only thing that writes is the authorship confirm: "these become your words."

The record isn't here. This modal reads and writes lucix's record over the API. The Slack message is I/O; the committed answer lives on lucix. However rich the thread gets, the thread never becomes the record.

Class-1 · event home

Record events coalesce into the initiative's thread

#apac-launch· the initiative's home in Slack

lucixAPPYesterday

The risk G. Tan named in October is now part of the committed plan:

"Platform v2 slips APAC to April."

APAC Launch committed Mar 31 · a record event — nothing needs doing

4 events this season — in thread

How the seam holds the laws

Threads never become the record. Slack reads and writes lucix's record over the API; the committed answer, the condition, the plan — all live on lucix. Slack is I/O, however rich it gets (the one fixed state rule, §6.1).
No one-click commit. The verb fork (commit / condition / changed / reroute / escalate) composes in a modal; the authorship confirm — "these become your words" — is the only primary action. A stray tap can't put words on the record.
Pressure is still a person. A nudge renders "R. Delgado via lucix", carrying the original ask, in the sender's words — never machine-authored copy. Defer completes natively ("Not now — remind me Thursday"); reminders render Slack-native; check-ins are one sentence + three buttons inline. Class-5 has no envelope to render.
lucix's color system does not carry into Slack. Block Kit permits only default, primary (green), and danger (red) buttons, and Slack's own type. So the brand travels through the app icon, the copy, and the register — not the navy. This is a deliberate seam decision, not a gap: the record's look is lucix's; the channel's look is Slack's.
One spec, two renders. Every interaction above is the same object the app renders — sent once through the render/delivery contract, dressed in each surface's native grammar. The channel default matrix (which class goes where) is the architect's to define; the client renders its flags.