{ "version": "0.1.0", "edition_date": "2026-09-15", "source_commit": "c833d39f606d2b237eeaecbd5c41a350dde823cb", "articles": [ { "path": "index.md", "title": "Vast Development Method Theory", "description": "A language-independent account of contextual recollection, staged synthesis, and persistent editorial reconciliation.", "section": "Overview", "evidence": "Formal framework", "url": "/", "html_file": "index.html", "markdown_url": "/markdown/index.md", "sha256": "f3eb1efb930a62c10dce14fc2bce09070abd1cf3c5da8e77627ac98be2ce43bf", "words": 524, "listed": true, "headings": [ { "level": 1, "id": "vast-development-method-theory", "text": "Vast Development Method Theory" }, { "level": 2, "id": "from-structured-knowledge-to-reproducible-artifacts", "text": "From structured knowledge to reproducible artifacts" }, { "level": 2, "id": "the-defining-insight", "text": "The defining insight" }, { "level": 2, "id": "read-at-the-right-depth", "text": "Read at the right depth" }, { "level": 2, "id": "what-is-established-and-what-remains-a-research-question", "text": "What is established, and what remains a research question?" } ] }, { "path": "white-paper.md", "title": "White paper", "description": "The integrated argument and formal account of contextual recollection, staged synthesis, and persistent editorial reconciliation.", "section": "Overview", "evidence": "Formal framework, source observations, and research hypotheses", "url": "/white-paper/", "html_file": "white-paper/index.html", "markdown_url": "/markdown/white-paper.md", "sha256": "6b5ec8cce996b96ee1e1ff9f41667cc022b049e3dec5dbf6bcdcf49e24ca937f", "words": 2616, "listed": true, "headings": [ { "level": 1, "id": "vast-development-method-theory", "text": "Vast Development Method Theory" }, { "level": 2, "id": "abstract", "text": "Abstract" }, { "level": 2, "id": "1-problem-and-contribution", "text": "1. Problem and contribution" }, { "level": 2, "id": "2-method-and-evidence", "text": "2. Method and evidence" }, { "level": 2, "id": "3-state-identity-and-interpretation", "text": "3. State, identity, and interpretation" }, { "level": 2, "id": "4-the-inner-loop-completing-the-context", "text": "4. The inner loop: completing the context" }, { "level": 2, "id": "5-hierarchical-reuse-and-output-expansion", "text": "5. Hierarchical reuse and output expansion" }, { "level": 2, "id": "6-staged-binding-and-materialization", "text": "6. Staged binding and materialization" }, { "level": 2, "id": "7-the-outer-loop-persistent-editorial-reconciliation", "text": "7. The outer loop: persistent editorial reconciliation" }, { "level": 2, "id": "8-originating-implementation-and-historical-record", "text": "8. Originating implementation and historical record" }, { "level": 2, "id": "9-self-generation-and-expressive-scope", "text": "9. Self-generation and expressive scope" }, { "level": 2, "id": "10-costs-performance-and-cognitive-hypotheses", "text": "10. Costs, performance, and cognitive hypotheses" }, { "level": 2, "id": "11-conclusion", "text": "11. Conclusion" } ] }, { "path": "reading-guide.md", "title": "Reading guide", "description": "Routes through the paper for researchers, implementers, reviewers, and machine readers.", "section": "Overview", "evidence": "Publication guidance", "url": "/reading-guide/", "html_file": "reading-guide/index.html", "markdown_url": "/markdown/reading-guide.md", "sha256": "05d29bc6aad27200d2288d6e56c873bb6a80c6a02947fe2cec05a1e33772a0c8", "words": 468, "listed": true, "headings": [ { "level": 1, "id": "reading-guide", "text": "Reading guide" }, { "level": 2, "id": "for-a-first-reading", "text": "For a first reading" }, { "level": 2, "id": "for-a-mathematical-review", "text": "For a mathematical review" }, { "level": 2, "id": "for-implementers", "text": "For implementers" }, { "level": 2, "id": "for-source-auditors", "text": "For source auditors" }, { "level": 2, "id": "for-researchers-studying-recollection", "text": "For researchers studying recollection" }, { "level": 2, "id": "for-machine-readers", "text": "For machine readers" }, { "level": 2, "id": "how-to-read-a-claim", "text": "How to read a claim" } ] }, { "path": "foundations/definition.md", "title": "Formal definition and scope", "description": "The minimum commitments of VDMT and the distinction between core synthesis, round-trip, and self-generative profiles.", "section": "Foundations", "evidence": "Formal model", "url": "/foundations/definition/", "html_file": "foundations/definition/index.html", "markdown_url": "/markdown/foundations/definition.md", "sha256": "1227498e6ecebd1aceee371b7589c2471d1c025ea14fa9bb97639bfc676e5943", "words": 610, "listed": true, "headings": [ { "level": 1, "id": "formal-definition-and-scope", "text": "Formal definition and scope" }, { "level": 2, "id": "definition", "text": "Definition" }, { "level": 2, "id": "architectural-commitments", "text": "Architectural commitments" }, { "level": 2, "id": "profiles", "text": "Profiles" }, { "level": 2, "id": "the-two-loop-distinction", "text": "The two-loop distinction" }, { "level": 2, "id": "exclusions", "text": "Exclusions" } ] }, { "path": "foundations/notation.md", "title": "Mathematical notation", "description": "Types, functions, relations, orders, identities, and the exact meaning of the symbols used throughout the paper.", "section": "Foundations", "evidence": "Formal model", "url": "/foundations/notation/", "html_file": "foundations/notation/index.html", "markdown_url": "/markdown/foundations/notation.md", "sha256": "a03742dd34eeaadecbf1cda46f8bf6e5bba64368afc6b269c5ede0f0d9baece2", "words": 519, "listed": true, "headings": [ { "level": 1, "id": "mathematical-notation", "text": "Mathematical notation" }, { "level": 2, "id": "universes-and-partial-information", "text": "Universes and partial information" }, { "level": 2, "id": "names-used-by-the-abstract-machine", "text": "Names used by the abstract machine" }, { "level": 2, "id": "information-order", "text": "Information order" }, { "level": 2, "id": "identity-and-context", "text": "Identity and context" }, { "level": 2, "id": "equivalence", "text": "Equivalence" } ] }, { "path": "foundations/epistemic-status.md", "title": "Evidence and claim status", "description": "A taxonomy that separates implementation observations, historical evidence, testimony, proofs, proposals, and empirical hypotheses.", "section": "Foundations", "evidence": "Methodology", "url": "/foundations/epistemic-status/", "html_file": "foundations/epistemic-status/index.html", "markdown_url": "/markdown/foundations/epistemic-status.md", "sha256": "c682a4a56365a0255e1ab2c088b84802b58faa55272096b92b59898dbc7852fb", "words": 582, "listed": true, "headings": [ { "level": 1, "id": "evidence-and-claim-status", "text": "Evidence and claim status" }, { "level": 2, "id": "s-source-observation", "text": "S — Source observation" }, { "level": 2, "id": "h-historical-record", "text": "H — Historical record" }, { "level": 2, "id": "a-author-testimony", "text": "A — Author testimony" }, { "level": 2, "id": "f-formal-model-or-deduction", "text": "F — Formal model or deduction" }, { "level": 2, "id": "p-proposed-implementation-extension", "text": "P — Proposed implementation extension" }, { "level": 2, "id": "e-empirical-hypothesis-or-measurement", "text": "E — Empirical hypothesis or measurement" }, { "level": 2, "id": "scope-of-this-edition", "text": "Scope of this edition" }, { "level": 2, "id": "reading-mixed-claims", "text": "Reading mixed claims" }, { "level": 2, "id": "publication-discipline", "text": "Publication discipline" } ] }, { "path": "foundations/provenance.md", "title": "Historical provenance and authorship", "description": "The public implementation date, author attribution, early source evidence, and the distinction between a method and a later formal edition.", "section": "Foundations", "evidence": "Historical record and author testimony", "url": "/foundations/provenance/", "html_file": "foundations/provenance/index.html", "markdown_url": "/markdown/foundations/provenance.md", "sha256": "e8b00f1c08c4d52ffa5431255f8b02e50cfa1708d4ce2f01bb5bf5f651923dc9", "words": 637, "listed": true, "headings": [ { "level": 1, "id": "historical-provenance-and-authorship", "text": "Historical provenance and authorship" }, { "level": 2, "id": "historical-public-implementation-date", "text": "Historical public implementation date" }, { "level": 2, "id": "development-before-public-release", "text": "Development before public release" }, { "level": 2, "id": "attribution", "text": "Attribution" }, { "level": 2, "id": "independent-development-and-related-work", "text": "Independent development and related work" }, { "level": 2, "id": "method-implementation-and-manuscript-dates", "text": "Method, implementation, and manuscript dates" }, { "level": 2, "id": "preserving-the-record", "text": "Preserving the record" } ] }, { "path": "foundations/related-work.md", "title": "Related work and intellectual boundaries", "description": "The closest mathematical and architectural precedents, their similarities, and the distinctions that remain meaningful.", "section": "Foundations", "evidence": "Literature comparison and interpretation", "url": "/foundations/related-work/", "html_file": "foundations/related-work/index.html", "markdown_url": "/markdown/foundations/related-work.md", "sha256": "681f1b50bb4731583f9b6c52dcf40ffa72e05a3476f0bb08823479bc4d28bacc", "words": 988, "listed": true, "headings": [ { "level": 1, "id": "related-work-and-intellectual-boundaries", "text": "Related work and intellectual boundaries" }, { "level": 2, "id": "a-composition-not-an-invention-of-every-ingredient", "text": "A composition, not an invention of every ingredient" }, { "level": 2, "id": "compiler-pipelines-and-intermediate-representations", "text": "Compiler pipelines and intermediate representations" }, { "level": 2, "id": "attribute-grammars-and-hierarchical-interpretation", "text": "Attribute grammars and hierarchical interpretation" }, { "level": 2, "id": "fixed-point-semantics-and-production-systems", "text": "Fixed-point semantics and production systems" }, { "level": 2, "id": "blackboard-architectures", "text": "Blackboard architectures" }, { "level": 2, "id": "tuple-spaces", "text": "Tuple spaces" }, { "level": 2, "id": "staging-partial-evaluation-and-templates", "text": "Staging, partial evaluation, and templates" }, { "level": 2, "id": "memoization-and-incremental-build-systems", "text": "Memoization and incremental build systems" }, { "level": 2, "id": "bidirectional-transformations-and-round-trip-engineering", "text": "Bidirectional transformations and round-trip engineering" }, { "level": 2, "id": "provenance-etl-and-materialized-views", "text": "Provenance, ETL, and materialized views" }, { "level": 2, "id": "cognitive-architectures", "text": "Cognitive architectures" }, { "level": 2, "id": "contribution-statement", "text": "Contribution statement" } ] }, { "path": "foundations/terminology.md", "title": "Terminology and category distinctions", "description": "Choosing established technical language without confusing memory, recursion, self-generation, determinism, and cognition.", "section": "Foundations", "evidence": "Definitions and terminology comparison", "url": "/foundations/terminology/", "html_file": "foundations/terminology/index.html", "markdown_url": "/markdown/foundations/terminology.md", "sha256": "9a0702e5039cf7b03e33d028e53b5ac9832c4c48385c9deddb5d82def6495dff", "words": 545, "listed": true, "headings": [ { "level": 1, "id": "terminology-and-category-distinctions", "text": "Terminology and category distinctions" }, { "level": 2, "id": "theory-framework-method-and-algorithm", "text": "Theory, framework, method, and algorithm" }, { "level": 2, "id": "logical-memory-versus-physical-allocation", "text": "Logical memory versus physical allocation" }, { "level": 2, "id": "recursion-iteration-and-feedback", "text": "Recursion, iteration, and feedback" }, { "level": 2, "id": "determinism-confluence-and-correctness", "text": "Determinism, confluence, and correctness" }, { "level": 2, "id": "self-generation-and-turing-completeness", "text": "Self-generation and Turing completeness" }, { "level": 2, "id": "recollection-and-comprehension", "text": "Recollection and comprehension" }, { "level": 2, "id": "a-compact-technical-description", "text": "A compact technical description" } ] }, { "path": "semantics/state-space.md", "title": "State space and abstract machine", "description": "A typed build state that separates durable knowledge, temporary stores, artifact plans, provenance, and external effects.", "section": "Semantics", "evidence": "Formal model", "url": "/semantics/state-space/", "html_file": "semantics/state-space/index.html", "markdown_url": "/markdown/semantics/state-space.md", "sha256": "a0133ee86606908917ab234d2e37dd5f2a447da4d70641e37ffe20e85a62a07b", "words": 567, "listed": true, "headings": [ { "level": 1, "id": "state-space-and-abstract-machine", "text": "State space and abstract machine" }, { "level": 2, "id": "a-build-is-an-epoch-not-an-unbounded-mutable-universe", "text": "A build is an epoch, not an unbounded mutable universe" }, { "level": 2, "id": "typed-and-scoped-bindings", "text": "Typed and scoped bindings" }, { "level": 2, "id": "consistency-and-joins", "text": "Consistency and joins" }, { "level": 2, "id": "phase-boundaries", "text": "Phase boundaries" }, { "level": 2, "id": "observable-behavior", "text": "Observable behavior" } ] }, { "path": "semantics/context-closure.md", "title": "Context closure", "description": "Finite dependency discovery, context-qualified requests, stable resolution, and the conditions for worklist saturation.", "section": "Semantics", "evidence": "Formal model", "url": "/semantics/context-closure/", "html_file": "semantics/context-closure/index.html", "markdown_url": "/markdown/semantics/context-closure.md", "sha256": "7aea5d14e3799658c0c4bf71f99cf62c5cdfec19e2d45dd8b93aa635d83e8b5f", "words": 525, "listed": true, "headings": [ { "level": 1, "id": "context-closure", "text": "Context closure" }, { "level": 2, "id": "requests-can-discover-further-requests", "text": "Requests can discover further requests" }, { "level": 2, "id": "worklist-execution", "text": "Worklist execution" }, { "level": 2, "id": "when-a-visited-set-is-insufficient", "text": "When a visited set is insufficient" }, { "level": 2, "id": "absence-and-completion", "text": "Absence and completion" }, { "level": 2, "id": "bounds", "text": "Bounds" } ] }, { "path": "semantics/derivation.md", "title": "Guarded derivation and strata", "description": "How recollected facts become new facts and fragments without hiding non-monotone conditions or destructive updates.", "section": "Semantics", "evidence": "Formal model", "url": "/semantics/derivation/", "html_file": "semantics/derivation/index.html", "markdown_url": "/markdown/semantics/derivation.md", "sha256": "9dbe3f377884442aee3f86184e3b5ed44176768712b5f43abdfc1780802423dc", "words": 542, "listed": true, "headings": [ { "level": 1, "id": "guarded-derivation-and-strata", "text": "Guarded derivation and strata" }, { "level": 2, "id": "from-availability-to-consequence", "text": "From availability to consequence" }, { "level": 2, "id": "positive-rules", "text": "Positive rules" }, { "level": 2, "id": "negative-conditions", "text": "Negative conditions" }, { "level": 2, "id": "aggregates-and-completeness", "text": "Aggregates and completeness" }, { "level": 2, "id": "context-sensitive-transformations", "text": "Context-sensitive transformations" }, { "level": 2, "id": "effects-and-extensions", "text": "Effects and extensions" } ] }, { "path": "semantics/fixed-points.md", "title": "Fixed points and closure laws", "description": "Conditional proofs of stabilization, least closure, monotonicity, and idempotence for a finite positive derivation model.", "section": "Semantics", "evidence": "Formal deductions", "url": "/semantics/fixed-points/", "html_file": "semantics/fixed-points/index.html", "markdown_url": "/markdown/semantics/fixed-points.md", "sha256": "70dd4d6aa9bc6522ac76940eabfa2b533535eea27f8d918c7cbe168987748aa8", "words": 528, "listed": true, "headings": [ { "level": 1, "id": "fixed-points-and-closure-laws", "text": "Fixed points and closure laws" }, { "level": 2, "id": "assumptions", "text": "Assumptions" }, { "level": 2, "id": "proposition-1-finite-stabilization", "text": "Proposition 1 — finite stabilization" }, { "level": 2, "id": "proposition-2-least-closed-superset", "text": "Proposition 2 — least closed superset" }, { "level": 2, "id": "proposition-3-closure-operator-laws", "text": "Proposition 3 — closure operator laws" }, { "level": 2, "id": "relationship-to-established-results", "text": "Relationship to established results" }, { "level": 2, "id": "counterexamples-that-delimit-the-result", "text": "Counterexamples that delimit the result" } ] }, { "path": "semantics/determinism.md", "title": "Determinism and reproducibility", "description": "The exact input boundary and output equivalence needed to make consistent outcomes a verifiable property.", "section": "Semantics", "evidence": "Formal deductions and implementation obligations", "url": "/semantics/determinism/", "html_file": "semantics/determinism/index.html", "markdown_url": "/markdown/semantics/determinism.md", "sha256": "bc7f9c6f37a25e87ee3a5692f33b432bdb9e6b9917c7f54b961ae685f912c4ed", "words": 543, "listed": true, "headings": [ { "level": 1, "id": "determinism-and-reproducibility", "text": "Determinism and reproducibility" }, { "level": 2, "id": "the-claim-that-matters", "text": "The claim that matters" }, { "level": 2, "id": "proposition-4-deterministic-staged-build", "text": "Proposition 4 — deterministic staged build" }, { "level": 2, "id": "hidden-inputs", "text": "Hidden inputs" }, { "level": 2, "id": "three-useful-comparison-levels", "text": "Three useful comparison levels" }, { "level": 2, "id": "errors-and-diagnostic-ordering", "text": "Errors and diagnostic ordering" }, { "level": 2, "id": "jcb-interpretation", "text": "JCB interpretation" } ] }, { "path": "semantics/confluence.md", "title": "Confluence and scheduling", "description": "Schedule-independent positive saturation, conflicting writes, ordered accumulation, and safe operation commutation.", "section": "Semantics", "evidence": "Formal deductions", "url": "/semantics/confluence/", "html_file": "semantics/confluence/index.html", "markdown_url": "/markdown/semantics/confluence.md", "sha256": "0ff2bdbcfc77ee675aba8ab1a1e5a0fcaaed98d77b028c6e6abdc4ad6cbcb25f", "words": 509, "listed": true, "headings": [ { "level": 1, "id": "confluence-and-scheduling", "text": "Confluence and scheduling" }, { "level": 2, "id": "same-result-is-not-the-same-as-the-same-execution-order", "text": "Same result is not the same as the same execution order" }, { "level": 2, "id": "proposition-5-schedule-independent-positive-saturation", "text": "Proposition 5 — schedule-independent positive saturation" }, { "level": 2, "id": "conflicting-writes", "text": "Conflicting writes" }, { "level": 2, "id": "ordered-accumulation", "text": "Ordered accumulation" }, { "level": 2, "id": "independence-criterion", "text": "Independence criterion" }, { "level": 2, "id": "implication-for-vdmt", "text": "Implication for VDMT" } ] }, { "path": "semantics/termination.md", "title": "Termination and bounded recursion", "description": "Separate stopping arguments for discovery, derivation, occurrence expansion, token substitution, and repeated builds.", "section": "Semantics", "evidence": "Formal deductions and implementation obligations", "url": "/semantics/termination/", "html_file": "semantics/termination/index.html", "markdown_url": "/markdown/semantics/termination.md", "sha256": "30910afe9b8bddb5ca841ce22ecee8c74a828ed11ba04f5478587f69fc33a17d", "words": 503, "listed": true, "headings": [ { "level": 1, "id": "termination-and-bounded-recursion", "text": "Termination and bounded recursion" }, { "level": 2, "id": "there-is-no-single-universal-stopping-argument", "text": "There is no single universal stopping argument" }, { "level": 2, "id": "discovery", "text": "Discovery" }, { "level": 2, "id": "positive-derivation", "text": "Positive derivation" }, { "level": 2, "id": "hierarchical-occurrence-expansion", "text": "Hierarchical occurrence expansion" }, { "level": 2, "id": "binding-and-rewriting", "text": "Binding and rewriting" }, { "level": 2, "id": "editorial-recovery", "text": "Editorial recovery" }, { "level": 2, "id": "the-outer-lifecycle", "text": "The outer lifecycle" }, { "level": 2, "id": "limits-as-failure-semantics", "text": "Limits as failure semantics" } ] }, { "path": "semantics/composition.md", "title": "Composition and dependency structure", "description": "How local interpretations combine into larger artifacts, and when shared definitions can be safely reused.", "section": "Semantics", "evidence": "Formal model and deductions", "url": "/semantics/composition/", "html_file": "semantics/composition/index.html", "markdown_url": "/markdown/semantics/composition.md", "sha256": "387b6a9666690889b8a2e89a5f2f992dde2199bff1f6752dfd9955d33d148cd4", "words": 521, "listed": true, "headings": [ { "level": 1, "id": "composition-and-dependency-structure", "text": "Composition and dependency structure" }, { "level": 2, "id": "more-than-a-linear-pipeline", "text": "More than a linear pipeline" }, { "level": 2, "id": "definition-level-and-occurrence-level-composition", "text": "Definition-level and occurrence-level composition" }, { "level": 2, "id": "inherited-and-synthesized-information", "text": "Inherited and synthesized information" }, { "level": 2, "id": "proposition-6-safe-independent-composition", "text": "Proposition 6 — safe independent composition" }, { "level": 2, "id": "compositional-correctness-is-conditional", "text": "Compositional correctness is conditional" }, { "level": 2, "id": "reuse-is-a-semantic-relation", "text": "Reuse is a semantic relation" } ] }, { "path": "mechanisms/scoped-memory.md", "title": "Scoped memory and recollection", "description": "Logical memory, ownership, missing values, availability, and lifecycle without confusing registries with physical allocation.", "section": "Mechanisms", "evidence": "Formal model and implementation interpretation", "url": "/mechanisms/scoped-memory/", "html_file": "mechanisms/scoped-memory/index.html", "markdown_url": "/markdown/mechanisms/scoped-memory.md", "sha256": "87b9ab457b6aeb5e32386883083b0af5d8eda2d9cef8211fc32d9745fa3e3d32", "words": 537, "listed": true, "headings": [ { "level": 1, "id": "scoped-memory-and-recollection", "text": "Scoped memory and recollection" }, { "level": 2, "id": "what-moves-between-stores", "text": "What moves between stores?" }, { "level": 2, "id": "a-contextual-lookup", "text": "A contextual lookup" }, { "level": 2, "id": "availability-is-not-truthiness", "text": "Availability is not truthiness" }, { "level": 2, "id": "store-roles", "text": "Store roles" }, { "level": 2, "id": "recollection-versus-memoization", "text": "Recollection versus memoization" }, { "level": 2, "id": "physical-memory-consequences", "text": "Physical memory consequences" } ] }, { "path": "mechanisms/nested-gathering.md", "title": "Nested gathering and the inner loop", "description": "The gather-then-gather-again behavior, its dependency semantics, and why two visible loops need not mean two fixed passes.", "section": "Mechanisms", "evidence": "Formal model and source-grounded interpretation", "url": "/mechanisms/nested-gathering/", "html_file": "mechanisms/nested-gathering/index.html", "markdown_url": "/markdown/mechanisms/nested-gathering.md", "sha256": "debbe571d2d74668b6e96c000c1390e0069d090ead7125035cea32eaa24fa292", "words": 524, "listed": true, "headings": [ { "level": 1, "id": "nested-gathering-and-the-inner-loop", "text": "Nested gathering and the inner loop" }, { "level": 2, "id": "the-first-answer-changes-the-next-question", "text": "The first answer changes the next question" }, { "level": 2, "id": "a-double-loop-is-an-implementation-shape", "text": "A double loop is an implementation shape" }, { "level": 2, "id": "three-kinds-of-recurrence", "text": "Three kinds of recurrence" }, { "level": 2, "id": "source-evidence", "text": "Source evidence" }, { "level": 2, "id": "correctness-obligations", "text": "Correctness obligations" }, { "level": 2, "id": "reusable-insight", "text": "Reusable insight" } ] }, { "path": "mechanisms/hierarchy-and-reuse.md", "title": "Hierarchical reuse and expansion", "description": "Shared definitions, contextual occurrences, fan-in, fan-out, cardinality, and the source of large output expansion.", "section": "Mechanisms", "evidence": "Formal model", "url": "/mechanisms/hierarchy-and-reuse/", "html_file": "mechanisms/hierarchy-and-reuse/index.html", "markdown_url": "/markdown/mechanisms/hierarchy-and-reuse.md", "sha256": "1e908484a586deb96ba99ecaff0c5f69f55b3530f5e2fee0b13f06c51ee390a4", "words": 493, "listed": true, "headings": [ { "level": 1, "id": "hierarchical-reuse-and-expansion", "text": "Hierarchical reuse and expansion" }, { "level": 2, "id": "definitions-form-a-graph-uses-form-occurrences", "text": "Definitions form a graph; uses form occurrences" }, { "level": 2, "id": "worked-cardinalities", "text": "Worked cardinalities" }, { "level": 2, "id": "expansion-function", "text": "Expansion function" }, { "level": 2, "id": "fan-out-and-fan-in", "text": "Fan-out and fan-in" }, { "level": 2, "id": "aggregate-ordering", "text": "Aggregate ordering" }, { "level": 2, "id": "failure-boundaries", "text": "Failure boundaries" } ] }, { "path": "mechanisms/occurrence-identity.md", "title": "Definition, occurrence, and artifact identity", "description": "Stable identity across reuse, multiple destinations, renaming, editorial recovery, and component boundaries.", "section": "Mechanisms", "evidence": "Formal model and proposed portability contract", "url": "/mechanisms/occurrence-identity/", "html_file": "mechanisms/occurrence-identity/index.html", "markdown_url": "/markdown/mechanisms/occurrence-identity.md", "sha256": "152532f32a13bc31b89b48dce8063da87610d334fefc2024e981e3e79d9f3da9", "words": 513, "listed": true, "headings": [ { "level": 1, "id": "definition-occurrence-and-artifact-identity", "text": "Definition, occurrence, and artifact identity" }, { "level": 2, "id": "three-identities-three-responsibilities", "text": "Three identities, three responsibilities" }, { "level": 2, "id": "repeated-files-and-singleton-files", "text": "Repeated files and singleton files" }, { "level": 2, "id": "scope-ownership", "text": "Scope ownership" }, { "level": 2, "id": "editorial-identity", "text": "Editorial identity" }, { "level": 2, "id": "renames-and-migrations", "text": "Renames and migrations" }, { "level": 2, "id": "identity-is-not-merely-hashing", "text": "Identity is not merely hashing" }, { "level": 2, "id": "conformance-check", "text": "Conformance check" } ] }, { "path": "mechanisms/binding-stages.md", "title": "Binding stages and placeholder semantics", "description": "Ordered substitution, delayed values, token namespaces, staging hazards, and the distinction between simultaneous and sequential replacement.", "section": "Mechanisms", "evidence": "Formal model and source comparison", "url": "/mechanisms/binding-stages/", "html_file": "mechanisms/binding-stages/index.html", "markdown_url": "/markdown/mechanisms/binding-stages.md", "sha256": "88d2d4631896aa2d076f68984069a4e9014734e5d3c30e38b8b96d94cd80d49e", "words": 523, "listed": true, "headings": [ { "level": 1, "id": "binding-stages-and-placeholder-semantics", "text": "Binding stages and placeholder semantics" }, { "level": 2, "id": "a-placeholder-is-an-unresolved-obligation", "text": "A placeholder is an unresolved obligation" }, { "level": 2, "id": "ordering-is-semantic", "text": "Ordering is semantic" }, { "level": 2, "id": "two-replacement-semantics", "text": "Two replacement semantics" }, { "level": 2, "id": "presence-filtering-is-not-unresolved-token-validation", "text": "Presence filtering is not unresolved-token validation" }, { "level": 2, "id": "scoped-and-late-bindings", "text": "Scoped and late bindings" }, { "level": 2, "id": "escaping-and-capture", "text": "Escaping and capture" } ] }, { "path": "mechanisms/materialization.md", "title": "Artifact planning and materialization", "description": "From logical output identities to validated files, with cardinality, collision, staging, and publication contracts.", "section": "Mechanisms", "evidence": "Formal model and proposed implementation contract", "url": "/mechanisms/materialization/", "html_file": "mechanisms/materialization/index.html", "markdown_url": "/markdown/mechanisms/materialization.md", "sha256": "7341ee6712fd22657cf06e6de21ae8dbb466ffed185f7e6ed697f7a7fe191537", "words": 494, "listed": true, "headings": [ { "level": 1, "id": "artifact-planning-and-materialization", "text": "Artifact planning and materialization" }, { "level": 2, "id": "plan-before-declaring-success", "text": "Plan before declaring success" }, { "level": 2, "id": "skeletons-and-completed-artifacts", "text": "Skeletons and completed artifacts" }, { "level": 2, "id": "path-validity", "text": "Path validity" }, { "level": 2, "id": "publication-protocol", "text": "Publication protocol" }, { "level": 2, "id": "manifest", "text": "Manifest" }, { "level": 2, "id": "validation-layers", "text": "Validation layers" }, { "level": 2, "id": "lower-bound", "text": "Lower bound" } ] }, { "path": "mechanisms/round-trip.md", "title": "Round-trip editing and preservation laws", "description": "A partial bidirectional contract for preserving marked adaptations without claiming to invert arbitrary generated code.", "section": "Mechanisms", "evidence": "Formal model and deductions", "url": "/mechanisms/round-trip/", "html_file": "mechanisms/round-trip/index.html", "markdown_url": "/markdown/mechanisms/round-trip.md", "sha256": "bf37e1ec6484c11475fcf9d4c3820f5ce7c620a27fff50f191da1d075757c03f", "words": 568, "listed": true, "headings": [ { "level": 1, "id": "round-trip-editing-and-preservation-laws", "text": "Round-trip editing and preservation laws" }, { "level": 2, "id": "the-output-becomes-a-bounded-input", "text": "The output becomes a bounded input" }, { "level": 2, "id": "a-precise-domain", "text": "A precise domain" }, { "level": 2, "id": "proposition-7-extraction-after-rendering", "text": "Proposition 7 — extraction after rendering" }, { "level": 2, "id": "no-edit-stability", "text": "No-edit stability" }, { "level": 2, "id": "admissible-edit-conservation", "text": "Admissible edit conservation" }, { "level": 2, "id": "what-changes-when-the-generator-changes", "text": "What changes when the generator changes?" }, { "level": 2, "id": "relationship-to-bidirectional-transformations", "text": "Relationship to bidirectional transformations" } ] }, { "path": "mechanisms/reconciliation.md", "title": "Editorial reconciliation and conflicts", "description": "Stable regions, authority, three-way comparison, occurrence-local edits, shared-definition updates, and persistence boundaries.", "section": "Mechanisms", "evidence": "Formal model and proposed implementation contract", "url": "/mechanisms/reconciliation/", "html_file": "mechanisms/reconciliation/index.html", "markdown_url": "/markdown/mechanisms/reconciliation.md", "sha256": "b06789188afeebad9f489a2b57bd2da5026e605122f27889505a60308229a74b", "words": 526, "listed": true, "headings": [ { "level": 1, "id": "editorial-reconciliation-and-conflicts", "text": "Editorial reconciliation and conflicts" }, { "level": 2, "id": "extraction-is-not-yet-authorization-to-overwrite", "text": "Extraction is not yet authorization to overwrite" }, { "level": 2, "id": "three-way-comparison", "text": "Three-way comparison" }, { "level": 2, "id": "occurrence-local-versus-shared-edits", "text": "Occurrence-local versus shared edits" }, { "level": 2, "id": "identity-and-relocation", "text": "Identity and relocation" }, { "level": 2, "id": "persistence-protocol", "text": "Persistence protocol" }, { "level": 2, "id": "removed-and-malformed-regions", "text": "Removed and malformed regions" }, { "level": 2, "id": "research-significance", "text": "Research significance" } ] }, { "path": "mechanisms/dependency-invalidation.md", "title": "Dependency invalidation and incremental builds", "description": "How changed sources invalidate derived knowledge, and the conditions under which an incremental rebuild equals a clean rebuild.", "section": "Mechanisms", "evidence": "Proposed extension and formal deductions", "url": "/mechanisms/dependency-invalidation/", "html_file": "mechanisms/dependency-invalidation/index.html", "markdown_url": "/markdown/mechanisms/dependency-invalidation.md", "sha256": "2141d8cee6fdfaeb8567490baa7240487df3d734baa5bb26456e57d649183955", "words": 442, "listed": true, "headings": [ { "level": 1, "id": "dependency-invalidation-and-incremental-builds", "text": "Dependency invalidation and incremental builds" }, { "level": 2, "id": "reuse-across-epochs-is-a-stronger-claim", "text": "Reuse across epochs is a stronger claim" }, { "level": 2, "id": "dependency-graph", "text": "Dependency graph" }, { "level": 2, "id": "deletion-and-alternative-derivations", "text": "Deletion and alternative derivations" }, { "level": 2, "id": "proposition-8-incremental-equivalence", "text": "Proposition 8 — incremental equivalence" }, { "level": 2, "id": "granularity", "text": "Granularity" }, { "level": 2, "id": "relation-to-established-build-system-work", "text": "Relation to established build-system work" }, { "level": 2, "id": "jcb-boundary", "text": "JCB boundary" } ] }, { "path": "mechanisms/provenance-traces.md", "title": "Provenance and explanations", "description": "Explaining why a value exists, why it was reused, where it was emitted, and which human adaptation affected it.", "section": "Mechanisms", "evidence": "Proposed extension and formal model", "url": "/mechanisms/provenance-traces/", "html_file": "mechanisms/provenance-traces/index.html", "markdown_url": "/markdown/mechanisms/provenance-traces.md", "sha256": "2ca59db60a435a1b303db7757d2eb7a2a913d3c45c6a590855584d04bd2d1cd6", "words": 437, "listed": true, "headings": [ { "level": 1, "id": "provenance-and-explanations", "text": "Provenance and explanations" }, { "level": 2, "id": "recollection-should-be-explainable", "text": "Recollection should be explainable" }, { "level": 2, "id": "derivation-graph", "text": "Derivation graph" }, { "level": 2, "id": "different-questions-require-different-traces", "text": "Different questions require different traces" }, { "level": 2, "id": "provenance-is-not-truth", "text": "Provenance is not truth" }, { "level": 2, "id": "storage-tradeoffs", "text": "Storage tradeoffs" }, { "level": 2, "id": "privacy-and-trust", "text": "Privacy and trust" } ] }, { "path": "mechanisms/lifecycle.md", "title": "The two-loop lifecycle", "description": "Inner context completion and outer editorial persistence, with explicit epoch boundaries and distinct correctness laws.", "section": "Mechanisms", "evidence": "Formal model", "url": "/mechanisms/lifecycle/", "html_file": "mechanisms/lifecycle/index.html", "markdown_url": "/markdown/mechanisms/lifecycle.md", "sha256": "d55fe770ee79e63cbfb753e1e2f3ea96f5cd97bc1adf4856fe3bfa375acb52ba", "words": 459, "listed": true, "headings": [ { "level": 1, "id": "the-two-loop-lifecycle", "text": "The two-loop lifecycle" }, { "level": 2, "id": "the-inner-loop-completes-knowledge", "text": "The inner loop completes knowledge" }, { "level": 2, "id": "the-outer-loop-preserves-development", "text": "The outer loop preserves development" }, { "level": 2, "id": "epoch-equation", "text": "Epoch equation" }, { "level": 2, "id": "why-the-distinction-matters", "text": "Why the distinction matters" }, { "level": 2, "id": "a-practical-execution-policy", "text": "A practical execution policy" }, { "level": 2, "id": "beyond-files", "text": "Beyond files" } ] }, { "path": "mechanisms/self-generation.md", "title": "Self-generation and bootstrapping", "description": "Regenerating a generator's host system, with precise distinctions from self-hosting compilers, fixed points, and Turing completeness.", "section": "Mechanisms", "evidence": "Formal model and terminology comparison", "url": "/mechanisms/self-generation/", "html_file": "mechanisms/self-generation/index.html", "markdown_url": "/markdown/mechanisms/self-generation.md", "sha256": "8246ef6b8bad70d8a319b4dace5d1e168ecacfe32be4e770612d8151799101dc", "words": 496, "listed": true, "headings": [ { "level": 1, "id": "self-generation-and-bootstrapping", "text": "Self-generation and bootstrapping" }, { "level": 2, "id": "a-system-can-be-one-of-its-own-products", "text": "A system can be one of its own products" }, { "level": 2, "id": "a-testable-construction", "text": "A testable construction" }, { "level": 2, "id": "a-fixed-point-at-the-right-level", "text": "A fixed point at the right level" }, { "level": 2, "id": "what-self-generation-demonstrates", "text": "What self-generation demonstrates" }, { "level": 2, "id": "established-comparison", "text": "Established comparison" }, { "level": 2, "id": "evidence-boundary-in-this-paper", "text": "Evidence boundary in this paper" } ] }, { "path": "jcb/overview.md", "title": "JCB as the originating case study", "description": "Mapping a production generator to VDMT without making Joomla or PHP part of the theory's definition.", "section": "JCB Case Study", "evidence": "Source observations and architectural interpretation", "url": "/jcb/overview/", "html_file": "jcb/overview/index.html", "markdown_url": "/markdown/jcb/overview.md", "sha256": "6c264f82c74cdaef3cd344cc485b2b2ae911c8f9bdb53d69d41c16c8dd671f3c", "words": 465, "listed": true, "headings": [ { "level": 1, "id": "jcb-as-the-originating-case-study", "text": "JCB as the originating case study" }, { "level": 2, "id": "scope-of-the-case-study", "text": "Scope of the case study" }, { "level": 2, "id": "the-observed-architecture", "text": "The observed architecture" }, { "level": 2, "id": "mapping-to-the-abstract-framework", "text": "Mapping to the abstract framework" }, { "level": 2, "id": "what-the-implementation-teaches", "text": "What the implementation teaches" } ] }, { "path": "jcb/source-map.md", "title": "Pinned source map", "description": "Exact source paths, inspected methods, and the narrow claims each supports.", "section": "JCB Case Study", "evidence": "Source observations", "url": "/jcb/source-map/", "html_file": "jcb/source-map/index.html", "markdown_url": "/markdown/jcb/source-map.md", "sha256": "abd77594bd3b403404a94119ec8ff496ba7517ca65b85f321fce7284ebc2787d", "words": 552, "listed": true, "headings": [ { "level": 1, "id": "pinned-source-map", "text": "Pinned source map" }, { "level": 2, "id": "revisions-and-path-convention", "text": "Revisions and path convention" }, { "level": 2, "id": "inspection-ledger", "text": "Inspection ledger" }, { "level": 2, "id": "reproduction-procedure", "text": "Reproduction procedure" }, { "level": 2, "id": "negative-evidence", "text": "Negative evidence" } ] }, { "path": "jcb/initialization.md", "title": "Initialization and phase ordering", "description": "Why constructor work, custom-code extraction, component building, and skeleton creation belong in the runtime account.", "section": "JCB Case Study", "evidence": "Source observations", "url": "/jcb/initialization/", "html_file": "jcb/initialization/index.html", "markdown_url": "/markdown/jcb/initialization.md", "sha256": "ce87724c97c1e2a773fb3e5faec314b378c0aecd1f1987e348514e0251b35614", "words": 467, "listed": true, "headings": [ { "level": 1, "id": "initialization-and-phase-ordering", "text": "Initialization and phase ordering" }, { "level": 2, "id": "compilation-begins-before-run", "text": "Compilation begins before run()" }, { "level": 2, "id": "the-initializer-s-visible-order", "text": "The initializer's visible order" }, { "level": 2, "id": "initialization-is-not-read-only", "text": "Initialization is not read-only" }, { "level": 2, "id": "skeleton-creation", "text": "Skeleton creation" }, { "level": 2, "id": "relation-to-the-inner-and-outer-loops", "text": "Relation to the inner and outer loops" }, { "level": 2, "id": "review-implications", "text": "Review implications" } ] }, { "path": "jcb/database-loading.md", "title": "Database loading and nested enrichment", "description": "Root queries, relationship metadata, field-type joins, indexed reuse, and context-dependent retrieval.", "section": "JCB Case Study", "evidence": "Source observations", "url": "/jcb/database-loading/", "html_file": "jcb/database-loading/index.html", "markdown_url": "/markdown/jcb/database-loading.md", "sha256": "3a00c331d592da08825330df49ffd75c558f9109e00ee9e53b35a5708aea90e2", "words": 462, "listed": true, "headings": [ { "level": 1, "id": "database-loading-and-nested-enrichment", "text": "Database loading and nested enrichment" }, { "level": 2, "id": "root-acquisition-is-only-the-beginning", "text": "Root acquisition is only the beginning" }, { "level": 2, "id": "relationship-metadata-matters", "text": "Relationship metadata matters" }, { "level": 2, "id": "fields-and-field-types", "text": "Fields and field types" }, { "level": 2, "id": "fallback-acquisition", "text": "Fallback acquisition" }, { "level": 2, "id": "architectural-consequence", "text": "Architectural consequence" } ] }, { "path": "jcb/builders.md", "title": "Builder registries and content environments", "description": "Specialized memory roles, shared bindings, view-scoped bindings, and the conversion from semantic data to output fragments.", "section": "JCB Case Study", "evidence": "Source observations and interpretation", "url": "/jcb/builders/", "html_file": "jcb/builders/index.html", "markdown_url": "/markdown/jcb/builders.md", "sha256": "ad25591dc216625664ce5c02cac7dc58397bd9c959abaff6a393b90ad4893f3e", "words": 418, "listed": true, "headings": [ { "level": 1, "id": "builder-registries-and-content-environments", "text": "Builder registries and content environments" }, { "level": 2, "id": "specialized-stores-encode-intent", "text": "Specialized stores encode intent" }, { "level": 2, "id": "contentone", "text": "ContentOne" }, { "level": 2, "id": "contentmulti", "text": "ContentMulti" }, { "level": 2, "id": "infusion", "text": "Infusion" }, { "level": 2, "id": "what-the-source-does-not-prove", "text": "What the source does not prove" } ] }, { "path": "jcb/placeholders.md", "title": "JCB placeholder behavior", "description": "Actual replacement modes, shared and local environments, marker families, and why replacement is not a general fixed-point solver.", "section": "JCB Case Study", "evidence": "Source observations", "url": "/jcb/placeholders/", "html_file": "jcb/placeholders/index.html", "markdown_url": "/markdown/jcb/placeholders.md", "sha256": "cc4cc57a1106cf8ce3e9ba4d0bad4a2424c7e484be29dbc8fada8cb9be73fa91", "words": 432, "listed": true, "headings": [ { "level": 1, "id": "jcb-placeholder-behavior", "text": "JCB placeholder behavior" }, { "level": 2, "id": "a-family-of-mechanisms", "text": "A family of mechanisms" }, { "level": 2, "id": "three-action-modes", "text": "Three action modes" }, { "level": 2, "id": "replacement-order", "text": "Replacement order" }, { "level": 2, "id": "tracking-markers", "text": "Tracking markers" }, { "level": 2, "id": "portability-lesson", "text": "Portability lesson" } ] }, { "path": "jcb/file-emission.md", "title": "File updates and final emission", "description": "The concrete shared-to-local binding order, late dependency injection, custom-code handling, and packaging boundary.", "section": "JCB Case Study", "evidence": "Source observations", "url": "/jcb/file-emission/", "html_file": "jcb/file-emission/index.html", "markdown_url": "/markdown/jcb/file-emission.md", "sha256": "165f17815c392f0e6532ef5bbf55051b796e1ccbc9a6ea6a3844c288a1268234", "words": 449, "listed": true, "headings": [ { "level": 1, "id": "file-updates-and-final-emission", "text": "File updates and final emission" }, { "level": 2, "id": "the-updater-coordinates-several-artifact-families", "text": "The updater coordinates several artifact families" }, { "level": 2, "id": "view-scoped-fan-out", "text": "View-scoped fan-out" }, { "level": 2, "id": "concrete-binding-sequence", "text": "Concrete binding sequence" }, { "level": 2, "id": "additional-finalization", "text": "Additional finalization" }, { "level": 2, "id": "counting-and-reproducibility", "text": "Counting and reproducibility" } ] }, { "path": "jcb/editorial-recovery.md", "title": "Recovery of marked editorial changes", "description": "Installed-file scanning, marker recognition, GUI recovery, reverse transformation, location fingerprints, and persistent reinsertion.", "section": "JCB Case Study", "evidence": "Source observations and author testimony", "url": "/jcb/editorial-recovery/", "html_file": "jcb/editorial-recovery/index.html", "markdown_url": "/markdown/jcb/editorial-recovery.md", "sha256": "a1c29f02fa44f41e319a556b96d30af010a94392393946a83e1fa88874520811", "words": 494, "listed": true, "headings": [ { "level": 1, "id": "recovery-of-marked-editorial-changes", "text": "Recovery of marked editorial changes" }, { "level": 2, "id": "the-omitted-feedback-path", "text": "The omitted feedback path" }, { "level": 2, "id": "what-is-scanned", "text": "What is scanned" }, { "level": 2, "id": "recognition-and-capture", "text": "Recognition and capture" }, { "level": 2, "id": "location-memory", "text": "Location memory" }, { "level": 2, "id": "reinsertion-and-persistence", "text": "Reinsertion and persistence" }, { "level": 2, "id": "generalization", "text": "Generalization" } ] }, { "path": "jcb/historical-implementation.md", "title": "The public compiler of January 2016", "description": "What the root source actually demonstrates, and what cannot be backdated from modern class names or features.", "section": "JCB Case Study", "evidence": "Historical source observations", "url": "/jcb/historical-implementation/", "html_file": "jcb/historical-implementation/index.html", "markdown_url": "/markdown/jcb/historical-implementation.md", "sha256": "395bee3bfab151340a50b960e80d1129351aa0e50b2cdd0161d6f17e3dd9538b", "words": 438, "listed": true, "headings": [ { "level": 1, "id": "the-public-compiler-of-january-2016", "text": "The public compiler of January 2016" }, { "level": 2, "id": "the-primary-artifact", "text": "The primary artifact" }, { "level": 2, "id": "dedicated-intermediate-memory", "text": "Dedicated intermediate memory" }, { "level": 2, "id": "staged-execution", "text": "Staged execution" }, { "level": 2, "id": "what-can-be-dated", "text": "What can be dated" }, { "level": 2, "id": "what-remains-undated-in-this-inspection", "text": "What remains undated in this inspection" }, { "level": 2, "id": "historical-interpretation", "text": "Historical interpretation" } ] }, { "path": "jcb/self-build.md", "title": "JCB generating JCB", "description": "Evidence for self-generation, the precise scope of the claim, and a reproducible multi-stage self-build protocol.", "section": "JCB Case Study", "evidence": "Project documentation and author testimony", "url": "/jcb/self-build/", "html_file": "jcb/self-build/index.html", "markdown_url": "/markdown/jcb/self-build.md", "sha256": "ea417bc60eff116fa071235a09bd4a57f472ac1aae3dedc926d68b4fa462f1cf", "words": 395, "listed": true, "headings": [ { "level": 1, "id": "jcb-generating-jcb", "text": "JCB generating JCB" }, { "level": 2, "id": "the-reported-capability", "text": "The reported capability" }, { "level": 2, "id": "correct-terminology", "text": "Correct terminology" }, { "level": 2, "id": "evidence-not-supplied-by-a-readme", "text": "Evidence not supplied by a README" }, { "level": 2, "id": "proposed-certificate", "text": "Proposed certificate" }, { "level": 2, "id": "trust-and-expressiveness", "text": "Trust and expressiveness" } ] }, { "path": "jcb/runtime-boundaries.md", "title": "Runtime boundaries and nonclaims", "description": "Where the abstract proofs apply, where production behavior is richer, and what evidence would close the gap.", "section": "JCB Case Study", "evidence": "Source observations and methodological limits", "url": "/jcb/runtime-boundaries/", "html_file": "jcb/runtime-boundaries/index.html", "markdown_url": "/markdown/jcb/runtime-boundaries.md", "sha256": "b3e8b7e6792191593a1cb6534fa5671bb5e0eccffb66a8845c2bc2dc7fecdfda", "words": 454, "listed": true, "headings": [ { "level": 1, "id": "runtime-boundaries-and-nonclaims", "text": "Runtime boundaries and nonclaims" }, { "level": 2, "id": "a-formal-abstraction-is-not-an-automatic-certificate", "text": "A formal abstraction is not an automatic certificate" }, { "level": 2, "id": "specific-boundaries", "text": "Specific boundaries" }, { "level": 2, "id": "what-a-stronger-audit-should-record", "text": "What a stronger audit should record" }, { "level": 2, "id": "why-these-limits-strengthen-the-theory", "text": "Why these limits strengthen the theory" } ] }, { "path": "engineering/implementation-guide.md", "title": "Language-independent implementation guide", "description": "A practical architecture for implementing VDMT contracts in another language or domain without copying JCB's class layout.", "section": "Engineering", "evidence": "Proposed implementation contract", "url": "/engineering/implementation-guide/", "html_file": "engineering/implementation-guide/index.html", "markdown_url": "/markdown/engineering/implementation-guide.md", "sha256": "b769cbecc1d14b71e5881244b9438b47a25b58bd5df76a572a940eef01fe6495", "words": 545, "listed": true, "headings": [ { "level": 1, "id": "language-independent-implementation-guide", "text": "Language-independent implementation guide" }, { "level": 2, "id": "begin-with-the-semantic-boundary", "text": "Begin with the semantic boundary" }, { "level": 2, "id": "separate-the-contracts", "text": "Separate the contracts" }, { "level": 2, "id": "an-implementation-sequence", "text": "An implementation sequence" }, { "level": 2, "id": "representation-choices", "text": "Representation choices" }, { "level": 2, "id": "pseudocode", "text": "Pseudocode" }, { "level": 2, "id": "adopting-only-part-of-the-framework", "text": "Adopting only part of the framework" } ] }, { "path": "engineering/reference-model.md", "title": "Executable reference model", "description": "The deliberately bounded Python model, its supported laws, its example, and its differences from JCB.", "section": "Engineering", "evidence": "Original reference implementation", "url": "/engineering/reference-model/", "html_file": "engineering/reference-model/index.html", "markdown_url": "/markdown/engineering/reference-model.md", "sha256": "77a9a098c257b51d1da22d5448b6743da8816a8d5f12e0a62168bff34190604c", "words": 501, "listed": true, "headings": [ { "level": 1, "id": "executable-reference-model", "text": "Executable reference model" }, { "level": 2, "id": "purpose-and-scope", "text": "Purpose and scope" }, { "level": 2, "id": "supported-operations", "text": "Supported operations" }, { "level": 2, "id": "run-the-example", "text": "Run the example" }, { "level": 2, "id": "relationship-to-the-mathematics", "text": "Relationship to the mathematics" }, { "level": 2, "id": "deliberate-omissions", "text": "Deliberate omissions" } ] }, { "path": "engineering/testing.md", "title": "Validation and conformance testing", "description": "Behavioral boundaries, property checks, adversarial cases, source audits, and the separation between tests and proofs.", "section": "Engineering", "evidence": "Test methodology", "url": "/engineering/testing/", "html_file": "engineering/testing/index.html", "markdown_url": "/markdown/engineering/testing.md", "sha256": "0a32d1d9e781102bca412001d6b3f8e3b1a7311dc37b05451e8cafe2f3f67a9d", "words": 474, "listed": true, "headings": [ { "level": 1, "id": "validation-and-conformance-testing", "text": "Validation and conformance testing" }, { "level": 2, "id": "test-contracts-not-anecdotes", "text": "Test contracts, not anecdotes" }, { "level": 2, "id": "core-synthesis-checks", "text": "Core synthesis checks" }, { "level": 2, "id": "binding-and-artifact-checks", "text": "Binding and artifact checks" }, { "level": 2, "id": "editorial-checks", "text": "Editorial checks" }, { "level": 2, "id": "whole-system-checks", "text": "Whole-system checks" }, { "level": 2, "id": "publication-checks", "text": "Publication checks" }, { "level": 2, "id": "reporting-a-result", "text": "Reporting a result" } ] }, { "path": "engineering/security.md", "title": "Security and trust boundaries", "description": "Source authority, code-generation trust, marker injection, path safety, dependency integrity, and safe publication.", "section": "Engineering", "evidence": "Proposed implementation contract", "url": "/engineering/security/", "html_file": "engineering/security/index.html", "markdown_url": "/markdown/engineering/security.md", "sha256": "15f32dbe159fdbc0413519e68d61531e57fe70c53b587c6bc200a580c8971015", "words": 488, "listed": true, "headings": [ { "level": 1, "id": "security-and-trust-boundaries", "text": "Security and trust boundaries" }, { "level": 2, "id": "generated-does-not-mean-trusted", "text": "Generated does not mean trusted" }, { "level": 2, "id": "context-and-ownership", "text": "Context and ownership" }, { "level": 2, "id": "editorial-marker-attacks", "text": "Editorial marker attacks" }, { "level": 2, "id": "filesystem-safety", "text": "Filesystem safety" }, { "level": 2, "id": "acquisition-and-supply-chain", "text": "Acquisition and supply chain" }, { "level": 2, "id": "resource-bounds", "text": "Resource bounds" }, { "level": 2, "id": "publication-and-recovery", "text": "Publication and recovery" } ] }, { "path": "engineering/concurrency.md", "title": "Concurrency and parallelization", "description": "Which operations can commute, where mutable context blocks parallelism, and how to preserve deterministic output order.", "section": "Engineering", "evidence": "Formal deductions and proposed implementation contract", "url": "/engineering/concurrency/", "html_file": "engineering/concurrency/index.html", "markdown_url": "/markdown/engineering/concurrency.md", "sha256": "1ecaf5d3b87eeee9987d4958f9daf949fac983f343aa3f9711bab468cbd9aeec", "words": 452, "listed": true, "headings": [ { "level": 1, "id": "concurrency-and-parallelization", "text": "Concurrency and parallelization" }, { "level": 2, "id": "parallelism-follows-dependencies-not-class-boundaries", "text": "Parallelism follows dependencies, not class boundaries" }, { "level": 2, "id": "safe-opportunities", "text": "Safe opportunities" }, { "level": 2, "id": "ordered-output", "text": "Ordered output" }, { "level": 2, "id": "jcb-specific-caution", "text": "JCB-specific caution" }, { "level": 2, "id": "phase-barriers", "text": "Phase barriers" }, { "level": 2, "id": "measurement", "text": "Measurement" } ] }, { "path": "engineering/performance.md", "title": "Cost model and performance hypotheses", "description": "Acquisition, derivation, binding, output size, live memory, reuse thresholds, and why no universal optimum follows from the architecture.", "section": "Engineering", "evidence": "Analytical model and empirical hypotheses", "url": "/engineering/performance/", "html_file": "engineering/performance/index.html", "markdown_url": "/markdown/engineering/performance.md", "sha256": "3e4ff8ab4cf4532f6872a5b0cfea38920b02b4958cdb99fc842666cc6958e5f5", "words": 509, "listed": true, "headings": [ { "level": 1, "id": "cost-model-and-performance-hypotheses", "text": "Cost model and performance hypotheses" }, { "level": 2, "id": "decompose-the-cost", "text": "Decompose the cost" }, { "level": 2, "id": "where-reuse-can-help", "text": "Where reuse can help" }, { "level": 2, "id": "binding-complexity", "text": "Binding complexity" }, { "level": 2, "id": "memory-cost", "text": "Memory cost" }, { "level": 2, "id": "expansion-is-not-compression-alone", "text": "Expansion is not compression alone" }, { "level": 2, "id": "what-optimal-would-require", "text": "What “optimal” would require" } ] }, { "path": "engineering/benchmarks.md", "title": "Benchmark protocol and reported scale", "description": "Preserving the author's performance report while specifying a reproducible, controlled evaluation.", "section": "Engineering", "evidence": "Author report and experimental protocol", "url": "/engineering/benchmarks/", "html_file": "engineering/benchmarks/index.html", "markdown_url": "/markdown/engineering/benchmarks.md", "sha256": "bbe76aa7ca74a1ac57a482729dbd275e9994cd7776411276fa93aa95507044e3", "words": 492, "listed": true, "headings": [ { "level": 1, "id": "benchmark-protocol-and-reported-scale", "text": "Benchmark protocol and reported scale" }, { "level": 2, "id": "the-reported-observation", "text": "The reported observation" }, { "level": 2, "id": "define-the-measurement-boundary", "text": "Define the measurement boundary" }, { "level": 2, "id": "reproducible-procedure", "text": "Reproducible procedure" }, { "level": 2, "id": "comparators-and-ablations", "text": "Comparators and ablations" }, { "level": 2, "id": "scaling-dimensions", "text": "Scaling dimensions" }, { "level": 2, "id": "publication-of-results", "text": "Publication of results" } ] }, { "path": "engineering/portability.md", "title": "Portability and conformance profiles", "description": "Reimplementing the method across languages and storage systems while retaining explicit semantic obligations.", "section": "Engineering", "evidence": "Proposed conformance framework", "url": "/engineering/portability/", "html_file": "engineering/portability/index.html", "markdown_url": "/markdown/engineering/portability.md", "sha256": "0bc0fe62f7c6f9b22b964acb51a192682863509c84d89d8d354c5a9d026dc2a5", "words": 450, "listed": true, "headings": [ { "level": 1, "id": "portability-and-conformance-profiles", "text": "Portability and conformance profiles" }, { "level": 2, "id": "port-the-contracts-not-the-incidental-syntax", "text": "Port the contracts, not the incidental syntax" }, { "level": 2, "id": "core-profile-checklist", "text": "Core profile checklist" }, { "level": 2, "id": "round-trip-profile-checklist", "text": "Round-trip profile checklist" }, { "level": 2, "id": "incremental-profile-checklist", "text": "Incremental profile checklist" }, { "level": 2, "id": "self-generative-profile-checklist", "text": "Self-generative profile checklist" }, { "level": 2, "id": "a-conformance-statement", "text": "A conformance statement" }, { "level": 2, "id": "extension-discipline", "text": "Extension discipline" } ] }, { "path": "applications/code-generation.md", "title": "Application to code generation", "description": "Reusing domain definitions across target languages while preserving context, typed bindings, and admitted custom behavior.", "section": "Applications", "evidence": "Proposed application", "url": "/applications/code-generation/", "html_file": "applications/code-generation/index.html", "markdown_url": "/markdown/applications/code-generation.md", "sha256": "cb00d863997689d11ba0a280c8644b58dc3dadbf22f9b13c2b7cbd7ebf23db57", "words": 447, "listed": true, "headings": [ { "level": 1, "id": "application-to-code-generation", "text": "Application to code generation" }, { "level": 2, "id": "a-language-independent-compiler-plan", "text": "A language-independent compiler plan" }, { "level": 2, "id": "definitions-and-occurrences", "text": "Definitions and occurrences" }, { "level": 2, "id": "staged-representations", "text": "Staged representations" }, { "level": 2, "id": "preserving-developer-adaptations", "text": "Preserving developer adaptations" }, { "level": 2, "id": "verification", "text": "Verification" } ] }, { "path": "applications/documents.md", "title": "Application to document synthesis", "description": "Structured evidence, reusable sections, occurrence-specific interpretation, and controlled editorial feedback in reports and publications.", "section": "Applications", "evidence": "Proposed application", "url": "/applications/documents/", "html_file": "applications/documents/index.html", "markdown_url": "/markdown/applications/documents.md", "sha256": "64be553229b3f27b7d2dc9a73d748c516197a445ed62cce36f9005ca33a0a53c", "words": 418, "listed": true, "headings": [ { "level": 1, "id": "application-to-document-synthesis", "text": "Application to document synthesis" }, { "level": 2, "id": "treat-claims-as-structured-inputs", "text": "Treat claims as structured inputs" }, { "level": 2, "id": "context-sensitive-reuse", "text": "Context-sensitive reuse" }, { "level": 2, "id": "a-bounded-editorial-loop", "text": "A bounded editorial loop" }, { "level": 2, "id": "multiple-publication-formats", "text": "Multiple publication formats" }, { "level": 2, "id": "evaluation", "text": "Evaluation" } ] }, { "path": "applications/configuration.md", "title": "Application to configuration synthesis", "description": "Deriving coherent deployment artifacts from shared requirements without confusing generated configuration with live operational state.", "section": "Applications", "evidence": "Proposed application", "url": "/applications/configuration/", "html_file": "applications/configuration/index.html", "markdown_url": "/markdown/applications/configuration.md", "sha256": "42bc45e16edb63867d5a3180f150031527a3a5eb2ef2f489af4f1a0e05748e4a", "words": 381, "listed": true, "headings": [ { "level": 1, "id": "application-to-configuration-synthesis", "text": "Application to configuration synthesis" }, { "level": 2, "id": "shared-requirements-different-destinations", "text": "Shared requirements, different destinations" }, { "level": 2, "id": "environment-is-part-of-meaning", "text": "Environment is part of meaning" }, { "level": 2, "id": "planning-before-activation", "text": "Planning before activation" }, { "level": 2, "id": "persistent-local-adaptations", "text": "Persistent local adaptations" }, { "level": 2, "id": "verification-and-limits", "text": "Verification and limits" } ] }, { "path": "applications/ai-memory.md", "title": "Application to AI context and memory", "description": "Scoped external memory, iterative retrieval, attributed interpretations, and authorized corrections.", "section": "Applications", "evidence": "Proposed application and empirical hypotheses", "url": "/applications/ai-memory/", "html_file": "applications/ai-memory/index.html", "markdown_url": "/markdown/applications/ai-memory.md", "sha256": "a548a7a610b43325ebb06ee8fe581d80eda1097051760671d0694f432762c4c6", "words": 470, "listed": true, "headings": [ { "level": 1, "id": "application-to-ai-context-and-memory", "text": "Application to AI context and memory" }, { "level": 2, "id": "a-structured-memory-layer-not-a-claim-about-model-internals", "text": "A structured memory layer, not a claim about model internals" }, { "level": 2, "id": "separate-evidence-from-generated-interpretation", "text": "Separate evidence from generated interpretation" }, { "level": 2, "id": "bounded-iterative-retrieval", "text": "Bounded iterative retrieval" }, { "level": 2, "id": "derived-comprehension-blocks", "text": "Derived comprehension blocks" }, { "level": 2, "id": "human-feedback", "text": "Human feedback" }, { "level": 2, "id": "evaluation", "text": "Evaluation" } ] }, { "path": "research/cognition.md", "title": "Recollection and cognitive correspondences", "description": "A disciplined account of the human-memory analogy and the evidence needed to turn resemblance into a scientific model.", "section": "Research", "evidence": "Interpretive analogy and empirical hypotheses", "url": "/research/cognition/", "html_file": "research/cognition/index.html", "markdown_url": "/markdown/research/cognition.md", "sha256": "4a09822eba59cccbc6bd431855ce67b6fdcb20a9f1728ecb41ec8b5f8bee5485", "words": 515, "listed": true, "headings": [ { "level": 1, "id": "recollection-and-cognitive-correspondences", "text": "Recollection and cognitive correspondences" }, { "level": 2, "id": "the-motivating-observation", "text": "The motivating observation" }, { "level": 2, "id": "operational-correspondences", "text": "Operational correspondences" }, { "level": 2, "id": "established-models-supply-stronger-commitments", "text": "Established models supply stronger commitments" }, { "level": 2, "id": "deterministic-recollection-is-a-restricted-model", "text": "Deterministic recollection is a restricted model" }, { "level": 2, "id": "what-would-constitute-evidence", "text": "What would constitute evidence?" }, { "level": 2, "id": "a-constructive-research-direction", "text": "A constructive research direction" } ] }, { "path": "research/hypotheses.md", "title": "Falsifiable hypotheses and experiments", "description": "Controlled tests of reuse, context isolation, editorial stability, incremental correctness, and memory orchestration.", "section": "Research", "evidence": "Experimental proposals", "url": "/research/hypotheses/", "html_file": "research/hypotheses/index.html", "markdown_url": "/markdown/research/hypotheses.md", "sha256": "143a6a700c9b5fc790bf734d18744826c877f79d45a7ca3c0551505e5c68dd80", "words": 523, "listed": true, "headings": [ { "level": 1, "id": "falsifiable-hypotheses-and-experiments", "text": "Falsifiable hypotheses and experiments" }, { "level": 2, "id": "h1-reuse-reduces-repeated-acquisition-on-high-fan-out-tasks", "text": "H1 — reuse reduces repeated acquisition on high-fan-out tasks" }, { "level": 2, "id": "h2-explicit-occurrence-context-reduces-cross-scope-errors", "text": "H2 — explicit occurrence context reduces cross-scope errors" }, { "level": 2, "id": "h3-admitted-edits-survive-regeneration-under-a-stable-region-contract", "text": "H3 — admitted edits survive regeneration under a stable region contract" }, { "level": 2, "id": "h4-complete-dependency-invalidation-matches-clean-rebuilding", "text": "H4 — complete dependency invalidation matches clean rebuilding" }, { "level": 2, "id": "h5-structured-external-memory-improves-bounded-ai-tasks", "text": "H5 — structured external memory improves bounded AI tasks" }, { "level": 2, "id": "h6-self-generation-is-stable-for-an-identified-model", "text": "H6 — self-generation is stable for an identified model" }, { "level": 2, "id": "optimality-is-a-separate-problem", "text": "Optimality is a separate problem" } ] }, { "path": "research/review-agenda.md", "title": "Review agenda and extension boundaries", "description": "The claims reviewers should challenge, the evidence still needed, and how the framework can grow without blurring its guarantees.", "section": "Research", "evidence": "Research agenda", "url": "/research/review-agenda/", "html_file": "research/review-agenda/index.html", "markdown_url": "/markdown/research/review-agenda.md", "sha256": "0b5d7347e24beb63bd5317a844ccb210f668a1eb150e22458b60dbf6b506bc99", "words": 470, "listed": true, "headings": [ { "level": 1, "id": "review-agenda-and-extension-boundaries", "text": "Review agenda and extension boundaries" }, { "level": 2, "id": "review-the-contribution-at-three-levels", "text": "Review the contribution at three levels" }, { "level": 2, "id": "formal-questions", "text": "Formal questions" }, { "level": 2, "id": "source-questions", "text": "Source questions" }, { "level": 2, "id": "empirical-questions", "text": "Empirical questions" }, { "level": 2, "id": "extension-policy", "text": "Extension policy" }, { "level": 2, "id": "scholarly-status", "text": "Scholarly status" } ] }, { "path": "reference/bibliography.md", "title": "Sources and bibliography", "description": "Pinned implementation evidence, scholarly precedents, official technical documentation, and licensing sources.", "section": "Reference", "evidence": "Source catalogue", "url": "/reference/bibliography/", "html_file": "reference/bibliography/index.html", "markdown_url": "/markdown/reference/bibliography.md", "sha256": "d3a923874a979c2e3033e67075184547eef45de70f349e1527f96a5d46386057", "words": 1805, "listed": true, "headings": [ { "level": 1, "id": "sources-and-bibliography", "text": "Sources and bibliography" }, { "level": 2, "id": "how-to-use-these-references", "text": "How to use these references" }, { "level": 2, "id": "j01", "text": "J01" }, { "level": 2, "id": "j02", "text": "J02" }, { "level": 2, "id": "j03", "text": "J03" }, { "level": 2, "id": "j04", "text": "J04" }, { "level": 2, "id": "j05", "text": "J05" }, { "level": 2, "id": "j06", "text": "J06" }, { "level": 2, "id": "j07", "text": "J07" }, { "level": 2, "id": "j08", "text": "J08" }, { "level": 2, "id": "j09", "text": "J09" }, { "level": 2, "id": "j10", "text": "J10" }, { "level": 2, "id": "j11", "text": "J11" }, { "level": 2, "id": "j12", "text": "J12" }, { "level": 2, "id": "r01", "text": "R01" }, { "level": 2, "id": "r02", "text": "R02" }, { "level": 2, "id": "r03", "text": "R03" }, { "level": 2, "id": "r04", "text": "R04" }, { "level": 2, "id": "r05", "text": "R05" }, { "level": 2, "id": "r06", "text": "R06" }, { "level": 2, "id": "r07", "text": "R07" }, { "level": 2, "id": "r08", "text": "R08" }, { "level": 2, "id": "r09", "text": "R09" }, { "level": 2, "id": "r10", "text": "R10" }, { "level": 2, "id": "r11", "text": "R11" }, { "level": 2, "id": "r12", "text": "R12" }, { "level": 2, "id": "r13", "text": "R13" }, { "level": 2, "id": "r14", "text": "R14" }, { "level": 2, "id": "r16", "text": "R16" }, { "level": 2, "id": "r18", "text": "R18" }, { "level": 2, "id": "l01", "text": "L01" }, { "level": 2, "id": "l02", "text": "L02" }, { "level": 2, "id": "l03", "text": "L03" }, { "level": 2, "id": "citation-practice", "text": "Citation practice" } ] }, { "path": "reference/licensing.md", "title": "Licensing, ownership, and attribution", "description": "Why CC BY 4.0 fits a reusable scientific paper, what it requires, and what copyright cannot promise about a theory.", "section": "Reference", "evidence": "License selection and official legal guidance", "url": "/reference/licensing/", "html_file": "reference/licensing/index.html", "markdown_url": "/markdown/reference/licensing.md", "sha256": "4bcae00d0642f4e62c5ba79f2225924ef31a28a08793a5431e21ba6a51647142", "words": 517, "listed": true, "headings": [ { "level": 1, "id": "licensing-ownership-and-attribution", "text": "Licensing, ownership, and attribution" }, { "level": 2, "id": "selected-license", "text": "Selected license" }, { "level": 2, "id": "attribution", "text": "Attribution" }, { "level": 2, "id": "what-ownership-means-here", "text": "What ownership means here" }, { "level": 2, "id": "why-not-a-no-derivatives-or-noncommercial-restriction", "text": "Why not a no-derivatives or noncommercial restriction?" }, { "level": 2, "id": "code-and-upstream-material", "text": "Code and upstream material" }, { "level": 2, "id": "irrevocability-and-review", "text": "Irrevocability and review" } ] }, { "path": "reference/citation.md", "title": "How to cite and share the work", "description": "Edition-aware citations, source-specific references, raw Markdown URLs, and attribution for adaptations.", "section": "Reference", "evidence": "Publication guidance", "url": "/reference/citation/", "html_file": "reference/citation/index.html", "markdown_url": "/markdown/reference/citation.md", "sha256": "e090fae360796cb88d66da969e2641684c36dc8420945d6d68a2f712c6aa4c4a", "words": 411, "listed": true, "headings": [ { "level": 1, "id": "how-to-cite-and-share-the-work", "text": "How to cite and share the work" }, { "level": 2, "id": "suggested-citation", "text": "Suggested citation" }, { "level": 2, "id": "cite-the-object-being-discussed", "text": "Cite the object being discussed" }, { "level": 2, "id": "machine-readable-citation", "text": "Machine-readable citation" }, { "level": 2, "id": "sharing-one-article", "text": "Sharing one article" }, { "level": 2, "id": "sharing-the-whole-edition", "text": "Sharing the whole edition" }, { "level": 2, "id": "adaptations-and-quotations", "text": "Adaptations and quotations" } ] }, { "path": "reference/glossary.md", "title": "Glossary", "description": "Concise definitions of the architectural and mathematical terms used in the VDMT specification.", "section": "Reference", "evidence": "Definitions", "url": "/reference/glossary/", "html_file": "reference/glossary/index.html", "markdown_url": "/markdown/reference/glossary.md", "sha256": "2463e544c7cc23e3c8b9a377bbfd6291258de519e81d61f3cfdb7dfe4368f975", "words": 607, "listed": true, "headings": [ { "level": 1, "id": "glossary", "text": "Glossary" }, { "level": 2, "id": "artifact", "text": "Artifact" }, { "level": 2, "id": "binding", "text": "Binding" }, { "level": 2, "id": "closure", "text": "Closure" }, { "level": 2, "id": "confluence", "text": "Confluence" }, { "level": 2, "id": "context", "text": "Context" }, { "level": 2, "id": "definition", "text": "Definition" }, { "level": 2, "id": "derivation", "text": "Derivation" }, { "level": 2, "id": "determinism", "text": "Determinism" }, { "level": 2, "id": "editorial-memory", "text": "Editorial memory" }, { "level": 2, "id": "epoch", "text": "Epoch" }, { "level": 2, "id": "fixed-point", "text": "Fixed point" }, { "level": 2, "id": "inflationary", "text": "Inflationary" }, { "level": 2, "id": "intermediate-representation", "text": "Intermediate representation" }, { "level": 2, "id": "materialization", "text": "Materialization" }, { "level": 2, "id": "memoization", "text": "Memoization" }, { "level": 2, "id": "monotone", "text": "Monotone" }, { "level": 2, "id": "occurrence", "text": "Occurrence" }, { "level": 2, "id": "provenance", "text": "Provenance" }, { "level": 2, "id": "recollection", "text": "Recollection" }, { "level": 2, "id": "reconciliation", "text": "Reconciliation" }, { "level": 2, "id": "registry", "text": "Registry" }, { "level": 2, "id": "round-trip", "text": "Round trip" }, { "level": 2, "id": "self-generation", "text": "Self-generation" }, { "level": 2, "id": "stratum", "text": "Stratum" }, { "level": 2, "id": "vdmt", "text": "VDMT" } ] }, { "path": "reference/faq.md", "title": "Questions and answers", "description": "Direct answers about the theory's contribution, provenance, mathematical status, portability, licensing, and evidence.", "section": "Reference", "evidence": "Summary of the specification", "url": "/reference/faq/", "html_file": "reference/faq/index.html", "markdown_url": "/markdown/reference/faq.md", "sha256": "59de1f44e6d5f976c7776095be3bccde162816eec25b4d23f5b2f212733d7993", "words": 584, "listed": true, "headings": [ { "level": 1, "id": "questions-and-answers", "text": "Questions and answers" }, { "level": 2, "id": "is-vdmt-just-a-new-name-for-a-dictionary-or-template-engine", "text": "Is VDMT just a new name for a dictionary or template engine?" }, { "level": 2, "id": "is-it-one-algorithm", "text": "Is it one algorithm?" }, { "level": 2, "id": "why-call-it-a-theory-when-jcb-already-works", "text": "Why call it a theory when JCB already works?" }, { "level": 2, "id": "when-was-the-method-public", "text": "When was the method public?" }, { "level": 2, "id": "who-developed-it", "text": "Who developed it?" }, { "level": 2, "id": "must-an-implementation-use-php-or-joomla", "text": "Must an implementation use PHP or Joomla?" }, { "level": 2, "id": "are-the-registries-physically-moving-the-same-memory-around", "text": "Are the registries physically moving the same memory around?" }, { "level": 2, "id": "does-jcb-s-self-build-prove-turing-completeness", "text": "Does JCB's self-build prove Turing completeness?" }, { "level": 2, "id": "does-the-round-trip-preserve-every-edit", "text": "Does the round trip preserve every edit?" }, { "level": 2, "id": "is-the-million-line-performance-example-independently-verified-here", "text": "Is the million-line performance example independently verified here?" }, { "level": 2, "id": "is-this-the-optimal-human-memory-design", "text": "Is this the optimal human-memory design?" }, { "level": 2, "id": "can-others-implement-and-extend-it", "text": "Can others implement and extend it?" }, { "level": 2, "id": "where-is-the-markdown-for-a-page", "text": "Where is the Markdown for a page?" } ] }, { "path": "reference/publication.md", "title": "Publication, maintenance, and Markdown access", "description": "How this repository produces equivalent article pages and Markdown sources, validates them, and deploys to GitHub Pages.", "section": "Reference", "evidence": "Publication implementation contract", "url": "/reference/publication/", "html_file": "reference/publication/index.html", "markdown_url": "/markdown/reference/publication.md", "sha256": "5eb6edaffadae547f774b2e8e5d908d4bb45b3181f13352de17f6b55d5041eff", "words": 572, "listed": true, "headings": [ { "level": 1, "id": "publication-maintenance-and-markdown-access", "text": "Publication, maintenance, and Markdown access" }, { "level": 2, "id": "markdown-is-the-source-of-truth", "text": "Markdown is the source of truth" }, { "level": 2, "id": "reader-surfaces", "text": "Reader surfaces" }, { "level": 2, "id": "complete-and-machine-readable-editions", "text": "Complete and machine-readable editions" }, { "level": 2, "id": "local-build", "text": "Local build" }, { "level": 2, "id": "deployment", "text": "Deployment" }, { "level": 2, "id": "maintenance", "text": "Maintenance" } ] }, { "path": "404.md", "title": "Page not found", "description": "Return to the VDMT reading guide or search the publication for the intended article.", "section": "Reference", "evidence": "Publication navigation", "url": "/404.html", "html_file": "404.html", "markdown_url": "/markdown/404.md", "sha256": "3195d435c1cf0bfea59fa688bef37932bddd2aa97451aa4be5be9508c29e380f", "words": 68, "listed": false, "headings": [ { "level": 1, "id": "page-not-found", "text": "Page not found" } ] } ] }