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
- requests
- 4
- upvotes
- 489
- planned
- 5,041
- shipped
- (motir-core) REGISTER `decision_confirmation` — the kind and its migration, `parseDecisionRecord` and its defect reasons, the handler, the gate RAISED on a complete `human` decision work item, and Confirm writing `done`Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) AMEND `approval-gates.md` — the DECISION work item's CONFIRM gate: `decision_confirmation` keyed on a `human` decision, its subject the parsed body, its verbs Confirm · Overturn, the record optional, and decisions that ACCUMULATEApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- The DECISION card — a re-plan that changes already-approved work items records WHY, at the epic, and the gate CONFIRMS it rather than recording itApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-meta) `core.md` gate 5's DOOR-is-not-the-room inverse is recorded `one-home:meta`, but the twin's `THE_DESIGN_GATE` (`kind-runnable-lay`) carries it verbatim — the REFINE probes were lower-case against upper-case textSelf-improvement — auto-reported quality bugs
- (motir-meta) run.md stops describing the pull-request Vitest lane as a diff-reached subset — sweep its `ci-affected-tests.md` / `vitest-full` referrers after the revertSelf-improvement — auto-reported quality bugs
- (motir-meta) `MIRROR.map.py --order` is red on `main` at 21 out-of-order pairs against ORDER_PIN 15, and no CI job runs it
- (motir-core) The story's E2E — a fake Sentry issue's evidence shows on the filed bug's Errors row, over `get_work_item` and in its dispatch prompt; a pre-story link is backfilled and enriched once; a refused read leaves the evidence standing — recorded as the acceptance videoProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The story's VITEST gate — the coverage floor over the evidence surface, the read → store → page / MCP / prompt seam and the sweep → enrichment seam on real Postgres, and the guards coverage cannot see (no provider call on a read path; no user-identifying tag anywhere downstream)Production errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The standing BACKFILL sweep in the poll — read evidence for live linked issues never read, and dispatch `author_bug` for monitor-filed bugs never dispatched, within the per-poll context-read budget, idempotent on the link and converging to nothingProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The dispatch prompt carries an ERROR EVIDENCE section for a card with monitor links — `DispatchPromptSource` gains the links' stored evidence, read with no provider call, and a card with no link renders exactly as beforeProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) `get_work_item` returns the card's ERRORS — every monitor link with its stored facts and evidence on the structured payload, through the same read the page renders, with no provider call; the tool's description and `docs/mcp.md` say soProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The Errors section shows the EVIDENCE — each row's evidence block with the exception, the frames, the tags, the request line and the event time, its never-read / no-exception / stale states, and its strings in both localesProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The link KEEPS the evidence — evidence columns on `monitor_issue` and their migration, written by every successful latest-event read (the reconcile visit and the hand-made link) and left standing by a failed one, and the card's error read and its DTO carry itProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The provider seam reads the latest event's EVIDENCE — `getIssueContext` also returns the exception's type and full message, the event's tags with user-identifying keys dropped, the request's method and path with no query, and the event id and time, all bounded; the fake honours itProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- A monitor-filed bug carries its error EVIDENCE on the card — the exception, the in-app frames, the tags and the request line, readable on the page, over MCP and in the dispatch prompt — and bugs filed before enrichment are backfilledProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core · test) No E2E spec asserts that an approval carried to the next green verdict MERGES — `pull-request/auto-merge.requested` runs in the job worker and no spec watches it land
- Reconnecting a reinstalled Sentry organisation leaves its monitored projects on the dead grant — connect adds a second grant row instead of moving the bindings, and the room keeps showing the old one as Degraded
- (motir-marketing) The public `/docs/sentry` guide — what the Sentry integration does, how to connect it, its settings, the permissions it asks for, and how to disconnectProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-meta) 71 MIRROR.md rows key no unit in their home pack and no twin segment, so neither `--check` leg can read them
- (motir-ai) The planner STAMPS `**Found while:** planning <walk target>` onto every bug it files — `log_bug` and `log_planning_bug` both, in code, not by asking the modelSelf-improvement — auto-reported quality bugs