# Something is still in there > A chain runs into a tree trunk and doesn't come out the other side; the bark has healed shut around it. The wood is the only witness, and it isn't talking. August 20, 2026 · https://justog.club/stories/the-tree-grew-around-it A section of trunk, drawn close enough to fill the whole print. Bark in cream and oxidised rust, rendered in real detail. An old iron chain comes out of the wood — three or four links, the rest swallowed. On both sides, the bark has healed into raised lips around it. The chain goes in. It doesn't come out anywhere. ## Why does bark closing over a chain look the way it does? Because a tree doesn't remove an obstruction — it grows around it, a little at a time, until the wood has folded over the object from both sides. A trunk doesn't stop growing where something's fastened to it; new wood keeps forming under the bark and the bark keeps expanding outward, and where an object is in the way, the growth simply diverts around it instead of through it. Once the two advancing edges meet, they close and seal, leaving the raised, puckered scar this print shows on both sides of the chain. The tree isn't reacting to the chain. It's doing what it always does, and the chain just happened to be there. ## Why is that scarier than the chain itself? Because a chain is a fact anyone could put there in an afternoon. A closed wound in a tree can't be staged that quickly. Bark doesn't heal on a schedule anyone controls, which is exactly what makes the closure convincing — nobody arranged this scene, because arranging it isn't something you can do on purpose in any useful hurry. The wood closing over the iron is the tree quietly reporting an interval, not a number, just the plain fact that whatever happened here happened once, and then a great deal of ordinary tree-time passed with nobody disturbing it. ## Why does the chain going in and not coming out matter? Because it rules out the ordinary explanation before you can reach for it. A chain looped loosely around a trunk, the kind used to tether or mark a tree, comes back out the same side it went in. This one doesn't — it disappears into the wood and the wood has closed behind it, which means whatever the chain is fastened to is inside the healed section, not looped around the outside of it. That's a different object than a tether. The print never says what it is. It only shows you that the wood no longer lets you see. ### What makes a good version of this design? Botanical accuracy in the bark, and total silence about everything else. The healed lips need to look like an actual tree closing over an obstruction — raised, folded, rust-stained where the iron has been sitting against wet wood — rather than a generic wound shape. Get that mechanism right and the print doesn't need to add anything: no implied face in the bark, no suggestion of what's on the other end of the chain, nothing built to editorialise. The accuracy is what makes the withholding convincing, the same discipline that keeps [a doorway cut into old brickwork](/stories/the-door-added-later) reading as a fact about the wall rather than a staged detail. ## Who has the rights to a tree and a chain? Nobody — there's no real tree being depicted and no specific object being reproduced. An invented trunk with an invented chain isn't drawn from a real location or a documented case, and a generic length of iron chain isn't anybody's intellectual property to begin with. What would need permission is a photograph of an actual, identifiable tree somewhere — a landmark, a specific grove — since that photograph belongs to whoever took it even though the tree itself belongs to nobody. Drawing your own trunk from scratch sidesteps that question entirely. ## Does this work for something other than a chain? Yes — anything a tree could plausibly grow around and seal shut works the same way. A rope gone to fibre, a padlock rusted solid, a sign nailed up and abandoned long before anyone stopped to read it — the same logic as [a path that quietly detours around an empty patch of ground](/stories/the-path-that-goes-around-nothing) never explaining what it's avoiding either. What matters is that the object reads as deliberately placed rather than naturally occurring; bark doesn't heal around a fallen branch the way it heals around something fastened on purpose. ## Does it print well? Yes, once the bark texture is simplified from what a photograph would show. Real bark carries very fine, irregular ridging that's well below what fabric can hold; kept coarser and with fewer distinct ridges than a photo-real reference, it keeps the same read at a size cotton can carry — the same adjustment [fine engraved hatching needs to survive a weave](/stories/cabinet-of-curiosities-plate). The rust staining works best as flat patches of colour rather than a soft blend. Bark brown or a warm oxidised rust for the shirt, cream and dark rust for the ink, keeps the whole print reading as wood rather than as a photograph sitting on top of fabric. ## How do I get one made? Describe the trunk at [JustOG](/) — how the bark has healed, what's still visible, and how much of it the wood has taken back. Pick a direction, drag the crop frame, see it composited on the real garment, and it's made to order and shipped. Designs other people have published are in the [shop](/shop). The chain still goes in. Nothing about the tree explains what it was for.