Independent researcher building the Unified Rigidity Framework (URF): a verification-first research program connecting rigidity, locality, entropy, formal proof surfaces, and executable status infrastructure across mathematics, computer science, and physics.

• Public front door: https://github.com/inaciovasquez2020/vasquez-index
• Core reference: https://github.com/inaciovasquez2020/urf-core
• Reference implementation: https://github.com/inaciovasquez2020/chronos-urf-rr
• Exposition: https://github.com/inaciovasquez2020/urf-textbook

URF is a repository-governed framework for separating verified structure, conditional reductions, executable certificates, and open frontiers.

URF is not presented as theorem-level closure of P vs NP, Yang--Mills, Poincare, Navier--Stokes, or any other major open problem unless a repository explicitly states and verifies that claim.

vasquez-index
   |
   +-- urf-core
   |      |
   |      +-- chronos-urf-rr
   |      +-- CorrRank
   |      +-- overlap-rigidity-lean-dev
   |
   +-- urf-textbook
   |
   +-- applications
   |      +-- biological-friction-framework
   |      +-- ym-os-quantization
   |      +-- poincare-new-derivation
   |
   +-- infrastructure
          +-- frontier-status-dashboard
          +-- non-clay-problem-closure-workspace

Build PASS means repository verification passed. It does not mean theorem-level closure unless the relevant repository explicitly states and verifies theorem-level closure.

• ORCID: https://orcid.org/0009-0008-8459-3400
• Research site: https://vasquezresearch.com
• Contact: inacio@vasquezresearch.com

Last updated: 2026-06-19

• This repository remains a documentation/profile README surface.
• It is a routing layer for public URF repositories, verification surfaces, and status boundaries.
• Profile text, repository maps, dashboards, badges, or build success do not independently establish theorem-level closure.

• vasquez-index: public front door for repository routing and public status indexing.
• urf-core: trusted definitions, schemas, certificate boundaries, Lean/Python verification artifacts, and bounded/frontier theorem surfaces.
• chronos-urf-rr: flagship executable URF/Chronos implementation with verified build and test surface.
• theorem-closure-classifier: bounded theorem-status classifier and external validation/replay ledger.
• urf-textbook: exposition and release-facing documentation layer.

• chronos-urf-rr: zero-visible-opaque-axiom conditional frontier status was reached in the H4.1 certified-family route; this does not claim unrestricted H4.1/FGL closure.
• theorem-closure-classifier: Iris-Lean external replay ladder and bounded closure proof-pattern reference are now part of the public classifier surface.
• urf-core: recent work continues to add bounded obligation, witness, dependency-certificate, and frontier-surface layers; these are proof-infrastructure advances, not final analytic closure.
• URC: container package publication surface exists for reproducible pull/run use; immutable digest/tag discipline remains part of the boundary.

• Public dashboard and profile surfaces record externally inspectable repositories only.
• Private/internal aggregate metadata is intentionally omitted from public profile status.
• No unrestricted H4.1/FGL closure is claimed.
• No UniversalFiberEntropyGap theorem is claimed.
• No Chronos-RR theorem closure is claimed.
• No Yang--Mills mass gap theorem is claimed.
• No gravity, cosmology, canonical quantization, P vs NP, or Clay-problem closure is claimed.

• Build PASS means the named repository verification passed under its stated scope.
• Conditional means the result depends on explicitly named assumptions or external theorem inputs.
• Open means the frontier object remains unresolved.
• Not claimed means executable evidence, dashboards, or profile text must not be promoted into theorem-level closure.

GitHub-visible public repository count: 19.

BOUNDARY := ¬ profile_repository_map_implies_theorem_level_closure