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
- 賛成票
- 418
- 計画済み
- 4,274
- リリース済み
- 3937.10 (motir-meta) COMPRESSION.measure.py's landing is SELF-REFERENTIAL — an inserted evidence tag scores as warrant in its turn, so performing § Decision 1's own remedy moves the check the WRONG way
- (motir-marketing) /docs/public-address tells customers the pane does NOT show the pointing record — a workaround that becomes a lie the moment it does
- Smoke the live journey on both hosts after the flip — the 308s, /p/* off the redirect bounce, the CORS answer, and the signed-in surfacesMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- Set the public-site origin on the deployed motir-core — MOTIR_PUBLIC_SITE_URL and MOTIR_DOCS_URL, read back from the platform (manual)Motir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- Verify every external registration that names an origin — Google OAuth, Better-Auth trustedOrigins, and the CLI / MCP defaultsMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- 8.68 (motir-core) `mockStateInkScan` grounds an element on the nearest OPAQUE ancestor and SKIPS a translucent one — a lightbox's white chrome measured 1.07:1 against the page behind its 80% scrim, where it is 6.90:1
- The pointing-record variables are unset on app.motir.co, so the settings pane still shows only the ownership TXT in production
- 3937.7 (motir-meta) COMPRESSION.measure.py's worst cell goes 14 lines over its DERIVED landing after MOTIR-4201's terminology sweep — "card" -> "work item" widened all five of its composed packs at once
- 3937.9 (motir-ai + motir-core) workItemTypes.ts's WORK_ITEM_TYPE_GLOSSES still teaches "card" via THE_TYPE_VOCABULARY interpolation — fixing it needs a motir-core ADR amendment FIRST
- Two green PRs can merge into a red `main` — nothing requires a branch to be up to date, so a stale check decides the merge
- 8.67 (motir-core) Two design mocks paint ink OUTSIDE the token layer, and the new state-ink arm can only COUNT them — 18 sub-AA elements under a hover tint with no token to swap
- The settings pane never shows the DNS record that POINTS a custom domain at us — only the ownership TXTMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- (motir-ai) Sweep `lessons.base.ts` part 2 — rows 167–238 (709), same masks, same `categories` invariant
- (motir-ai) THE GUARD — `\bcards?\b` over `composePlanningRules()` for every legal cell returns 0, the masked senses and every `categories` key unchanged
- (motir-meta) RECONCILE `COMPRESSION.conserve.py` with the swept packs — run it first; its output decides the deliverable
- (motir-ai) Sweep `SHARED_PLANNING_RULES` part 2 — `phase-author` and every `kind-*` / `type-*` tag (414)
- (motir-ai) Sweep `lessons.base.ts` part 1 — rows 1–166 (718), the four text fields only, every `categories` key byte-identical
- (motir-ai) Sweep `SHARED_PLANNING_RULES` part 1 — the segments tagged `core` / `phase-lay` / `phase-conversation` (321)
- (motir-ai) MIRROR the withdrawn carve-out into `BANNER_AND_TERMINOLOGY` — the shipped planner's home of the same rule
- (motir-meta) Sweep the remaining 15 COMPOSED packs (315), and give the 19 non-composed files an explicit disposition