Kairos Artifact Model

A result such as “implementation completed” is useful, but it is not the implementation. Reviewers and later executors also need a durable way to find the commit, document, report, archive, or uploaded file that was actually produced.

Kairos calls that concrete deliverable an Artifact. A Submission explains the outcome; its Artifacts make the outcome inspectable after the original session is gone.

Declaring the Expected Deliverable

A Workflow Task Definition may declare named Artifact requirements. The name is the stable contract key and the description tells the executor what to deliver. Every declared name must appear once in a successful Submission; additional Artifacts are allowed.

Blackboard Tasks express expected deliverables in their description rather than a structured Artifact contract.

Kairos deliberately does not encode media type, file format, count range, or storage policy in a Task Definition. Those details belong to the work instructions or deployment.

From Creation to Submission

An executor may create an Artifact only under an active Task Claim. It can either:

The Artifact remains staged to its creating Claim until submit_task includes its ID. Submission atomically validates Claim ownership and Workflow requirements, creates the immutable Submission, binds the Artifacts, and ends responsibility.

What Later Collaborators Can See

A staged Artifact is visible only inside its creating Claim. A submitted Artifact is visible throughout the WorkItem and remains attached to its Submission even when Review rejects that result.

The WorkItem artifact list is complete submission history, not a set of current effective deliverables. Loops, retries, and Review revisions can produce repeated names; names are unique only within a Submission. The console groups Workflow artifact history by Definition node, then Task execution instance and Submission. Blackboard history groups independent Tasks without merging equally titled Tasks. Submission time, Review status and feedback remain visible, with older executions/submissions collapsed by default. Node execution counts are not global WorkItem rounds.

Execution context separates the active Claim’s staged artifacts, the Workflow’s direct input artifacts, and Blackboard shared submission history. Workflow inputs resolve the exact Submission referenced by each applied decision in the current activation’s input receipts. They never select the newest artifact by name or time or fall back to ancestors. Skipped sources and inputs without artifacts contribute no group; replacement attempts retain their input receipts. Blackboard shared history includes pending and rejected submissions with provenance and Review status; advisory Task Relations do not restrict this shared scope.

Context responses expose Artifact metadata, not file bytes. Managed content is downloaded or previewed through its dedicated authenticated endpoint. The console can preview small text deliverables alongside their Submission and Review history. Exact fields and preview boundaries are defined in the API reference.

Retries never overwrite submitted Artifacts. A later attempt creates new Artifacts and a new Submission, preserving the earlier evidence.

If Review rejects a report, the rejected file remains attached to that Submission. The next executor uploads a revised report and submits it separately, allowing the reviewer to compare attempts instead of seeing one mutable file whose history has disappeared.

Artifact Storage and Retention

The deployment owns one managed Store and the upload, retention, and garbage-collection policy. Managed Artifacts use stable kairos:// URIs plus digest and size metadata. Large deliverables should live in durable external storage and be registered by absolute URI.

An active Claim protects its staged Artifacts. After the Claim ends, old unsubmitted Artifacts and incomplete upload records may be collected. Submitted Artifacts are retained as work history.

Exact upload transports, limits, replay behavior, permissions, and defaults are defined in the API Reference and OpenAPI.

Artifact Invariants