moooon
Motir
Vibe the project. Bring an idea — Motir's three AI layers plan it, track it, and ship it, end to end. You're looking at Motir, built in Motir.
- Vibe Project
- Open Source
- AI Agent
- AI Loop
- 5
- 需求
- 4
- 赞同
- 416
- 已规划
- 4,241
- 已发布
- The SUBJECT axis — `pack(phase, kind, type, subject)` derived at `lay`, a vocabulary the PACK TREE defines, and `data` · `jobs` · `llm` · `mcp` as its first four membersSelf-improvement — auto-reported quality bugs
- (motir-ai) The key-space migration DEADLOCKS — the backfill copies without deleting, so `legacy_project_keyed` can never reach zero and MOTIR-5127's refusal disarms the offboarding backstop for ever
- 2200.38 (motir-ai) NOTHING typechecks `tests/` or `scripts/` — `tsconfig.json` includes `src/**` alone and CI has no typecheck job, so 644 type errors across 109 files sit unseen
- 2200.35 (motir-core) A workspace-cap refusal reaches the user as a 500 — `createWorkspaceAction` catches nothing, so a typed `EntitlementExceededError` carrying the plan limit and its upgrade key escapes as a server fault
- APPROVE A DESIGN THAT HAS NO PULL REQUEST — the gate contract, the record, the decide door, the frame, and approval as the TERMINAL actApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Story vitest gate — the coverage floor, the decide-door → status-effect seam, the gate's concurrency guard, and the ONE-LANGUAGE guard that the control is sharedApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core · design) The lesson-library asset still draws `phase skeleton` / `phase deepen` — 6 chips across 5 panels and the PNG, describing a badge the product no longer renders
- (motir-core) design(work-items) — `provenance.mock.html` gains a THIRD group: Planning · Implementation · Subject, in the same read-only disclosureSelf-improvement — auto-reported quality bugs
- 2200.25 (motir-core · design) `design/repository-set/` draws the REFUSED arm — what the created panel says when the account is known and GitHub said no
- (motir-core) The runner-image lane is blowing its 20-minute ceiling REPO-WIDE — it stopped restoring its cache around 07:15 and now rebuilds cold on pull requests as well as queue entries; `changes` failing open on `merge_group` is why even a docs-only diff pays it
- (motir-core) Story E2E (Playwright) + acceptance video — a published design waits, the control clears it, and the card it was blocking becomes readyApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-ai) A lay session's DECLARED level does not bind its proposals — `propose_node` accepts any `parentRef`, so a session opened to lay one level may propose into another, and nothing refuses it
- (motir-meta) The runbook MIRROR of MOTIR-4774 — the SEARCH THE LESSONS twin says `lay` / `author`, the three "the lesson axis keeps the old names" notes are deleted, `run.md` tells a local planner to pass its own phase, and the five guards stay green
- (motir-ai) `main` is RED a SECOND way — `authorTitleOnAProposal` carries a SEVENTH subtask-under-a-committed-`epic` fixture, the class MOTIR-4631 corrected six of, because #452 was cut before #450 landed
- (motir-ai) MOTIR-4638 left a THIRD constant behind — `THE_GATE_RECONCILE_CONTINUATION` still routes a wrong committed TITLE to "a re-write in that work item's own authoring session" and omits `retitle_node` from the reconcile palette, so GATE 1(b) contradicts STEP 1 and the reconcile rule in the same `phase-lay` prompt
- (motir-ai) An ANCHORED walk's lay session cannot DECLARE its own level — `layTargetKind` resolves a committed target from the grounding, the `lay` executor resolves an id against `proposed` only, so `lay(kind, <a real key>)` is refused "not a known proposed node"
- (motir-ai) `main` is RED — `onboardingIsAFactAboutHistory` re-derives the AUTHOR discriminator from the bare literal, which MOTIR-5060's one-place guard forbids; two PRs green apart, red in sum
- 31 (motir-core) A card the plan RE-PARENTS AWAY from a level is still drawn as an ordinary committed child of it — the level's membership is the FOURTH fact `mergePlanLevel` inherits from the committed read and never revisits
- (motir-core) The lesson MCP tools and the lesson library speak `lay` / `author` — `add_lesson` / `search_lessons` enums and descriptions, the API-docs schema, and the settings badges follow the renamed axis, accepting the old names inbound for one release
- (motir-meta) `MIRROR.map.py --check` has been RED on `main` since before MOTIR-4382 closed — two `one-home:ai` rows have never been adjudicated, and the three cards that owned the queue are all `done`