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
- 6
- requests
- 4
- upvotes
- 517
- planned
- 4,919
- shipped
- 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
- (motir-core) `decisionPageService.publish` — check the card and the page, SEAL the latest version, record the publication, raise or supersede `decision_approval` on an agent card, and move it to `in_review`, every refusal namedPages — 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 VERSION POLICY in `@motir/pages` honours the marks — a save never extends a sealed version, the 100 cap never deletes a sealed or frozen one, and `assertPageDeletable` refuses a page holding a frozen versionPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) `get_page` reads ONE VERSION — an optional `version` argument returns that version's markdown, number, author and sealed / frozen state, refused by name when it does not existPages — 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-PAGE schema — one migration adding `sealed_at`, `frozen_at` and `frozen_by_gate_id` to `page_version` and the `decision_page_publication` table, the Prisma models, and the repository methods that seal, freeze and read themPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) AMEND `approval-gates.md` and `pages.md` for PAGE decisions — `publish_decision_page`, a SEALED version at publish, a FROZEN version at approve, approval terminal at `done` with no pull request, the page subject winning over the file, and the human record as a pagePages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- Pages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- Decisions become PAGES — an agent writes its decision as a page and publishes it, the decision gate asks about that page VERSION, and approving it completes the card and FREEZES the version, with 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