This is a great idea for implementing a QA process. Unfortuantely, the publish permission is not currently broken out, but you can suggest the idea here on experience league. Count me in for an upvote of support!

Description - Presently, Query Service jobs do not write to the DCCS (Data Collection Core Services) which results in these events being ineligible to be qualified for event qualification to kick off a journey. I would like to be able to use a Query Service job to kick off a qualifying event for Why...

Interesting idea! The use case of multiple apps is one that I'm sure is all to common for many users like us. It works out to have multiple configurations in the channel for push that sute our needs, but I imagine this could allow for some easier configuration in the journey/campaign canvas!

Hey Chasin! Awesome response here.For option 2: You seem to indicate that the ability to just combine the event data the other data (seemingly profile data?) is an easy step. What process are you referencing to utilize to do the joining of the data? 

Hey Michael.There are lots of different opinions on this question.Before establishing our connection with our Paid environments, we did significant amounts of testing on match rates between our platforms.Once we had a good idea of what to expect when porting audiences over, we ran our queries to che...

But yes, using a customer audience, I think you should be able to use opens 

We trigger off of sends, not opens, but you should be able to do the same. 

We have implemented a use case similar to this. You can make an audience for that specific action, and then have a different journey using a read audience that triggers daily. 

Yeah unfortunately you cannot  Easiest workaround is to only select the columns that you need and then create a subquery, then regenerate your new column with your new data!