Delivery Graph
The relationships underneath the modules.
Illustrative delivery chain · not customer data
Define the acceptance criterion.
↔Record the proposed commitment.
↔Keep the exact agreed answer.
↔Carry the commitment forward.
↔Design against the baseline.
↔Record the verification.
↔Keep the completion evidence.
Linked items · REQ-014
Requirement
The package must sustain the agreed duty throughout the acceptance test.
Different ways a connection is made.
Implemented in defined workflows
Workflow-created links
Tender award creates explicit contract and frozen-baseline references. These are controlled workflow links, not a promise that every item links automatically.
Implemented in registers
User-selected references
Teams can select linked requirements, documents and source records in supported registers. Project Management references existing items rather than copying them.
Planned concept
AI-suggested connections
Suggestions for new relationship links would need human review and permission checks. Automatic AI graph enrichment is not implemented.
Present today
References and a stored relationship layer.
TENOPER stores relationship edges and supports linked source records, requirement references and document references. Existing module views expose specific connections, including baseline traceability.
The direction
Follow the work in both directions.
The example above illustrates moving from a requirement to its evidence, or back from evidence to the commitment. A universal “Linked items” explorer and fully automatic lineage across the entire chain are not available today.
Your next project