Repository navigation
Declare this repo's own foundational record - #3
Merged
Merged
Conversation
Authored by driving the authoring MCP's real tools (record_facts + finalize_record, conversation mode) rather than hand-writing the file. created_by/maintained_by/model_access.mode are author-confirmed; technologies come from this repo's own pyproject.toml. created_by is the point: the forensic path infers SettleTop-Inc (the owning org) because GitHub exposes no creator field. The declared value is the person, with the inference retained as evidence. Co-Authored-By: Claude Opus 5 <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.
Adds
asset-record.jsonfor this repo — the Assessor is itself an agentic asset and should carry its own declared provenance.Authored by driving the authoring MCP's real tools (
record_facts→finalize_record, conversation mode), not hand-written.validate_record→[]; this repo's ownparse_recordround-trips it.Why this one, now: it also closes a live-verification gap. This repo has 37 marker hits — the corpus's own proof that marker scanning works here — so once merged and re-acquired it gives the first live before/after test that a record perturbs nothing:
asset-record.jsonHonest scope note: this record is
model_access: byo, so its body is not marker-bearing (0 hits if scanned directly). It therefore tests perturbation, not the marker-exclusion path itself — that needs an asset that legitimately pins a model, and fabricating one would be declaring something false. The exclusion is verified wired in the deployed image and covered by the adversarial unit test with its own non-vacuity control.🤖 Generated with Claude Code