1. OVERVIEW
| Roster | Date | Author | Record |
|---|---|---|---|
| Equals other label | 2001-06-25 | jl | f366 (structure) [Input: L625JL.j] |
| 2001-08-25 | jl | f374 (structure) [Input: L825JL.j] | |
| Category | !! | !! | installation |
| Best definition | 2000-07-09 | jl | wall [Input: K711JL.j] |
| Best image | 2001-02-26 | jl | V13d1071 [Input: M815JL.j] |
| 2001-02-26 | jl | V13d1212 [Input: M815JL.j] |
2. IDENTIFICATION
Designation
| Roster | Date | Author | Record |
|---|---|---|---|
| Description (summary) | 2000-07-11 | jl | possible wall, bricky-looking material in semicircle around edge of k27. Apparently the cause of the fissure f321 and f303. However, its purpose and construction are still unknown. It is not a brick wall, although the top layer does look bricky. Instead, it is probably a mud wall, made by layering successive layers of mud brick on top of each other. [Input: K711JL.j] |
3. STRATIGRAPHY
Volumetric Localization
| Roster | Date | Author | Record |
|---|---|---|---|
| Locus | 2000-07-09 | jl | k26 [Input: K711JL.j] |
Contact Association
| Roster | Date | Author | Record |
|---|---|---|---|
| Type of contact: latest events | 2000-07-20 | jl | f336 (accumulation) abuts f326 (wall) [Input: K720JL.j] |
| 2000-07-20 | jl | f338 (floor, type a) abuts f326 (wall) [Input: K720JL.j] | |
| 2000-07-20 | jl | f344 (accumulation A) abuts f326 (wall) [Input: K720JL.j] | |
| 2000-07-22 | jl | f345 (accumulation A) abuts f326 (wall) [Input: K722JL.j] | |
| 2000-07-26 | jl | f348 (floor, type a) abuts f326 (wall) [Input: K726JL.j] | |
| 2000-08-06 | jl | f349 (pavement, type c) abuts f326 (wall) [Input: K806JL.j] | |
| Type of contact: contemporary events/movable items | 2002-09-15 | !! | q971.1 (lithic artifact) sits in f326 (wall) [Input: M915JL.j] |
| 2002-09-15 | !! | q981.1 (sample) sits in f326 (wall) [Input: M915JL.j] | |
| 2002-09-15 | ms | q971 (bones, items, pottery) sits in f326 (wall) [Input: M915JL.j] | |
| 2002-09-15 | ms | q973 (bones, pottery) sits in f326 (wall) [Input: M915JL.j] | |
| 2002-09-15 | jl | q979 (pottery) sits in f326 (wall) [Input: M915JL.j] | |
| 2002-09-15 | ms | q981 (items, pottery) sits in f326 (wall) [Input: M915JL.j] | |
| Type of contact: earliest events | 2000-07-11 | jl | f326 (wall) abuts f307 (accumulation) [Input: K711JL.j] |
| 2000-07-11 | jl | f326 (wall) abuts f308 (accumulation) [Input: K711JL.j] | |
| 2000-07-11 | jl | f326 (wall) abuts f320 (accumulation C) [Input: K711JL.j] | |
| 2000-07-11 | jl | f326 (wall) abuts f321 (hole) [Input: K711JL.j] | |
| 2000-07-11 | jl | f326 (wall) abuts f328 (accumulation) [Input: K711JL.j] | |
| 2000-07-11 | jl | f326 (wall) abuts f330 (accumulation) [Input: K711JL.j] | |
| 2000-08-06 | jl | f326 (wall) abuts f349 (pavement, type c) [Input: K806JL.j] | |
| 2000-08-06 | jl | f326 (wall) covers f352 (stone installation) [Input: K806JL.j] |
Deposition
| Roster | Date | Author | Record |
|---|---|---|---|
| Evidence | 2001-08-13 | jl | In order to have any stabiliy, the mud ledge must have accumulated against another surface, presumably the accumulation within a36. [Input: L913JL.j] |
| Assumption | 2001-08-13 | jl | Presumably, the mud ledge increased apace with the ^a within a36. However, there are two possible reconstructions of this event: first, k26 and k27 increased at roughly the same pace, so the ledge was never more than half a meter (or whatever appropriate size) high. In this case, it served to keep to the accumulation within k27 out of k26. Second, k27 continued in use as a well after a36 was constructed, so k26 increased in elevation for a long time as k27 remained lower. In this case, the mud ledge probably served to keep the contents of k26 out of k27. [Input: L913JL.j] |
