Four ideas from a late conversation with Tavi:
- Publish the architecture prompt with articles so readers can build their own version.
- Track who uses which design document. Auto-register, subscribe for updates.
- Route change ideas from readers back to the doc. Relay what others suggested.
- Incentivize engagement.
Architecture prompt as artifact
We ship design notes. We don't ship the prompt you'd hand an AI to rebuild the tool. Publishing it means any reader gets a running implementation in their language. If re-implementing is expensive, the design is tangled with implementation detail.
Subscribing to a design doc
A reader who builds from a spec is a stakeholder. When the spec changes they should know. Subscribe button, small identity, index of who's reading what. Doc moves, subscribers get a diff.
Ideas flowing back
Not just incoming change ideas. Re-broadcast: reader B sees that A and C wanted the same thing. The doc becomes a slow async conversation, not a monologue.
Incentives
- Attribution. Ideas that land cite the source.
- Early access. Subscribers see draft specs first.
- Builder index. Others who implemented the same spec.
- The prompt itself. Subscribers get it; drive-by readers don't.
What this isn't
Not open source (one repo, bus-factor). Not a community (no forum). Closer to a protocol: many repos, one doc, explicit subscribers. Status: four ideas from a chat. Not decided.