8.3 Marketing site + brand mark

8.3.16 The public design showcase at motir.co (`/design`) — live Style × Palette × Type over the published `@motir/design-system` (motir-marketing)

8.10.1 Decision — launch shape + what Motir exposes publicly

Captured planning-mistake bugs

Plan in Jira

Decide the shape axis's DENSITY SCALE — what padding / height tokens exist, so the own-box escapes have somewhere to go

`app.motir.co/robots.txt` 404s — motir-core ships a sitemap, JSON-LD and canonicals on its public surface but no `app/robots.ts`

Decision (ADR) — one origin per hostname: which host answers for each public surface, and what becomes of motir-marketing

Repoint the motir.co apex, issue the certificate, and update every external registration (manual)

8.3.9 Early directory listings — G2 / Product Hunt / GitHub (manual)

8.3.8 Trademark clearance search for the Motir brand mark (classes 9 + 42)

Epic 9: Native AI coding (hosted agent execution)

8.10 Take Motir public — the build-in-public launch

Global lessons added since the day-one seed batch do not RETRIEVE — two rows queried near-verbatim are absent from the ranked set, and every global row `search_lessons` returns carries a `cmr11*` id

Build-in-public is a CLOUD feature — MOTIR_CLOUD gates /explore and /p/*, and a self-hosted Motir is single-tenant

Epic 10: Platform administration & operations

Plan in other PM software

The own-box PADDING / HEIGHT axis of the shape swap — decide the density scale, then route the 447 escapes onto it

Sweep the `Modal.Body`-bypass class app-wide — measure every `<Modal>` call site that owns no scroll container, fix the ones that clip, and add a guard so there is no fourth instance

(motir-core) The re-plan submit SETS `context.replanTrigger` — MOTIR-3324 ships a consumer that nothing populates

The token-permission picker's design asset is THREE rows behind its measurement — re-measure the two-column split, or say the numbers are no longer drawn

(motir-core) The code-graph refresh costs ~35 minutes to re-derive a graph that measures 32 seconds — index ONCE per repo, and reach `codegraph sync`

(motir-core) A merge reaches production hours late — `Deploy to Fly` sits behind the whole verification matrix a second time, and a merge burst leaves only the newest run

Motir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)

WATCH — DeepSeek V4-Pro official release: re-verify the planner's DEFAULT model (pricing, id, the tool_calls workaround, Responses support) when it ships

(motir-meta) Land RUNG 1 + GATE 1's rewrites in the written playbook — the second home, or the rules are half-landed

(motir-meta) W6 — the third limb's other half: NAME WHAT ANSWERED, when the address comes from our own config (`kind-leaf-deepen.md`)

(motir-meta) W7 + W7b — two `phase-deepen.md` widenings: a lifecycle VERB is a precondition, and a CHARACTERISED set owes its histogram

(motir-meta) W8 — the INWARD limb of a decision's close-out: an ADR's own *Consumed by* list is the worklist (`core.md` + `run.md`)

(motir-meta) W9 — a defect card's MECHANISM owes the DISCRIMINATING measurement, and that measurement is the FIRST acceptance criterion (`kind-bug.md`)

(motir-meta) W10 + W10b — a NON-REPRODUCTION obliges the MATRIX not the verdict, and a `shape` advisory's remedy is not always a criterion CUT (`run.md` + `log-bug.md`)

Planning bug: a `blocked_by` wired to an ARCHIVED predecessor gates nothing — the card sealed `ready: true` against a retirement that has not shipped, and the advisory that named it was never read

Planning bug: an acceptance criterion quoted durations from a run where the jobs were SKIPPED — a skipped job reports zero, not an absence, and the ceiling it implied would have failed a green run

Planning bug: the 8.3 re-plan moved the public marketing surface to motir.co and never swept MOTIR-1043, whose whole premise was that surface — it kept `(motir-core)` in its title, and had no design blocker, for two months

Planning bug: a `coding_agent` card carried a criterion only a BROWSER SESSION can discharge — minting a `CLI_TOKEN_GRANT` token is cookie-session-only by design, and no gate noticed

Planning bug: a bug card filed mid-run asserted an ORM reader nobody grepped, and promoted that mechanism into two acceptance criteria that cannot be satisfied

Planning bug: a copy card scripted a PUBLIC marketing claim about an unshipped capability — no gate checks a customer-facing sentence against the product, because the precondition rule only asks whether the card can be BUILT

Planning bug: MOTIR-3868's AC 1 required a diff against `work_item.targetRepoRole`, a column retired 11 days earlier — the enumeration was verified, the column behind it was not

Planning bug: the `AgentRun` collision was RECORDED and not removed — the name shipped into the plan anyway, and a year's drift made it three-way

Planning bug: MOTIR-3892 "measured" a closed PR from its CARD — #332 never split the constant, changed no test, and turned no guard red

Planning bug: a story was authored with three children whose acceptance criteria can only be met after the story's own merge and deploy — the container had no exit, and every gating signal read green

Planning bug: a story ACCEPTANCE CRITERION had no child that owns it — MOTIR-3870 pre-dates MOTIR-3891 and was scoped against a different parent

Planning bug: a card planned a live-run indicator on the READY list, whose membership predicate excludes every item that has a run — and removing it exposed that a run had no general door at all

(motir-core) `sandbox-staleness` has failed EVERY scheduled run for 17 days — the tripwire is right: `packages/cli` is 30 commits past `cli-v0.3.0` and the published sandbox image is what users pull

(motir-core) `roadmap-flow.spec.ts`'s seed races the status-derivation job — the SECOND spec in this class, and `retries: 1` made the run green

Mirror the SUM re-cut into motir-meta — retire `kind-leaf`, cut `phase-deepen` on its subjects

8.10.2 Curate Motir's own public project — Overview, tagline, tags, README, epic-privacy

Plan in Linear

motir.co answers for the public reading surface — /explore, /docs and the crawl directives move to the brand host

Design — one public chrome for motir.co: the landing, /explore, /docs and /legal under a single header, nav and footer

8.10.3 Take Motir's project public + smoke the public surfaces on motir.co

Plan in Plane

Public project pages join the brand host — /p/* answers on motir.co, and leaves the session's origin behind

One robots.txt and one sitemap.xml for the whole host — and publicSiteOrigin() stops delegating to MOTIR_BASE_URL

8.10.4 Launch-day execution — Product Hunt / Show HN / GitHub / #buildinpublic / waitlist

Plan in TAPD (Tencent 腾讯)

Customer-owned addresses for a public project — per-tenant subdomains + custom domains

8.10.5 First changelog posts + "follow the build" announcement copy

Plan in Yunxiao 云效 (Alibaba Cloud DevOps) — incl. the non-OAuth credential substrate

Plan in Feishu Project 飞书项目 (ByteDance / Meego)

301 app.motir.co/{explore,docs,legal}/* and / to motir.co — plus the in-code sweep of every absolute-URL reader

Plan in Huawei CodeArts Req 华为云 (ex-DevCloud / ProjectMan)

Vitest gate (motir-core) — coverage floor over the moved surface, the host/origin seams, and a guard that every app/(public) segment has a declared host

Playwright E2E + acceptance video — the whole public journey on one host, and the old app-host paths redirecting

moooon's legal documents leave motir-core — /legal moves to motir-marketing, and the core keeps configurable legal links

THE CUTOVER — the apex moves, the certificate is issued, and every external registration follows

(motir-ai) Mirror W6 into `SHARED_PLANNING_RULES` — name what ANSWERED when the address comes from our own config

(motir-ai) Mirror W7 + W7b into `SHARED_PLANNING_RULES` — a lifecycle VERB is a precondition, and a characterised set owes its histogram

(motir-ai) Mirror W8 into `SHARED_PLANNING_RULES` — a decision's close-out asks BOTH directions, and its *Consumed by* header is the inward worklist

(motir-ai) Mirror W9 into `SHARED_PLANNING_RULES` — a defect card's mechanism owes the measurement that rules the alternatives out

Epic 8: Launch readiness

Planner self-improvement — auto-reported quality bugs

The Motir agent loop — plan → implement → deploy, closed end to end

Mirror the pack restructure into motir-meta — and teach `split.py` about packs that do not exist in the pre-split corpus

Decision: is a LINE still a RULE? Settle the clause unit before any rule text moves

`type` becomes an output of SKELETON — `propose_node` carries it, and `bug` leaves the typed set

The selector re-cut — phase → kind at skeleton, kind OR type at deepen, and the cell space becomes a SUM

Re-cut 1 of 3 — the CROSS-CUTTING rules: what every cell gets, and the back-reference rewrites

Re-cut 2 of 3 — the KIND packs: `epic`, `story` and `bug` at deepen

Re-cut 3 of 3 — the TYPE packs: what each of the 14 types receives, and what it must not

The story's coverage + integration gate — the assembled selector, end to end from a generation pass

The planning rule packs, re-cut on a phase → kind | type selector — and `type` becomes an output of SKELETON

(motir-core) 19 of the 30 most expensive test files landed on ONE Vitest leg — `--shard` slices the alphabet, so the `tests/integration/**` cluster travels together

(motir-core) With Vitest balanced, E2E becomes CI's ceiling at ~15.5 min — five bulk legs carry 1705 s of test work behind a 178 s per-leg boot nobody has costed

(motir-core) The Vitest lane is CI's critical path at 24.8 min — 1.6x the next-longest job — and the runners it would need to halve that are sitting idle (queue time is zero)

8.3.18 The `/design` design asset predates the package it draws — both mocks inline 0.1.0's dark accent ink, and the current-page nav treatment is justified by a 4.41:1 that is now 5.76:1 (motir-marketing)

One pack PER TYPE, and containers get their packs at `deepen` — eight types have no authoring bar, and `deepen/epic` and `deepen/story` compose byte-identically

`replan` is `plan` — retire the operation axis from rule selection, because a fresh plan already carries the reconcile TOOLS without the reconcile RULES

The `type` axis reaches only 4 of 14 types, and `phase-deepen` carries the other ten's rules — every deepen cell pays 78,304 chars it cannot all need

8.3.17 motir.co serves `@motir/design-system@0.1.0`, which predates MOTIR-3745 AND MOTIR-3774 — five accent-ink cells fail AA on the live site, and `/design` is about to make every one of them reachable in one click

8.3.15 Copy — the `/design` showcase page's words + the nav label, at the marketing register (motir-marketing)

8.3.14 Design — the public design showcase at motir.co (`/design`): the composed specimen, the three axis pickers + theme toggle, and the site's first current-page nav entry (motir-marketing)

(motir-core) MOTIR-3569 bounded `ci.yml` and left 19 runner jobs across ELEVEN sibling workflows on the 6-hour default — including `sandbox-images.yml` and `runner-image.yml`, which `ci.yml` itself calls

8.3.7 Entity-signal SEO root at motir.co (motir-marketing) — Organization+WebSite JSON-LD, root OG, robots, GSC

Planning bug: the IMPORT door's `?intent=import` has no reader and no owning card — its tracker twin got MOTIR-3639 and the import half was never carved

Planning bug: MOTIR-3735 deliverable 2 asserted `schema.prisma`'s `sessionBranch` "carries no comment" — it carries a 12-line one at the cited ref

Planning bug: an acceptance criterion's own COMMAND enumerated a strict superset of its claim, so the criterion was unpassable and its literal reading was destructive

Planning bug: a card generalised the side-effects-outside-the-transaction rule onto the AUDIT ROW, which is the one write that must be inside it

Planning bug: a card's rung-2 evidence asserted an absent workflow edge that ships — the decision survived, the argument's KIND did not

Planning bug: a card whose precondition is a DEPLOY was gated by a `blocked_by` edge, which discharges at MERGE — the RULE half (the lesson shipped)

Planning bug: the delivery-reader inventory's own re-measurement was short by two — its grep cannot match `?.workItemId`

Planning bug: a story was authored with a DEPLOYED-tenant verification card inside it, gating three siblings that ship at merge — so the story's own pull request could never open

Planning bug: the corpus CONTRADICTS ITSELF on what approve does to a proposal's status — `_shared.md` and `run.md` say it derives nothing and cite the code, `plan-procedure.md` says it derives from the edges, and the shipped `materialize` agrees with `plan-procedure.md`

Planning bug: a card that ENUMERATES the homes of a symbol quotes a grep it did not run — MOTIR-3777 named seven of ten

Planning bug: MOTIR-3750's measurement block secured the SET and left the CAUSAL sentence beside it unmeasured — the file it blames the classifier for was last touched two days BEFORE the classifier existed (and the count was one high)

Planning bug: the CORRECTION to MOTIR-3721's inventory was itself scoped by a one-file grep, so nine is short by seven in the same shape as five was short by four

Planning bug: MOTIR-3634's own TEST asserts a property of sibling MOTIR-3635's output, and the split left the two edge-free

Planning bug: a bug card's root cause was derived from a STALE COMMENT and from a call path a memo makes unreachable — two mechanisms, both falsified at the first grep

Planning bug: a card's second half was inferred from a MODULE PATH — `lib/ai/codeContext` was read as "calls motir-ai" while its whole import closure is Prisma

Planning bug: MOTIR-3739 called a neighbouring line "protected" without reading its call chain, and named ONE instance of a copy-pasted pattern as the population

Planning bug: MOTIR-3721 inherited its reader inventory from the ADR that authorised the retirement, so the readers the replacement CANNOT serve were never counted

Planning bug: MOTIR-3721's dependency on a sibling's OPEN pull request was written as prose, not a `blocked_by` — and two cards in the same story shipped with a null `explanationMd`

(motir-core) A `modify` proposal's body cannot carry an intra-plan CHIP — materialize rewrites `motir-ref:planItem:` on `add`s only, so an amendment naming a card the same plan proposes ships an inert link

8.3.6 Build the motir-marketing landing (new repo) — THREE cross-origin doors: idea hero · import existing · start free

8.43 `motir-marketing` is provisioned but NOT connected to Motir — `targetRepo` is refused and a merge on that repo moves no card

8.45 `motir-marketing` publishes no DESIGN RESULT — it has no publish lane at all, and a `<name>.design-notes.md` basename is invisible to the classifier in either repo

8.46 (motir-core) Adding a repo from GitHub's OWN installation settings always shows "We couldn't finish setting up the GitHub App" — the install SUCCEEDED, and only the signed `state` is missing

E2E flake: a bulk shard's whole shell-flows suite reds when the Playwright webServer / inngest dev server fails to come up (sign-up 404 + inngest 404)

8.18 Hand-Drawn style stops short of the app shell — rail/top-bar frame borders aren't roughened

8.17 /dashboard (DashboardsHome) list card has no data-surface — Neumorphism (and glass/aurora) material never reaches it

8.16 Create-work-item modal renders "Explanation" twice (disclosure header + editor label)

8.15 Switching org leaves stale old-org content in the page body (switchers refresh in place; no navigation)

bug-e2e-custom-fields-empty-state-hydration-flake Custom-fields E2E spec flakes on the Fields-admin empty state — finding-#89 hydration churn recurs on a surface bug-e2e-suite-flaky-specs did not cover

bug-e2e-suite-flaky-specs E2E suite has flaky specs that intermittently red CI on unrelated PRs (drag-reorder reload, at-scale cursor paging, inline-edit reload, watch-popover hydration)

8.3.13 Publish `@motir/brand@0.1.0` to npm by hand + configure its Trusted Publisher (manual)

Planning bug: a card's post-merge PUBLISH obligation was recorded as a comment and offered as a question ("say so and I will propose one") instead of filed as a card — MOTIR-1456 went `done` with `@motir/brand` unpublished, and MOTIR-1152 hit it eight hours later

8.3.4 Content — motir-marketing landing copy + positioning (idea · import-existing · tracker-first audiences)

8.3.3 Design — motir-marketing landing (motir.co): THREE entry doors (idea hero · import existing · start free) + descriptive blocks

Planning bug: a card proposed 'restore the yield, not the stepping' — the two are not separable, and the record it cited already said so

(motir-core) 11 of ci.yml's 14 jobs declare NO `timeout-minutes`, so a hung job burns SIX HOURS and is indistinguishable from a slow one — the same gap MOTIR-2970 closed at one call site

Own the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it

(motir-core) `code-graph-refresh-engine.spec.ts` hand-rolls a TRUNCATE that bypasses `db-reset.ts`'s 40P01 retry — it deadlocks against the E2E job worker and reds unrelated PRs

(motir-core) A double-click of Replay RAISES P2002 out of the dashboard action — the engine's DLQ replay enqueues by INSERT and does not treat the dedup violation as "already enqueued"

8.3.10 Provision the motir-marketing repo + motir.co domain + Fly app + CI (manual)

(motir-core) The engine has NO per-job concurrency, and a job that wanted one lost it silently — `account/data-export.requested` declared `{ limit: 1, key: userId }` and the engine never read the field

Planning bug: MOTIR-3693 enumerated its population by hand-reading ONE folder — the guard it was filed about counts 18 assets across 9 areas, not 6

Planning bug: a design that merges AFTER the card it gates re-opens that card's SIZING, and MOTIR-1136 reached dispatch at 5 pts / 65 min for a ten-card feature

Planning bug: a diagnosed defect was recorded ONLY inside another card's body — "this paragraph is currently the only record" — and then ran unnoticed for 23 days

Planning bug: a card ABOUT a stale population count carried a stale population count — MOTIR-3682 says "exactly one thing" remains on Inngest, and three did

Planning bug: the ADR allocated the account-SUSPEND action to a card while the suspension MECHANISM — a schema column, session revocation and a sign-in refusal — was owned by nobody and priced into nothing

Planning bug: two stories in different epics planned the SAME deliverable (`@motir/design-system`) two days apart, with no edge — MOTIR-1524 shipped it and MOTIR-1456 stayed claimable for eight weeks

A plan proposal's `type` is a bare `z.string()` while every enum beside it is a `z.enum` — an out-of-enum value is stored, passes validate, and 500s at approve

Planning bug: MOTIR-3230 deferred its filing-time limb with NO card — the prerequisite has since landed, and the duplicate that limb exists to prevent was filed two hours later

Planning bug: a card's central premise was a config COMMENT quoted as fact — six counter-examples sat nine lines below it, and two "options" were both already shipped

Retire Inngest — delete the SDK, the serve route and the dependency, and prove the substrate stands alone

Planning bug: the `subsumption` advisory only sees MERGED pull requests — a defect filed 48 min into the OPEN window of the PR fixing it is invisible to every check

8.3.11 Ship Motir's BRAND chrome for cross-repo reuse — the design-system half already shipped as `@motir/design-system`

8.3.8 Google Search Console — motir.co property setup + verification (manual)

8.3.12 Decision — where Motir's BRAND chrome lives for cross-repo reuse, given `@motir/design-system` is installed by every scaffolded product

Decision (ADR) — where does the motir-marketing site (motir.co) run? 8.3.10 plans a NEW Vercel project while MOTIR-2396 is closing the account

(motir-core) Cut the THREE container supervisors over IN PRODUCTION — ADD the ids to `MOTIR_POSTGRES_JOB_IDS`, watch a real push coalesce, boot and index

(motir-core) Two concurrent first-workspace creates give ONE user TWO free orgs — the §4.5 org-creation gate takes no lock at all

Planning bug: MOTIR-2508 asserts "ONE PR, one file" in two criteria and then requires a second file in a third

Planning bug: `motir run <id>` step 0a CLAIMED an archived card — `transition_status` does not reject one, and no gate before the worktree reads `archivedAt` or `readiness.ready`

Planning bug: a STACKED design PR merged into its already-merged base branch, so its deliverable never reached main while the card read done

Planning bug: MOTIR-3595 plans a cross-repo READ seam no card creates — "read the plan's proposals through core" has no producer

Planning bug: MOTIR-3573's criteria asserted a violation the API cannot express — the input type was never read before two ACs were written about it

Planning bug: MOTIR-3560 was sealed at 5 pts / 60 min carrying its OWN six enumerated deliverables — the sizing advisory is blind to a card whose numbers are present and wrong

Planning bug: MOTIR-3557's AC 3 forbade a behaviour a shipped test deliberately guarantees — a criterion phrased as a NEGATIVE about rendered output carries an ungrepped code claim

Planning bug: MOTIR-3487 claims an E2E lane 'already has every piece' from a sibling spec's SUBJECT — the spec seeds the ledger and its own header says the writer path has no seam

Planning bug: MOTIR-3547 was sealed UN-SIZED at ~5h across three repos, and asserted a code fact read from ONE of a tool's TWO return channels

Planning bug: the COLLAPSED supervisors run on Inngest between MOTIR-3417's merge and MOTIR-3489's flip, holding one invocation for the container's whole life

Planning bug: MOTIR-3626 recorded the over-gate advisory as "REAL" and declined it IN WRITING — an advisory ACKNOWLEDGED is not an advisory DISCHARGED, and the acknowledgement makes the card read as careful

(motir-core) Re-measure the fast lane on the engine and RECORD the figure — flip the honesty assertion, or say why it still stands

(motir-core) A free org CAN exceed its work-item cap — `lockByIdForUpdate` locks ZERO rows under `withWorkspaceContext`, and nobody reads the `false` it returns

(motir-core) NOTHING reconciles the census against the live secret — `MIGRATED_TO_ENGINE` and `MOTIR_POSTGRES_JOB_IDS` drift silently, and each newly-routed job costs one more operator card

(motir-core) A FOURTH job landed mid-cutover and is unrouted — `system.job-run-reap` declares `MIGRATED_TO_ENGINE` in the census while the live secret does not carry it, so it will run on Inngest

(motir-core) The entitlements FOR-UPDATE race test has gone red three times on unrelated diffs, and it THROWS AWAY the one measurement that would say whether the lock broke

(motir-core) TWO event-triggered jobs landed after MOTIR-3463's wave and are still unrouted — `plan-drift/transitioned` and `public-follow/digest` are on Inngest and no card owns them

(motir-core) One failed run writes TWO `job_run` rows and neither is legible — the `running` row never resolves and the failure lands on a second row with an unattributable `event_id`

(motir-core) `main` cannot deploy — the `billing-cloud` at-scale leg has been red since 07:18Z on the transient double-subtree strict-mode class at `/settings/project/ai-planning`, and no production deploy has gone out since 01:50Z

(motir-core) `system.code-graph-refresh` fails ~32% of the time — 62 of 194 runs in 7 days die on `admission_deferred: index admission was refused for 60 attempts`

(motir-core) A 15th scheduled job landed mid-cutover and is still on Inngest — `system.public-follow-digest-tick` breaks MOTIR-3418's "nothing remains on Inngest" premise

(motir-core) The daily health check has been RED for 23 days and nobody noticed — `IndexFleetImageUnpullableError` every night since 2026-08-04, last success 2026-08-03

(motir-core) TAKE the fast-lane latency reading on the engine — the six figures, from inside the deployment, on a tail worth reading

(motir-core) Cut the 14 SCHEDULED jobs over IN PRODUCTION — ADD the ids to `MOTIR_POSTGRES_JOB_IDS`, read each cadence back from the ledger

(motir-core) `coverage-gate-globs` is a whole-tree scan MOTIR-3144's lane left behind — it globs 483 files in 0.8 s and times out at 15 s on a loaded coverage shard, twice in three days

Planning bug: three 8.4 legal cards were typed `coding_agent` while their acceptance required counsel review — and the human-sized estimate was the tell nobody read

Planning bug: two bugs were filed mid-run WITHOUT the bug-filing protocol — one proposed a rule the corpus already carries in both homes, and the rule forbidding exactly that was routed to the pass that skipped it

(motir-ai) The lesson-delivery guard still reads the PRE-`occ:` marker grammar, so the first migration generated after MOTIR-3552 fails CI on a correct corpus

(motir-core) The fast-lane latency probe reads the POOLED url and reports `samples: 0` — RLS hides every row, so it says "no fast-lane engine runs" while the engine is running the whole lane

(motir-core) Every deploy ends RED on a deploy that SUCCEEDED — `FLY_EXPECTED_MACHINE_COUNT` still says 2, and MOTIR-3425's worker group made the pool 4

(motir-core) Cut the 20 event-triggered jobs over IN PRODUCTION — `MOTIR_POSTGRES_JOB_IDS` in waves, read back from the ledger

Planning bug: a design entry cited an existing component as a surface's pending stand-in without measuring it — 9 tracks against 4, 40px rows against 48

Planning bug: a card with NO acceptance criteria passes every gate vacuously — and the one mechanised sizing check needs the very field an under-authored card is missing

(motir-ai) The mirror — `SHARED_PLANNING_RULES` teaches the shipped planner that a hit reinforces (gate 19's second home)

(motir-meta) The sweep's HIT reinforces — `run.md` step 5 and `_shared.md`'s lesson-store row stop being read-only

(motir-core) Integration vitest through the real MCP transport — a global row reinforced across the boundary, and a retired one that stays retired

(motir-core) `reinforce_lesson` — the MCP door a hand-run sweep calls, on the `id` `search_lessons` already hands back

(motir-ai) The generator carries the OCCURRENCE explicitly — a widening bumps the clock, a wording correction never does

(motir-ai) `POST /v1/lessons/:id/reinforce` — the named act, over BOTH scopes, not the tenant-only resolver the retire endpoints use

(motir-ai) The OCCURRENCE ledger — a hit becomes a row, and that row is what makes the clock bump exactly once

A lesson matched BY HAND is never reinforced — the runbook sweep's hit and every widening leave `lastOccurredAt` untouched, so only the two automatic paths can reset the retirement clock

(motir-core) The E2E seam for the index WRITER path — the run-credential mint and the tarball redirect, on the app server AND the worker

(motir-core) `docs/jobs.md` § Debounce + the fleet decision record — the engine's debounce, and the `maxDuration` premise the stepped shape was built on is GONE

(motir-core) Story E2E — a push burst coalesces into ONE refresh run that boots, polls and settles on the engine, and survives a mid-index worker restart

(motir-core) Story gate — a supervisor RESUMES after a real worker restart, the debounce coalesces a burst, and the ledger contract and admission cap are untouched

(motir-core) COLLAPSE the CI-RUNNER supervisor — `system.ci-runner-boot` converges onto `ciRunnerBootService.runIntent`, and the second composition goes

(motir-core) COLLAPSE the INDEX supervisor — `indexFleetSteps.ts` becomes one `while` loop over the service's own composition, and the `maxDuration` comments are CORRECTED rather than deleted

(motir-core) The engine's DEBOUNCE — a same-key `run_at` pushed forward on each arrival, so a push burst still coalesces into ONE run carrying the latest event

(motir-core) Decision — what survives a WORKER RESTART mid-supervision: which waits stay durable steps, which become plain `await`s

Cut the container supervisors over — and COLLAPSE the stepped shape now that nothing times out

Record the never-fires lesson — an acceptance criterion that asks to OBSERVE something in production is unsatisfiable when the trigger has never fired (5 of MOTIR-3463's 20 ids, all_time=0)

16 Roadmap: a level draws edges whose BLOCKED end is not on it — "Not in an epic" redraws the whole EPIC chain as 12 anonymous "blocked elsewhere" ghosts, and the root draws a grouped task as one

Planning bug: a mechanism-withdrawal amendment swept four of five dependents — the one it missed was the one whose SCOPE had not moved

(motir-core) Three dedup layers, none legible where a reader looks — `docs/jobs.md`'s canonical-job § and `JobEvent`'s index comment still name Inngest as the only enforcer after MOTIR-3459

(motir-core) Decision — where a NON-ADMIN's workspace-scoped settings live at one workspace, and §6d's amendment

(motir-core) An org-scoped READ arm on `workspace` — the org's TRUE workspace count, readable inside a user-bound org transaction

(motir-core) Hide the workspace-settings SURFACE at one workspace — fold Name / Members / Danger into org settings and 404 the area

(motir-core) Org add joins the org's SOLE workspace — the count-1 arm §5 and §6 never reconciled

14 Progressive disclosure is half-shipped at ONE workspace — the workspace-settings surface is still exposed, and an org invite lands the invitee in ZERO workspaces with no way in

Planning bug: a card was sealed carrying a heading that said "split it", and criteria duplicating a still-open operator card's DNS records — where the duplicate would have BROKEN the card that owns them

Planning bug: a card RELOCATED a surface without checking that its destination is reachable by everyone the source was

Planning bug: a card specified a write + its guarding read inside an existing transaction without checking that the transaction's SECURITY BINDING admits either

Planning bug: MOTIR-3462 asks an E2E to assert same-key idempotency on a journey that mints a FRESH key each time — the criterion cannot be run at all

Planning bug: MOTIR-3455's evidence grep was never RUN — it reports 3 files where its own named ref returns 19

Planning bug: a defect was verified against `origin/main` and filed 47 minutes after the card fixing it went `implemented` — the pre-flight never searched the PLAN

Planning bug: two of MOTIR-3451's acceptance criteria were never RUN before they were written — one quotes markup the file has never carried, the other asserts an output that was already false

Planning bug: run.md says a card at `todo` is structurally safe from a PR naming it — the sync WALKS the hops, and a one-criterion PR closed a four-criterion card

Planning bug: MOTIR-3264 imported a suspend delay measured on OTHER endpoints and stated it as its own subject's property — in the title, while its body correctly forbade exactly that

Planning bug: a bug card's MECHANISM was taken from an untested code comment, and three candidate fixes were planned off it

Planning bug: MOTIR-3274 closed `done` on criteria written over ONE project while its own Context refs named a SECOND consumer — the credential meant to unblock MOTIR-3264 cannot reach the gateway

Planning bug: MOTIR-3371 turned "toHaveLength(1) passed, SO a second window opened" into an acceptance criterion — a second mechanism produces that presentation and reproduces 2 in 10

Planning bug: the MID-SENTENCE WIDENING sweep is owed AGAIN — three packs red for the third time, so MOTIR-2966's remedy collects the debt without stopping it accruing

Planning bug: an acceptance criterion demanded evidence from a substrate on the OTHER side of a service boundary — "asserted against a real database" for an HTTP seam

Planning bug: a story scoped its population from where a corpus "STOPS" — but the coverage was a SET, not a prefix, so 44 entries below the boundary were invisible to every check

Planning bug: a card forbade the only layer at which its own acceptance criterion was implementable — a prescribed layer is a CLAIM about that layer, and it owes the ADR check

Planning bug: a test card's fixture table encoded axis semantics that contradict the three-axes-are-independent rule its own parent story states in prose

Planning rule: NEVER reopen a `done` work item — plan forward, and log a bug or a new story instead

Planning bug: guard #4 says an advisory's reference is "a `blocked_by` to WIRE" — followed literally on a CROSS-STORY reference it produces a cross-parent edge, which gate 7 forbids

Planning bug: `_shared.md` says "Epic is not an offered kind" — the MCP has offered it all along, so every pass routes around a tool that works

A story whose deliverable was a PAGE planned no instrument that OPENS it until its last card — a client-boundary 500 lived through five green subtask PRs

Planning bug: MOTIR-2853 read `ready: true` with two unexecutable preconditions — an external credential and a post-deployment soak window, neither expressible as an edge

Planning bug: MOTIR-3249 gates four children behind a POST-DEPLOY measurement, so the story cannot be run as a parent

Planning bug: two MOTIR-3249 children were pinned to ONE repo while their criteria need the other

Planning bug: MOTIR-3229 names THREE homes and assigns home 2 to MOTIR-3203, which closed without it — `run.md`'s parent-run still stops only on a `design`/`manual` stopper

Planning bug: an acceptance criterion named TWO triggers for one event-driven seam, and one of them is a non-terminating loop — the card's own explanation names only the other

Planning bug: a grep-shaped acceptance criterion whose PATTERN also appears in the comments FORBIDDING it is unfalsifiable — MOTIR-3226's AC 7 returned 3 hits on `origin/main` at authoring time

Planning bug: a card's own detection query prescribed `gh pr view --json files`, which caps at 100 — and the cap became a finding in the card's evidence table

Planning bug: a contrast ratio was measured in ONE theme context and generalised to "light" — `data-palette` makes it twenty, and four of them failed

Planning bug: `run.md` never says the at-scale lane is LABEL-gated, so a run labels the PR AFTER creating it — a second trigger at the same sha whose cancelled run poisons the card's CI verdict

Planning bug: a design card specified a CONSTRUCTION (a true normal-offset band) without checking it was geometrically possible at the mark's own proportions

Planning bug: the two-homes obligation is stated only in `CORPUS-MAINTENANCE.md`, which no planning pass loads — six occurrences, five sibling cards, no gate

Planning bug MIRROR: (motir-ai) carry the widened deferral surfaces + the placeholder triggers into `SHARED_PLANNING_RULES`

Planning bug: (motir-meta) a deferral written in a DESIGN ASSET or a source COMMENT is invisible to the deferral-is-a-card rule — the AI orb shipped a mock "M" for 18 days with no card

Planning bug: a card's "Read and deliberately LEFT" section states a COMPLETENESS claim ("every other literal was read") that a re-run falsifies — a false absence the next card inherits

Planning bug: the totality rule (#29) cannot reach a renderer keyed on a DATABASE-defined set — a `Record<Union, …>` is total against a union that is itself the hand-authored subset, so the compiler certifies the lie

Planning bug: a card's SCOPE-PROXY criterion contradicted its own instruction criterion — "no `app/` path" forbade the very file another criterion required a comment in

(motir-ai) Mirror the sweep-is-not-its-grep-pattern limb into `SHARED_PLANNING_RULES` — a pattern's silence is a result, never a scope verdict

(motir-core) The E2E job worker sends email through the CONSOLE provider, so no engine-routed send ever reaches the outbox — `jobs-postgres-engine.spec.ts` is red on `main`

(motir-core) Story E2E — one transition fans out to all four fast-lane consumers on the engine, and a repeated invite emails once

(motir-core) Story gate — vitest coverage floor, the emit-to-run seams, and the totality guards a percentage cannot see

(motir-core) `docs/jobs.md` — the emit seam, engine-side idempotency, and what "cut over" means to an operator

(motir-core) Event-level IDEMPOTENCY on the engine — carry `defineJob`'s key through and dedupe on it, so `email.send` still sends once

(motir-core) Make the subscriber set reachable from the emit path, with a guard that fails when it is not

(motir-core) The engine's fast-lane latency probe — event to run p95, read from the ledger instead of a vendor API

(motir-core) Route every emitter through `sendEvent`, and make the ESLint boundary enforce it

(motir-core) Decide how the EMIT PATH learns the subscriber set — the engine registry is empty on a web request

Cut the EVENT-triggered jobs over — fan-out, the fast lane's latency budget, and the notification / automation / email paths

15 3D / Immersive leaves 199 of 280 interactive controls flat — the physical-key rule matches `rounded-(--radius-btn)` only, so Plan with AI, Re-plan, the 3-dots menu and the roadmap search have no depth (motir-core)

Planning bug: MOTIR-3440 NAMED `PageSkeleton` as unowned and created no card, so MOTIR-3443 shipped `ready` with an acceptance criterion nothing could satisfy

Planning bug: MOTIR-3324 ships a consumer whose motir-core PRODUCER half owns no card — a conditional in a card body defers a decision the run cannot act on

Planning bug: MOTIR-3224 defers the cross-machine wake to MOTIR-2783, which was already `done` when the card was written — so the gap it names has no owner

Planning bug: MOTIR-3414 cannot close — its `manual` post-deploy child needs the merge the story needs the child for, and the E2E is edged to it while forbidding the worker it needs

Planning bug: MOTIR-3414/3422 assert "84 step.run call sites across 37 files, incl. services outside lib/jobs/" — measured 58 across 26, ALL inside lib/jobs/

Planning bug: a story planned building a column that already shipped, and a `manual` card the pipeline can do — the lesson forbidding the second was IN the store, where the runbook planner cannot read it

Planning bug: `notes.html` entries #68 and #203 still PRESCRIBE the dead branch-prefix CI-skip mechanism — the MOTIR-819 retrieval hands it to future runs as advice

Planning bug: run.md's branch-prefix rule still cites the `startsWith(head_ref, …)` CI gate that MOTIR-3148 replaced with a diff-based predicate — and understates which prefixes skip the Vercel preview

Planning bug: MOTIR-3193's AC 4 asks the generated OpenAPI document to reflect an MCP tool ARGUMENT shape it has never contained

Planning bug: a RECORD card asserted "no repository deliverable" in its first line and then spent TWO repos in its criteria — and `likely-repo-straddle` was silent because the paths were bare filenames

(motir-core) `docs/jobs.md` § Scheduled jobs — there IS a scheduler now, what a missed tick does, and what the health probe still proves

(motir-core) Story E2E — a scheduled job fires on the engine and appears on the jobs dashboard, and a worker restart honours the declared catch-up

(motir-core) Story gate — two workers do not double-fire a tick, the coverage floor, and the totality guards a percentage cannot see

(motir-core) The SCHEDULER — a tick in the worker that enqueues every due cron fire, with a guard that refuses to run against an empty registry

(motir-core) DECLARE the catch-up disposition beside the cron — a `defineJob` option a scheduled job cannot omit, on all 14

(motir-core) The per-tick KEY — `job_queue.scheduled_for`, a unique on `(job_id, scheduled_for)`, and an insert-if-absent enqueue

(motir-core) Decide the CATCH-UP POLICY for a missed tick — per job, and where the disposition is DECLARED

Cut the 14 SCHEDULED jobs over — crontab, catch-up after downtime, and the sweeps that keep the platform tidy

Planning bug: the design gate makes the design card a CHILD of the card it gates — a prerequisite must be a SIBLING wired `blocked_by`, never a child

12 Roadmap root level draws every parentless bug as a top-level node beside the epics, and its 200-row cap then drops the NEWEST epics silently

(motir-core) Prove the PILOT job on the engine in production — route `email.send`, read the run row back, and close MOTIR-3414's stated scope

(motir-core) Design — the roadmap ROOT level's non-epic rows: the grouped defects node, the level it drills into, and a cap that is visible rather than silent

Planning bug: a falsified-premise card named TWO of the ten cards its finding invalidated — the referrer sweep was done by memory, not by grep

(motir-core) Provision the worker process group on Fly — `fly scale count`, read back from the platform

Split `VERIFY_EVERY_PRECONDITION` into its numbered limbs — one segment of 49,449 chars is 24% of the corpus and cannot be selected off any cell

Sandbox: the `claude` profile build is broken by an UNPINNED `@anthropic-ai/claude-code` — 2.1.237 needs its postinstall, npm's allowScripts default skips it, and the arm's smoke test fails every CI run

(motir-core) CI: stop RUNNING apt — `install-deps` is defensive on a cache hit, and it is the only thing in the E2E path the Ubuntu mirror can hang

Cut `cli-v0.2.1` — `package.json` has said 0.2.1 since MOTIR-2537 and four CLI commits sit unreleased, including a user-visible `motir link` error fix and the ACME copy rename the docs already show

(motir-core) The Vercel deployment fails on `main` AND on every open PR — read the build log; `next build` is green in CI, so the failure is after the build

6.12.13 Public work-item detail page — read-only public view (with child / sub-issue panel) at /p/[identifier]/items/[key]

2.8.8 [design] Work-item ⋯ actions menu (detail/list/board) + Archive action flow + archived-item state

2.8.9 Work-item ⋯ actions menu + Archive action (detail/list/board) — route + UI + page-state

startSprint locks committedPoints=null when items are unestimated at start — immutable baseline never reflects later estimates (breaks burndown/velocity/report)

6.10.9 Copy-on-create — seed a new workspace’s config from the source workspace (the "looks-inherited" behaviour)

bug-notification-pref-transitioned-still-disabled-after-5-4-shipped Notification preferences: the "An item you're watching changes status" row is still drawn disabled with "Soon" + "Available once issue-watching ships (Story 5.4)" copy, but Story 5.4 (issue-watching) shipped — the row should be settable