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
- 6
- 需求
- 4
- 贊同
- 497
- 已規劃
- 4,958
- 已發布
- A multi-repository card whose run finds one repository needs no change never completes: the run leaves that repository on the card, and removing it later does not re-run the completion gate
- Design the refined /onboarding and /onboarding/migrate pages
- Every planner-recorded decision card is reported incomplete: the section registry does not know its four required headings
- Planning bug (hosted planner): a childless task laid title-only can never get an executor. Lay does not require one, the `author` tool has no field for it, and the walk only reports the gap while the plan closes as planned
- Design the animated Motir mark for Motir AI activity in the plan overlay
- Decision (planner-recorded) — amendment 5 to the turn-intent decision: no intent classifier; every conversation turn is one grounded read ending in an answer and at most one offer (plan it or log a bug), confirmed by the personMotir AI reads first, then offers to plan or log a bug — one conversation with no turn intents
- plan.py: in `--code-read mcp` mode, stop with a resumable exit when a target repository's code cannot be searched, and tell the person which repository and why
- Core: the planning run pause takes a `code_unsearchable` kind carrying each blocked target repository and its state, and a person's resume answers it
- Planning bug (both planners): a planning phase that cannot search a target repository's code plans anyway. The hosted planner is told "Never refuse to plan over this", so a never-indexed graph left sessions searching for a rule they could not find. Every phase that reads code should stop, tell the person, and resume on their word
- Planning bug (both planners): the post-merge cut fires on a design card's provenance line ("absent on `main` at authoring time"), spawns a stale human "post-merge steps" card, and then retypes the design card itself to `deploy`
- motir-ai: every planning phase that reads code stops when a target repository's code cannot be searched, through a `code_unsearchable` run pause, and resumes on the person's word
- Pages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- Embed a work item in a page as a card — a block card with key, title, live status, type and assignee, written as an `embed` link the work item's Pages section showsPages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- E2E + acceptance video — insert an embedded card, read its five facts, find the page under "Embedded", add a chip, convert the card back to a chip and follow a reassignment, in a clip paced for a humanPages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- Story INTEGRATION gate — the coverage floor over the changed package and app surface, `embed` rows derived on real Postgres on every body write, `manual` rows surviving, a chip and a card read back as one page carrying both sources, the access-safe summary, and RLS / Visitor withholdingPages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- EMBED in the PAGE EDITOR — the card node view in edit and read with its archived and unavailable states, the picker's Embed-as-card choice, the toolbar entry, the chip↔card convert commands, and their strings in `en` and `zh`Pages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- The resolved work-item REFERENCE carries TYPE and ASSIGNEE — the ref-summary DTO, its mapper and resolver, and the picker's candidate rows, so a card shows all five facts before and after a reloadPages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- `@motir/pages` EMBEDS — the `workItemEmbed` block node in the page schema with its `` markdown round-trip on a line of its own, and `extractLinks` deriving `embed` rows on every body writePages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- The acceptance video cannot be published for a run on a bug (or any runnable container that is not a story): the lane refuses with ACCEPTANCE_EVIDENCE_NOT_A_STORY and turns CI red
- E2E — planning against an unsearchable target repository stops with the banner, the link reaches the Codebase page, and resume continues once the code can be searched