<feed xmlns='http://www.w3.org/2005/Atom'>
<title>moon/zygotec/docs/history/17-o3-boundaries/code/tests, branch main</title>
<subtitle> work-in-progress programming language.
</subtitle>
<id>https://git.downsta.ir/moon/zygotec/atom?h=main</id>
<link rel='self' href='https://git.downsta.ir/moon/zygotec/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.downsta.ir/moon/zygotec/'/>
<updated>2026-10-14T05:39:21+00:00</updated>
<entry>
<title>docs: archive the frozen stage code as one compressed tarball</title>
<updated>2026-10-14T05:39:21+00:00</updated>
<author>
<name>Moon Flower</name>
<email>moonflower@elhenney.local</email>
</author>
<published>2026-10-14T05:39:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.downsta.ir/moon/zygotec/commit/?id=dc7f7407e08f54e4a2a3c1d1723b2a7d6959532d'/>
<id>urn:sha1:dc7f7407e08f54e4a2a3c1d1723b2a7d6959532d</id>
<content type='text'>
docs/history kept six stages with a full copy of the project under code/,
3.8 mb of sources duplicated from stage to stage and already superseded. store
them as docs/history/code-snapshots.tar.gz, 0.66 mb, and extract one in place
to read it. every stage's notes.md stays browsable, and the index says where the
code went and how to get it back.

the top-level README points at the archive too. its other two links into
docs/history, 21-micro and 35-bench, were notes that were never kept and do not
resolve; the index now records that.
</content>
</entry>
<entry>
<title>a</title>
<updated>2026-10-12T05:16:23+00:00</updated>
<author>
<name>Moon Flower</name>
<email>moonflower@elhenney.local</email>
</author>
<published>2026-10-12T05:16:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.downsta.ir/moon/zygotec/commit/?id=ecc350ca5c2eb50be8309c5f14f8bf0d87db9a02'/>
<id>urn:sha1:ecc350ca5c2eb50be8309c5f14f8bf0d87db9a02</id>
<content type='text'>
</content>
</entry>
</feed>
