"people use the word "design" in a way that does always imply an intelligent agency of some sort. I don't prefer that usage, but Richard Dawkins, for example, does."
I have noted for you that I reject your 'artificial design' descriptor, and I here once again re-iterate that rejection for the record. It is a bit more than semantics, however. For example, you are contradicting yourself by saying that 'design always does' and then turning around and finding a way for it to 'not to.' This is a problem in the category of equivocation that is going to come back and bite us eventually. But having said that for the record, we can move on.
"I would say that such piles were not designed by an intelligent agent but by forces of nature."
But unless you have a methodology of your own that helps you tell the difference, this can remain only your opinion. Offering such a methodology, however, means admitting that it is possible to apply a method in order to detect the difference. If you want to go further and say that it is a scientific fact that it was the 'forces of nature' then that would make ID at least as scientific as the method you are employing.
OK, but you are using "not designed" in the same meaning as my expression "naturally designed". I also use "artificial design" as a rough synonym of "intelligent design", although the intelligent agency may only have indirectly caused the artifical design.
This is an example of the danger of equivocation. I would suggest that now is not the time to impose your usage on the rest of the world, which you have said (again sniping at my information comment) "does always imply an intelligent agency of some sort." It would be nice to know that on such a very basic concept, we are meaning the same thing by the words we are using.
"This is too vague a description to be considered a prediction."
Not really. It just means that I was offering a principle which can be extended into different contexts. No point in over-specifying. Not to totally knock your point- I agree that given a particular system, we'd want to refine the terms of the predictive framework a little bit more.
"Presumably, the rock pile would usually fail to cross the 'threshold' of criteria for intelligent agency. You need to state precisely what that threshold is."
I explained this in the blocks analogy. In that particular example, as we could in many other examples, we could run a battery of tests appropriate for the system we are looking at in order to find out where the threshold is in that system. For example, with the blocks, I actually went and videotaped a series of tests where the blocks would only 'naturally' stack up no higher than 3 high. Then I ran a couple of designed tests, where I could get the blocks up to between 12-14 high.
This gave us the limits of the natural causes as well as the ultimate capability in terms of designed capability. We might allow some statistical ambiguity if we ever came upon some blocks stacked 5 high, but technically, given the data at hand only showed 3 high as the max, we would have good cause to consider design FIRST until proven otherwise, instead of the other way around.
This principle can be used in other contexts, as well, even though some obvious practical difficulties await us in certain systems.
"The problem is that you have not specified any criterion for distinguishing the complexity of naturally evolved systems and artificially designed systems. "
No, you're right. But that is only because I have only been trying to explain the principle to you. Obviously it would be pointless to go further if you won't even allow the validity of the technique even in principle.
So, do you acknowledge the validity of this idea
in principle?
You run your empirical tests to determine what nature is observed to do. Then you run your tests to see what intelligent agents can do. Then you compare. Real simple, in my book.
"It has been proposed (by me and others) that intelligently designed complexity can be distinguished from artifical complexity on the grounds that intelligent designers consciously remove nonfunctional parts of the design."
Like the hood ornament?
"First of all, the alleged "intelligent designer", despite frequent denials by IDists, is really an infallible God."
Well, if you can't allow them to define the terms of their own argument, you are not really treating the argument with respect, just as you would not appreciate me saying that evolutionary theory is just a cover for atheism. You might say, "Well, that's simply not true, that's the difference" but I can retort the same way. Such statements as the one that I have quoted really get us nowhere. You have to take people at their words in these contexts, or simply not participate.
""Down's Syndrome is believed to be a DNA flaw related to a problem with a single chromosome. Humans can survive with Down's Syndrome, but at a significantly diminished capacity.""
"Quite so. What does Down Syndrome tell us about Intelligent Design?"
Not much, if your contention is that ID means persistent intervention. Quite a bit, if you understand that you are allowed to design something and 'let it go' without later on having people challenge that it is designed (on grounds perhaps not defined right now). Thus a house left untended will tend towards disrepair, but no one thinks on this account that it was not designed. The inference, if anything, would be that it was poor design, but not that it was NOT designed. Here we see where your persistent notion that 'despite denials' the only designer that ID refers to is an infallible designer fails to take the measure of the situation. It could be Crick's aliens that seeded our planet's life, for example. I don't recall Crick suggesting that the aliens were infallible, so he certainly wouldn't have been turned off by evidence of 'poor design.'
In terms of the biological system in question- the human one- Down's syndrome is just one deviation from the genetic code that leads to either death or significantly diminished operating capacity. There are quite a few of them, aren't there? A single mutation in the wrong place is all it takes.
But this is something we could test. With the aid of our intelligent agency (Can biologists detect when another biologist has tampered with genes? Or is any genetic tampering in principle not scientifically detectable in your view?) we can change out aspects of the genes to see what happens and get a really concrete idea about just how much deviation the human genome can tolerate.
"Yes, but that is based on our knowledge about children's toy blocks and the usual processes that create such stacks"
Actually, it was based on 30 minutes of video taped experimentation. :)
"It is not about a naturally occurring stack of things (e.g. balancing rocks) that can reasonably be expected to emerge by natural forces over large periods of time."
Well, this might be a good idea to point out the flaw in your rebuttal example. Balancing rocks such as you describe are formed by erosion. They are not built up, they are carved out. Its apples and oranges.
Your 'reasonably be expected' fails on the same 'threshold' question you have been raising in my regards. What kind of objective methodology do you have for establishing what can be 'reasonably be expected.'
"Your experiment would only tell us about the probability of such structures within a relatively small collection of random events. Expand the search space, and you will come to a point where it is reasonable to expect such a stack to occur somewhere in that large collection of events."
Why do you think this is a problem? You think it is better to not be bound to any collection of events at all? How do you know that if we expand the search space 'it is reasonable to expect' without performing the type of test I am mentioning it? If you have no intention of doing any test at all, your 'threshold' of reasonability is not rooted in any kind of empirical constraint. I am afraid I don't think its very reasonable to perform no experiments and rely on subjective notions about where the 'point' where 'it is reasonable to expect' things. At least, not from a scientific point of view.
"Be very careful here. DNA is part of a self-replicating process. The stack of blocks scenario does not address that kind of phenomenon, but it is key to the understanding of evolutionary design."
Indeed it is, but that is no hope for a rescue, because we can (and I did) come up with self-replicating processes that still undermine the your idea of 'evolutionary design.'
"DNA is itself thought to have been the result of self-replicating processes over extremely long periods of time. One hypothesis is that it evolved out of RNA."
Nothing like a string of 'is thoughts' to really bring me around to the strength of your
scientific position.
"Is there? What is that threshold? You never specify it."
Again, my focus on the principle. Again, your own view is depending on a threshold. Somehow, and somewhere, you appear to be aware of what you can expect given enough time or chances or whatever, but I'll bet 10 hamburgers you can't tell me when that threshold begins or ends.
"You can come up with an arbitrary measure of complexity, such as Behe once did,"
I really have trouble comprehending how my measure is considered arbitrary, even though I have specifically explained how it is arrived at, while you manage to be able to reasonably "expect such a stack to occur somewhere in that large collection of events."
How large a collection of events, my friend?
"I'm not sure that I follow you. Many self-replicating programs do not co-opt external systems."
My emphasis is not on the co-opting of external systems, though when I think about it I wonder if I may have more there than I thought. I only used the example. I even said 'many' not 'all.' Given your propensity to really nail me on anything giving you any ambiguity, I'm surprised you missed it. My emphasis was how the program's functionality depended on accuracy at the most basic level.
In the example of calling 'copyme.exe' Any single letter of that file-name could be off, and the program simply would not reproduce. I gave the example of one letter off. The point is that when you've got a program where the whole point of it is to reproduce (as I think it would be agreed is the case for biological organisms), then an error in such a system may not be fatal to its own functioning per se, but defeats its ultimate purpose. An email virus may successfully send out emails, but it may not successfully attach itself to the emails that go out. Or, the emails won't go out- but if they had, the virus would have successfully attached. The more failure points we have the less room for error exists.
Of course, now we get into questions of redundancy.
As I said, we can go to the code and start omitting letters, or replacing them, and come up with an empirically derived assessment of just how much deviation is possible before the system doesn't work at all. Its not arbitrary.
"This is not a problem with reproduction in general so much as it is a problem with the analogy that you are trying to impose on reproduction."
Or perhaps the problem is that you are treating biological systems as a special case. I would argue that if biological systems are a special case, a singularity of sorts, where like the time preceding the 'big bang' nothing is known and yet you still wish to make pronouncements about what is known, then your position is suitably weak. If the rules you think apply to biological systems only apply to them and have no application anywhere else, I hardly even see why they deserve the time of day.
This begs the question: in human reproduction, are there examples in the genes where even a single change can end the process? We can go further, and look at the actual macro effects. In human reproduction, there are a gazillion things that happen when a woman is giving birth- never mind the 10 months gestation- where if this or that didn't happen, you would not have either a living baby or a living mother, or perhaps neither. There are a whole series of things that happen that are vital to the survival of the organism and its offspring that if they don't happen, results in 'termination.' That would be bad for evolution.

These things happen first in the genome.
""To do that, we can RUN TESTS""
"Some processes can be detected as suspicious."
You aren't following me. I am only asserting that we can look at the code itself and manipulate it in order to see how much deviation it can handle before it doesn't work at all. Somehow you've gotten on this 'virus detection' kick which is nowhere near the point I'm making. Its the same as with the blocks: you CAN run tests to establish your statistical threshold. It IS possible. It does not have to be arbitrary.
That is the main point of both my computer program example and my children's blocks analogy.