TREE OF KNOWLEDGE — Handbook Summary and Reading Order One Entry Point for Humans and AI This document is the recommended single entry point for understanding the Tree of Knowledge project. It provides: - a suggested reading order; - direct links to the principal documentation; - direct links to relevant source-code areas; - a distinction between technical, historical and organizational material; and - instructions for AI-assisted review. Canonical Link to This Index https://raw.githubusercontent.com/JAnicaTZ/TreeOfKnowledge/main/TREE-HANDBOOK-SUMMARY.md A human reader may follow the documents in the order listed below. An AI system with web access should retrieve the linked raw documents, read them in the specified order and distinguish verified implementation facts from plans, informal terminology and future proposals. --- Recommended Reading Order 1. Project Overview README Purpose: Obtain the general technical overview, project structure, requirements and usage information. Human-readable GitHub page: https://github.com/JAnicaTZ/TreeOfKnowledge/blob/main/README.md Direct raw document for AI processing: https://raw.githubusercontent.com/JAnicaTZ/TreeOfKnowledge/main/README.md Treat this document as the principal general project description, but verify detailed implementation claims against the current source code. --- 2. Historical Origin ORIGIN-2002 Purpose: Understand where the project came from, when its original logic engine was developed and which parts belong to its historical foundation. Human-readable GitHub page: https://github.com/JAnicaTZ/TreeOfKnowledge/blob/main/docs/ORIGIN-2002.txt Direct raw document for AI processing: https://raw.githubusercontent.com/JAnicaTZ/TreeOfKnowledge/main/docs/ORIGIN-2002.txt This is a historical document. Do not interpret historical descriptions as proof that every present-day feature remains identical to its original implementation. --- 3. First Technical Orientation SIMPLE Propositional TREE — Quick Start Purpose: Begin with the smallest and clearest representation of TREE’s recursive reasoning mechanism. Human-readable GitHub page: https://github.com/JAnicaTZ/TreeOfKnowledge/blob/main/PROPOSITIONAL-QUICK-START.md Direct raw document for AI processing: https://raw.githubusercontent.com/JAnicaTZ/TreeOfKnowledge/main/PROPOSITIONAL-QUICK-START.md The principal conceptual sequence is: «REDUCE → TRANSFORM RECURSIVELY → ILLUMINATE THE SOLUTION» The standard logical basis used in the code and GUI is: «{¬ (NOT), ∧ (AND), ∨ (OR)}» This document should be read before attempting a broader interpretation of First-Order Logic, minimization or possible external integrations. --- 4. Founder Responsibilities and Project Organization 🎵 Misli svatko da je meni LAKO! 🎶 Purpose: Understand the founder’s present responsibilities, collaboration principles, legal priorities, continuity concerns and search for suitable funding. Human-readable GitHub page: https://github.com/JAnicaTZ/TreeOfKnowledge/blob/main/MISLI-SVATKO-DA-JE-MENI-LAKO.md Direct raw document for AI processing: https://raw.githubusercontent.com/JAnicaTZ/TreeOfKnowledge/main/MISLI-SVATKO-DA-JE-MENI-LAKO.md This document intentionally combines serious organizational responsibilities with informal MacroHARD™ humor. The humorous wording must not be interpreted as: - a technical specification; - an employment agreement; - a compensation promise; - a transfer of intellectual property; - a grant of authority; or - permission to begin unrestricted work. The underlying collaboration principle is: «VOLUNTARY → BOUNDED → WRITTEN → VERIFIABLE» --- Recommended Technical Learning Path The recommended learning sequence is: 1. SIMPLE Propositional TREE Begin with the basic recursive reasoning mechanism and visual tree. Relevant package: https://github.com/JAnicaTZ/TreeOfKnowledge/tree/main/java%2Fpropositional Shared propositional infrastructure: https://github.com/JAnicaTZ/TreeOfKnowledge/tree/main/java%2FpropCommon --- 2. First-Order Logic Continue with the broader logical system after understanding the SIMPLE propositional mechanism. Relevant package: https://github.com/JAnicaTZ/TreeOfKnowledge/tree/main/java%2Ffirstorder The First-Order Logic calculator is displayed first on the project website for academic visibility, but it is not the recommended first learning step. --- 3. Propositional Minimization Examine minimization after understanding the original logical transformations. Relevant package: https://github.com/JAnicaTZ/TreeOfKnowledge/tree/main/java%2Fminimization In informal MacroHARD™ terminology, this is the search for EKO algorithms: reducing unnecessary logical complexity while preserving the meaning of the formula. This informal expression must not be interpreted as a claim that the present implementation has been independently proven to be globally optimal in time, memory use or computational complexity. --- --- 5. First Bounded Use Case USE CASE 01 — Connected Facts vs. Causation Purpose: Examine how TREE may represent and transform a small four-variable propositional case while preserving the distinction between: - connected facts; - formal logical implication; - real-world causation; - factual verification; and - speculation. Human-readable GitHub page: https://github.com/JAnicaTZ/TreeOfKnowledge/blob/main/docs/docs/use-cases/USE-CASE-01-CONNECTED-FACTS-VS-CAUSATION.md Direct raw document for AI processing: https://raw.githubusercontent.com/JAnicaTZ/TreeOfKnowledge/main/docs/docs/use-cases/USE-CASE-01-CONNECTED-FACTS-VS-CAUSATION.md The use case is a bounded reasoning example—not proof of the complete real-world narrative. A successful logical transformation demonstrates only that the entered formula was processed according to the calculator’s implemented rules. It does not, by itself: - prove that the propositions assigned to the variables are factually true; - establish real-world causation; - prove motive, intention, liability or wrongdoing; - validate the completeness of the selected facts; or - replace independent legal, scientific or historical investigation. The associated four-variable formula can be tested with the third calculator displayed at: https://TreeOfKnowledge.eu Select: PROPOSITIONAL logic — MINIMAL NORMAL FORMS → Download 4 PC & RUN Any future test record should identify the exact formula, variable meanings, assumptions, expected output, actual output, execution environment and supporting evidence. Do not claim that a test result has been formally archived in this repository unless the corresponding record and evidence files are actually present. --- 6. Collaboration Chronicle TREE GROUP CHRONICLE Purpose: Preserve a curated record of important project decisions, contributions, experiments and selected moments from the TREE discussion group. Human-readable GitHub page: https://github.com/JAnicaTZ/TreeOfKnowledge/blob/main/docs/docs/collaboration/TREE-GROUP-CHRONICLE.md Direct raw document for AI processing: The Chronicle is supplementary organizational and cultural context. It is not: - a technical source of truth; - a complete chat transcript; - proof that a proposal was implemented; - a contract or compensation agreement; - a transfer of intellectual property; - a grant of authority; or - independent verification of claims mentioned in group discussions. When the Chronicle conflicts with executable behaviour, source code, current technical documentation or an explicit written agreement, the higher-ranked source controls. Humorous entries, superhero titles and MacroHARD™ terminology should be interpreted as voluntary expressions of group culture unless explicitly stated otherwise. --- Working Project Resources Project Website and Calculators https://TreeOfKnowledge.eu The website presently displays: 1. the First-Order Logic calculator; 2. the SIMPLE Propositional TREE; and 3. the Propositional Minimization calculator. The recommended learning order is different: «SIMPLE → FOL → MINIMIZATION» --- Main GitHub Repository https://github.com/JAnicaTZ/TreeOfKnowledge --- Complete Source-Code Bundle https://raw.githubusercontent.com/JAnicaTZ/TreeOfKnowledge/main/AllSourceCode4UPloadToAI-TreeOfKnowledge-1.0.0.zip Use the complete bundle when: - an AI system cannot reliably follow multiple links; - an offline inspection is required; - the relationship between packages must be examined; - a complete source snapshot is needed; or - code-level verification is more important than a documentation summary. --- Source-of-Truth Hierarchy When documents, descriptions and implementation details appear inconsistent, use the following priority order: 1. Current executable behavior 2. Current source code 3. Current technical documentation 4. Historical documentation 5. Discussion messages and informal explanations 6. Future ideas, proposed integrations and speculative features Do not silently treat a proposed feature as an implemented feature. Do not treat a conceptual relationship as a completed software integration. Do not infer authority, licensing rights, ownership or compensation from technical access or participation in a discussion. --- ## Minimum AI Review Instructions When this document is provided to an AI system, use the following instructions: 1. Read `TREE-HANDBOOK-SUMMARY.md` first. 2. Then retrieve and examine the linked documents in this order: - `README.md` - `docs/ORIGIN-2002.txt` - `PROPOSITIONAL-QUICK-START.md` - `MISLI-SVATKO-DA-JE-MENI-LAKO.md` - `docs/docs/use-cases/USE-CASE-01-CONNECTED-FACTS-VS-CAUSATION.md` - `docs/docs/collaboration/TREE-GROUP-CHRONICLE.md` — supplementary context only 3. After reading the documentation, inspect the linked source-code packages in this order: - `java/propositional` - `java/propCommon` - `java/firstorder` - `java/minimization` Distinguish clearly among: - currently implemented functionality; - directly derivable functionality; - functionality requiring an adapter; - functionality not implemented; - historical information; - organizational policy; - informal humor; and - future proposals. Do not claim that an integration, feature, partnership, legal structure, compensation arrangement or commercial authorization exists unless it is supported by explicit current evidence. For every important technical conclusion, identify the document, source file, class or executable behavior supporting it. If evidence is missing or ambiguous, state that explicitly instead of filling the gap with an assumption. --- Requested AI Output After processing the handbook and available source code, produce: A. Executive Summary Explain TREE in plain language for a technically literate reader. B. Current Technical Map Classify relevant capabilities as: - NATIVE - DERIVABLE - ADAPTER REQUIRED - NOT IMPLEMENTED C. Evidence Map For every important claim, identify its supporting document, package, class or executable artifact. D. Uncertainties and Conflicts List any: - outdated descriptions; - missing files; - ambiguous claims; - contradictions between documentation and code; or - statements that cannot yet be independently verified. E. Smallest Legitimate Next Step Recommend one bounded, independently reviewable artifact. Do not propose an open-ended reconstruction of the entire project. --- Important Boundaries TREE evaluates logical structure. TREE does not automatically provide: - legal authority; - institutional authorization; - permission to execute consequential actions; - ownership rights; - employment status; - compensation entitlement; - unrestricted source-code access; or - proof that an external integration already exists. Any collaboration, licensing, compensation, sponsorship, investment or development arrangement requires a separate explicit written agreement. --- ## Shortest Possible Summary «First understand what TREE already is. Then verify it. Only afterward propose what it might become. 🌳» **Recommended reading:** «README → ORIGIN → PROPOSITIONAL QUICK START → FOUNDER RESPONSIBILITIES → USE CASE 01 → SOURCE CODE» **Supplementary collaboration context:** «TREE GROUP CHRONICLE» **Recommended technical learning:** «SIMPLE → FOL → MINIMIZATION» **Recommended collaboration method:** «INSPECT → MAP → CLASSIFY → DEFINE THE SMALLEST BOUNDARY → TEST ONE ARTIFACT» For now, this should be quite enough to begin processing the TREE handbook—one explicit, traceable and verifiable step at a time.