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
- solicitações
- 4
- votos
- 499
- planejadas
- 4.367
- entregues
- (motir-core) A `deploy` card can reach `done` with its artifact nonexistent — the one card type exempted from the authoring gate has no close-out gate either
- (motir-core) `shared-store.test.ts`'s atomicity case cannot tell an ATOMIC store from one that FAILED OPEN — 12 concurrent requests, 2 hit the 250ms store deadline, all 12 served
- The platform starter's own maintenance — keeping the vendored copies, CI lanes and scaffold-time defaults true as motir-core movesEpic 1: Foundation
- (starter) `Cleanup preview deployments` fails on EVERY PR close — the repo has no Vercel config, so a workflow with nothing to do red-lights every merged PR
- (motir-meta) `core.md` has two dangling section stubs left by the split — a promised gate section with no gates, and a "load-bearing contracts:" list that is missing
- `resolveLastActiveContext` reads `project` under a USER-only context — no arm admits it, so every sign-in silently lands on the wrong workspace
- (starter) The vendored acceptance uploader still PUTs via `@vercel/blob` — the mint has returned an S3 presigned URL since MOTIR-2389, so the first adopter to write an acceptance spec gets a lane that cannot publish
- DECIDED — status derivation becomes a recompute (no exemption for the planner-bug home): a parent returns to To Do when a new open child is added
- PLANNING BUG — 8.5.10 planned a platform-admin design that Epic 10 shipped 3 days later, and nothing re-read it for 52 days; the SAME collision is live and unsettled between 8.5.11 and 10.1.3
- Planning bug: a mirrored constant MOVED and nothing swept the referrers — and the stale pointer RESOLVES, so it manufactures a false absence
- Planning bug: MOTIR-2872's real blocker was wired `relates_to`, and its advisory landed in the tier guard #4 tells you to skip
- Planning bug: a partition hedged the axis it had an instrument for and ASSERTED the one it did not — "issued by application code, not a test fixture" was wrong for 50 of 174 rows
- `COMPRESSION.conserve.py` cannot express a rule ADDITION — its per-pack baseline is a fixed historical commit, so any pack that gains a rule after its first compression goes red forever
- Planning bug: the FOURTH line-target miss, and the re-shape — `--check` compares against a hand-typed constant instead of deriving the floor from the corpus
- Three planning rules have no counterpart in `SHARED_PLANNING_RULES` — cardinality, the repeat-defect trigger, the suppressor limb
- Planning bug: eleven cards were cut on a measurement the SAME pass created a card to replace — and one target survived only in a title
- PLANNING BUG — a story titled "the tenant reads" decomposed into fixtures only, and its adjudication card was given an AC that required it to fix the class it was scoped to merely CATALOGUE
- Planning bug: the app-layer cards were declared independent of the fixture batches, but their verification RUNS ON them — the dependency arrow points the wrong way
- Planning bug: the repository pin was planned as a SINGULAR — the cardinality rule's own standing instance, missed on the one card that was entirely about that field; and the story shipped no E2E
- Planning bug: a card's acceptance number was inherited from an automated projection whose detector counts the rule's own heading as removable evidence