feat(integrations): commit cpex-ocsf-audit reference implementation - #412
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The crate has sat untracked in the working tree for several sprints. Unlike the review-package copy under docs/cosai-ws4-ocsf-mapping/, this path was not covered by any .gitignore rule — so it had neither the protection of an ignore rule nor the backup of being tracked, and was one `git add -A` from an undeliberate publication. Its own Cargo.toml header states the intent: standalone, outside the cpex workspace, "so it can live in the AI-Identity repo as a reference implementation". This makes that deliberate. Own code, Apache-2.0, all deps from crates.io. contextforge-org/cpex is a public repo and this crate is a near-twin of its public audit-logger builtin. Prepared for publication: - Build docs point at the public `dev` branch (verified to carry crates/cpex-core). The feat/hil_apl baseline is not a public branch; kept as provenance with API drift against dev called out as unverified. - README no longer links two gitignored files (CMF-OCSF-FIELD-MAP.md, cmf-ocsf-mapping-review.md) that would 404 publicly and name a private review artifact. The mapping now points at src/ocsf.rs, which is the executable mapping anyway. - ANTIGRAVITY-TASK*.md offload briefs excluded and gitignored — internal workflow, not deliverables. Not rebuilt against dev; last verified green against feat/hil_apl ad666ba. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Levaj2000
force-pushed
the
feat/cpex-ocsf-audit-refimpl
branch
from
July 27, 2026 18:44
fcca7a6 to
bdb2647
Compare
Levaj2000
added a commit
that referenced
this pull request
Jul 27, 2026
…no API drift (#414) #412 shipped the crate with an honest caveat: last verified green against feat/hil_apl ad666ba (not a public branch), never rebuilt against public dev. Closed today: against dev @ baa9e17 (shallow clone, path dep repointed, lockfile regenerated) cargo build, all 13 tests, and the emit_sample example pass unchanged. No API drift at the surface this crate uses. Manifest header, README (Building + Status), and the changelog entry updated from 'expect API drift' to the dual-baseline verified claim. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Commits
integrations/cpex-ocsf-audit/— the CPEX CMF plugin that emits each dispatched request as an OCSF AI Operation event off therun(audit-log)seam, optionally hash-chained and DSSE-signed.Why now
The crate had sat untracked in the working tree for several sprints. Unlike the review-package copy under
docs/cosai-ws4-ocsf-mapping/(gitignored at.gitignore:75), this path matched no ignore rule — so it had neither the protection of an ignore rule nor the backup of being tracked, and was onegit add -Afrom undeliberate publication. Its own manifest already stated the intent:This makes that deliberate.
Why it's safe to publish
license = "Apache-2.0", every dependency from crates.io (no git-sourced or vendored deps).contextforge-org/cpexis itself a public repo; this crate is a near-twin of its publicaudit-loggerbuiltin, differing only in record shape.scripts/check-no-confidential.shpasses; a secret/PII scan of the diff found only the synthetic fixturealice@corp.com.Prepared for publication
dev(verified to carrycrates/cpex-core).feat/hil_aplis not a public branch — confirmed absent from the 26 public heads — so it's kept only as verified-green provenance, with drift againstdevflagged as unverified.CMF-OCSF-FIELD-MAP.mdandcmf-ocsf-mapping-review.md, both gitignored: they would have 404'd for every public reader and named a private review artifact. The mapping now points atsrc/ocsf.rs, which is the executable mapping anyway.ANTIGRAVITY-TASK*.mdexcluded and gitignored at any depth — offload briefs are internal workflow, not deliverables.Known gap
Not rebuilt against
dev. Last verified green againstfeat/hil_aplad666ba(2026-07-06); API drift is unverified and called out in both the manifest header and the changelog. Needs acargo buildagainst adevcheckout to close.Closes the "decide a home for the CPEX crate" item (sprint 18 #436).