Skip to content

feat(domain): vendor the AI vendor classification registry artifact - #430

Closed
JeremyFunk wants to merge 1 commit into
mainfrom
ai/01-registry-artifact
Closed

feat(domain): vendor the AI vendor classification registry artifact#430
JeremyFunk wants to merge 1 commit into
mainfrom
ai/01-registry-artifact

Conversation

@JeremyFunk

@JeremyFunk JeremyFunk commented Aug 11, 2026

Copy link
Copy Markdown
Collaborator

What this layer contains

The vendored classification artifact and nothing that reads it:

  • packages/domain/src/ai-registry/registry.json — the compiled per-span AI/agent telemetry classification registry (21 vendors, 88 matchers, 29 session candidates, a 5-rule unknown tier).
  • UPSTREAM.json — the trace-capture pin (cb29d84) and the artifact sha256, so drift is detectable without a diff.
  • README.md — provenance, the four compile-time merge decisions, and why the capture corpus is deliberately not vendored.
  • .oxfmtrc.jsonc — ignores registry.json.

Why it is shaped this way

The artifact is ~280 KB of generated JSON with no logic in it, so it lands alone: a reviewer can diff the data once here and never have to re-read it while reviewing the six behavioural layers stacked on top. It is a build output that happens to be checked in — trace-capture is the source of truth, and patching the artifact in maple to fix a classification bug is the thing the README exists to prevent. The oxfmt ignore is part of that: it is copied verbatim from upstream, and formatting it would turn every future resync into a whole-file false diff.

The README's "TypeScript consumers" section is deliberately absent here — those files do not exist yet. It arrives with them in the fourth PR of this stack.

Gates run at this level

  • bun run --cwd packages/domain typecheck — clean.
  • oxlint and oxfmt --list-different over the touched paths — no findings, no formatting differences.

Dependencies

Based on main. Nothing in the stack below it.

🤖 Generated with Claude Code


Stack created with GitHub Stacks CLIGive Feedback 💬


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Adds `packages/domain/src/ai-registry/registry.json`, the compiled per-span
AI/agent telemetry classification registry generated by trace-capture
(pinned at cb29d84), plus `UPSTREAM.json` recording the pin and sha256 so
drift is detectable without a diff, and a README explaining the artifact,
its provenance, which of the two implementations reads it and why, and why
the capture corpus is deliberately not vendored.

The artifact is added on its own, with no consumers, so the ~280 KB of
vendored JSON lands in a reviewable commit of its own. `.oxfmtrc.jsonc`
ignores it: it is copied verbatim from upstream and formatting it would
turn every future resync into a false diff.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@JeremyFunk
JeremyFunk force-pushed the ai/01-registry-artifact branch from d6c7d9b to 1860da6 Compare August 12, 2026 20:04
@JeremyFunk

Copy link
Copy Markdown
Collaborator Author

Superseded by the v2 stack: #451#452#453. The registry-artifact + SQL-equivalence design this stack implemented was dropped in the write-side plan's v2 revision; vendor rules are now plain Rust with the vendored classification fixture as the CI gate.

@JeremyFunk JeremyFunk closed this Aug 13, 2026
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.

1 participant