Skip to content

Re-vendor OGIT from d0f489f to 18f8177e - #335

Closed
AdaWorldAPI wants to merge 1 commit into
mainfrom
claude/ogit-revendor-18f8177e
Closed

AdaWorldAPI wants to merge 1 commit into
mainfrom
claude/ogit-revendor-18f8177e

Conversation

@AdaWorldAPI

Copy link
Copy Markdown
Owner

What

Moves vocab/imports/ogit to AdaWorldAPI/OGIT 18f8177e (2026-07-06), the commit the new stack's ontology already uses. The old copy lacked upstream changes such as two Automation attributes, manualProcessingTimeSeconds on KnowledgeItem and savedTimeSeconds on AutomationIssue.

The change is the exact upstream delta inside the mirrored set (NTO, SGO, SDF, ogit.ttl):

Change Files
Added 1332: NTO/Utilities 1295 (Electricity and Emissions, an AdaWorldAPI fork addition), NTO/GFS 24 (upstream almatoai), Auth 9, Automation 2, Healthcare 1, SGO 1 (revokedAt)
Modified 9
Deleted 25: NTO/Medical/sql_mirror, which upstream removed as a private schema that belongs in the MedCare family only

A plain cp -r, as the recipe said, would have kept those 25 deleted files and broken the byte-mirror claim. PROVENANCE.md now says to apply the deletions too. OGAR's own files are untouched: both provenance files, the MARS XSD oracle, and the three NTO docs kept at the vendored root.

Verification

  • Mirror: 3294 mirrored files, 0 differ from 18f8177e, 0 extra, 0 missing. NTO/MARS is unchanged.
  • Tests: ogar-from-schema (52 unit and 3 integration tests) and ogar-vocab (172 unit and 6 doc tests) pass on the new snapshot. No OGAR test pins a count that moved.

Docs

  • PROVENANCE.md: new SHA and date, counts re-measured, and a re-vendor log row. The counting rule is stated, and the same rule reproduces the old 1940 TTL files, 1431 NTO files, 508 SGO files and 72 domains at d0f489f. It gives a different entity/verb/other split than the old note, which the file now says.
  • MARS/PROVENANCE.md: new SHA and date.
  • OGIT-DOMAIN-LIFT-CATALOGUE.md: rows for GFS and Utilities, changed rows updated by their file delta, new totals, SGO at 509, and the provenance line.

Follow-up

Bardioc-rs's bardioc-ogit-codebook pins counts measured on this vendored tree, so it needs a re-pin after this merges. That PR is next.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VysoWJ6vsyg3wEGc5v7T5v


Generated by Claude Code

Moves vocab/imports/ogit to AdaWorldAPI/OGIT 18f8177e (2026-07-06), the
commit bardioc's external/OGIT and Bardioc-rs's codebook target. The old
copy lacked upstream changes the new stack's ontology already has, among
them two Automation attributes (manualProcessingTimeSeconds on
KnowledgeItem, savedTimeSeconds on AutomationIssue).

Applied as the exact upstream delta inside the mirrored set (NTO, SGO,
SDF, ogit.ttl): 1332 added, 9 modified, 25 deleted.
- Added: NTO/Utilities 1295 (Electricity and Emissions, an AdaWorldAPI
  fork addition), NTO/GFS 24 (upstream almatoai), Auth 9, Automation 2,
  Healthcare 1, SGO 1 (revokedAt).
- Deleted: NTO/Medical/sql_mirror, 25 files upstream removed as a private
  schema that belongs in the MedCare family only. A plain cp -r would have
  kept them and broken the byte-mirror claim.
- OGAR's own files are untouched: both PROVENANCE files, the MARS XSD
  oracle, and the three NTO docs kept at the vendored root.

Verified: 3294 mirrored files, 0 differ from 18f8177e, 0 extra, 0 missing.
NTO/MARS is unchanged.

Docs: PROVENANCE (SHA, date, counts re-measured with the counting rule
stated, a re-vendor log row, and a note that a re-vendor must apply the
deletions), MARS/PROVENANCE (SHA, date), OGIT-DOMAIN-LIFT-CATALOGUE (rows
for GFS and Utilities, changed rows updated by their file delta, totals,
SGO 509, provenance line).

ogar-from-schema (52 unit + 3 integration) and ogar-vocab (172 unit + 6
doc) pass on the new snapshot.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VysoWJ6vsyg3wEGc5v7T5v
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@coderabbitai

coderabbitai Bot commented Oct 10, 2026

Copy link
Copy Markdown

Walkthrough

Warning

Review details and warnings were omitted to fit the comment limit.

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