Skip to content

Commit 4e9a0de

Browse files
author
waleed
committed
added scaffolding and authors for everyone's articles
1 parent e702a05 commit 4e9a0de

File tree

10 files changed

+329
-1
lines changed

10 files changed

+329
-1
lines changed

‎apps/sim/content/authors/adam.json‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
{
2+
"id": "adam",
3+
"name": "Adam Gough",
4+
"url": "https://x.com/adamgough",
5+
"xHandle": "adamgough",
6+
"avatarUrl": "/blog/authors/adam.png"
7+
}

‎apps/sim/content/authors/sid.json‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
{
2+
"id": "sid",
3+
"name": "Siddharth",
4+
"url": "https://x.com/siddharth",
5+
"xHandle": "siddharth",
6+
"avatarUrl": "/blog/authors/sid.png"
7+
}

‎apps/sim/content/authors/vik.json‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
{
2+
"id": "vik",
3+
"name": "Vikhyath Mondreti",
4+
"url": "https://x.com/vikhyathm",
5+
"xHandle": "vikhyathm",
6+
"avatarUrl": "/blog/authors/vik.png"
7+
}

‎apps/sim/content/blog/copilot/index.mdx‎

Lines changed: 101 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,101 @@
1+
---
2+
slug: copilot
3+
title: 'Inside Sim Copilot — architecture, benchmarks, and how it fits'
4+
description: 'A technical overview of Sim Copilot: the architecture behind it, our early benchmarks, and how Copilot integrates with agentic workflows in Sim.'
5+
date: 2025-11-08
6+
updated: 2025-11-08
7+
authors:
8+
- sid
9+
readingTime: 7
10+
tags: [Copilot, AI Assistant, Benchmarks, Architecture, Sim]
11+
ogImage: /blog/copilot/cover.png
12+
ogAlt: 'Sim Copilot technical overview'
13+
about: ['AI Assistants', 'Agentic Workflows', 'Retrieval Augmented Generation']
14+
timeRequired: PT7M
15+
canonical: https://sim.ai/blog/copilot
16+
featured: false
17+
draft: false
18+
---
19+
20+
> This is a technical deep‑dive scaffold for Sim Copilot. We’ll keep updating it as we publish more results and open up additional capabilities.
21+
22+
## TL;DR
23+
24+
- Copilot is a context‑aware assistant embedded into the Sim editor.
25+
- It has first‑class access (with user approval) to workflows, blocks, logs, and docs.
26+
- The system is retrieval‑centric with strong guardrails and deterministic execution paths.
27+
28+
## Architecture at a glance
29+
30+
1. Intent understanding
31+
- Lightweight classifier + instruction parser directs requests into tools.
32+
2. Context assembly
33+
- Indexed sources (workflows, blocks, logs, docs) with semantic and lexical signals.
34+
- Safety filters for scope + permission checks.
35+
3. Tooling and actions
36+
- Read‑only tools (explain, compare, search), propose‑changes tools, and execution tools.
37+
4. Response synthesis
38+
- Deterministic templates for diffs, plans, and explanations.
39+
5. Human‑in‑the‑loop
40+
- All writes gated behind explicit user approval.
41+
42+
```mermaid
43+
flowchart LR
44+
U[User] --> I(Intent)
45+
I --> C(Context Builder)
46+
C -->|RAG| R[Retriever]
47+
R --> T(Tools)
48+
T --> S(Response Synth)
49+
S --> U
50+
```
51+
52+
## Retrieval and grounding
53+
54+
- Sources: workspace workflows, block metadata, execution logs, and product docs.
55+
- Indexing: hybrid scoring (BM25 + embeddings) with recency decay and per‑source caps.
56+
- Normalization: chunking with stable anchors so diffs remain line‑referential.
57+
58+
## Early benchmarks (scaffold)
59+
60+
> Numbers below are placeholders for the structure; we’ll replace with full runs.
61+
62+
| Task | Top‑1 Retrieval@K | Edit Accuracy | Time (p50) |
63+
| ----------------------------------- | -----------------:| ------------: | ---------: |
64+
| Explain a workflow block | 92% | 88% | 1.2s |
65+
| Propose a safe fix for an error | 78% | 70% | 2.1s |
66+
| Generate a new block configuration | 74% | 65% | 2.6s |
67+
| Find relevant execution logs | 90% | 84% | 1.4s |
68+
69+
Measurement notes:
70+
71+
- Retrieval@K: correctness of the top candidate chunk for a labeled query.
72+
- Edit Accuracy: human‑validated acceptance rate for proposed changes.
73+
- Time: server‑side latency (excludes model cold‑start).
74+
75+
## Guardrails and safety
76+
77+
- Scope enforcement: actions limited to the open workspace with explicit user triggers.
78+
- Sensitive data policies and redaction in logs.
79+
- Proposal mode: diffs are reviewed and applied only on user approval.
80+
81+
## How Copilot fits into Sim
82+
83+
- In‑editor assistant for building and editing workflows.
84+
- Shortcut to documentation and examples with live context from your canvas.
85+
- Bridge to evaluation: Copilot can set up test runs and compare outputs side‑by‑side.
86+
- Works with the same permissions model you already use in Sim.
87+
88+
## Roadmap (high‑level)
89+
90+
- Multi‑turn plans with sub‑tasks and rollback.
91+
- Deeper evaluation harness and dataset management.
92+
- First‑party tool plugins for common blocks and providers.
93+
94+
## Repro and transparency
95+
96+
- We’ll publish a benchmark harness and anonymized evaluation sets.
97+
- Expect a detailed methodology post as we widen the beta.
98+
99+
— Sid @ Sim
100+
101+

‎apps/sim/content/blog/emcn/index.mdx‎

Lines changed: 97 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,97 @@
1+
---
2+
slug: emcn
3+
title: 'Introducing Emcn — Sim’s new design system'
4+
description: Emcn is the heart of our new design language at Sim. Here’s the scaffolding of the system—principles, tokens, components, and roadmap—as we prepare the full launch.
5+
date: 2025-11-08
6+
updated: 2025-11-08
7+
authors:
8+
- emir
9+
readingTime: 6
10+
tags: [Design, Emcn, UI, UX, Components, Sim]
11+
ogImage: /blog/emcn/cover.png
12+
ogAlt: 'Emcn design system cover'
13+
about: ['Design Systems', 'Component Libraries', 'Design Tokens', 'Accessibility']
14+
timeRequired: PT6M
15+
canonical: https://sim.ai/blog/emcn
16+
featured: false
17+
draft: false
18+
---
19+
20+
> This post is the scaffolding for Emcn, our new design system. We’ll fill it in as we publish the full documentation and component gallery.
21+
22+
![Emcn cover placeholder](/blog/emcn/cover.png)
23+
24+
## What is Emcn?
25+
26+
Emcn is the design system that powers Sim’s product and brand. It aims to give us:
27+
28+
- Consistent, accessible UI across web surfaces
29+
- A fast path from Figma to code with strongly‑typed tokens
30+
- A composable component library that scales with product complexity
31+
32+
## Principles
33+
34+
1. Opinionated but flexible
35+
2. Accessible by default (WCAG AA+)
36+
3. Strongly‑typed, themeable tokens (light/dark + brand accents)
37+
4. Composable components over one‑off variants
38+
5. Performance first (minimal runtime, zero layout shift)
39+
40+
## Foundations (Tokens)
41+
42+
- Color: semantic palettes (bg, fg, muted, accent, destructive) with on‑colors
43+
- Typography: scale + weights mapped to roles (display, title, body, code)
44+
- Spacing: 2/4 grid, container and gutter rules
45+
- Radius: component tiers (base, interactive, card, sheet)
46+
- Shadows: subtle elevation scale for surfaces and overlays
47+
- Motion: duration/easing tokens for affordances (not decoration)
48+
49+
## Components (Initial Set)
50+
51+
- Primitives: Button, Input, Select, Checkbox, Radio, Switch, Slider, Badge, Tooltip
52+
- Navigation: NavBar, SideBar, Tabs, Breadcrumbs
53+
- Feedback: Toast, Banner, Alert, Dialog, Drawer, Popover
54+
- Layout: Grid, Stack, Container, Card, Sheet
55+
- Content: CodeBlock, Markdown, Table, EmptyState
56+
57+
> Each component will include: anatomy, a11y contract, variants/slots, and code examples.
58+
59+
## Theming
60+
61+
- Light + Dark, with brand accent tokens
62+
- Per‑workspace theming hooks for enterprise deployments
63+
- SSR‑safe color mode with no flash (hydration‑safe)
64+
65+
## Accessibility
66+
67+
- Focus outlines and target sizes audited
68+
- Color contrast tracked at token level
69+
- Keyboard and screen reader interactions defined per component
70+
71+
## Tooling
72+
73+
- Tokens exported as TypeScript + CSS variables
74+
- Figma library mapped 1:1 to code components
75+
- Lint rules for token usage and a11y checks
76+
77+
## Roadmap
78+
79+
- v0: Foundations + Core components (internal)
80+
- v1: Public docs and examples site
81+
- v1.x: Data display, advanced forms, charts bridge
82+
83+
## FAQ
84+
85+
- What does “Emcn” mean?
86+
A short, crisp name we liked—easy to type and remember.
87+
88+
- Will Emcn be open‑sourced?
89+
We plan to share the foundations and many components as part of our commitment to open source.
90+
91+
## We’re hiring
92+
93+
We’re hiring designers and engineers who care deeply about craft and DX. If you want to help shape Emcn and Sim’s product, we’d love to talk.
94+
95+
— Team Sim
96+
97+

‎apps/sim/content/blog/multiplayer/index.mdx‎

Lines changed: 109 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,109 @@
1+
---
2+
slug: multiplayer
3+
title: 'Realtime and Multiplayer in Sim — how it works under the hood'
4+
description: "A technical look at Sim's realtime and multiplayer architecture: presence, collaboration, conflict resolution, and scale."
5+
date: 2025-11-08
6+
updated: 2025-11-08
7+
authors:
8+
- vik
9+
readingTime: 8
10+
tags: [Multiplayer, Realtime, Collaboration, CRDT, WebSockets, Sim]
11+
ogImage: /blog/multiplayer/cover.png
12+
ogAlt: 'Sim multiplayer architecture overview'
13+
about: ['Realtime Systems', 'Operational Transform / CRDT', 'Collaboration']
14+
timeRequired: PT8M
15+
canonical: https://sim.ai/blog/multiplayer
16+
featured: false
17+
draft: false
18+
---
19+
20+
> This post outlines the key pieces of Sim’s realtime and multiplayer stack. It’s a scaffold we’ll keep enriching with diagrams, traces, and code snippets as we publish more details.
21+
22+
## Goals
23+
24+
- Low‑latency collaboration on shared canvases and workflows
25+
- Deterministic conflict resolution and auditability
26+
- Scales from small teams to enterprise orgs
27+
28+
## High‑level architecture
29+
30+
1. Transport
31+
- Secure WebSocket channels per workspace/session with fallbacks.
32+
2. Session and presence
33+
- Authenticated connections; presence, cursors, and selections broadcast on a lightweight channel.
34+
3. State model
35+
- Canonical workflow state stored in a durable DB; clients hold ephemeral working copies.
36+
4. Conflict resolution
37+
- Operation‑based CRDT/OT hybrid for block changes; idempotent ops with causal timestamps.
38+
5. Persistence and snapshots
39+
- Append‑only operation log; periodic compaction into snapshots for fast loads.
40+
6. Observability
41+
- Per‑op metrics, client RTT, and reconnection traces; room health dashboards.
42+
43+
```mermaid
44+
sequenceDiagram
45+
participant C1 as Client A
46+
participant C2 as Client B
47+
participant GW as Realtime Gateway
48+
participant S as State Service
49+
C1->>GW: connect(ws, auth)
50+
C2->>GW: connect(ws, auth)
51+
C1->>GW: op(block.update)
52+
GW->>S: validate & persist(op)
53+
S-->>GW: ack(op, version)
54+
GW-->>C1: ack(op)
55+
GW-->>C2: broadcast(op)
56+
```
57+
58+
## Presence and awareness
59+
60+
- Presence channel carries user metadata (name, color), cursor positions, and ephemeral selections.
61+
- Heartbeats + timeouts remove stale presence; reconnects recover presence state.
62+
63+
## Operations and versions
64+
65+
- Every mutating action becomes an operation with: opId, actorId, version, path, payload.
66+
- Servers validate permissions and consistency (version checks) before persisting.
67+
- Clients apply local‑first (optimistic) and reconcile on ack or transform.
68+
69+
## Conflict handling
70+
71+
- Commutative ops where possible; otherwise use a simple priority rule (timestamp + actor tie‑break).
72+
- Path‑scoped transforms for list inserts/deletes to prevent positional drift.
73+
74+
## Latency compensation
75+
76+
- Local optimistic apply → render immediately.
77+
- On ack mismatch, transform local queue and rebase.
78+
- Visual hints for pending vs. confirmed states.
79+
80+
## Scale and sharding
81+
82+
- Rooms keyed by workspace + resource; sticky routing ensures op ordering.
83+
- Horizontal gateway workers; state service partitions by workspace.
84+
- Backpressure and fan‑out limits on large rooms.
85+
86+
## Security model
87+
88+
- Auth tokens scoped to workspace and resources; server‑side permission checks per op.
89+
- Rate limits per actor and per room; anomaly detection for spammy clients.
90+
91+
## Benchmarks (placeholder)
92+
93+
| Metric | Result (p50) | Result (p95) |
94+
| ------------------------------ | -----------: | -----------: |
95+
| Round‑trip op latency | 60ms | 140ms |
96+
| Broadcast fan‑out (100 users) | 8ms | 22ms |
97+
| Reconnect time | 120ms | 280ms |
98+
99+
We’ll publish a full methodology and open telemetry traces as we finalize numbers.
100+
101+
## Roadmap
102+
103+
- Presence enrichments (inline comments, threads)
104+
- Partial‑document subscriptions for massive canvases
105+
- Time‑travel and per‑block history
106+
107+
— Team Sim
108+
109+

‎apps/sim/content/blog/series-a/index.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
slug: series-a
3-
title: 'Sim raises $7M Series A led by Standard Capital'
3+
title: 'Sim raises $7M Series A'
44
description: We’re excited to share that Sim has raised a $7M Series A led by Standard Capital to accelerate our vision for agentic workflows and expand the team.
55
date: 2025-11-08
66
updated: 2025-11-08

‎apps/sim/public/blog/copilot/cover.png‎

114 KB
Loading

‎apps/sim/public/blog/emcn/cover.png‎

90.2 KB
Loading

‎apps/sim/public/blog/multiplayer/cover.png‎

148 KB
Loading

0 commit comments

Comments
 (0)