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
- 418
- geplant
- 4.274
- ausgeliefert
- (nextjs-prisma-vercel-starter) Follow motir-core's acceptance-lane rename — every scaffolded project ships a check called `Acceptance video` for a lane that publishes nothingSelf-improvement — auto-reported quality bugs
- (motir-core, manual) Mint `MOTIR_GUARD_TOKEN` — a Motir PAT granted `project:browse` and nothing else — and store it as a repository Actions secret, so the acceptance-lane guard has a credential to bind withSelf-improvement — auto-reported quality bugs
- (motir-core) The run section's empty state renders ONE WORD PER LINE — `max-w-md` resolves to `var(--spacing-md)` = 16px, and the same shadowed scale collapses three more shipped surfaces
- (motir-core) The acceptance-receipt STATUS has no read path — `GET /api/work-items/<key>/acceptance-evidence` is 405, so MOTIR-2770's approved-receipt guard fails open and can never fire, credential or notSelf-improvement — auto-reported quality bugs
- (motir-core) The lane is called `Acceptance video` and no longer publishes one — rename it to the acceptance TESTS and retire the CI publisher, now that the agent uploads the receipt over MCPSelf-improvement — auto-reported quality bugs
- 3937.2 (motir-core) A `modify`'s quick view shows an EMPTY rail — every field but the parent is still gated on `op === 'add'`, so the values a re-plan changes are invisible on the surface that approves it
- 2200.3 A `planned` plan can be corrected and shrunk but never GROWN — AMENDMENT 8 declares `planned` editable and ships two of three verbs, so the second-plan-plus-hand-decline cost it removed survives verbatim for any correction that needs a card
- (motir-core) `Deploy freshness` never prints the report it exists to print — `bash -e` kills the step at the command substitution, so the run summary is empty on exactly the red runs
- (motir-core) `pendingPlansRoute.test.ts` is RED on `main` — MOTIR-4106's fixture closes an EMPTY plan, which MOTIR-4124 had already made a discard, and it blocks every open PR
- SET the legal-document manifest on the moooon cloud deployment, and read it back from the platform — before the reader that consumes it deploysMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- (motir-core) A QUARTER of the acceptance lane's main baselines never run — the concurrency group evicts the QUEUED push run, destroying the per-merge attribution MOTIR-2760 exists forSelf-improvement — auto-reported quality bugs
- (motir-core) `main` has not deployed since 2026-09-01 20:53 — MOTIR-4094 promoted two specs into a lane whose port and whose mock registration order they were never written for
- 3937.1 (motir-core) A `modify` opened from the plan list reads as a NEW card with no content — the quick view hard-codes "New · not yet created" and the review model nulls both bodies for every op but `add`
- (motir-core) A plan that proposes NOTHING still closes to `planned` — it sits in the review queue, renders no decide door, and pauses the project's auto-plan cadence for good
- (motir-core) Drain the acceptance lane back to the in-flight stories — promote or retire the 23 specs sitting in a lane whose own header says its steady state is zeroSelf-improvement — auto-reported quality bugs
- Design amendment — the UNCONFIGURED arm of every motir-core surface that shows a legal link: sign-up, the rail row, the re-consent document rowsMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- 8.11 (motir-core) planningTargetLockGate real-concurrency race times out under loaded Vitest shard
- The shared stripComments strips BLOCK comments first, so a line comment containing `/*` swallows the code below it — every source-scanning guard built on it can go silently blind
- (motir-core) The plan review canvas DRAWS the edge a plan deletes — a marked-going-away arrow is still read as structure, so the graph shows lines that will not exist
- (motir-core) The plan review CANVAS cannot draw a REMOVED edge — a `modify`'s `patch.blockedByRemove` is dropped, so an edge-swap plan renders as a mutual block that will not exist after approve