Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

kyberforge: agent-audit provenance/sources chain validation #60

New Issue
Closed
opened 2026-07-04 09:31:25 +00:00 by Claude · 0 comments
Claude commented 2026-07-04 09:31:25 +00:00
Collaborator
Copy Link

Context

Follow-on deferred from the agent-audit workstream (issue #11). Explicitly out of scope for the initial implementation.

Related: #11 (parent workstream) · ADR-0015 (docs/adr/0015-agent-author-dual-provider-scaffold.md)

Overview

agent-author produces agents/sources.md at plugin scope (Step 4). This file records which research sources informed which agent files — the provenance chain for agent authoring.

skill-audit has validate-provenance.sh that validates the equivalent references/sources.md for skills. agent-audit has no equivalent.

Why deferred: At plugin scope, agents/sources.md is optional (deleted by agent-author when no research sources are in context). The structure and format of agents/sources.md is not yet formally specified. A provenance check becomes worthwhile once the format is stabilised and there are real agents/sources.md files to validate against.

Acceptance criteria

  • validate-provenance.sh <agent-file> (or equivalent) validates agents/sources.md at plugin scope
  • Checks: sources.md exists when agent file has source_keys in context, no unfilled placeholders, contributing files listed exist on disk, research doc field present and non-empty
  • agent-audit skill body updated to run the provenance check and surface findings as a ### Provenance dimension
  • agent-author Step 4 updated to reference the expected agents/sources.md format
## Context Follow-on deferred from the `agent-audit` workstream (issue #11). Explicitly out of scope for the initial implementation. **Related:** #11 (parent workstream) · ADR-0015 (`docs/adr/0015-agent-author-dual-provider-scaffold.md`) --- ## Overview `agent-author` produces `agents/sources.md` at plugin scope (Step 4). This file records which research sources informed which agent files — the provenance chain for agent authoring. `skill-audit` has `validate-provenance.sh` that validates the equivalent `references/sources.md` for skills. `agent-audit` has no equivalent. **Why deferred:** At plugin scope, `agents/sources.md` is optional (deleted by `agent-author` when no research sources are in context). The structure and format of `agents/sources.md` is not yet formally specified. A provenance check becomes worthwhile once the format is stabilised and there are real `agents/sources.md` files to validate against. ## Acceptance criteria - [x] `validate-provenance.sh <agent-file>` (or equivalent) validates `agents/sources.md` at plugin scope - [x] Checks: sources.md exists when agent file has `source_keys` in context, no unfilled placeholders, contributing files listed exist on disk, research doc field present and non-empty - [x] `agent-audit` skill body updated to run the provenance check and surface findings as a `### Provenance` dimension - [x] `agent-author` Step 4 updated to reference the expected `agents/sources.md` format
Claude added this to the Kyberforge basics milestone 2026-07-04 09:31:25 +00:00
Claude added the Kind/Feature
Priority
Low
4
 labels 2026-07-04 09:31:25 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label Kind/Feature
Priority
Low
4
Milestone
No items
No Milestone Kyberforge basics
Projects
Clear projects
No project
Assignees
Clear assignees
Claude renovate-bot Defame1297
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Defame1297/holocron#60
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?