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
- 賛成票
- 417
- 計画済み
- 4,269
- リリース済み
- Planning bug: a design amendment settled "nothing else branches" from a RENDERED fixture whose fields cannot co-occur — `tier: null` beside `balance: -4210`, on the org whose tier the debit itself assigns
- Planning bug: a card NAMED its own missing design in prose — "a design ruling is likely owed before the fix ships" — and sealed `ready: true` with no design blocker. A gate is an EDGE, not a sentence.
- Planning bug: a card's context ref named `ProposalRecord.blockedByRefs` as substrate to READ, and the field has never existed — a proposal's `blocked_by` set is dropped at the registry
- Planning bug: MOTIR-4258 asserted every action on the row survived elsewhere, and wrote an acceptance criterion requiring a door it never checked existed — the ⋯'s Expand / Re-plan had none
- Planning bug: MOTIR-4206's Q7 cited Atlassian's rename cap as 3; the documented figure on the cited page is 15
- Planning bug: the 8.3 re-plan moved the public marketing surface to motir.co and never swept MOTIR-1043, whose whole premise was that surface — it kept `(motir-core)` in its title, and had no design blocker, for two months
- 2200.12 (motir-core) Repository reads still key on the RETIRED workspace tier — the project link is an isolation boundary and the workspace rung leaks past it
- 30 (motir-core) `motir doctor` PASSES the agent-credential check on a DIRECTORY — `claude` (and `codex`, `kimi`) probe `~/.claude`-style folders, so "credential present" is true on any machine that ever launched the agent, and always true in the sandbox because the folder IS the mount
- Planning bug: MOTIR-4652 was laid `ready: true` with an acceptance criterion only a SIBLING FOUR HOPS DOWN ITS OWN CHAIN can satisfy — and its "not in scope" section names that sibling
- Planning bug: the corpus asserts the default workflow has NO direct `in_progress → done` edge — MOTIR-1625 ADDED it, with a backfill, and the false claim is what makes a container's unguarded close read as impossible
- Planning bug: a re-plan enumerated a table's RLS arms from two MIGRATION FILES instead of `pg_policy`, missed one, and wrote the resulting false absence into a plan, two cards, a bug and a shipped global lesson
- Planning bug: a bug card's FIX DIRECTION named one refused read and stopped — the next read in the same bound transaction was never checked, and the card sealed with an accepted over-gate advisory it had named a split for
- (motir-marketing) Publish the disposable-container recipe on `motir.co/docs/sandbox` — transcribe the literal the motir-core sibling settled, and drop the keep-the-container paragraphs it makes wrong
- (motir-core) The CLI REPORTS its version on a dedicated field and the server warns below a floor — the only signal that reaches a sandbox already running in the wild
- (motir-core) `motir` tells you when it is OUTDATED and offers to upgrade — with the sandbox's root-owned global prefix handled rather than assumed writable
- (motir-core) Make the sandbox container DISPOSABLE in the in-app guide — the credential moves to a named volume, and `--rm` + `--pull=always` replace `--name` and `docker start`
- (motir-core) Three `packages/cli` specs fail on macOS and pass on Linux CI — they compare an unresolved `join(root, …)` against a realpath'd cwd, so `/var` vs `/private/var` reddens every local run
- (motir-core + motir-marketing) A returning reader's sandbox silently runs a STALE CLI — `motir login` was `Unknown command` on a six-week-old container, because the guide has to tell readers to keep the container the credential is trapped in
- (motir-core · design) A class the TREE styles and Tailwind cannot name is unmeasured — 165 occurrences of 21 across 28 mocks, and `ic` is declared in 60 assets while 3 carry it bare
- (motir-marketing) Bring the PUBLISHED devcontainer recipe on `/docs/sandbox` back into agreement with the one the image ships — the `postStartCommand` line and the paragraph that stops calling the two routes interchangeable