Skip to content

docs(knowledge): staleness banner on OGAR-VOCAB-SURFACE — kausal rows stale since #168 (council Q4)#27

Merged
AdaWorldAPI merged 1 commit into
mainfrom
claude/odoo-transcode-ruff-ast-5ejqvr
Jul 7, 2026
Merged

docs(knowledge): staleness banner on OGAR-VOCAB-SURFACE — kausal rows stale since #168 (council Q4)#27
AdaWorldAPI merged 1 commit into
mainfrom
claude/odoo-transcode-ruff-ast-5ejqvr

Conversation

@AdaWorldAPI

Copy link
Copy Markdown
Owner

What

Council Q4 tail (docs/COUNCIL-5+3-2026-07-07.md): the study-fleet map docs/knowledge/OGAR-VOCAB-SURFACE.md was accurate at its pin (OGAR 748ba11) but has been stale since AT-CARRY-2 (OGAR #168 / ruff #49) landed — lift_actions now populates KausalSpec (Depends/Constrains/Onchange) and ActionDef.raises, so the doc's "kausal always None" rows are false at OGAR HEAD.

R5 flagged this as a next-session hazard: the living handover names this doc as required reading, and a reader trusting the stale rows would re-plan already-done work.

Fix is a loud, dated banner at the top — not silent row edits — because the doc is a map at a pin, and what IS still true at HEAD (body_source unset, Class.methods shape) stays listed. Append-only ledger discipline.

Docs-only; no code paths touched.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Fy8D6Boh4ZBaHSBpadSENN


Generated by Claude Code

…tale since #168 (council Q4)

The map was accurate at its pin (748ba11) but AT-CARRY-2 (#168/#49) landed
after: lift_actions now populates kausal (Depends/Constrains/Onchange) +
ActionDef.raises. R5 caught a next-session hazard: the handover names this
doc required reading, and its 'kausal always None' rows are false at HEAD.
Loud dated banner instead of silent row edits (the doc is a map at a pin);
what IS still true at HEAD stays listed (body_source unset, Class.methods
unassigned, THROW type slotless).
@cursor

cursor Bot commented Jul 7, 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_1a58fe03-7721-4c71-b0bd-47a20637f9c8)

@AdaWorldAPI AdaWorldAPI merged commit 200252c into main Jul 7, 2026
1 check passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 97eb32e261

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

> `src/ogar.rs::kausal_parity_pinned_ogar_vs_corpus_witness` +
> `tests/real_source_compile.rs` (92 kausal-carrying ActionDefs from the real
> account_move.py). Still true at HEAD: `body_source` never populated;
> `Class.methods` never assigned; THROW exception type has no slot.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Remove the stale THROW-slot claim

For readers using this banner against OGAR main, this clause keeps row #17 marked as an unsolved carrier gap even though the same banner cites the newly added ActionDef.raises slot; on OGAR main that slot carries the exception/error type names from Function::raises, so the THROW exception type is no longer slotless. Leaving this as “Still true at HEAD” will make the next-session plan re-file already-completed upstream work.

Useful? React with 👍 / 👎.

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