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
- solicitudes
- 4
- votos
- 419
- planificados
- 4272
- publicados
- (motir-core) Make the NINE in-repo devcontainer recipes and the guide's published recipe RUN the agent-config setup — `postStartCommand`, and the sentence that says why the VS Code route needs it
- (motir-core) Make the sandbox image's agent-config setup RE-RUNNABLE and reachable from a shell that never went through the entrypoint — `motir-sandbox-agent-config` + the login-shell hook
- 29 (motir-core + motir-marketing) The sandbox's devcontainer route BYPASSES the image entrypoint — `overrideCommand: true` replaces `motir-sandbox-entrypoint`, so `CLAUDE_CONFIG_DIR` is never exported and the agent falls back to the read-only `~/.claude` it can never sign in to
- 2200.8 (motir-core) A proposal's ROW pin `targetRepositoryRef` has NO reader anywhere in motir-core — the one pin that lifts the repeated-role ceiling is persisted and dropped at approve
- (motir-core) SCHEMA — the `ApprovalGate` table, its migration, its RLS under the `motir_app` non-bypass role, and the repository leafApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- 27 (motir-core) A card the plan RE-PARENTS onto a level arrives with NO dependency edges — the review canvas seeds its arrows from the level's CURRENT children, so a committed edge appears only after approve
- (motir-core) AMEND the approval-gate ADR — the two WORKFLOWS, the `approved` status, the third kind, relationship-or-admin authority, and the pin re-keyed onto the subjectApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core · design) An un-declared PLAIN class is unmeasured in every direction — 4419 occurrences across 46 mocks, and the predicate that would report them cannot tell a utility from an icon library's identity class
- (motir-core) `item-detail-reads`'s `gate` is ONE module-level promise resolved by the first `afterEach` — so from case 2 on `deferred` IS `immediate`, and the "actually concurrent" assertion cannot fail
- (motir-core) The code-context design still draws the button and the connect row that MOTIR-1768's re-scope moved OFF the page — and §3 instructs a re-point that would break a member's door
- (motir-ai) The SHIPPED planner still cannot propose a repository SET — `MODIFY_PATCH_KEYS` and the `author` field set carry only the singular `targetRepo`
- (motir-core · design) The correspondence guard's `isArbitrary` predicate cannot see a PLAIN inert variant — 93 occurrences survive direction (A) reaching zero, on the argument that a mock inherits a stylesheet it does not have
- (motir-core) A repository SET cannot be PROPOSED — every plan-authoring door takes only the singular `targetRepo`, so a multi-repo card must be patched after approval
- (motir-core) The acceptance-lane guard fetches one story at a time, SEQUENTIALLY, against app.motir.co inside a 15 s timeout — so it gets slower with every acceptance spec and now reds the merge queue
- (motir-core) `item-detail-reads`'s FIRST case pays the whole page module graph — 4.2 s of a 15 s budget — and a case that times out leaves its page call in flight, consuming the NEXT case's `mockResolvedValueOnce`
- (motir-core) `item-detail-reads` holds two sibling assertions about the same property that tolerate DIFFERENT read sets — one is order-dependent and fails only under full-suite load
- (motir-core) The ORG inventory lists a repository MOTIR HOSTS as the organisation's, unmarked — and its `Disconnect` sends the reader to an installation the repository is not in
- (motir-core · design) The two COMPILED-build mocks carry 1128 dead rules — decide whether machine output is excused by a predicate or swept like the rest
- (motir-core) The E2E SESSION HELPERS — `signUp` settles on the onboarding entrance and `createFirstProject` is retired, fixed AT THE HELPER for all ~15 specs that go through them
- (motir-core) Amend `docs/decisions/home-scope.md` §2.2 and §2.3 ON THE RECORD — the premise both reasoned from is the thing this story removes