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
- 371
- geplant
- 4.149
- ausgeliefert
- The CHOICE gate — a person PICKS one of N options, each with its why, and what they chose is stampedApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) VERIFY on the DEPLOYED meta tenant — the migration ran, MOTIR-1465 is empty and archived, and a freshly filed planning bug lands in the folderSelf-improvement — auto-reported quality bugs
- (motir-core) The Vitest file selection diffs the PR's merge commit against a STALE base sha — what `main` gained since counts as the PR's own change, so a subset PR falls back to the full suite with no coverage gate
- (motir-meta) MIRROR.md's CITE-limb row names its twin as `phase-author (the same pack)` while the map pairs it with the lifecycle-verb constant on `criteria-author` — the one-cell divergence (`author/epic`) is unrecorded, and `--check` cannot see itSelf-improvement — auto-reported quality bugs
- 8.103 (motir-ai) code_audit and propose_convention read the code graph through the LOCAL-ONLY adapter and never hydrate the snapshot — every audit of an INDEXED repo on a machine without a warm cache measures nothing, grades "unknown" and says "your code meets the convention"
- (motir-core) The affected-test selection now picks a MEDIAN 73% of the suite on real pull requests — past `ci-affected-tests.md`'s own 50% no-go line — because ordinary service files reach 1,000+ specs through the import graph
- (motir-ai) Rung 1 was renamed THE REFERENCE PRODUCT, but the shipped planner still says "mirror product" in rung 3, the ladder's bounds, the decision bar, four walks and discovery — the vocabulary is half-renamed
- (motir-meta) W10 + W10b — a NON-REPRODUCTION obliges the MATRIX not the verdict, and a `shape` advisory's remedy is not always a criterion CUT (`run.md` + `log-bug.md`)Self-improvement — auto-reported quality bugs
- (motir-core · UI) To approve and an OPEN overlay learn the withdrawal live — the held row and count, the overlay's notice with its verbs disabled, then the withdrawn frame (§ 30 Panels 3, 4a, 4b)Self-improvement — auto-reported quality bugs
- (motir-core · UI) The item page and the press draw the conflict — `Conflicts with {base}` on the row, the `conflict` band + cite + fix part in State G, the at-press and stale-tab refusals (§ 30 Panels 1, 2, 5a, 5b, 6, 7)Self-improvement — auto-reported quality bugs
- (motir-core) REFUSE THE PRESS on a conflict before anything is written — the approve-and-merge door reads each member's mergeability BEFORE the decision, `dirty` → `MERGE_CONFLICT` with no `approved`, then withdraws with `conflict`Self-improvement — auto-reported quality bugs
- (motir-core) WITHDRAW the question when a base-branch push makes a member conflict — the `conflict` supersede cause, the whole-gate withdrawal + Implemented hold, and the default-branch push re-evaluation jobSelf-improvement — auto-reported quality bugs
- (motir-core) PERSIST the host's mergeability — `GithubPullRequest.mergeableState`, a provider read, and the three readers that hold a `dirty` member (merge candidate, CI promotion, `motir fix`)Self-improvement — auto-reported quality bugs
- (motir-core) A CONFLICTED pull request still gets a "To approve" merge gate, and the gate accepts the approval — `mergeCandidateHead` reads CI but never the host's mergeability, so the conflict is only discovered by the failed mergeSelf-improvement — auto-reported quality bugs
- (motir-core) The planner-bug folder migration matched NOTHING in production — it keys the meta project on `p."name" = 'motir'` and the deployed project is named `Motir`, so MOTIR-1465 still holds five children, is not archived, and the pointer is unsetSelf-improvement — auto-reported quality bugs
- (motir-ai) The LIFECYCLE-VERB rule never reaches the shipped planner's STORY author cell — it rides `leaf-author`, which `author/story` does not compose, so a story's criteria get no lifecycle-verb checkSelf-improvement — auto-reported quality bugs
- (motir-meta) Land RUNG 1 + GATE 1's rewrites in the written playbook — the second home, or the rules are half-landedSelf-improvement — auto-reported quality bugs
- (motir-core) VERIFY on real runs after the merge — a one-file app PR runs a fraction of Vitest, a force-full PR runs all of it, a package-only PR skips the other package lanes, and a queue entry still runs everythingSelf-improvement — auto-reported quality bugs
- The lesson `kinds` axis knows only CARD kinds — a mistake made laying a project or an onboarding level has nowhere to be filed
- (motir-core) A merge's post-merge status sync TRUNCATES — motir-ai#487 merged with 36 linked work items, 11 transitioned in 14 seconds and 25 stayed at In Review, with every delivery reading `merged` and no error anywhere