Axiom Logic Sources (Where The “Dots” Live)
This vault distinguishes:
- gathering (collecting files) from
- curation/toil (making the claim graph correct).
When you need logic (dependencies, “feeds into,” chain structure, defeat conditions), the primary reference is the walkthrough-site axiom corpus.
Primary Logic Corpus (Walkthrough Site)
Paths (authoritative for logic articulation):
C:\Users\lowes\OneDrive\Desktop\Folders\theophysics_walkthrough_site\site\content\00_PRIMORDIALC:\Users\lowes\OneDrive\Desktop\Folders\theophysics_walkthrough_site\site\content\01_AXIOMS
What’s inside (typical per-note structure):
- YAML frontmatter fields like
id,type,stage,tier,depends_on,feeds_into/enables,defeat_conditions,iron_chain_position - Sections like Formal Statement, Defeat Conditions, Defense Grid, Logical Flow
How to use it (rules of engagement):
- Treat
depends_onas minimal prerequisites (not “all related concepts”). - Treat
feeds_intoas downstream commitments (what becomes possible next). - Use Defeat Conditions as the “falsification interface” (even for non-empirical claims, use logical/scope defeat).
- Prefer the note’s Logical Flow section when it conflicts with casual link-graphs elsewhere.
Local Exports (For Fast Graph Work)
These exports are generated from the walkthrough-site YAML into simple node/edge tables and a vault-readable summary:
O:\Theophysics_Master\TMSUB\GO FOLDER\Axiom\10_Maps\MAP_WalkthroughSite_Logic.mdO:\Theophysics_Master\TMSUB\GO FOLDER\Axiom\10_Maps\WalkthroughSite_LogicNodes.csvO:\Theophysics_Master\TMSUB\GO FOLDER\Axiom\10_Maps\WalkthroughSite_LogicEdges.csv
Compiled Axiom Catalog (for “list all axioms”)
O:\Theophysics_Master\TMSUB\GO FOLDER\Axiom\10_Maps\MAP_WalkthroughSite_AxiomsCatalog.mdO:\Theophysics_Master\TMSUB\GO FOLDER\Axiom\10_Maps\WalkthroughSite_AxiomsCatalog.csvO:\Theophysics_Master\TMSUB\GO FOLDER\Axiom\10_Maps\WalkthroughSite_ContentNodes.csvO:\Theophysics_Master\TMSUB\GO FOLDER\Axiom\10_Maps\WalkthroughSite_ContentEdges.csv
Use these when you need to:
- find orphan nodes / missing targets
- compute “what collapses if X fails”
- auto-generate dependency checklists for manual curation passes
What Not To Do
- Don’t treat a file dump as “logic.”
- Don’t infer dependencies purely from shared keywords.
- Don’t fabricate missing nodes; mark them unresolved and locate their real source.
Evidence Bundles (AxiomMatches)
Path:
O:\_THEO\AxiomMatches\Match_20260115_102431
How to use it:
- Treat it as per-axiom source/evidence buckets (useful for reading and provenance), not as the authoritative place where dependency logic is authored.
- The “make it right” work still requires writing/maintaining curated axiom notes (clean statement, minimal dependencies, defeat conditions, objections/defenses, collapse analysis) using the walkthrough-site logic as the primary reference when conflicts arise.