Skip to content

Commit f0d44fc

Browse files
k11kirkyPostHog
andauthored
feat: array q1 goals (#14173)
* feat: array q1 goals * Fix typos * fix: typo * fix: add line * fix: add signals * fix: typo --------- Co-authored-by: PostHog <[email protected]>
1 parent 405132b commit f0d44fc

File tree

2 files changed

+54
-4
lines changed

2 files changed

+54
-4
lines changed

contents/teams/array/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,4 +8,4 @@ template: team
88

99
## What the Array team does:
1010

11-
Super secret AI project that may or may not change the world for better or worse, maybe.
11+
Agentic Development Environment
Lines changed: 53 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,55 @@
1-
## Q4 2025 Objectives
1+
## Q1 2026 goals
22

3-
### Objective 1: Launch to public beta
3+
### Sense of winning / losing
4+
**Winning feels like:** Array has real external users giving fast feedback, the core loop is obviously valuable, and reliability is no longer a blocker to feedback. We’re shipping quickly on top of stable infra.
5+
**Losing feels like:** we’re still “getting ready to launch”, feedback is mostly internal/opinion-based, and instability is causing internal users to churn.
46

5-
We want to launch an early version of Array to public beta by the end of Q4 2025 and start getting feedback from our users as early as possible.
7+
---
8+
9+
## Objectives
10+
11+
### Objective 1: Get Array into external users hands and get real feedback
12+
**Owner:** Peter
13+
**Motivation:** Without real external usage, we can’t validate priorities. Everything else becomes speculative.
14+
15+
**What we’ll ship:**
16+
- An invite-only external beta, looking to see market pull with people asking to be added
17+
- A fully instrumented dmg so we can track usage and product metrics
18+
19+
---
20+
21+
### Objective 2: Make Array positioning and value obvious in the first session
22+
**Owner:** Jonathan
23+
**Motivation:** Users don’t understand why they’d use Array yet. We need a clear value prop and onboarding that leads to the first moment-of-magic.
24+
25+
**What we’ll ship:**
26+
- Seamless onboarding that gets users to a working PR in the first session
27+
- A great UX to use parallel agents in both cloud and local execution modes
28+
- Have PostHog generated signals create tasks in Array
29+
30+
---
31+
32+
### Objective 3: Make Array reliable and stable
33+
**Owner:** Charles
34+
**Motivation:** Stability problems destroy trust and poison feedback. Reliability is prerequisite to learning.
35+
36+
**What we’ll ship:**
37+
- Improved reliability of the Array product
38+
- Continuous delivery of the Array updates so users are always running the latest version
39+
- Lightweight testing strategy focused on key services
40+
41+
---
42+
43+
### Objective 4: AI Infra to support Array and future products
44+
**Owner:** Josh
45+
**Motivation:** Building agents is hard, if we can solve these problems ourselves can can ship more products in the future to help others with this problem.
46+
47+
**What we’ll ship:**
48+
- LLM Gateway service for model routing and LLMA integration
49+
- Sandbox environment for agent execution that is seamlessly parsed between cloud and local execution
50+
51+
---
52+
53+
## Anti-goals (explicitly out of scope for Q1)
54+
- Broad public launch
55+
- Heavy E2E testing

0 commit comments

Comments
 (0)