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
- Anfragen
- 4
- Stimmen
- 442
- geplant
- 4.442
- ausgeliefert
- 11.4.9 Story vitest gate — coverage floor, the schema→emitter→document→page seams, and the contract guards the spec work owesPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.4.8 The getting-started guide and the published `v1` stability + deprecation policy, mounted in the docs surfacePublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.4.7 The published API reference — the docs surface rendering every operation from the spec, plus the two doors that reach itPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.4.6 The route↔spec conformance guard — three drifts fail CI: a route with no operation, an operation with no route, and a response that does not match its declared schemaPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.4.5 Declare the remaining `/api/v1` operations — projects, sprints, backlog, ready set, workspaces and `/me` — so the document covers the whole surfacePublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.4.4 The operation registry + the OpenAPI 3.1 emitter, and the route that serves the spec — proven on the work-item resourcePublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.4.3 The shared v1 wire-schema layer — the error envelope, the TWO page envelopes, the rate-limit headers and the bearer security scheme, declared oncePublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.4.1 Decision — amend the `/api/v1` ADR: the OpenAPI emission mechanism, the operation registry, the spec's public URL, and the reference surface's home + rendererPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.4 The OpenAPI 3.1 spec as the SINGLE response-schema source + the published API referencePublic REST API — the versioned `/api/v1` integration surface every client shares
- (motir-core) `createTestWorkItem` writes a ZERO-PADDED `position`, so the next TOP-LEVEL create in that project 500s on `invalid order key head: 0` — the exact trap `scripts/plan-seed/seed.ts` warns about in prose
- 11.4.2 Design — the developer documentation surface: the API reference, the getting-started guide, the stability policy, and the two doors that reach themPublic REST API — the versioned `/api/v1` integration surface every client shares
- Mirror the asserted-ABSENCE widening into `SHARED_PLANNING_RULES` — a card whose deliverable is an EDIT must grep its target on `origin/main` (motir-ai)
- PLANNING BUG — a deletion card cannot require a test that CONSTRUCTS the deleted thing to "pass unchanged"; MOTIR-2145's ACs 2 and 3 were provably unsatisfiable together
- Widen the claim-vs-pointer gate to asserted ABSENCE — a card whose deliverable is an EDIT must grep its target on `origin/main` (`plan-rules.md`)
- PLANNING BUG (record) — a card demanded a rule change that had already shipped three days earlier in both homes; it read a prior lesson's conditional "on recurrence, do X" as an outstanding TODO and never grepped X
- (motir-ai) `codeRepoService.recordLocalIndex` / `deleteCoordination` are caller-less after MOTIR-2154 — the SIXTH link, and the one that asks what repo OFFBOARDING is under the fleet
- PLANNING BUG — a WORK card that also PARENTS its mirror has NO legal `motir run` flow: MOTIR-2121 kept its own leaf fields and took a child that was `blocked_by` it
- Mirror the UNVERIFIABLE-precondition limb into `SHARED_PLANNING_RULES` — the shipped planner must not state a live system's state it cannot read (motir-ai)
- The precondition-verification rule needs an UNVERIFIABLE limb — a precondition behind an access path you have no read to may not be stated in the indicative (`plan-rules.md`)
- (motir-ai) `CodeGraphStore.indexRepo` / `CodegraphAdapter.indexRepo` is caller-less — the FIFTH link: the seam's whole WRITE half is now dead while its read half stays live