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
- solicitações
- 4
- votos
- 486
- planejadas
- 4.341
- entregues
- Faint-ink sweep — projects, public projects, settings & the repository set: 274 sites across 17 mocks
- Faint-ink sweep — the planning surfaces (boards · backlog · roadmap · sprints · triage · ready · estimation): 332 sites across 26 mocks
- Faint-ink sweep — the developer surfaces (cli-guide · coding-convention · api-docs · mcp-server · cli-connect): 342 sites, and one GENERATED mock
- Faint-ink sweep — design/work-items/: 404 sites across 25 mocks re-inked off `--el-text-faint`
- The design tree's `--el-text-faint` population — 1745 sites across 101 files, an ink that clears AA on NO surface
- (motir-core) A DECIDED plan stops flagging itself out of date — `computePlanStaleness` gains the `planned`-only rule its other two callers already write by hand
- (motir-core) Story E2E — a DECIDED plan still shows its cards: `plans-review.spec.ts` amended to assert the outcome ALONGSIDE the proposals
- (motir-core) The planning-workspace canvas KEEPS its decided overlay — `review` survives approve and discard instead of being nulled
- (motir-core) The plan-detail canvas draws a DECIDED plan — one node per approved `add` on its materialized work item, in the treatment the design decides
- (motir-core) A declined plan KEEPS its proposals — `declinePlan` stops deleting, and the review model keys a materialized `add` by its work item
- (motir-core) A DECIDED plan's cards vanish from the planning canvas — decline DELETES every proposal row, approve hands the pane to the establish step, and no node style says accepted or declined
- (motir-core) `projectSquareRanking.test.ts` rides the global 15s `testTimeout` while its own CI runtime swings 14s → 32s — a timer bomb, not a slow runner
- Provision the attribution trust pair on Fly — the planner's token id at the gateway, and GATEWAY_RUN_ATTRIBUTION_SECRET on BOTH apps
- (motir-ai) Mirror W2/W3/W4 into `SHARED_PLANNING_RULES` — the measurement arrow, the cross-parent edge, and the story title as a checklistSelf-improvement — auto-reported quality bugs
- (motir-core) `/api/v1` gained an endpoint without moving `V1_CONTRACT_VERSION` — `uploadWorkItemAttachment` ships under `1.11.0`, the number a client reads off every response header
- (motir-meta) Four trigger WIDENINGS the planner-bug home proved owed — the advisory tier, the measurement arrow, the cross-parent edge, and the story title as a checklistSelf-improvement — auto-reported quality bugs
- (motir-core) `design/ai-planning` Part VI — the DECIDED plan-review surface: the accepted and declined node treatments, and what the canvas pane holds after approve
- `validate_work_item` has no advisory for a leaf over the ESTIMATION GATE — a 13 SP / 600 min `coding_agent` card returns `valid: true` with nothing in `advisories`
- The plan canvas never draws a committed card — the roadmap DTO is CAST to canvas nodes instead of built, so every sibling paints nothing, nothing is drillable, and the "Plan" crumb strands the reviewer on a blank canvas
- The plan-review diff line renders a RAW MESSAGE KEY for a sizing change — `planReview.field_storyPoints` / `field_estimateMinutes` were never added to the catalogs MOTIR-1532 taught `buildChanges` to emit