Workspace tab primitives

Brainstorm with Claude — 2026-05-08. Five primitives that everything in workspace + apples client tabs collapses to.

1. Note

Single editable doc. Examples: case, tiktok-shop. Rich text. Auto-save. Linkify URLs.

2. Wiki

Collection of Notes with search + tagging + linkage. Examples: Nikipedia. A wiki is just a tagged folder of notes.

3. Feed

Auto-curated chronological stream plus manual edits. Examples: queue, oranges public, askcraig threads, search results, news. Schema: (source, item_id, title, body, ts, kind, status). Sources can be auto (RSS, scraper, firehose) or manual entries. Filter + status workflow built in.

4. Console

Read-only admin dashboard backed by a DB. Examples: apples, oranges admin, quiddler, spidergpt, askcraig admin, collage. Recursive grid pattern: Layer 2 = section tiles, Layer 3 = section content (table).

5. Tool

Live service the user interacts with. Examples: n8n, browser, video, copilot, terminal, meet. Also third-party links (Claude, DigitalOcean, Enformion).

Nothing else needed. APIs aren't a tab type — they're a source that feeds Notes / Feeds / Consoles. They belong in a per-platform "Integrations" panel inside whichever tab consumes them. Tools are the catch-all for third-party UI that already exists.

Notes ↔ Wiki

Merge them. Wiki = view of all Notes with metadata (tags, project, pinned). Each Note has a pinned: bool flag. Pinned notes show up as Layer-1 tiles. Unpin = removes from Layer-1 but stays in Wiki. Drop a note onto Layer-1 = pins it. Single source of truth, two views.

Feed as core tab type

Strong fit. Schema: (source, item_id, title, body, ts, kind, status). Sources can be auto (RSS, scraper, oranges firehose, askcraig finder) or manual. Filter + status workflow built in. Queue is exactly this. Each platform Nik builds for a client gets a Feed tab automatically; sources configured per client.

Apples client template system

With these 5 primitives, "create new tab" becomes 5 buttons. User picks Note / Wiki / Feed / Console / Tool, fills in 1-3 required fields:

Note: title
Wiki: title, project tag
Feed: title, sources (URL list, integration picker)
Console: title, db path or API endpoint
Tool: title, service URL

Zero room for error because the schema enforces what each type needs.

18 apples.live tools collapse

Most are Console (CRM, Bookings, Inventory, Finance, Influencers tracking…) or Feed (Social Posts, Email, Discover) or Tool (Browser, Studio). The categorization is much smaller than 18 once you abstract.

Shape this could take

Layer 1 grid = mix of pinned Notes / Feeds / Consoles + Tools. Each tile is one of the 5 primitives. The recursive grid pattern already built works for all 5. Adding a new tab = pick primitive + minimal config.