# `myArch`: A Systematic Development Framework

myArch implements *architectonic* development: the practice of organizing a codebase or a Markdown knowledge store as a fixed, four-level tree of indexed cells, then generating and maintaining the real filesystem from that structure.
A single Google Sheet is the ground truth.
`arch` parses it, models every source file as re-renderable data, and keeps the tree, the database, and the disk in agreement.

It's aimed at developers building large, highly-structured systems and is especially worth a perusal if you're:

- Looking for a disciplined, **index-addressed** way to lay out a growing codebase, where
  every module has a canonical place in a hierarchy rather than an ad-hoc directory.

- Treating source files as **structured data**: parsing Python and TypeScript by string into
  models you can query, transform, and re-render rather than rewrite by hand.

- Synchronizing a repository against an external **source of truth** (a spreadsheet, a
  database) and want the filesystem reconciliation handled for you.

- Curious about the *antithesis / thesis / synthesis* dialectic as a concrete organizing
  principle for the "moments" of a software element.

The package is organized into a handful of subpackages, presented here in rough order from most- to least-general:

```{toctree}
:maxdepth: 2
1. Base Primitives <base>
2. Document Idx Guide <idx>
3. Why Idxs Are Mappings <idx-design>
4. Header Formatting <headers>
5. Document Idx API <idx-api>
6. The Architectonic <architectonic>
7. Source Code Models <code>
8. Irix Colors <irix>
9. Other Command-Line Tools <tools>
```