moooon
Motir
Vibe your whole 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
- 1
- requests
- 0
- upvotes
- 145
- planned
- 1,361
- shipped
- ▸MOTIR-2255The permission MODEL — a catalog derived from the real operation surface, and a role becomes a permission SETdone
- ▸MOTIR-2256Per-domain administrative permissions — split `project:administer` so a role can hold one settings domain without the restdone
- ▸MOTIR-2257Custom project roles — author a role from a base, choose its permissions, assign members to itdone
- ▸MOTIR-2258Permission-gated UI — hide what the actor cannot reach, disable what they cannot usedone
- ▸MOTIR-2282The Roles & permissions screens — the role list a project admin drills into to see what each role can dodone
- ▸MOTIR-2291Close the ungoverned-operation gap — the member-facing permissions, and the gates the guard cannot confirmdone
- MOTIR-2459The ink-contrast SCANNER — an AST guard that can tell a faint GLYPH from faint TEXT, proven on fixtures before it is pointed at the repodone
- MOTIR-2475Sweep `--el-text-faint` off ACTIVE informational text — every site the scanner rules a violation, and its faint arm turned on repo-widedone
- MOTIR-2477Sweep `--el-text-muted` off TINTED surfaces — it clears AA on the white card by 0.04 and fails everywhere else — and turn on the guard's muted armdone
- MOTIR-2481PLANNING BUG — a card said in its own words that the defect count was unknown, then carried a 5-point estimate and a prescribed mechanism built on that unknowndone
- MOTIR-2482The a11y sweeps load 9 routes and load them EMPTY — 108 of 134 files carrying a measured contrast defect sit on routes axe never visitsdone
- MOTIR-2489The ink scanner reads the WRONG ELEMENT three ways — a descendant variant, a conditional `disabled`, and `placeholder:` text — so its verdict can be about an element that is not the one being painteddone
- MOTIR-2493/backlog rows are role="row" inside a role="list" — two CRITICAL axe violations on every populated backlog, and neither role can do its jobdone
- MOTIR-2494Every code block on the public API docs is a scroll region a keyboard cannot reach — 20+ panes of the reference are readable by mouse onlydone
- MOTIR-2495A disabled Input's opacity-50 composites its affix text below AA — no ink choice can fix it, because opacity halves whatever you pickdone
- MOTIR-2496main IS RED — MOTIR-2489 and MOTIR-2477 merged 37 seconds apart, each green on its own base, and their composition reports five muted sites neither PR had to fixdone
- MOTIR-2497The ink scanner walks PAST an element's own white fill — `--el-page-bg` and `--el-card` are the same colour and only one of them stops the surface walkdone
- MOTIR-2499The acceptance-video publish FAILS OPEN — "Published 0 of 2", an ##[error] in the log, and the step + the check both go GREENdone
- MOTIR-2500design/backlog still annotates every row `role="row"` + `aria-selected` — the asset describes the composition MOTIR-2493 removeddone
- MOTIR-2504PLANNING BUG — measured a stale design asset file-by-file inside the right folder, and the surface had three mocks, so the card's own grep would have returned 0 with 17 sites still staledone
- MOTIR-2507(motir-ai) MIRROR the design-area-is-a-FOLDER limb into `SHARED_PLANNING_RULES` — the shipped planner must scope an asset-defect grep to the directory, not the file it openeddone
Showing 21 of 21