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
- 赞同
- 462
- 已规划
- 4,328
- 已发布
- (motir-core) Measure WHY the fast lane is SLOWER when the system is idle — p95 29.5 s with no refresh running
- (motir-core) STATE and ASSERT the interactive-latency budget for the fast lane
- (motir-core) A `work-item/transitioned` consumer landed 17 minutes late — the starvation mechanism is FALSIFIED, the latency budget is still owed
- E2E — an admin reaches the lessons from settings, reads one, and a non-admin never sees the doorTenant lessons are visible and controllable — a project sees what its planner learned, and decides what it keeps
- Integration test — the seam: permission refused before any upstream call, and no global row crosses itTenant lessons are visible and controllable — a project sees what its planner learned, and decides what it keeps
- motir-core: the lessons list and detail UI, built to the design, with its empty stateTenant lessons are visible and controllable — a project sees what its planner learned, and decides what it keeps
- motir-core: the seam — motirAiClient lesson reads behind a permission-checked server routeTenant lessons are visible and controllable — a project sees what its planner learned, and decides what it keeps
- motir-core: the lesson permission keys — one to view, one to change the library — granted to adminTenant lessons are visible and controllable — a project sees what its planner learned, and decides what it keeps
- motir-ai: GET /v1/lessons — list and detail for ONE project's tenant lessons, pagedTenant lessons are visible and controllable — a project sees what its planner learned, and decides what it keeps
- An admin can SEE the project's lessons — list and detail in AI-planning settings, permission-guardedTenant lessons are visible and controllable — a project sees what its planner learned, and decides what it keeps
- (motir-core) A REFUSED trace is dropped like an over-cap one — register the video's receipt instead of discarding it
- (motir-core) Decide whether a partial acceptance publish is recoverable without re-running the lane — every byte is already in the retained report artifact
- (motir-core) Decision — does a stepped supervisor hold its Inngest concurrency slot while it sleeps? Measure it, and state what the fast lane may rely on
- (motir-core) A coalesced same-key burst does NOT reliably carry the LAST event — six SERIAL awaited sends 0 ms apart on the scheduler's clock ran as event 5
- Design the lessons surface in design/ai-settings — list, detail, empty, retired, and the doorTenant lessons are visible and controllable — a project sees what its planner learned, and decides what it keeps
- Planning bug: the corpus's conservation check cannot express a RESTATEMENT, and its historical baseline cannot conserve post-baseline text — MOTIR-3293 leaves conserve.py permanently red on thirteen packs
- A planning job that WAITS more than 15 minutes in the queue is dead on arrival — renewal cannot rescue it, because there is no live token left to renew with
- `stallDiagnosis` measures the span WE observe, not the window the SCHEDULER opened — a burst that fits on our clock can still miss it
- Approving a 15-item plan 500s — materialize runs in ONE interactive transaction on Prisma's DEFAULT 5s budget, and wires blocked_by edges ONE round trip per link
- `expand_item` and `replan` send NO `targetKeys`, so every expansion in a project shares ONE concurrency key — the project-wide serialization MOTIR-2788 explicitly rejected is what ships