Skip to content

[proposal] Tracking statement dependencies #37

@Tiendil

Description

@Tiendil

This task is a proposal for discussion and a container for ideas. We'll decide to implement it or not after Donna achieves some maturity and we collect enough experience and use cases.

This proposal copupled with next proposals:

There are a lot of cases when we need to track and validate dependencies between various statements in the documents.

Here are some examples for the case of a fictional Request for Comments (RFC) document:

  • Each goal statements must be referenced by at least one objective statement.
  • Each objective statement must reference a single goal statement.
  • Each objective statement must be referenced by at least one requirement statement.
  • Each requirement statement must reference at least one objective statement.
  • Each requirement statement must be referenced by at least one action point statement.
  • Each requirement statement must reference at least one verification statement.
  • etc.

Having formalized dependencies is great for ensuring consistency and fullness of the documents. It also allows us to automate various tasks.

However, currently agents can work with such dependencies only directly (via LLM), which leads to eating tokens, context, and producing unreliable results.

We should find a way to formalize such dependencies in the document structure so Donna can track and validate them automatically.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions