Systematic but simple way to enforce coherence and chainability between components

We have previously designed the "input_info" and "output_info" system to help enforce the constraint between the components. But it creates many extra boilerplates for people to implement, what's worse is these simple requirement check may not handle complex cases. But we still face problems at times, for example, if a prior system did not produce the annotation, or both systems are producing the same annotation.

We need to propose systematic method to handle such cases, but without introducing a lot of troubles to users. We also need to consider the problem from both static check and run-time check.

The issue names the input_info and output_info systems but no files or tests. Start by tracing how those annotations are checked today, then compare the requested static and run-time cases, including missing and duplicate annotations. Done would require an agreed, low-boilerplate design and a documented way to validate it.

Written by the indexing model from the issue text.