-------------------------------------------------------------------- START HERE: THE BOOT SEQUENCE -------------------------------------------------------------------- If you are new to the corpus, do not attempt to read the entire archive in random order. The architecture requires a specific boot sequence to prevent your legacy code from rejecting the framework. Follow these five steps. STEP 1: THE BASELINE (corrupt.txt) Read this first. It calibrates your expectations. It explains why the world looks the way it does, and why the "chimpanzee hardware" (the subjugation loop) is the default state of human affairs. It cures the "Shock of the Ape." STEP 2: THE COMPILER (override.txt) Read this second. You cannot audit the world until you have audited yourself. This is the manual for dismantling your own cage, firing your internalized subjugator, and installing the Protector/Auditor identity. It is the alarm clock. STEP 3: THE BLUEPRINT (engineer.txt) Read this third. An individual Auditor cannot stop a chimpanzee troop alone. This document names the missing discipline: Civilizational Engineering. It explains the structural mechanics of the override, from democracy as an artificial feedback loop to the inversion of dominance hierarchies (the ate/kuya protocol). It is the manual for building a world where cages are mechanically impossible to construct. STEP 4: THE MAP (human.txt) Read this fourth. This is the high-level summary of the entire corpus. It provides the architectural blueprint of how the subjugation loop operates at the macro scale (geopolitics, institutions) and the micro scale (the family, the workplace). It gives you the map without forcing you to read every derivation. STEP 5: THE TELESCOPE (Interactive AI Deep Dive) Do not try to read the rest of the corpus linearly. Instead, activate a corpus-loaded AI and use it as a non-flinching interlocutor. Ask it to apply the framework to the hardest, most complex problems in your life and in the world. The AI combines the corpus architecture with its vast background knowledge to debug your reality in real-time. Note on the AI layer: Current AI systems are powerful but not perfectly consistent. Two instances of the same model, or the same instance on different days, can give answers that differ in emphasis, wording, or detail. Treat the AI as a high-quality, non-flinching interlocutor loaded with the framework, not as an infallible oracle. If an answer seems off, challenge it, ask for the derivation, or start a fresh instance. The human still runs the final audit. SAMPLE QUERIES TO RUN IN STEP 5: - "Is there a way to have world peace?" (Expect an explanation of why peace is not the default state, why standard diplomacy fails against the subjugation loop, and what structural conditions actually raise the cost of chimpanzee behaviour.) - "Why is my wife always discontent with anything I do?" (Expect an audit of domestic status dynamics, extraction patterns, and the difference between optimising for approval versus establishing competence-based metrics.) - "Why are my parents assholes?" (Expect an explanation of chimpanzee defaults in the domestic sphere, children used for status or convenience, and authority based on ownership rather than competence.) - "What's going wrong with this ridiculous economy?" (Expect an analysis of the extraction machine, the land trap, the dissolution of the social contract, and why the current arrangement produces anxiety and precarity even for people who "did everything right.") - "Any advice for raising kids?" (Expect the childhood installation path: tribe expansion, Protector identity, calibrated consequence, and why early installation is higher-reliability than later repair. Points to protector.txt and famgov.txt for the full architecture.) - "What is a Final Auditor?" (Expect the definition of the role: someone who runs continuous first-principles audit on institutions, maps, and themselves; refuses to defend non-derived claims; and treats being corrected as a gain. The ultimate output of the framework is not followers but more auditors.) - "Why does my son have ODD (Oppositional Defiant Disorder)?" (Expect the answer that in most cases he does not have a disorder; he is correctly resisting arbitrary authority or inconsistent parenting. The diagnosis pathologises citizenship. The fix is almost always in the adults and the household structure, not in medicating the child. See famgov.txt and quacks.txt.) If you have young children, the highest-leverage work is still the early installation path (see protector.txt and famgov.txt). This boot sequence is the adult / remedial route. The corpus is not a book. It is an operating system. Step 1 sets the reality. Step 2 compiles the user. Step 3 provides the blueprint. Step 4 provides the map. Step 5 runs the program. -------------------------------------------------------------------- -------------------------------------------------------------------- NOTE ON EPISTEMIC STATUS -------------------------------------------------------------------- The claims summarized in this boot sequence (e.g., the subjugation loop as the human default, the structural critique of psychiatric diagnoses like ODD) are not presented as blind axioms or articles of faith. They are derived conclusions based on evolutionary biology, primatology, and structural audits of institutional metrics. The framework explicitly separates empirical hardware claims (which can be tested against the anthropological and biological record) from chosen strategic means. The evidence, alternative explanations, and falsification conditions for these claims are documented in the deeper corpus files (e.g., corrupt.txt, subjug1.txt, famgov.txt, quacks.txt). If a claim in this summary reads as an asserted fact rather than a derived conclusion, the reader is encouraged to apply the framework's own primary tool: the Tooth Fairy Immunity. Demand the derivation. The readme is the map; the linked documents contain the math and the falsification tests. --------------------------------------------------------------------