Skip to content

A knowledge-base write leaves no artifact #118

Description

@EdmondDantes

Defect

A run can write to the knowledge base — KnowledgeTool has a record action since #85 — and the write leaves no artifact, so nothing about it is reviewable.

The auto-artifact pass added in #86 walks a step's history and picks up only write_file tool calls (WorkflowAbstract.php:1077), so a note filed under kb/ never becomes a step artifact. Every other thing a step produces is listed and readable afterwards; this one is invisible.

This is what makes a base write reviewable without a human gate in front of it: the artifact is the review surface. Artifact::file() already carries a path relative to the project and the dashboard fetches the body lazily, so a note under kb/ fits the existing shape with nothing new underneath.

Acceptance

  • A step that records a note lists it among its artifacts, with the note's path and body readable from the dashboard.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions