Skip to content

revert: tear down the DocIr composition arc (#218, #219, #220) — restart from scratch#221

Closed
AdaWorldAPI wants to merge 3 commits into
mainfrom
claude/ogar-docir-architecture-jjzlig
Closed

revert: tear down the DocIr composition arc (#218, #219, #220) — restart from scratch#221
AdaWorldAPI wants to merge 3 commits into
mainfrom
claude/ogar-docir-architecture-jjzlig

Conversation

@AdaWorldAPI

Copy link
Copy Markdown
Owner

What

Operator-directed full teardown of this arc's work, ahead of a from-scratch restart. Three clean git revert -m 1 commits, newest first:

Net: −1,217 lines; ogar-doc-ir returns exactly to its pre-arc W1 observation-IR state.

Why

A three-reviewer audit found the arc built an address/storage type skeleton while the directive's payload — the resolution-and-rendering pipeline (resolve ObjectSlot → renderer-neutral FieldView enum → the same document through Askama HTML and Typst), proven by a vertical slice — was never started. Rather than patch types that nothing consumes, the operator directed: delete everything, start from scratch. The restart will be slice-first — every type earns its existence by being consumed by a resolver/renderer in the same PR.

Deliberately NOT touched (other sessions' work)

Ledger note

The reverts remove this arc's DISCOVERY-MAP entries. The append-only canon normally forbids deleting ledger entries; this is a direct operator override ("delete everything you did"), and the entries remain recoverable in git history via the reverted merges.

Verification (Rust 1.95)

  • cargo test -p ogar-doc-ir → green at the reverted state (W1 tests intact).
  • Default build back to serde-only, zero canon deps.

🤖 Generated with Claude Code


Generated by Claude Code

claude added 3 commits July 20, 2026 22:53
…chitecture-jjzlig"

This reverts commit 63ac9c0, reversing
changes made to 2255643.
…chitecture-jjzlig"

This reverts commit 2255643, reversing
changes made to 91e2cb8.
…chitecture-jjzlig"

This reverts commit 91e2cb8, reversing
changes made to 6149a84.
@cursor

cursor Bot commented Jul 20, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_6bc440d9-8565-49f9-8d5d-37ac1243a5fc)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants