Skip to content

Document retrospective-only provenance limitation #8

Description

@marklubin

Synix provenance is retrospective: it tracks which inputs and prompts produced each artifact, but it cannot answer forward-looking questions like "if I change this transcript, what downstream artifacts would be affected?" without re-running synix plan. This is a known limitation of the content-addressed caching model.

Add a "Known Limitations" section to README documenting this, with a pointer to synix plan as the workaround.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlogDeferred from v0.9documentationImprovements or additions to documentationprovenanceProvenance tracking

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions