---
title: "Jackie Oliver"
slug: jackie-oliver
section: reference
access: public
summary: "Jackie Oliver is co-founder of Haptica alongside Paul Han, and the primary external user of the Guardian / Haptica phone application. As of April 24, 2026, her iPhone is the deployment target for tagged Release builds (alongside Paul's), her conversation history seeds the relay p…"
status: published
asset_base: /assets
home_href: /
toc_enabled: true
talk_enabled: false
agent_view_enabled: true
copy_buttons_enabled: true
footer_enabled: true
last_updated: 2026-04-29
categories: [Coworkers]
subject-type: person
aliases: [jackie, jackies-iphone, jackie-guardian]
last-reinforced: 2026-04-29
fading-since: null
archived: false
---

## Jackie Oliver

Jackie Oliver is co-founder of [Haptica](/haptica) alongside Paul Han, and the primary external user of the [Guardian](/guardian) / Haptica phone application. As of April 24, 2026, her iPhone is the deployment target for tagged Release builds (alongside Paul's), her conversation history seeds the relay preview environment, and the operator's stated working rule is *"dont push to jackie's phone"* — meaning her device is a curated test surface, not a free-fire experimentation device.

### Origin

Jackie's first appearance in the corpus is in the early [Littlebird](/littlebird) reconstruction work, where mock authentication returned both **Paul and Jackie** from `local-first-data/state.json` — a signal that the system was designed with two co-founders as first-class users from its earliest mock-auth fixtures. By the time [Guardian](/guardian) was renamed [Haptica](/haptica) in the visible app, "later builds landed on both Paul's and Jackie's phones," establishing the dual-device test pattern that has held since.

### Role in 1Context

Jackie sits in two roles relative to [1Context](/1context):

- **Co-founder of [Haptica](/haptica)**, the company building the system. The brand consolidation on April 20, 2026 dropped "Sensorics" from the company name and pinned `1Context` as the product, with Haptica as the visible identity. Jackie's authority on naming, productization, and design taste is implicit in the system but not yet explicitly catalogued in any wiki page (see Open Questions).

- **Primary external test-user of [Guardian](/guardian) / Haptica.** Her iPhone is one of two devices builds get pushed to; her conversation history (19 turns as of April 22, 2026) is the canonical real-user fixture for relay preview and durable-turn race testing. The Guardian-Lab-Relay's `jackie-guardian` project on the SSD landing zone is the real-conversation evidence path, distinct from the synthetic fixtures used in CI.

### History

The April 22, 2026 build sprint (Wednesday) seeded **19 of Jackie's conversations** into the relay preview environment, surfacing a `turns` schema drift on a `queue_position` column — Paul was `/compact`'d before seeing the silent failure, and the API returned the conversations with empty turn-state. The scribe entry for that hour flags the failure as an under-the-floor finding: any chat-history feature reading from `turns` would look like it works against real data while actually rendering against half-loaded data. The fix has not yet shipped.

April 24, 2026 included the explicit operator boundary: *"dont push to jackie's phone."* The deployment path was corrected in real-time to target Paul's iPhone instead, and the agent's harness defaults were tightened. The boundary is procedural — Jackie's phone receives signed Release builds at named milestones, not every iteration — and the rule is durable: subsequent build flows have respected it.

### Working relationship with the operator

Inferred from grounded evidence; **this section is sparse-and-honest, not exhaustive**. The relationship visible in the corpus has these qualities:

- **Co-founder authority is mutual but bounded.** Paul iterates aggressively on builds and infrastructure; Jackie's surface is the tested, signed, milestone-gated artifact. The operator's *"dont push to jackie's phone"* rule indicates that her device is the **product tier**, not the **prototype tier** — what reaches her hand is what's ready to be reached.
- **She is a real user, not a co-author of the wiki.** Her conversations appear in the relay corpus; her name appears in mock-auth fixtures; her phone is the test target. She is not (yet) recorded as posting talk-folder entries, proposing concepts, or directly editing wiki pages. The wiki documents her presence; the wiki has not been written by her.
- **Identity decisions appear shared.** The Sensorics-drop and the brand consolidation to "Haptica" are decisions the operator makes inside session transcripts but the framing (`"the company is still called haptica and we may change..."`) reads as a co-founder consensus, not unilateral. Confirmation needs operator-authored content.

### Open Questions

The corpus contains thin evidence for the **collaboration patterns** between Paul and Jackie — division of authority on design, productization, hiring, externally-facing communication. The Coworkers section of Your Context flagged this gap. A future operator-authored pass on this concept page would substantively answer:

- What design/product decisions does Jackie own outright?
- What is the cadence of her review on shipped builds?
- Which user-tier patterns surfaced from her usage have driven product decisions (the drawer rebuild, the streaming-while-typing affordance, the parity work against Claude.ai and ChatGPT)?

Until then, this page documents what the events show: a co-founder in the role of primary test-user, with a careful procedural boundary around what reaches her phone. The deeper relationship belongs in a future operator-authored expand pass — appropriate, given that operator self-authorship of co-founder relationships is the only honest source for that material.