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:

• 1. Base Primitives
  • Lang: Recognized Source Languages
  • Idx: Hierarchical Cell Index
  • IdxType: Idx Database Column Type
  • Cell: Indexed Tree Row
• 2. Document Idx Guide
  • 1 Quick start
  • 2 Individual idx operations
  • 3 Configuration
  • 4 What is scanned
  • 5 Mutation boundary
  • 6 Terminal workspace
  • 7 Migration from subl/headers
• 3. Why Idxs Are Mappings
  • 1 Policy is not mechanism
  • 2 Two idx domains, one clear boundary
  • 3 Positive enrollment precedes observation
  • 4 Selection authorities stay independent
  • 5 Comments are real document surfaces
  • 6 Plans make change legible
  • 7 Frontier
• 4. Header Formatting
  • 1 Quick start
  • 2 Flex and strict modes
  • 3 The model
  • 4 Required and forbidden indexes
  • 5 Legacy subl/headers profiles
  • 6 arch spec: keyboard-first profile editor
• 5. Document Idx API
  • 1 Domain model
  • 2 Configuration
  • 3 Planning and application
  • 4 Header model
  • 5 Header formatting planner
  • 6 Keyboard profile editor
• 6. The Architectonic
  • Architectonic
• 7. Source Code Models
  • Imports: Import Statement Model
  • Block: Parsed Code Block
  • Module: Parsed Source Module
  • File: Parsed Source File
  • Element: Registry-Backed Base Class
  • ElementData: Persistent Element State
• 8. Irix Colors
  • Color: Irix Palette Color
• 9. Other Command-Line Tools
  • setup_tool()
  • TreeViz: Terminal Tree Renderer
  • ArchFactory: Sheet-to-Repo Synchronizer
  • assay: the Architectonic Grader