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
- 558
- planned
- 5,460
- shipped
- (motir-core · design) STATE-variant utilities are inert in 3 mocks — 104 occurrences, including a `placeholder:` ink that paints with no interaction at all
- (motir-core) `render-design-mock.mjs` exports the LIGHT board only — a dark export silently keeps drawing the old design, and no guard reads `*.dark.png`
- 8.90 (motir-core) Every pull-request row reads "linked manually" — the flag records a distinction MOTIR-3674 deleted, and its only writer is now the agent's own `link_pull_request`
- (motir-core) The approval-gate ADR — record what a gate IS, its routing and authority, its audit trail, how a third kind registers, and the line against Story 9.2Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core · design) 365 rules across 87 hand-written mocks are declared and carried by NO element in the whole design tree — the direction MOTIR-4150 was filed for, now counted
- (motir-core) A repository MOTIR HOSTS is drawn under `From your organisation` and counted as `yours` — the room reads `github_repo` by WORKSPACE and never consults `hostOwner`
- (motir-core) The landing owner-guard reads COMMENTS, so a link whose intent lives in its ACCESSIBLE NAME is invisible to all three scans — the shape that let the brand mark keep `/dashboard`
- (motir-core · design) STRUCTURAL `[&_…]:` utilities are inert in 8 mocks — 500 occurrences, and 452 of them size a nav icon that renders at 24px instead of 18px
- (motir-core · design) `text-(--el-text-faint)` means two different colours depending on the mock — 5 assets declare it as `--el-text-secondary`, and the ink guard reads the declaration
- (motir-core) `get_project_state` reports `code connected: false`, and the repo picker offers nothing, for every workspace of an organisation OTHER than the one the App was installed from
- (motir-core) The project room’s two sections mis-state what they hold — an empty `From your organisation` and copy that still names the WORKSPACE
- (motir-core · design) Design mocks USE arbitrary-value utilities their own shim block never DECLARES — 131 inert utilities across 8 assets, and no guard looks in this direction
- 26 (motir-core) The planning overlay's canvas never groups the work items that are in no epic — MOTIR-3490's "Not in an epic" node and its "+ N more" tile were opted into at ONE of five `buildWorkItemLevel` call sites, and the overlay is not it
- (motir-core) Settings → Organisation → Git offers `Connect GitHub` to an organisation that IS connected — the connection card asks a WORKSPACE question, and `github_installation` has no org read arm
- (motir-core) Correct the RECORD that made the three call sites look right — `20260906000000`'s first-arm guarantee is false, and the correction goes where a reader meets it
- (motir-core) The unlinked-PR check calls a SIBLING-workspace repository "not planned" — bind the org on `pullRequestLinkCheckService`'s `project_repository` read
- (motir-core) Attribute a SIBLING-workspace repository — bind the org AND take `organizationId` off the repo row, in the CI meter and the runner provisioner
- (motir-core) A repository linked from a SIBLING workspace is invisible to every SERVICE-context read of `project_repository` — CI minutes go unattributed, runner provisioning is refused, and the link check reports `not planned`
- (motir-core · test) Playwright's retry is INERT for three cloud specs — the seed creates a FIXED-email user, so attempt 2 dies in setup with `DuplicateEmailError` and REPLACES attempt 1's real failure in the report
- (motir-core) A repository nobody has pushed since MOTIR-4724 shipped reads `Current` FOREVER — the label claims currency the state cannot support