Motir

← Back to the top level

• MOTIR-2933Planning bug: a decision forbade every in-product path that could write the column it governs, and no card owned the one path left — a dev-only seed criterion made it look owneddone
• MOTIR-2934Planning bug: `COMPRESSION.conserve.py` cannot express "a gate gained a sub-bullet" — the enumeration's COUNT NUMERAL is surviving text, so every future limb re-words itdone
• MOTIR-2938Planning bug: an acceptance criterion asserted a PIPELINE's outcome ("the PR is green") when the card owned one STAGE of it — the other stages were never verifieddone
• MOTIR-2942Planning bug: MOTIR-2939 attributed a count rise to two specs from what LANDED RECENTLY, not from measuring — one of the two was already inside the baselinedone
• MOTIR-2943Planning bug: a card quoted the exact line it was changing and called it unexplained — the twelve-line comment directly above it said the oppositedone
• MOTIR-2944Planning bug: a card described a SESSION LIFECYCLE the shipped model does not have — and two of its release paths would have defeated the lockdone
• MOTIR-2950Planning bug: 8.1.5 shipped a checkout endpoint that could never work, because the deferral was written into a CODE COMMENT ("EITHER … OR …") instead of a card — the orphaned-deferral shape, on the revenue pathdone
• MOTIR-2951Planning bug: the correction was posted as a COMMENT and the description kept the false claim — second instance, and both times the run that wrote the comment also wrote the card that asserted it was applieddone
• MOTIR-2955Planning bug: an ADR run swept OUTWARD for what it left unowned and never INWARD for the criteria it had just falsified — including the card its own header names firstdone
• MOTIR-2958Planning bug: `motir run <id>` has NO claim, so two sessions built MOTIR-2952 at once — and the tell was a `git status`, not anything the MCP saiddone
• MOTIR-2964Planning bug: a flake card named its MECHANISM in the title and enumerated the two allowed repairs — the first measurement falsified bothdone
• MOTIR-2966Three packs stay `[FAIL]` on invariant C for the MID-SENTENCE WIDENING shape — the remedy is decided and nobody owns the sweepdone
• MOTIR-2967`SHARED_PLANNING_RULES` has NO historical baseline — invariant B compares the rebuild to itself, and the 58 phrase assertions pin 1.20% of it, so a re-wording of the shipped planner corpus passes every testdone
• MOTIR-2968Planning bug: a coverage card measured its own DENOMINATOR off the FILE that declares the constant, not off the constant — and the two differ by 14%done
• MOTIR-2969Planning bug: invariant C's verdict rides the DIFFER'S ALIGNMENT — a run boundary landing on a markdown marker reds a pack no fixture span can fixdone
• MOTIR-2972The hosted planner still sweeps the PRE-taxonomy work-type list — `SHARED_PLANNING_RULES` offers `doc`/`spike`/`human`, which are unsettable, and never offers `chore`done
• MOTIR-2973Nothing conserves the ROUTING — `SHARED_PLANNING_RULES` drops the pack tag, so re-tagging a rule silently changes which cells receive it while every check stays greendone
• MOTIR-2975Planning bug: a `notes.html` #27 filing writes `relates_to` where gate 4 also owes `blocked_by` — when the found-in card IS the consumed card, one edge hides the otherdone
• MOTIR-2976`work-item-type-taxonomy.md` Amendment 1's follow-up table has no row for `motir-ai`'s `SHARED_PLANNING_RULES` — the sweep list that missed the mirror still misses itdone
• MOTIR-2977Planning bug: a bug card was authored with a DIAGNOSIS the fixed lock order already excludes — the observation was read as a leak, not as a winner-order artifactdone
• MOTIR-2979Planning bug: a card specified a state check by pointing at an EVENT check — the completion gate's default-branch comparison reads a live payload field the mirror never persistsdone
• MOTIR-2980`corpusConservation.ts` carries the `. **⚠️` limb of MOTIR-2969 unfixed — the port dropped clause (3) but kept clause (1), so the next rule added before a `⚠️` marker reds the mirrordone
• MOTIR-2981Planning bug: a design child's deliverable is a PUBLISHED artifact, and the artifact-obtainable rule's example list read as a membership test that excluded it — the run reported In Review on a PR link while the card showed nothingdone
• MOTIR-2995(motir-ai) Mirror the ALREADY-LINKED-KEY clause into `SHARED_PLANNING_RULES` — an existing edge to a key is not evidence its status was resolveddone
• MOTIR-2998Planning bug: a card asserted a MECHANISM from a log line, and the run that ran the probe could not reproduce itdone
• MOTIR-3053Planning bug: a card written to remove an unverified mechanism claim carried two of its own — a false clause in its remediation, and a sweep scoped by a grep pattern rather than by the claimdone
• MOTIR-3065Planning bug: an acceptance criterion keyed on a COUNT that the code's own idempotency argument forbids — the falsifying comment sat one file from the card's own context refsdone
• MOTIR-3071Planning bug: a guard's declined boundary was warranted by an unmeasured claim about its population's COMPOSITION — only the count had been measured, and the named fixture was 5 of 277done
• MOTIR-3072(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 verdictdone
• MOTIR-3076Planning bug: a card said its mechanism must be MEASURED and then made one hypothesis an acceptance criteriondone
• MOTIR-3079Planning bug: a story's "The gap, verified" section enumerated three true facts and drew a false conclusion — the capability it was written to build had shipped six days earlier, under a name the search never useddone
• MOTIR-3087Planning bug: a card that hands the runner a SCAN defines the population BY that scan — and this one's pattern was incomplete in three ways, one of which hid a real defectdone
• MOTIR-3108Planning bug: a card sealed at 13 SP / 600 min carried "expect this to SPLIT" in its own explanation — the FOURTH prose discharge of the estimation gate, which nothing executesdone
• MOTIR-3109Planning bug: a card that ENUMERATES a population measured it with `find` over the working tree, and shipped a count 4 shortdone
• MOTIR-3120Planning bug: a card's "what must NOT change" clause described a sibling's behaviour the sibling had already reverseddone
• MOTIR-3130Planning bug: `run.md` says the design-result publish is "keyed off the `design/MOTIR-<n>-<slug>` branch" — it is keyed off ANY resolvable `MOTIR-<n>` in the branch ref or the PR title, on every PRdone
• MOTIR-3134Planning bug: a coverage card enumerated uncovered arms as work items without asking which of them a test can REACH — three of five bullets were dead codedone
• MOTIR-3150Planning bug: `run.md` tells every run that a `design/*` / `docs/*` BRANCH PREFIX is what skips the E2E + Vitest lanes — MOTIR-3148 makes that mechanism falsedone
• MOTIR-3153Planning bug: a POST-DEPLOY verification child is discharged by the merge it exists to outlive — the story's completion cascades `done` onto it 27 seconds laterdone
• MOTIR-3155Planning bug: a surface with a LIFECYCLE was planned one state at a time and nobody owned the state AFTER the terminal transition — four cards each answered it locally and one of them answered with a DELETEdone
• MOTIR-3156(motir-ai) Mirror the post-merge card's PLACEMENT limb into `SHARED_PLANNING_RULES` — the shipped planner has gate 14(c) and not its second halfdone
• MOTIR-3158Planning bug: a card carried its OWN design as criterion 1 and the UI criteria that consume it as criteria 4–5 — the planning-time design gate has no detector, so a leaf can be its own design blockerdone
• MOTIR-3164Planning bug: a re-plan verified every claim it made and still missed a fourth root cause TWELVE LINES ABOVE the code it quoted — nothing audits what a diagnosis OMITSdone
• MOTIR-3166Planning bug: a card's SCOPE-PROXY criterion contradicted its own instruction criterion — "no `app/` path" forbade the very file another criterion required a comment indone
• MOTIR-3168Planning 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 filenamesdone
• MOTIR-3172Planning 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 liedone
• MOTIR-3174Planning 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 inheritsdone
• MOTIR-3175Planning 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 carddone
• MOTIR-3176Planning bug MIRROR: (motir-ai) carry the widened deferral surfaces + the placeholder triggers into `SHARED_PLANNING_RULES`done
• MOTIR-3186Planning bug: MOTIR-3076 named one of its rule's two homes — mirror the mechanism/criterion check into `SHARED_PLANNING_RULES`done

Showing 100 of 255

Load more at this level