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
- 要望
- 4
- 賛成票
- 420
- 計画済み
- 4,274
- リリース済み
- The public project SUBJECT gets a route — app/api/public/p/[identifier], the one endpoint the page's own subject has never hadMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- Vitest gate (motir-core) — the public read contract, the anonymous posture per route, and both arms of the origin seamMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- The public origin motir-core EMITS — the follow-digest links, and what app/sitemap.ts contains once nothing public is servedMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- Decision (ADR) — one origin per audience: motir.co is served by motir-marketing over motir-core's public API, and motir-core keeps no public pagesMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- `app.motir.co/robots.txt` 404s — motir-core ships a sitemap, JSON-LD and canonicals on its public surface but no `app/robots.ts`Motir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- motir-core becomes an application plus a public read API — the project-subject route, and the contract a second repository depends onMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- (motir-core) Bump `@motir/design-system` to 0.1.2 — the commit `design-system-v0.1.2` is cut fromMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- motir.co's footer ships `--el-text-muted` on `--el-surface-soft` — 4.34:1 on EVERY page of the site, and `aaMatrix`'s PAIRS carries that ink against the card but not against the band
- Global lessons added since the day-one seed batch do not RETRIEVE — two rows queried near-verbatim are absent from the ranked set, and every global row `search_lessons` returns carries a `cmr11*` id
- Planning bug: MOTIR-3965 put a human MERGE between two of its own acceptance criteria — a release authored as one card, sized for the publish alone
- The base palette's `implemented` status dot is 2.66:1 on the card it sits on — under 1.4.11's 3:1, and the guard that would catch it skips the base palette by construction
- Scoped design previews are not ISOLATED — 69 `[data-style='X'] <descendant>` material rules cross the nesting boundary, so 10 of 11 style previews wear the ancestor's style
- A plan can be CLOSED into the review queue in a state approve will refuse — `final: true` runs no whole-graph check, so the reviewer discovers a dangling ref by clicking Approve
- The `/design` asset draws muted captions on `--el-surface-soft` — 4.34:1, under AA in the default palette, and its own AA sweep never measured the pairMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- The product calls a work item a "card" in ~14 shipped `messages/*.json` strings (and their `zh` twins) — the noun users read is not the product's noun
- (motir-core) `sandbox-staleness` has failed EVERY scheduled run for 17 days — the tripwire is right: `packages/cli` is 30 commits past `cli-v0.3.0` and the published sandbox image is what users pull
- 8.56 (motir-core) Every deploy re-salts the Server Action ids — a tab open across a release 404s on EVERY write, and the quick-view rail shows the change as if it saved
- A scoped `StyleVignette` shows the ACTIVE palette, not its own — `data-appearance-scope` is missing, the `motir` base has no block, and the nine palette DARK blocks are compound selectors a nested scope cannot match
- (motir-core) Every E2E leg DISCARDS the shared `.next` artifact and rebuilds the app — `webServer.command` runs `next build` unconditionally, 110 s of it re-running TypeScript the `TypeScript` job already ran
- (motir-core) Turn the Vitest leg count 8 → 12 — the dial MOTIR-3912 deferred until the balanced lane had been measured, which it now has