A12 aggregates – Sequential

description (summary)	1999-6-20	jo	niche	[Input File: zg1183ms.j]
description (summary)	1999-6-26	jo	A12 corresponding number of A10 a31	[Input File: zg127ms.J]

Spatial Aggregation

features within aggregate

1999-6-20

f13, f12, f39 and f70

[Input File: zg1183ms.j]

Descriptive

a7

/MZ/A/A12/D/A/0007.HTM

Labeling/Designation

category	!!	!!	installation	[Input File: !!]
definition (typological label)	1999-6-26	jo	pit aggregate	[Input File: j718jo.j]

Description/Count

description (summary)	1999-6-26	jo	cut and fill of pit	[Input File: j718jo.j]
description (summary)	1999-6-26	jo	a 110cm in diameter pit S k6, 440cm W f41.	[Input File: zg127ms.J]

Spatial Aggregation

features within aggregate

1999-6-26

f78,f79

[Input File: j718jo.j]

Descriptive

a8

/MZ/A/A12/D/A/0008.HTM

Labeling/Designation

category	!!	!!	installation	[Input File: !!]
definition (typological label)	1999-6-26	jo	grave	[Input File: j718jo.j]

Description/Count

description (summary)	1999-6-26	jo	child grave	[Input File: j718jo.j]
description (summary)	1999-6-28	jo	irregular rectangular shaped grave, 72 cm max length, x 41 cm max width, x 15 cm depth: oriented NW to SE. There are no particular signs of any type of construction related to the grave; it seems to have been simply dug into the ground and its base f95 was levelled. The grave was found in poor condition and the human bones were found mixed in f83 within the boundaries of f84. we only noticed that most of the skull bones were located at the NW end of the grave, next to i14 and i18: the sizes of the grave and of the bones suggest that it was a child burial.	[Input File: zg127ms.J]

Spatial Aggregation

features within aggregate

1999-6-26

f83,f84,f95,i14,i15,i16,i17,i18

[Input File: j718jo.j]

Descriptive

a9

/MZ/A/A12/D/A/0009.HTM

Labeling/Designation

category	!!	!!	clay artifact	[Input File: !!]
definition (typological label)	1999-6-26	jo	tannur	[Input File: j718jo.j]

Spatial Aggregation

features within aggregate

1999-6-26

f93,f94

[Input File: j718jo.j]

Descriptive

a10

/MZ/A/A12/D/A/0010.HTM

Labeling/Designation

category	!!	!!	other features	[Input File: !!]
definition (typological label)	1999-6-26	jo	grave	[Input File: j718jo.j]
definition (typological label)	1999-6-30	ab	burial	[Input File: j803ab.j]

Description/Count

description (summary)	1999-6-26	jo	animal grave	[Input File: j718jo.j]
description (summary)	1999-6-30	ab	skeleton deposition on the ground without any specific construction. The animal skeleton and several metal objects (i20, i21, i22, i23, i24, q73.1) are laid together. Associated with these bronze offerings there is also a small, cylindrical, carneol bead, but there is no pottery. All bones (A12q73 b) are in one bag; we found some large fragments, but are mostly broken into small pieces.	[Input File: j803ab.j]

Recovery/Assignment

notes on recovery

1999-6-30

we took no pictures and did no drawings of the burial because the bones and artifacts come out step by step. The metal artifacts, which are particularly rich and well preserved, laid mostly under the bones. The burial wasn't clearly defined and was very small (different than the animal deposition in A7 MZ10, where the complete skeleton was "carefully" laid down on the ground).

[Input File: j803ab.j]

Spatial Aggregation

features within aggregate	1999-6-26	jo	f98,q73,i20,i21,i22,i23,i24,i25, q73.1, q73.2	[Input File: j718jo.j]
elements (included within aggregate)	1999-6-30	ab	i20, i21, i22, i23, i24, q73.1, q73.2, q73-b	[Input File: j803ab.j]
notes on aggregation	1999-6-30	ab	A12q69.1-ja and A12q69.2-ja were at the same elevation but ca. 80 cm East of a10. They aren't directly associated with the burial, but they are the only vessels in the vicinity.	[Input File: j803ab.j]

Descriptive

notes on typology

1999-6-30

Prof. Castelletti j731 did a general analysis about the bones and observed that the bones belong to an old cow, whose teeth were almost completely used. Not all the cow's bones are present. Apparently only some parts of the body's bones were selected (head, lower part of two legs). He couldn't say if this should be associated with some sort of ritual.

[Input File: j803ab.j]

a11

/MZ/A/A12/D/A/0011.HTM

Labeling/Designation

category	!!	!!	installation	[Input File: !!]
definition (typological label)	1999-6-26	jo	pit aggregate	[Input File: j718jo.j]

Recovery/Assignment

daily notes	1999-7-04	ab	as we dug the rest of accumulation f40 we found that it is also contained by a circular line of bricks at the S part, as it was the case in the W and N parts. That confirms that it is the filling of the pit, therefore we assigned a feature number for the cut and several feature's numbers equal to f40.	[Input File: j718ab.j]
daily notes	1999-7-08	ab	f141 is the best accumulation removal from inside the pit a11, below the accumulation the floor of the part is found by the remaining bricks of the wall and the stone foundation f151.	[Input File: j718ab.j]
strategy (projected or implemented)	1999-7-03	ab	since we dug the whole N portion of the filling of a12 (in k5) as f40, we are going to dig the S portion (in k10) by dividing the filling accumulation into number of features, separating them by elevation, since there is no distinct difference in the type of accumulation.	[Input File: j718ab.j]

Spatial Aggregation

features within aggregate

1999-6-26

f40,f118,f123,f124,f126,f128,f152

[Input File: j718jo.j]

Descriptive

a12

/MZ/A/A12/D/A/0012.HTM

Labeling/Designation

category	!!	!!	installation	[Input File: !!]
definition (typological label)	1999-6-26	jo	installation	[Input File: j718jo.j]

Description/Count

description (summary)

1999-6-26

andiron

[Input File: j718jo.j]

Spatial Aggregation

features within aggregate

1999-6-26

f122,f127

[Input File: j718jo.j]

Descriptive

a13

/MZ/A/A12/D/A/0013.HTM

Labeling/Designation

category	!!	!!	other features	[Input File: !!]
definition (typological label)	1999-6-26	jo	grave	[Input File: j718jo.j]
definition (typological label)	1999-6-30	ab	burial	[Input File: j803ab.j]

Description/Count

description (summary)	1999-6-26	jo	1 large and 2 small jars and a human bones	[Input File: j718jo.j]
description (summary)	1999-6-30	ab	deposition in the ground. Almost traingular shaped grave. A large jar with rope decoration (i23),laid on the ground, is broken in many pieces but seems to be complete. Inside it there was only dirt, no bones as usually one would expect. Near its rim there were a small, double rim necked jar (q148.3) and a bit higher a broken, incised jar (q148.1). South of the rim of the big jar there was an other borken jar (q143.2), the sherds of which were large and pilled in four layers. On top of them laid the skull and many small bones all grouped togheter. Very unusual deposition. No other offerings seem to be associated with it.	[Input File: j803ab.j]

Spatial Aggregation

features within aggregate	1999-6-26	jo	f135,i32,i33,q148.1,q148.2,q148.3	[Input File: j718jo.j]
elements (included within aggregate)	1999-6-30	ab	i32, i33, q148.1, q148.2, q148.3.	[Input File: j803ab.j]
notes on aggregation	1999-6-30	ab	the photos of this burial are v26 and v25.	[Input File: j803ab.j]

Descriptive

notes on typology

1999-6-30

maybe a fallen brick broke the Southern most jar and the skull.

[Input File: j803ab.j]

a14

/MZ/A/A12/D/A/0014.HTM

Labeling/Designation

category	!!	!!	installation	[Input File: !!]
definition (typological label)	1999-6-26	jo	pit aggregate	[Input File: j718jo.j]

Spatial Aggregation

features within aggregate

1999-6-26

f137,f163

[Input File: j718jo.j]

Descriptive

a15

/MZ/A/A12/D/A/0015.HTM

Labeling/Designation

category	!!	!!	unknown	[Input File: !!]
definition (typological label)	1999-6-26	jo	unknown	[Input File: j718jo.j]

Spatial Aggregation

features within aggregate

1999-6-26

f156,f160

[Input File: j718jo.j]

Descriptive

a16

/MZ/A/A12/D/A/0016.HTM

Labeling/Designation

category	!!	!!	installation	[Input File: !!]
definition (typological label)	1999-6-26	jo	installation	[Input File: j718jo.j]

Description/Count

description (summary)

1999-6-26

drain

[Input File: j718jo.j]

Spatial Aggregation

features within aggregate

1999-6-26

f169,f170

[Input File: j718jo.j]

Descriptive

a17

/MZ/A/A12/D/A/0017.HTM

Labeling/Designation

category	!!	!!	surface	[Input File: !!]
definition (typological label)	1999-6-26	jo	pavement	[Input File: j718jo.j]

Spatial Aggregation

features within aggregate

1999-6-26

f96,f146,f174,f110,f116,f158,f167,f172

[Input File: j718jo.j]

Descriptive

a18

/MZ/A/A12/D/A/0018.HTM

Labeling/Designation

category	!!	!!	other features	[Input File: !!]
definition (typological label)	1999-6-26	jo	burial	[Input File: j718jo.j]

Spatial Aggregation

features within aggregate

1999-6-26

f178,f177,q274.1,q247,q248

[Input File: j718jo.j]

Descriptive

a19

/MZ/A/A12/D/A/0019.HTM

Labeling/Designation

category	!!	!!	clay artifact	[Input File: !!]
definition (typological label)	1999-6-26	jo	tannur	[Input File: j718jo.j]

Spatial Aggregation

features within aggregate

1999-6-26

f181,f182

[Input File: j718jo.j]

Descriptive

a20

/MZ/A/A12/D/A/0020.HTM

Labeling/Designation

category	!!	!!	installation	[Input File: !!]
definition (typological label)	1999-6-26	jo	wall	[Input File: j718jo.j]

Description/Count

description (summary)	1999-7-05	ab	is the A12 number of A10 a32	[Input File: j718ab.j]
description (summary)	1999-6-26	jo	= A10 a32	[Input File: j718jo.j]

Spatial Aggregation

features within aggregate

1999-6-26

f41,f45,f142

[Input File: j718jo.j]

Descriptive

a21

/MZ/A/A12/D/A/0021.HTM

Labeling/Designation

category	!!	!!	installation	[Input File: !!]
definition (typological label)	1999-6-26	jo	pavement	[Input File: j718jo.j]
definition (typological label)	1999-7-13	gb	installation	[Input File: j718okk.j]

Spatial Aggregation

features within aggregate

1999-6-26

f146,f96,f89,f172,f110,f116,f158,f167

[Input File: j718jo.j]

Descriptive

Manufacturing

evidence

1999-7-13

One argument against considering these as regular steps or terracing stages is that they are very distinct in nature (one is bricks, the other is stones).

[Input File: j718okk.j]

a22

/MZ/A/A12/D/A/0022.HTM

Labeling/Designation

Description/Count

description (summary)	1999-7-22	gb	Horseshoe wall of stone, possibly encircling a gate to the East	[Input File: j718gb.J]
best view	2001-2-26	jl	V13d1051	[Input File: M815jl.j]
best view	2001-2-26	jl	V13d1054	[Input File: M815jl.j]

Recovery/Assignment

daily notes	1999-7-22	lr	fan-xi & Carol are sick- I am working with GB continuing digging k16, k18, k19 & resumed k17.	[Input File: j718gb.J]
strategy (projected or implemented)	1999-7-22	gb	We will move the current section to the West so as to have it run through the center of the U.	[Input File: j718gb.J]
strategy (projected or implemented)	1999-7-22	gb	It appears that we have a definite U-shaped gateway, filled with gully wash. We will leave a section moving EW along it's axis (which seems perfectly alined with the cardinal points), and we will expose the two passageways (E&W), trying to reach a floor level at the bottom. If it reaches the level of the base of the perimetral wall of AK, it would be standing up to almost four meters! We should be on the look out for steps (&door sockets?)	[Input File: j718gb.J]

Deposition

definition of process(es)	2000-7-04	gb	Several possible processes are contemplated (see note H2 for description of characteristics that have led us to these possibilities). (1) The fissure reflects a lower structure, which caused settling. It is not clear then why the section does not allow a clear connection of layers on either side of the fissure. (2) A rodent may have opened a way through pre-existing deposition, but this would be possible only for part of what we observe, in particular the soft brown fill at elevation matching q397. (3) There may have been a wooden structure (or wood and matting) that disintegrated (e.g., a curtain wall). But there is no impression along the face of the fissure, nor is there any obvious remanent (though this may have fallen at the bottom).	[Input File: K705jl.j]
evidence	2000-7-04	gb	The fissure 321 has two clear faces and very soft dirt, the type found as a secondary fill (e.g., from rodent activity). One face shows scalloping in at least one place. The excavated portion of f303 in section shows a clear upper portion of the same element that corresponds to f321, but it slopes inward and it leans a smooth face on the convex face. Also, tho color appears to be different. Note that the fissure continues all around a33, along the face of the stones. We noted this from the beginning, but it is becoming more and more marked.	[Input File: K705jl.j]

Descriptive

shape, form

1999-7-22

Horseshoe shape is definite, and seems to allow an opening of about 150cm to it's Eastern end.

[Input File: j718gb.J]

Analogical Record

general notes on photos

1999-7-22

We will get a view of stones in k15,16,19 with section running through it's middle. purpose of section is to show gully wash material for top 2ms. of deposition within gate.

[Input File: j718gb.J]

a26

/MZ/A/A12/D/A/0026.HTM

Labeling/Designation

Descriptive

Analogical Record

view/drawing of aggregate

v188a 2002-9-07 / ms / [Input File:M911jl.j]

a27

/MZ/A/A12/D/A/0027.HTM

Labeling/Designation

Descriptive

Analogical Record

view/drawing of aggregate

v188a 2002-9-07 / ms / [Input File:M911jl.j]

v213 2002-9-15 / dc / [Input File:M915jl.j]

v214 2002-9-15 / dc / [Input File:M915jl.j]

a31

/MZ/A/A12/D/A/0031.HTM

Labeling/Designation

category	!!	!!	installation	[Input File: !!]
definition (typological label)	2000-6-26	jl	installation	[Input File: k627jl.j]
notes on labeling	2000-7-31	jl	The relays of all of the steps were very difficult, and so the relays from the center three steps (f315) are inaccurate and should not be used, or used with caution.	[Input File: K731jl.j]

Description/Count

description (summary)	2000-6-26	jl	This aggregate contains the whole entrance to the apsidal structure (old k21, new k23 and k24), f302, f283, f286, f281, f239, and f282, as well as any features yet to be discovered within k23 and k24.	[Input File: k627jl.j]
description (summary)	2000-6-26	jl	entrance to a22 apsidal structure	[Input File: k627jl.j]
best view	2001-2-26	jl	V13d1051	[Input File: M815jl.j]
best view	2001-2-26	jl	V13d1054	[Input File: M815jl.j]

Spatial Aggregation

features within aggregate

2000-6-26

k23,k24

[Input File: k627jl.j]

Descriptive

Function

notes on function

2001-8-13

Whatever the function of a32 was, it seems impossible that it was used regularly, since the stairway is far too narrow to have admitted regular access. Such a stairway suggests infrequent use.

[Input File: L813jl.j]

a32

/MZ/A/A12/D/A/0032.HTM

Labeling/Designation

category	!!	!!	unknown	[Input File: !!]
definition (typological label)	2000-6-26	jl	unknown	[Input File: k627jl.j]

Description/Count

description (summary)	2000-6-26	jl	a22 apsidal structure and a31 entryway taken as a whole	[Input File: k627jl.j]
description (summary)	2000-6-26	jl	This aggregate is a combination of a22 and a31, so that we can refer to the apsidal structure as a whole, including its entryway, by one title, embracing k23, k24, k25, k26, and k27 (old k21 and k22).	[Input File: k627jl.j]
best view	2001-2-26	jl	V13d1051	[Input File: M815jl.j]
best view	2001-2-26	jl	V13d1054	[Input File: M815jl.j]

Recovery/Assignment

daily notes

2000-7-27

In the N wall, there appears to be a stepping down of stones between the wall of a32 and the stone and brick apron f354. This is because we are interpreting the stone apron and the stone circle f353 as an earlier structure, underneath a32. Also, in terms of the overall layout of a32, the walls of the apsidal structure curve in slightly towards the circle before following its curve back out, similar to a keyhole.

[Input File: K727jl.j]

Spatial Aggregation

features within aggregate

2000-6-26

k21,k22 / a22,a31

[Input File: k627jl.j]

Deposition

evidence	2001-8-13	jl	The clarification of the stone ledge, f375, shows that it is a continous part of the north wall of a32. It is also the upper half of f352. A fairly clear seam of mud-mortar separates the stones of the square, a36, from the stones of the circle, a33. The first floor in a37, f348, is much higher than the floor in a33 (which we have not yet reached). f353, the remains of the previous circular stone wall underneath the sherd packing, f349, seems to be in a fairly continous alignment with the stone ledge f375. a33 is becoming very deep, over a meter lower than the floor in a36.	[Input File: L813jl.j]
assumption	2001-8-13	jl	Finally, the underground structure's architecture is beginning to make sense. It appears that f375 and f352 are the remains of the original western wall of a33, which was once the original extent of the underground building, i.e. it was a stone-lined circular shaft into the earth. At some point, this wall either fell or was knocked down, and a36 was added on in the western half as an entrance area to the building. Another possibility, of course, is that there was an earlier western antechamber, but that it was smaller than a36, and that they were forced to enlarge the hole in the western wall when they built a36.	[Input File: L813jl.j]

Time Sequencing

phase (to which element belongs)

2000-6-28

okk

mkb mentioned that the pottery that was washed from the excavation of f307 and f308 appeared to be very early, Early Simple Ware. That would place this accumulation in Phase 1, Sr 18, the pre-palace phase. This is very interesting because it indicates that the apsidal structure a22 might not have been in use in the palace period because the accumulation pre-dates the AK occupation. It should be noted that this is a preliminary consideration because the pottery sample wasn't large enough to be conclusive, nor was the processing finished. We spoke about this with gb, and he suggested that the structure might not have been visible during the AK occupation. This morning jl, lr, ed and I spoke about all of these possibilities, and lr thought that it was unlikely that this structure wasn't visible because structure W was so close to the surface, and the brick fall and gully wash dip into the apsidal structure. See drawing A12w__.

[Input File: k701okk.j]

Descriptive

Function

generic fnc. (1st degree of specificity)	2001-8-13	jl	Our current understanding of the evidence suggests that a32 was an ancient well of some sort.	[Input File: L813jl.j]
notes on function	2001-8-13	jl	This building continues to surprise us. The clarification of f375 shows that a33 was probably the original extent of the building, and has brought us back to our original idea about the structure's function: a well. Urkesh was clearly a large city even in the middle of the Early Bronze Age, and such a city would have needed a lot of water, which either a large well or many small wells could provide. But if it was a well, why let it fill in? Perhaps the well went dry at a certain point, or perhaps the city was sacked and the well despoiled by invaders. That might explain the thick ash layer f307, which we currently believe immediately postdated the loss of the roof of a32. However, there is no evidence except possibly f307 for such a situation; further, the apparent progression of the pottery within the circle suggests that the accumulation within it occurred over an extended period of time. Further, why have one central well, rather than many smaller ones? gb has pointed out that one large well would probably deplete the water table in its area much more quickly than many smaller wells spread around. Of course, perhaps this is just what happened. Its later use is also unclear; the contents of the fill within the building, especially the circle, resemble the contents of a dump or a pit, but the fill itself seems to clean and orderly to have belonged to a garbage pit. gb has again jokingly raised the idea that it might have been some sort of cage for wild animals, such as a lion, but this idea also has its problems. One, the bone specialists ruled out the possibility of a lion having gnawed on the bones within the circle. Two, the mud ledge f326 seems to be precious little protection against the claws of a lion or other wild beast. Even though this theory is mostly tongue-in-cheek, it illustrates an important point: at some point, presuming that the structure started as a well, it changed its function at the same time that it began to fill in with accumulation.	[Input File: L813jl.j]

Analogical Record

view/drawing of aggregate

v118 2000-7-17 / jl / [Input File:K717jl.j]	v118a 2000-7-17 / jl / [Input File:K717jl.j]	v118b 2000-7-17 / jl / [Input File:K717jl.j]	v118c 2000-7-17 / jl / [Input File:K717jl.j]
v161 2001-7-21 / jl / [Input File:L827jl.j]	v163 2001-7-30 / jl / [Input File:L827jl.j]	v163a 2001-7-30 / jl / [Input File:L827jl.j]	v164i 2001-7-31 / jl / [Input File:L827jl.j]
v164j 2001-7-31 / jl / [Input File:L827jl.j]	v165 2001-8-27 / jl / [Input File:L827jl.j]	v163f 2001-7-30 / jl / [Input File:L827jl.j]	v163g 2001-7-30 / jl / [Input File:L827jl.j]
v164 2001-7-31 / jl / [Input File:L827jl.j]	v164a 2001-7-31 / jl / [Input File:L827jl.j]	v163e 2001-7-30 / jl / [Input File:L827jl.j]	v164b 2001-7-31 / jl / [Input File:L827jl.j]
v164e 2001-7-31 / jl / [Input File:L827jl.j]	v166a 2001-8-27 / jl / [Input File:L827jl.j]	v165a 2001-8-27 / jl / [Input File:L827jl.j]	v166 2001-8-27 / jl / [Input File:L827jl.j]
w26 2001-9-01 / jmf / [Input File:M718jl.j]	w38 Lxxx / lr / [Input File:M719jl.j]	w37 Lxxx / lr / [Input File:M719jl.j]	v179 2002-9-04 / jl / [Input File:M904jl.j]
v179a 2002-9-04 / jl / [Input File:M904jl.j]	v180 2002-9-04 / jl / [Input File:M904jl.j]	v180b 2002-9-04 / jl / [Input File:M904jl.j]	v183 2002-9-05 / jl / [Input File:M906ms.j]
v181 2002-9-04 / jl / [Input File:M904jl.j]	v182 2002-9-05 / jl / [Input File:M906ms.j]	v184 2002-9-05 / jl / [Input File:M906ms.j]	v185 2002-9-05 / jl / [Input File:M906ms.j]
v185a 2002-9-05 / jl / [Input File:M906ms.j]	v186 2002-9-07 / jl / [Input File:M911jl.j]	v186a 2002-9-07 / jl / [Input File:M911jl.j]	v192 2002-9-09 / jl / [Input File:M911jl.j]
v188a 2002-9-07 / ms / [Input File:M911jl.j]	v188b 2002-9-07 / ms / [Input File:M911jl.j]	v188c 2002-9-07 / ms / [Input File:M911jl.j]	v186b 2002-9-07 / jl / [Input File:M911jl.j]
v187 2002-9-07 / ms / [Input File:M911jl.j]	v187a 2002-9-07 / ms / [Input File:M911jl.j]	v188 2002-9-07 / ms / [Input File:M911jl.j]	v188d 2002-9-07 / ms / [Input File:M911jl.j]
v189 2002-9-07 / ms / [Input File:M911jl.j]	v190 2002-9-07 / jl / [Input File:M911jl.j]	v193 2002-9-09 / jl / [Input File:M911jl.j]	v194 2002-9-09 / jl / [Input File:M911jl.j]
v205 2002-9-11 / jl / [Input File:M922ms.j] 2002-9-11 / ms / [Input File:M914jl.j]	v205b 2002-9-11 / jl / [Input File:M922ms.j] 2002-9-11 / ms / [Input File:M914jl.j]	v205d 2002-9-11 / jl / [Input File:M922ms.j] 2002-9-11 / ms / [Input File:M914jl.j]	v208 2002-9-13 / jl / [Input File:M914jl.j] 2002-9-13 / jl / [Input File:M922ms.j]
v208a 2002-9-13 / jl / [Input File:M914jl.j] 2002-9-13 / jl / [Input File:M922ms.j]	v208b 2002-9-13 / jl / [Input File:M914jl.j] 2002-9-13 / jl / [Input File:M922ms.j]	v209 2002-9-13 / jl / [Input File:M914jl.j] 2002-9-13 / jl / [Input File:M922ms.j]	v204 2002-9-11 / ms / [Input File:M914jl.j]
v206 2002-9-11 / jl / [Input File:M922ms.j] 2002-9-11 / ms / [Input File:M914jl.j]	v210a 2002-9-13 / jl / [Input File:M914jl.j]	v195 2002-9-10 / jl / [Input File:M914ms.j]	v197a 2002-9-10 / jl / [Input File:M914ms.j]
v198 2002-9-10 / jl / [Input File:M914ms.j]	v198a 2002-9-10 / jl / [Input File:M914ms.j]	v199 jl / jl / [Input File:M914ms.j]	v196 2002-9-10 / jl / [Input File:M914ms.j]
v196a 2002-9-10 / jl / [Input File:M914ms.j]	v197 2002-9-10 / jl / [Input File:M914ms.j]	v200 jl / jl / [Input File:M914ms.j]	v201 2002-9-11 / ms / [Input File:M914ms.j]
v202 2002-9-11 / ms / [Input File:M914ms.j]	v203 2002-9-11 / ms / [Input File:M914ms.j]	v204a 2002-9-11 / ms / [Input File:M914ms.j]	v212 2002-9-15 / dc / [Input File:M915jl.j]
v212a 2002-9-15 / dc / [Input File:M915jl.j]	v207b 2002-9-13 / ms / [Input File:M922ms.j]	v209a 2002-9-13 / jl / [Input File:M922ms.j]	v224 2002-9-22 / ms / [Input File:M923ms.j]
v224a 2002-9-22 / ms / [Input File:M923ms.j]	v224b 2002-9-22 / ms / [Input File:M923ms.j]	v224c 2002-9-22 / ms / [Input File:M923ms.j]	v224d 2002-9-22 / ms / [Input File:M923ms.j]
v224e 2002-9-22 / ms / [Input File:M923ms.j]	v224f 2002-9-22 / ms / [Input File:M923ms.j]	v225a 2002-9-22 / ms / [Input File:M923ms.j]	v286 2003-8-29 / jl / [Input File:N920jl.j]
v286a 2003-8-29 / jl / [Input File:N920jl.j]	v286b 2003-8-29 / jl / [Input File:N920jl.j]	v287 2003-9-10 / jl / [Input File:N920jl.j]	v288 2003-9-10 / jl / [Input File:N920jl.j]
v289 2003-9-10 / jl / [Input File:N920jl.j] 2004-6-02 / jl / [Input File:O602jl.j]	v290 2003-9-10 / jl / [Input File:N920jl.j]	v291 2003-9-10 / jl / [Input File:N920jl.j]	v292 2003-9-10 / jl / [Input File:N920jl.j] 2004-6-02 / jl / [Input File:O602jl.j]
v282 2004-6-02 / jl / [Input File:O602jl.j]

a33

/MZ/A/A12/D/A/0033.HTM

Labeling/Designation

equals other label	2000-6-27	gb	W3	[Input File: k627jl.j]
category	!!	!!	unknown	[Input File: !!]
definition (typological label)	2000-6-27	jl	unknown	[Input File: k627jl.j]

Description/Count

description (summary)	2000-6-27	jl	circular area within apsidal structure	[Input File: k627jl.j]
	2000-6-27	jl	At gb's request, I have made the circular area, k27, into an aggregate of its own. Although its function is still unknown, it is clearly distinct from the accumulation adjacent to it, and probably deserves its own aggregate number.	[Input File: k627jl.j]
	2000-6-27	gb	equals ^rm W3	[Input File: k627jl.j]
	2000-7-31	jl	a33 also includes any features found within k27 this season, since the aggregate is defined by the fissure f321/subsidance of the area, and therefore includes everything that had accumulated before the fissure came into existence.	[Input File: K731jl.j]
best view	2001-2-26	jl	V13d1051	[Input File: M815jl.j]
best view	2001-2-26	jl	V13d1054	[Input File: M815jl.j]

Spatial Aggregation

features within aggregate

2000-6-27

k27

[Input File: k627jl.j]

Deposition

evidence	2001-8-13	jl	We have always presumed that a32 (and hence a33) predated the AP building, since the walls of the AP building were clearly built to accomodate its presence, i. e. they change course to skirt around it. The top level of the eastern wall of a33, being at approximately the same elevation as the first floors in AP, also gives a fairly good indication of the level of the tell surface at that location at the time that AP was constructed, i. e. the ground was already higher there than around the AK building. The level of the floors of the AK building, however, are much lower than the top of a33, suggesting that the tell surface was lower around the AK building, or that there was a fairly significant slope already in existence at that time.	[Input File: L813jl.j]
assumption	2000-7-04	gb	The marked fissure all around this aggregate suggest that the accumulation inside it shrank towards the center, possibly as a result of subsidence.	[Input File: K705jl.j]
assumption	2001-8-13	jl	If the hypothesized slope did in fact exist, and if the a33 shaft was dug straight down into the hillside, it seems possible that part of the western wall of a33 would have been exposed to view. The walls of a32 do not appear to have ever been freestanding, nor do they appear capable of ever having stood without earth behind them for support. However, since the original western wall no longer exists, it strikes me as possible that the construction technique could have been different, a difference about which we cannot comment because it is unobservable now. If it was exposed to the elements and to view, then this might explain why it no longer exists, that it was not built strongly enough for such wear. However, this theory has problems, for example, height of a36. This construction also does not seems to have ever been freestanding, and so must have been dug into something, the height of which would have been nearly equal with the top of a33. Perhaps the retaining walls which terraced the tell underneath the AP building also brought the level of the tell surface up to that elevation further out west, necessitating or precipitating the construction of a36. This theory still needs more development and consideration.	[Input File: L813jl.j]

Descriptive

Function

generic fnc. (1st degree of specificity)

2000-6-27

a kiln? but no waster

[Input File: k627jl.j]

Analogical Record

view/drawing of aggregate

w26 2001-9-01 / jmf / [Input File:M718jl.j]

a34

/MZ/A/A12/D/A/0034.HTM

Labeling/Designation

category	!!	!!	surface	[Input File: !!]
definition (typological label)	2000-7-05	okk	pavement, type b	[Input File: K706jl.j]

Description/Count

description (summary)

2000-7-05

okk

scattered line of stones S of south wall of a32

[Input File: K706jl.j]

Spatial Aggregation

features within aggregate

2000-7-05

okk

f322,f332

[Input File: K706jl.j]

Deposition

evidence

2000-7-05

Floating stones appear to be in a line parallel to the S part of the apsidal structure. Stones are the same type used for the walls of the apsidal structure. We see that stones are probably missing.

[Input File: K705jl.j]

Descriptive

a35

/MZ/A/A12/D/A/0035.HTM

Labeling/Designation

equals other label	2000-7-18	jl	f342	[Input File: K718jl.j]
category	!!	!!	installation	[Input File: !!]
definition (typological label)	2000-7-18	jl	installation	[Input File: K718jl.j]

Description/Count

description (summary)	2000-7-18	jl	sherd-stone-bone installation	[Input File: K718jl.j]
best view	2001-2-26	jl	V13d1103	[Input File: M815jl.j]

Recovery/Assignment

notes on recovery

2000-7-31

Excavating a35, we discovered that it was very shallow, similar to the pit f325 above it. It was also directly in line with the doorway of the apsidal structure.

[Input File: K731jl.j]

Spatial Aggregation

features within aggregate

2000-7-18

f342 q695,696,697

[Input File: K718jl.j]

Descriptive

Function

generic fnc. (1st degree of specificity)

2000-7-31

Presuming that the apsidal structure did have some sort of religious/ritual function, then the installation was probably related to this usage. What specifically it was, however, is still a mystery. It would be worth examining the bones when we have a specialist available to do that.

[Input File: K731jl.j]

a36

/MZ/A/A12/D/A/0036.HTM

Labeling/Designation

category	!!	!!	installation	[Input File: !!]
definition (typological label)	2001-8-13	jl	strainer	[Input File: L813jl.j]

Description/Count

description (summary)	2001-8-13	jl	The square part of a32, i. e. the western half. It seems to have been added on later to the original structure, a33, but the reason for this is still unclear.	[Input File: L813jl.j]
best view	2001-2-26	jl	V13d1051	[Input File: M815jl.j]

Spatial Aggregation

features within aggregate

2001-8-13

k26

[Input File: L813jl.j]

Descriptive

Function

generic fnc. (1st degree of specificity)	2001-8-13	jl	This room was probably the entrance to the underground structure a32, a later addition after the collapse/removal of the western wall of a33.	[Input File: L813jl.j]
notes on function	2001-8-13	jl	We do not understand at this point the reason for the construction of a36. If a32 was in fact a regular well, why was the stairway built so narrow? It is too narrow to have been effectively used to supply water to any significant number of people. Also, what need could there have been of an antechamber to a well? Even if the structure had a ritual purpose, the stairs still seem unnecessarily difficult.	[Input File: L813jl.j]

Analogical Record

view/drawing of aggregate

w36 Lxxx / lr / [Input File:M719jl.j]

a37

/MZ/A/A12/D/A/0037.HTM

Labeling/Designation

Descriptive

Analogical Record

view/drawing of aggregate

w26 2001-9-01 / jmf / [Input File:M718jl.j]

w38 Lxxx / lr / [Input File:M719jl.j]

w36 Lxxx / lr / [Input File:M719jl.j]

w37 Lxxx / lr / [Input File:M719jl.j]

a38

/MZ/A/A12/D/A/0038.HTM

Labeling/Designation

category	!!	!!	installation	[Input File: !!]
definition (typological label)	2003-8-19	jl	pit aggregate	[Input File: N920jl.j]

Description/Count

description (summary)

2004-6-02

This is the final overhead photo of the excavations within the circle, a33. It shows clearly the area of white material (f449, f446, f440) concentrated in the south-east corner of the locus.

[Input File: O602jl.j]

Spatial Aggregation

features within aggregate

2003-8-19

f447,448

[Input File: N920jl.j]

Descriptive

Analogical Record

view/drawing of aggregate