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
- 추천
- 463
- 계획됨
- 4,338
- 출시됨
- (motir-core) `ai:view_plan` gates no view — one key holds AUTHOR and DECIDE, so a custom role granted "can see plans" can materialize a tree
- (motir-core) A titles-first plan cannot be CLOSED — `add_plan_items` demands at least one proposal, and the two-phase path has nothing left to append
- (motir-core) A `modify` proposal renders UN-PARENTED on the plan review surface, so an amendment to an existing card reads as a new card at the project root
- A design child that ships on the PARENT-RUN branch reaches no card — the publisher resolves its target from the BRANCH, which names the container, so the assets are declined and never re-addressed
- (motir-core) The signed-in shell scrolls the DOCUMENT as well as its own `<main>` — the body floor is `100vh` where the shell is `100dvh`, so a browser whose two viewports differ gets an empty band and a second scrollbar
- (motir-core) A DECIDED plan breaks the planning workspace — the rail keeps a LIVE Approve gate and never says what landed, and every accepted card is drawn TWICE on the canvas (holding `main` red since MOTIR-3154)
- The `claude` sandbox image stopped building at 00:53 UTC — `@anthropic-ai/claude-code@2.1.237` shipped WITHOUT its x64 platform packages, and an absent OPTIONAL dependency is not an error
- Planning bug: a card said its mechanism must be MEASURED and then made one hypothesis an acceptance criterion
- Planning bug: MOTIR-3076 named one of its rule's two homes — mirror the mechanism/criterion check into `SHARED_PLANNING_RULES`
- (motir-core) `validate_work_item` has no advisory for a card that is its OWN design blocker — one criterion draws the design, another builds the surface it draws
- (motir-ai) Mirror the design gate's NON-SELF limb into `SHARED_PLANNING_RULES` — `THE_DESIGN_GATE`'s (b) may not be the card itselfSelf-improvement — auto-reported quality bugs
- (motir-core) The canvas card shows `implemented` and `planning` as "To Do" — three hand-copied six-member status literals coerce every unrecognised workflow status to `todo`
- (motir-meta) The design gate's NON-SELF limb — `(b) the type: design subtask` may not resolve to the card under test (`plan-rules/kind-leaf.md`)Self-improvement — auto-reported quality bugs
- Planning bug: a card carried its OWN design as criterion 1 and the UI criteria that consume it as criteria 4–5 — the planning-time design gate has no detector, so a leaf can be its own design blocker
- The settings rail's "← Back to {project}" link returns to `/dashboard`, the retired home — the project home has been `/home` since MOTIR-2654, and the account rail head carries the same stale constant
- The widened scanner stopped one coordinate short — it still abstained on TAG selectors, hiding 381 faint findings and 270 MUTED violations
- Reconcile the 105 `--el-text-faint` references in 33 `design-notes.md` against the swept mocks — the spec half the guard cannot read
- Turn ON the design guard's FAINT arm — `violations()` rules on both inks, and the scanner's last boundary is DELETED rather than reworded
- Faint-ink sweep — AI, notifications, reports, home, shell & brand (211 sites, 15 mocks) plus the six zero-finding areas' notes
- Faint-ink sweep — admin, billing, import, onboarding, epic privacy, audit coverage & the project square: 182 sites across 12 mocks