Line of inquiry
Inquiring lines›What determines the reliability an…›Why do component-level checks miss…›this line of inquiry
How can workflow-level validation detect semantic corruption that protocol compliance misses?
A broader line of inquiry — a family of 30 specific questions the research asks around this. Follow one into its inquiring-line page, or move sideways to a related line below.
Questions in this line of inquiry 30
Specific inquiring lines the field asks around this — ordered from the most general framing down to the most specific angle.
- How does workflow-level validation reconstruct risk context from coarse request-level taints?
- How does semantic taint survive paraphrase across agent hops?
- Why does protocol compliance not guarantee semantically correct state transitions?
- Can workflow-level validation reconstruct the global risk context that no single step holds?
- How does taint propagation track risk along delegation paths?
- Can delegation prevent silent corruption in long delegated workflows?
- Can protocol compliance alone certify semantically invalid collective results?
- Can a quorum of protocol-compliant validators certify semantically invalid transitions?
- How does workflow-level validation reduce false positives from over-tainting sensitive data?
- Why does increased model capability make detection harder in delegated workflows?
- Do chain-level and flow-level checks face the same copyable-policy problem?
- Can human inspection of auto-generated workflows catch harmful or incorrect API compositions?
- Can SafeFlow distinguish benign uses of sensitive material from actual exfiltration?
- Why can every step pass its local check while a workflow still fails?
- How can we detect when protocol-compliant validators certify semantically incorrect states?
- When is information-flow tracking worth its cost over classification?
- Does semantic similarity monitoring face the same paraphrase failures in SafeFlow as in chain-of-thought monitors?
- Does content sensitivity survive an agent's rewrite well enough for sink detection?
- How does error accumulation in workflows scale across multiple model calls?
- Can a quorum of protocol-compliant validators certify a semantically invalid state?
- How much safety burden shifts between provider filters and model alignment in rerouted requests?
- Can domain-expert workflows always decompose into inspectable stages for AI?
- Can protocol compliance certify that a validator's objectives remain aligned?
- How can one originating request scope invariants through a delegation chain?
- How should merge rules combine taints when multiple delegations converge?
- When should a pipeline substitute defaults versus rejecting malformed outputs?
- What happens to approval rates when authorization checks are enabled?
- What are the three known routes for laundering harmful plans?
- What schema do SafeFlow's structured taints use to carry sensitivity information?
- Where does the responsibility lie for unsafe fallback behavior in modular systems?