experimenting with 5,000-year-old techniques for charting the cap table
the cap table is not the team.
synastrycap-tableorgdasha
two founders, aligned at seed. same vision, same whiteboard, same enemy. by Series A one of them is optimizing for something the other didn't know was in the contract.
this is not a communication problem. it is a cycle problem.
jyotish has a name for the overlay of two charts: synastry. not romance. architecture. where do the two dasha cycles run parallel and where do they diverge at exactly the wrong moment? whose Saturn return lands in year three when the company gets hard? whose creativity peaks when the other's is in a consolidation window?
fig.02 — planisphaerium coeleste, frederik de wit, amsterdam, c. 1670. two hemispheres overlaid: where signs meet, weight transfers. synastry made visible four hundred years before silicon valley named the same problem.
these aren't vague impressions. they are calculable intersections. the synastry either compounds or it cancels. holding under pressure is a third outcome, visible in the charts before the pressure arrives.
organizations have their own chart. founding date carries one signature. first transaction carries another. the hires made in year one are a third layer. the institutional character is already encoded. a founder whose operating style fights that encoding will feel it before they can name it.
Artiji reads all three layers. the person. the pair. the org they are building together.
most due diligence answers: can they build it? this answers: will they still be in the same room when it matters?
without birth times and founding times, the read is a magnifying glass. precise enough to see the pattern. with exact times, it is a telescope. the same object, orders of magnitude sharper. that question belongs to the next post.
