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
- Anfragen
- 4
- Stimmen
- 370
- geplant
- 4.141
- ausgeliefert
- (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
- (motir-core) The dispatched agent's FOUND A DEFECT steps open the bug with the literal line `**Found while:** running <in-flight key>`, key filled inSelf-improvement — auto-reported quality bugs
- (motir-meta) `log-bug.md`'s bug shape opens with `**Found while:** <activity> <card>` — planning, running, verifying, dogfooding or sweeping, replacing the activity-less `Discovered in`Self-improvement — auto-reported quality bugs
- Every bug an agent logs says what it was doing when it found it — "Found while planning MOTIR-X" or "Found while running MOTIR-Y", on all three filing doorsSelf-improvement — auto-reported quality bugs
- A slow Sentry token refresh kills the monitor connection for good — the provider rotates the refresh token, but the 5 s Prisma transaction holding the lock has already expired, so the new pair is never saved
- (motir-core · test) The E2E JOB WORKER installs no mock agent, so anything a job merges, fetches or posts leaves for the real api.github.com — and dies there
- (motir-meta) `criteria-author.md`'s enumeration rule opens "The block above catches an AC that describes the WORLD", but the block above it is the STATE-SET limb — the pack's own "ORDER BELOW IS LOAD-BEARING" note is false
- (motir-meta) Move the six `core.md` gate limbs narrowed for MOTIR-5945 into `criteria-author` / `leaf-author` — gate 2's QUANTITY + COVERAGE, gate 5's state axis, gate 6's executor half, gates 9, 18 and 20's bodiesSelf-improvement — auto-reported quality bugs
- (motir-core · design) THE CONFIRM PORT — the decision's sections drawn as the question, Confirm · Overturn with Overturn's required note, the record link or its absence, the confirmed and overturned record bands, the defect and read-only states, and the To-approve rowApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-meta) 14 `type-choice` rows in MIRROR.md still say "TEMPORARY, twin not landed" after the twin landed, and `MIRROR.map.py --check` cannot see a row whose recorded verdict is stale
- (motir-meta) `type-seam.md`'s *A METHOD IS NOT A PATH* rule ends on a dangling colon — the examples it introduces were routed to `phase-author.md` / `type-runtime.md` and the sentence was never closed
- (motir-core) Design — the EVIDENCE block inside an Errors row: the exception line, the frames list in-app first, the tags, the request line and the event it came from, and its never-read / no-exception / stale-after-a-failed-read states (a delta of MOTIR-5727's `work-item-errors.mock.html`)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-ai) AMEND `session-model.md` — `propose_node` writes a body for a choice or decision task ONLY, and why the limitation still holds for every other proposalApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-ai) Story VITEST gate — a choice and a decision proposed WITH a body through the walk driver, every other kind refused through the same path, the body stored and still deepenable, and the coverage floorApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join