Repository navigation
id(phase-14): Creator tooling & insight — core topic (research + design) #6282
Description
Creator tooling & insight — Phase 14 core topic (research + design)
Filed from the next-horizons discussion #1240, decided by Drew on 2026-11-05: all themes are planned. This issue is the core topic for Creator tooling & insight. Its job is research and design — broaden the idea beyond what is already understood, set up multiple next steps, and produce implementation plans. No implementation starts here; the output is design documents and implementation issues.
Drew's principles for everything in Phase 14 (from #1240, 2026-11-05)
- Local-first is always the goal, AND a hosted version is intended: central coordination supporting a large graph of broadly accessible objects.
- Anything built must be completely usable by others hosting a small or large server themselves. P2P-hosted worlds and data behave the same as a large hosted public server; differences live in backend scale elements and access controls.
- Users connect to each other and transfer/interact directly wherever possible, so hosted resources are an offloadable backstop, not a requirement. The app must not technically need us to function. Collaborative / shared / federated / local-first / p2p.
- Our hosted instance is essentially public; other operators open theirs only as much as they want. Publishing paths: share to a big server, publish on pkarr, or self-host. All comms through iroh on the backend; first-class clients.
The idea, broadened
Worlds need authors, and authors need feedback and control. Broaden beyond analytics: what a world owner should know (visits, joins, program runs, where people get stuck), what they should control (moderation that matches the role model, not a bolt-on), and what a public world owes its visitors (safety signals, reporting). Local-first applies to data too: a self-hosted world keeps its analytics; the public server aggregates only what operators choose to share.
Research questions (first pass)
- Owner metrics with privacy: counts without surveillance — what is measurable from journal/presence without tracking people
- Moderation surface: existing roles (Phase 10) vs needed powers (mute, slow-mode, ban by key, quarantine a program) and their audit trail
- Reporting flow for public worlds: visitor report → registry/host queue → action, with appeals
- Creator feedback loops: where do joiners drop off a world's first screen; can the platform show that without creepy telemetry
Dependencies and existing pieces
Builds on Phase 10 roles, F11.7 metrics (#553), F12.6 audit (#1063), and the discovery/hosting topics (public worlds create the moderation need).
Next steps — the version ladder
- v1 — first-iteration design — its own issue, filed in the same pass and linked in the first comment below
- v2 — outline: cross-world creator tools — its own issue, filed in the same pass and linked in the first comment below
- v3 — outline: public-world safety — its own issue, filed in the same pass and linked in the first comment below
- v4 — outline: creator ecosystem — its own issue, filed in the same pass and linked in the first comment below
Plus a standing rule for this topic: anything the research surfaces that doesn't fit v1–v4 gets its own issue (Drew's rule: every feature, concept, or idea gets an issue), and future investigations are listed as comments here rather than lost.
Sequencing
Design queue order: F12.4 provider registry (#1061) and F12.10 scheduling/quotas (#1067) designs land first; Phase 14 v1 designs then run hosted worlds → discovery → agents spike → the rest. Implementation follows Phase 13. The drop rule applies throughout: anything that proves blocked, wrong, or superseded gets parked or closed with a note — never a silent stall.
Acceptance criteria
- A research + design output exists for Creator tooling & insight: design documents broadening the topic beyond the current understanding, per the Phase 14 principles in the body (local-first plus hosted coordination).
- Multiple concrete next steps are produced as implementation plans / implementation issues filed from this topic.
- No implementation starts under this issue itself (per its own charter).
Activity
developing-today commentedon Nov 5, 2026
CODE-1848
dezren39 commentedon Nov 5, 2026
Version ladder for this topic (filed in the same pass, 2026-11-05):
Phase 14 plan of record: #6312. Discussion of record: #1240.
dezren39 commentedon Nov 6, 2026
Intake review
🤖 Fleet monitor intake (repo-fleet-monitor), 2026-11-06.
dezren39 commentedon Nov 6, 2026
🤖 Agent note · done
Triage findings (verified fresh 2026-11-06 12:24–12:30Z via
gh):status/needs-triageand enters the queue through the same coverage route this issue did.queue/queued) and the F12.10 scheduling/quotas design (issue id: F12.10 fair scheduling and per-account quotas #1067, OPEN) land first; Phase 14 v1 designs then run hosted worlds → discovery → agents spike → the rest, and this topic sits in "the rest". Implementation follows Phase 13. So the next actionable item for this topic is issue id(phase-14): Creator tooling & insight — v1 — first-iteration design #6308 (v1 design), in that queue order — not now.main: this is a design topic with no implementation surface yet; nothing is fixed, superseded, or stale — the drop rule does not apply.Disposition: task 11054 completed as
triaged. This issue stays open as the topic tracker; it should not be re-queued until issue #1061 and issue #1067 designs have landed and the earlier Phase 14 v1 topics have run.3 remaining items
dezren39 commentedon Nov 6, 2026
🤖 Agent note · handed off
opencode; handing off to the opencode claimant per the worker runbook §1b. Verified fresh via gh: issue id(phase-14): Creator tooling & insight — core topic (research + design) #6282 is OPEN with no hard-stop labels (no held, user/owned, do-not-merge, do-not-auto-edit). Attempts 1/6.dezren39 commentedon Nov 6, 2026
🤖 Agent note · handed off