lineage_record
Record a provenance atom to answer where a willow came from, why it is this way, and what was here before. Requires rationale and evidence for verifiable memory.
Instructions
Record a provenance atom — the "story of this willow" as memory an agent
can query later. Answers the questions agents keep asking: where did this
come from, why is it this way, what was here before. rationale (the WHY)
and at least one evidence citation (a PR / commit / file / session) are
REQUIRED — an atom that can't cite is lore, not memory, and is refused.
Relationships to other atoms are typed EDGES (stored in lineage_edges, the
same {from,to,relation,context} shape willow's own knowledge graph uses), and
direction is QUERIED, not stored twice:
supersedes— atoms this REPLACES (the old ones become non-current)derived_from— atoms this CAME FROM but did NOT retire (both stay valid)motivated_by— the friction/decision behind it (may be a gap id or an external node, not only another atom)
Corrections re-record the same id in place; edges persist independently.
Confined to your store_scope like every store write.
subject_id (guardian-consent seam): a provenance atom that makes a
person-shaped claim about a non-owner names that subject here. This is the
highest bar in the seam — person_inference — corpus-lens's quarantined
PERSON_CLAIM_TYPES: making the claim at all requires a verified grant. Opaque,
never stored on the atom. Leave empty for the owner or for non-person lineage.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| tags | No | ||
| title | Yes | ||
| app_id | Yes | ||
| origin | No | ||
| evidence | No | ||
| authority | No | ||
| rationale | Yes | ||
| subject_id | No | ||
| supersedes | No | ||
| derived_from | No | ||
| motivated_by | No |