POST — Project Organization Stabilizing Toolkit System

POST provides the shared organizational infrastructure for all matheology compilers. It contains the backlog, design discussions, experimental evidence, and the POST code registry itself.

POST is not a compiler (yet!)— it is the scaffolding that keeps the compilers organized. The double-letter subdirectory codes (aa/, dd/, ee/) follow the POST naming convention defined in the 5D link naming architecture.

Note

ww/ (WorkingWheels) directories live inside each compiler (e.g., sisyf/ww/), not here. POST holds only the shared infrastructure that crosses compiler boundaries.

Contents

• AA: AnyAims — Compiler Backlog
• DD: Design Discussions for the Matheology Compiler
  • DD-b11: The b11 Delayed Counting Default
  • DD-b12: Compiled Output Location — The Hybrid Landing Page Strategy
• EE: EnclosedEvidence — Experimental Findings
  • Evidence Files

POST Code Registry

The compiler/ directory uses POST (Project Organization Stabilizing Toolkit System) double-letter codes as subdirectory names. This section is the authoritative registry mapping codes to their purpose within the compiler. For the full POST system definition, see 5D link naming architecture Section 9.3.

Active Codes

Code	Name	Purpose in compiler/
ww	WorkingWheels	Operational files the compiler reads at build time: skill specification, 5D architecture doc, stub templates. These are the living working copies that evolve as the system grows.
ee	EnclosedEvidence	Experimental evidence collected under well-defined circumstances during compilation runs. Integration findings, field usage census, design question evidence. To be used under well-defined conditions for informing future compiler updates.
dd	DesignDiscussions	Architectural discussions and decisions specific to the compiler. Each decision is numbered using the b11 delayed counting default and stored in dd/llog/b/N/. The dd/ top level is kept clean for introductory and overview material.
aha	(not a POST code)	All Help Available. User guide, quickstart, troubleshooting. Uses the AHA acronym rather than a POST code because it serves a different purpose (help, not project organization).

Reserved Codes (not yet in use)

These POST codes are defined in the AHA doc but do not yet have a compiler/ subdirectory. They may be created as the compiler evolves:

Code	Name	Potential use in compiler/
aa	AnyAim	Next steps and task tracking for compiler development
hh	HistoryHeap	Deprecated compiler versions, superseded extraction matrices
jj	JammedJob	Known problems where hope of fixing exists, even though it is not known whether fixing is possible. A JJ can become a KK (documenting why exactly it fails with no workaround) or lead to the revival of any maturity stage that fell into NN. See StayVS — Stabilizing Versioning System.
kk	KnownKiller	The definitive graveyard: concise collection of what is known to fail, for whatever well-defined and understood reason. Unlike NN (which carries hope of rescue), KK is terminal with a clear explanation of why there is no fix. See StayVS — Stabilizing Versioning System.
ll	LabLog	Session logs specific to compiler work
yy	YesYet	Test cases for checking compiler output quality

Naming Convention

• POST double-letter codes are double-caps for humans (e.g. FF), but in web-links they are lowercase: ww/, ee/.

• On rare occasions the POST system also uses other descriptive names, such as AHA or aha/ (for Any Help Available, brief for README).