Component library
Signals
One shared presentation for a signal, wherever it appears. Explore the layouts, review decisions, and supporting context, then try a save or correction.
Compact design proposalsTry the component
Change the presentation and container, open the signal, or make a local review decision. Reset returns the example to its starting state.
Four layouts, one anatomy
The claim, source, related records, and review context keep their order. Only the surrounding space and framing change.
Card · a standalone review
A complete signal with a visible boundary.
Row · a continuous list
A divider connects consecutive signals.
Compact · dense lists
Small type and spacing for scanning.
Detail · a drawer or expanded view
The containing surface supplies its own frame.
Review and publication states
A proposal can be accepted before publication. A published signal can also carry a separate concern or trust warning; those do not replace its decision history.
Proposed
A decision is ready to review.
Published · accepted
A live signal retains its source and decision.
Accepted · awaiting publication
A reviewed proposal is distinct from a published signal.
This proposal has been accepted. It will become a live signal when publication completes.
Published · verified
A verified record is shown as a live signal.
Held by a reviewer
An explicitly parked proposal stays separate from pending work.
Maya parked this proposal while waiting for the revised operating table.
Proposed · suggested hold
An advisory judgment does not itself park the proposal.
Suggested decision: hold. The reporting period is unclear; check the source before accepting.
Published from a proposal
The proposal history and resulting live signal are distinguishable.
Modified
A correction retains the original context.
Original wording: “Revenue grew 28% year over year.” The period was corrected after checking the source.
Rejected
The reason explains the decision.
The source describes a planned round, not a completed financing.
Quarantined
A held item has a clear explanation.
Quarantined after a trust reset. The company match needs review before this signal can return to the live view.
Reported for review
An open concern stays attached to the signal.
Reported concern: this percentage may refer to bookings rather than recurring revenue.
Legacy pending
Older pending records use the same review structure.
Saving, errors, and recovery
Only the signal being saved is busy. Failures keep the proposed decision visible and give the reviewer a local retry.
Saving a decision
The pending label names the current operation.
Accepting & publishing…
Failed save · retry it
Retry keeps the original intent and succeeds in this simulation.
An independent decision
This example remains usable while a different signal is saving.
Decision saved, refresh failed
An acknowledged save stays successful even if the surrounding list needs to refresh.
The decision was saved. The surrounding list could not refresh; reload the view to see its latest state.
Source, authorship, and discussion
Evidence, personal interpretations, and authored notes stay distinguishable. A signal can include supporting context without introducing another visual pattern.
Document evidence
A claim with the exact supporting passage.
“Recurring revenue increased 28% quarter over quarter. Expansion accounted for 61% of net new revenue.”
Human read shared in Slack
Authorship and interpretation are explicit.
Person context
A personal fact is distinct from an investment claim.
Commitment and next step
An authored follow-up keeps its owner and context.
Captured source unavailable
The original source remains available when a capture cannot load.
The captured source could not be loaded. Open the original source to review the claim.
Removed signal snapshot
A resolved concern can retain a historical snapshot.
Resolved report: this signal duplicated an earlier update. This is the retained snapshot of the removed signal.
External source
An external link is clearly distinguished.
Discussion and history
Supporting discussion shares the same container.
Discussion · 2 comments
Maya · Sep 19
The attached table supports the quarter-over-quarter comparison.
Noah · Sep 19
Confirmed. The retention trend is worth revisiting next quarter.
Real content is uneven
Long copy, missing data, unresolved names, and unfamiliar categories use the same component. Unavailable information stays absent rather than being presented as neutral or zero.
Long signal and many relationships
Content wraps without hiding the decision or source.
Minimal context
Missing optional data does not become a fake score or date.
Unresolved matches
People and companies can be unresolved independently.
Negative trend and risk
Risk has a text label as well as visual emphasis.
The runway estimate assumes spending stays at the current level.
Long unbroken text
A narrow container still accommodates identifiers.
Unrecognized type
A new category can render without a special layout.
Signal types
Category labels are content. Each type uses the same body, source, and decision structure.
The surrounding collection
These examples belong to the list around the signal component. They distinguish loading, empty results, and a failed request.
Loading a collection
The surrounding view owns list loading.
Loading signals…
Empty collection
Empty describes the scope of this view.
No signals to review
New proposals for this record will appear here when they are ready.
Collection error and retry
A failed read is different from an empty queue.
Signals could not be loaded.
The example request failed. Try loading the collection again.
All people, organizations, figures, and review activity on this page are fictional. Example controls only change this page’s local state.