Maintained change-impact review

Trace concrete changes through maintained dependencies and review affected documents, tests, processes and responsible roles without inventing impact links.

Input

Result

A change becomes reviewable when its starting elements, baseline and maintained relationships are explicit. The AI selects meaningful exact passages from changed elements and affected records; server-side traversal supplies the actual paths and dependency evidence. Documents, tests, systems and process owners remain attached to their source IDs. A source-approved label never becomes an automatic release approval.

Your texts, pages and images are processed on our own servers in the EU. Trust Center

Try it now Pricing

Who it is for

Engineering, product, operations and quality teams reviewing changes against a maintained dependency register. Suitable for preparing a change meeting or handover, not for discovering undocumented relationships or certifying regulatory compliance.

Typical uses

Trace an interface change to maintained documentation and test records.
Review upstream prerequisites or both directions without reinterpreting reverse links as proven downstream impact.
Filter review candidates by type, criticality and source approval while retaining intermediate path nodes.
Expose missing owners, missing reachable document or test records, draft approvals, cycles and depth limits before a human release decision.

Example

Input

Maintained elements: id,name,kind,criticality,approval,owner,description S1,Order service,system,high,approved,Platform team,The service validates incoming order fields. D1,Order handbook,document,medium,draft,Documentation team,The handbook describes required order fields. T1,Order validation test,test,high,approved,Quality team,The test checks missing required order fields. Maintained dependencies: id,from,to,evidence L1,S1,D1,The handbook documents the order service interface. L2,S1,T1,The test exercises the order service validation. Concrete proposed changes: id,element,description C1,S1,Add a mandatory delivery reference to each order. Starting element IDs: S1 Traversal direction: Forward Maximum path depth: 10 Element type filter: All Criticality filter: All Source approval filter: All Baseline version: BASE-1 Maximum review selections: 10 Quotation detail: Detailed Display order: Path depth

Result

The order-service change reaches the handbook through L1 and the validation test through L2. Both results retain exact change and source quotations. Separate evidence rows show the full maintained text and endpoints for L1 and L2 once each. The handbook remains labelled draft in the supplied baseline. No test is executed and no approval is inferred.

A fixed example, shortened. Real results are AI-generated: please check them.

Price and limits

Price: usually 1–3 credits
Available with: Free, With package
Input limit: One page with up to 100,000 characters of HTML

Privacy

Processed on our own servers in the EU (Poland). Inputs and results are deleted after 7 days (Free) or 30 days (packages), or right after you see the result if you choose not to store them. Images are deleted right after processing.

In the API

Tool name: change_impact. Create a job with POST /api/v1/jobs and fetch the result with GET /api/v1/jobs/{id}. You find your API key in your account.

curl -X POST https://do4u.eu/api/v1/jobs \
  -H "Authorization: Bearer d4u_…" -H "Content-Type: application/json" \
  -d '{"tool": "change_impact", "url": "https://example.com/"}'

Full API documentation →

Questions and answers

Does the model discover new impact links?

No. Each selected change must belong to the server-computed allowlist for the selected element. Every displayed path contains only maintained dependency IDs. Full exact evidence for each used edge appears once in a separate evidence row with explicit endpoints. Missing relationships remain unknown.

What do cycles and filters mean?

Traversal visits nodes once and reports cycle edges. Type, criticality and approval filters select review candidates after traversal, so hidden intermediate nodes still support the path. A depth boundary explicitly limits coverage.

Does approved mean safe to release?

No. It is a label copied from the supplied element register. Baseline labels, ownership and approval evidence require human review.

Is my text stored?

Only as long as needed: 7 days on Free, 30 days with a package – or not at all if you choose not to store it. Processing happens on our own servers in the EU (Poland).

Can I use the result right away?

Results are AI-generated. Please read them before you publish or send them.