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
- 0
- Stimmen
- 369
- geplant
- 4.052
- ausgeliefert
- motir-ai `Coverage (planning pool)` fails at random: the branch threshold on `planJobService.appendProgress` depends on a real concurrent-append race actually happening
- (motir-ai · test) The planning-pool peer-wake seam test is flaky: machine B's start-up claim tick can land while queue(4) is inserting and take jobs meant for machine A
- (motir-core · design) To fix keyed by RUN — one Workbench entry per dead or red run with the cards it carries under it, one repair, a count of runs, and the per-card tag and banner pointing at that entry (en + zh) — deltas on `design/workbench/` and the To fix tag-and-banner design
- Design — the warm-orange touches in the default Motir palette: which `--color-*` / `--el-*` roles warm up, light + dark, measured against every hue they sit beside, drawn on the real board, chips and `--el-*` showcase (motir-core)
- Hosted planning is refused at the gateway for every audience — the seeded planner model `claude-opus-5-5` is on neither the planner token's allowlist nor the Anthropic channel
- (motir-ai) 15 of motir-ai#643's failures come from its MIGRATION, not its fixture — rate tests pin the rates in force for models the sync re-prices, and two pin decisions the sync now contradicts
- (motir-ai) The first schemaVersion-4 rate sync (#643) fails Vitest and five coverage jobs — rate tests still treat `tests/fixtures/upstream-prices.json`, which the sync rewrites, as a frozen 4-model v3 input
- Monitoring acceptance spec fails when the database ping also reads 42 ms
- (motir-core) The CONFIRM PORT takes a page as its record — Choose page, the published version shown with its number, and the frozen state after Confirm, per the delta mocks (en + zh)Pages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) Playwright acceptance E2E + VIDEO — an agent's decision published as a page waits for a person, Approve completes the card, and a later edit leaves the frozen version intactPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-ai) `planningRulePacks.ts` — the `decision` bar's document is a published PAGE, not a `docs/decisions/*.md` file in a mandatory pull request (the twin of the runbook pack)Pages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) Story VITEST gate — the coverage floor over the seal, freeze, publish and page-resolver modules, and the publish → approve → freeze seam on real Postgres with a concurrent savePages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-meta) `type-decision.md` — an agent ships a decision as a published PAGE, its gate freezes the approved version, and the repository pin is context rather than the record's homePages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-meta) `run.md` step 5b — a decision run writes and publishes a PAGE and opens no pull request, and a parent run stops at a decision child's gate without a PR of its ownPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) The prompt's CONFIRMED DECISIONS include approved decision PAGES — each by page id and frozen version, with the `get_page` call that reads itPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) The dispatched DECISION LANE writes a page — `create_page` / `update_page`, then `publish_decision_page`, with no branch and no pull requestPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) The decision PORT renders a page version — the Development frame, the approval overlay, the item page, the To-approve row and the History panel's Frozen tag, per the delta mocks (en + zh)Pages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) The human decision's RECORD is a page — `decision_confirmation` reads the card's published page version as its record and FREEZES it at Confirm; attachment records keep renderingPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) The PUBLISH DOORS — the `publish_decision_page` MCP tool in every home a new tool has, with `CLI_TOKEN_GRANT` carrying its key, and the REST route the confirm port's page picker callsPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) `decision_approval` asks about a PAGE — the page resolver beside the file one, a published page wins the subject, and Approve FREEZES the version and writes `done`Pages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history