I was assuming that you would run the script that created the folders, thus the script would have your permissions, the folders would be created as owned by you, etc. That was the scenario I outlined above.
If the script is not going to be run from your account, then you could make use of setuid functionality to have it effectively run as you.
See 'man chmod' and look at the section on "set-user-ID-on-execution bit".
You set this bit with 'chmod +s name_of_script'

I never got a really specific "yes that would work" response to my question, but I'd like to try doing the following:

•*use SSH session to set the permissions of the enclosing (Client X) folder so that all Job folders within it are locked (but not their contents).

• also use SSH session before creating new Job Folders within Client X folder, to temporarily un-set those permissions so things can be created within Client X again, briefly; run the AppleScript; then, from SSH session, set the permissions back again.

So, in baby talk, character for character exactly as I would type the string, what do I type on the command line so as to make the folders within Client X folder protected? What do I type to turn it back off again later? And where does this "sticky bit" thing come into play?

(I have read man pages and tutorials and still don't get it. Please help?)

Actually, I just got off the phone with xinet, and it appears that there is a way to set the appletalk "Can't move, rename or delete this item (locked)" flag on a folder from the SSH Unix command line.

I'll post again with specifics if I get that working, and if that works it looks easier than the Unix solution (which would require resetting the Client folder's permissions every time a new Job folder is created).

Got it :)

/usr/etc/appletalk/kats -l /path/to/folder

That locks the sucker from the command line for AppleShare/AppleTalk users, doing exactly what checking the little checkbox does in the Mac GUI. That checkbox, incidentally, is not visible at all in any shape way or form from a MacOS X Finder but setting that flag locks the folder for MacOS X clients as well.

This is probably xinet-specific.