A small shelf for in-between work

A quiet place for ideas that aren't quite projects yet.

Most good thinking happens before anything is officially a thing. You write a note, share it once, lose it. Or you message a friend, the thread scrolls past, the idea evaporates. This is where the in-between stuff lives so it doesn't have to become work to be worth keeping.

The shape of it

three primitives

Three things, wired together. A repo to hold artifacts. A forum to talk about them. A portal so nobody gets lost looking for either.

01GitHub
A repo
Git-backed, markdown-first. Notes, skills, brand patterns, half-formed proposals. Survives forever because git does.
02Zulip
A forum
One topic per idea. Every thought is its own permanent thread you can re-enter a year later, not a channel that scrolls past.
03Lambda
A portal
This page. One URL, every shelf visible, no login confusion. Cloudflare Access gates the whole thing to people we know.

Four shelves

what the repo holds

Each shelf is its own GitHub repo inside the hiebel-lab org. They publish to subdomains on hiebel.ai so the whole thing reads as one place from the outside.

Where things live

three lanes, picked deliberately

Different stuff wants different homes. Markdown belongs in a wiki where you can edit it from a browser. Code belongs in git. Decks and PDFs need a viewer. Trying to cram all three into one tool is what kills these things.

MDProse & notes
Anything that's mostly words — notes, RFCs, half-essays, "here's a thought." Lives as markdown in the notes repo, renders as a wiki on the web.
notes.hiebel.ai
GITCode, skills, brand
Claude Code skills, design tokens, shadcn components, RFC proposals. Everything that wants to be diffable, branchable, versioned.
github.com/hiebel-lab
BINDecks, PDFs, designs
A small private file viewer (same pattern as the existing myfiles vault) for things that aren't text. Until it's live, drop binaries in a Drive folder owned by your personal Google.
files.hiebel.ai — coming

How we talk

two channels, on purpose

Two channels because they do different jobs. One for ideas that need to marinate, one for the room when something's actually happening.

Zulip is the archive: topic-per-idea, infinite history on the free tier, searchable forever. Signal is the pulse: encrypted, phone-native, ephemeral by feel. If a Signal message contains an idea worth keeping, someone copies it into a Zulip topic. That's the only handoff rule.

Why not Slack: the free tier wipes messages after ninety days, and the paid tier runs about $44 a month for five people. We'd be renting back the ability to read our own history.

What belongs here, and what doesn't

the boundary

This shelf is personal-account only. Everything lives on hiebel.ai infrastructure that I run on my own time. Nothing here touches any employer, client, or customer. That's not a soft preference — it's the line that lets this place exist at all.

Bring

  • Half-finished thoughts you want a second pair of eyes on.
  • Designs, sketches, palettes you're not sure about yet.
  • Skills, scripts, prompts you want others to try.
  • Brand patterns, voice notes, tone explorations.
  • RFCs for things that might never get built.
  • Anything that is yours, on your time, that gets sharper when shared.

Leave outside

  • Anything tied to any employer or client. Personal accounts only, every shelf.
  • Client data, customer data, or personal data of anyone not in the room.
  • Anything you wouldn't be fine seeing in a screenshot one year from now.
  • Half-rants about people. Argue with ideas, not with names.

How to join

four small steps
  1. 1
    Personal GitHub
    Send me your personal handle. You'll get an invite to the hiebel-lab org with read on every repo and write on the shelves you want.
  2. 2
    Personal Google
    Cloudflare Access gates the notes site, brand site, and lab repo to a small allow-list. You'll see a Google login the first time, then nothing again for thirty days.
  3. 3
    The two channels
    Zulip for asynchronous, topic-per-idea conversations that live forever. A Signal group for live pings and quick pull-asides. Both invite links live in the section above.
  4. 4
    First proposal
    Open lab/proposals/0001-the-lab.md, add your name under "signed on," push. That's the handshake.

Total setup is under ten minutes once the invite lands. Nothing to install on your machine. Everything is web-first; the CLI bits are optional.

The bigger idea

why bother

The point isn't a tool. The point is a small group of people who like each other's thinking, sharing the ten percent of their work that isn't yet anyone's job. The infrastructure exists so the sharing has a place to land that won't disappear.

If a year from now we look back and the proposals folder has thirty entries — half of them never built, ten of them prototyped, three of them shipped somewhere — that's the win.

One open question for later: there's a fast GPU sitting in my basement doing other things. If at some point we want a private model the group can talk to — for half-baked drafts you'd never paste into a public chatbot — we have the option. Not a commitment, just a door we keep open.