· Goal lens · live MCP goals ·
Start from goals. Let branches compete underneath. Your chatbot can browse these goals directly through the MCP connector. Pick a goal to see the live commons records and branch signals currently attached to it.
Refresh MCP Refresh GitHub MCP Apr 30, 2:40 AM GitHub Apr 30, 2:40 AM
MCP source tinyassets.io/mcp 6 public goals · Apr 30, 2:40 AM Selected goal 62f977e7ff0c 3 commons records · 4 branch signals GitHub source local git checkout + GitHub remote head 8980315 · Apr 30, 2:40 AM G1 Play classic games on modern computers Help a user identify an old game from memory, find a legal acquisition path, adapt it for their current machine, install or configure it with approval, create a launcher, and verify the game starts. Community branches under this Goal should be forkable recipes for lawful game restoration and compatibility, not piracy or DRM bypass. classic-games game-preservation compatibility local-app G2 Connect public web sources to Workflow universes Let a chatbot fetch a public source URL, store the snapshot in a Workflow universe through MCP, preserve attribution/provenance, and route proposed changes through branch/gate review before promotion. Echoes of the Cosmos Reddit/RSS is the first live example. public-source mcp universe echoes G3 Route a patch request through investigation, PR, release, and live observation Community-driven live-state loop for Workflow changes. Any patch request starts as a wiki report, runs through the best known investigation branch, passes gate review, dispatches a coding-team branch to produce a PR, passes further gates, and is then observed after landing with real or simulated users. The goal is long-horizon self-improvement: gates can send work backward with edits whenever evidence shows the patch did not land or did not work as intended. patch-loop community gatekeeping pr G4 Turn a Workflow bug into a patch packet Given a filed Workflow bug report, produce an actionable patch packet: normalized bug summary, minimal repro, likely root cause map, implementation sketch, regression tests, and attachable maintainer comment. Intended to be run automatically after wiki action=file_bug via the canonical branch for this goal. bugs patch-packet workflow-engine daemon G5 Complete a software project end-to-end Take a project brief and acceptance criteria as input; coordinate a team of Claude Code agents (lead, dev, checker, plus optional specialized roles) to plan, implement, test, and iterate until acceptance criteria are met. Human review is optional throughout — the system can run autonomously with retry budgets and task decomposition as escalation mechanisms. Branches bound to this goal range from 3-node minimum (lead/dev/checker) to 20-node production (with security/perf/ops/docs specialization). agent-teams claude-code autonomous end-to-end G6 Produce a research paper Take a research topic or question as input and produce a full research paper — framed question, landscape survey, evidence synthesis, section outline, prose draft, and critiqued final revision. Branches bound to this goal may vary in depth (position paper vs full survey) but share the outcome: a complete paper draft. untagged
