My apologies for the vagueness of that question, but I'm not sure how else to pose it. Here is the situation. We have a Sitecore 8 project that uses TDS for syncing items. We have a policy of not adding most content into TDS, only one-off structural items are to be added, otherwise it's only templates and renderings and whatnot. One of the content items we do have in TDS is the main homepage item which apparently mistakenly got set to "AlwaysUpdate." We have the TDS project set to "disable file deployment."
Last night we did a deploy to production and verified that the site was correct. It was also verified to be correct this morning. This afternoon, the homepage had magically reverted to an older state (values on some fields were changed and a few components went missing). I looked on the file system and sure enough, there was a "sitehome.item" file sitting in the /data/serialization/master/content folder that has a timestamp of our deploy the night before. I'm not surprised by this since the item was set to "AlwaysUpdate," though I thought "disable file deployment" would have stopped this from being uploaded.
What I am surprised at is how the site was seemingly fine all day, and then all of a sudden seemed to not only install the sitehome.item file back into the database, but also publish itself to the CD.
Does Sitecore monitor that serialization folder on a schedule job and import that data back into the system somehow?