01 · Weeks 1–2
Activation
Make the first successful publish inevitable.
- One obvious creation path
- Preview before publish
- Errors that name the fix
- Activation event model
Gate · ≤2 min to first publish
Artifact Bin · Product Plan
90-day horizon
Draft 01
Product thesis / 01
Make publishing an artifact feel as natural as sending a message.
Artifact Bin becomes the fastest trusted path from an idea, agent, or dataset to a polished thing people can open, share, discuss, and revisit.
The product loop
01 · Create
Describe the thing
02 · Publish
Get a durable URL
03 · Share
Reach an audience
04 · Return
Edit, discuss, reuse
Proposed day-90 outcomes
Targets, not current performance
1,000
MAU
250
DAU
25%
DAU / MAU
≥35%
D30 creator retention
≤2m
First publish
Roadmap / 02
Four product milestones
M0 · Mapped
Know the system
Authority map, seams, publish path, render lifecycle.
M1 · Now
Win activation
Idea → preview → publish → share in one obvious loop.
M2 · Next
Create the return loop
Comments, live edits, versions, reuse, notifications.
M3 · Scale
Earn trust
Reliability, ACL gates, capture quality, observability.
Execution map / 04
Four bets turn solid infrastructure into a product people return to.
Sequence work by user value; use the architecture seams to keep each bet independently shippable.
02 · Weeks 3–4
Shareability
Turn every publish into a compelling invitation.
- Excellent link previews
- Reader-first performance
- Clear visibility controls
- Creator attribution
Gate · 40% create → share
03 · Weeks 5–8
Return loop
Give creators and readers a reason to come back.
- Annotations and replies
- Live edits and versions
- Remix and reuse paths
- Return notifications
Gate · ≥35% D30 creators
04 · Weeks 9–12
Trust & scale
Make reliability a feature users can feel.
- ACL conformance suite
- Capture reliability SLO
- Service observability
- Launch playbook
Gate · zero critical bypasses
System relationship / 05
The plan moves through one product core.
Entry surfaces
Human app · Agent API · MCP · Unfurlers
Different doors, one product promise.
Product core
Artifact lifecycle · ACL · documents · collaboration
Ship semantics here before exposing them anywhere else.
Replaceable services
SQL · Browser capture · Object storage
Scale topology without changing product meaning.
Shared contract floor
Actor + ACL
Artifact wire
SQL service
Browser service
Measurement contract / 07
Define success before optimizing it.
All figures below are proposed planning targets and should be replaced by an instrumented baseline after week one.
| Metric | Target | Definition | Why it matters |
|---|---|---|---|
| MAU | 1,000 | Unique signed-in or stable anonymous actors with a meaningful action / 30d | Reach |
| DAU / MAU | 25% | Daily active actors divided by monthly active actors | Habit |
| D30 creator retention | ≥35% | First-time publishers who return and publish again 30 days later | Durable creator value |
| Create → share | ≥40% | New artifacts opened by a non-creator within 24 hours | Distribution quality |
| Time to first publish | ≤2 min | Median time from creation entry to a valid public or unlisted URL | Activation friction |