CI Status

Skeleton (lightweight checks only)

URF Core — Foundational Logic Layer

This repository defines the mathematical, logical, and certificate-semantic base of the URF program. All downstream executable, packaging, and environment layers derive their meaning from this layer.

---

Status (Canonical)

This repository reflects the current reduction status of the Unified Rigidity Framework spine.

• FO^k locality: Conditionally closed via Configuration Pumping.
• EF traps: Retired (non-canonical).
• Remaining obstruction: CCL (Cycle-Complexity Lemma) only.
• No new math introduced here. This repo records structure, boundaries, and dependencies.

Canonical alignment commits:

• FO^k locality closure: see final-wall-fo-k-locality
• Chronos / EntropyDepth boundary alignment: see Chronos-EntropyDepth

State: CONDITIONAL / FROZEN (pending CCL).

URF-ADMISSIBLE (v1.0)

URF-ADMISSIBLE is the frozen decision interface enforcing locality, capacity, and accounting. All URF claims must pass this gate or provide a certified NO witness.

• Spec: docs/foundations/urf_admissible_spec.md
• Schemas: admissible/schema/
• NO Benchmarks: admissible/no_benchmarks/

---

Purpose

To provide the canonical source of:

• URF axioms and invariant definitions
• Formal reduction theorems and obstruction statements
• Primitive certificate semantics (meaning and validity conditions)
• Formal proof-architecture entry points (Lean, LaTeX, logical certificates)

This repository is the semantic authority for URF correctness.

---

Layer Position

URF Layer Stack

Core → Prefab → Infrastructure → Applications

• Core defines truth conditions and invariant structure.
• Prefab freezes executable realizations of Core outputs.
• Infrastructure provides reproducible execution environments.
• Applications consume certified logic.

---

Canonical Scope

Structural laws governing admissible strategies are indexed in docs/foundations/structural_laws_index.md.

Mathematical Foundations

• Rigidity principles
• Capacity–locality constraints
• Admissibility and invariant structure
• EntropyDepth and Chronos structural reductions

Certificate Semantics

• Logical validity rules
• Certificate meaning definitions
• Structural admissibility interpretation
• Primitive schema semantics (not packaging format)

Proof Architecture

• Lean formalization entry points
• Reduction skeletons
• Conditional closure boundaries (explicitly labeled)

---

Structural Invariants

• Structural invariants and recurring constraints: docs/foundations/structural-laws.md

This reference records derived structural invariants that recur across URF components. These are not physical laws, but invariant constraints under explicit locality, capacity, and admissibility assumptions.

---

Explicit Non-Scope

This repository intentionally does not provide:

• CI packaging or pipeline orchestration
• Frozen prefab bundles
• Container or environment reproducibility layers
• End-user execution tooling
• Deployment workflows

These belong to the Prefab or Infrastructure layers.

---

Dependencies

• Semantic dependencies: None
• Mathematical dependencies: Standard mathematical foundations only

Downstream Consumers

• URF Prefab System https://github.com/inaciovasquez2020/urf-prefab-system

• Scientific Infrastructure https://github.com/inaciovasquez2020/scientific-infrastructure

---

Stability Model

Status: Canonical Foundational Layer

Change Rules:

• Mathematical meaning changes must originate here
• Downstream layers must not redefine certificate semantics
• Conditional components must remain explicitly labeled
• Versioning follows semantic mathematical compatibility

---

Formal Interfaces Exported

Core exports:

• Certificate semantic definitions
• Invariant and admissibility logic
• Formal theorem reference identifiers
• Lean formalization modules
• Logical validity boundary definitions

---

References

• Framework Overview https://inaciovasquez2020.github.io

• Project Index https://inaciovasquez2020.github.io/vasquez-index/

• Scientific Infrastructure Environment https://inaciovasquez2020.github.io/scientific-infrastructure/

• Research Website https://www.vasquezresearch.com

---

Relationship to Prefab Layer

Prefab Layer Responsibilities:

• Freeze executable schema realizations
• Provide deterministic verifiers
• Provide CI reproducible bundles
• Provide importable prefab logic modules

Core remains the semantic authority.

---

Citation

If you use URF foundational logic or reductions, cite:

@manual{Vasquez_URF_Core_2026,
  author = {Vasquez, Inacio F.},
  title  = {URF Core: Foundational Logic Layer for the Unified Rigidity Framework},
  year   = {2026},
  url    = {https://github.com/inaciovasquez2020/urf-core}
}

---

Quickstart (60 seconds)

./scripts/urf verify demo

URF applies only to post-hoc certification of asserted results. It is unnecessary for exploratory or provisional work and does not govern discovery, intuition, or consensus formation. It provides a voluntary, artifact-based mechanism to make consequential claims auditable.

• Chronos–EntropyDepth: https://github.com/inaciovasquez2020/Chronos-EntropyDepth

URFVIS (Released)

URFVIS is a frozen, tag-scoped certification primitive for visual and structural admissibility checks.

Current release:

• urfvis-v0.1 (tagged)

Scope:

• Defines a JSON schema for admissible inspection inputs
• Supports minisign-based verification of submitted artifacts
• Produces signed, reproducible certification inputs or explicit refusal

Non-scope:

• No execution, inference, or proof generation
• No dependency on Lean or global URF CI state
• No roadmap beyond tagged releases

Verification: Artifacts under certs/urfvis/** are self-contained and can be verified using the published public key.

URFVIS releases are immutable once tagged.

URFOPS (Defined)

URFOPS defines certified operation envelopes for assistant behavior.

Status:

• Defined
• Not released
• No execution authority

Scope:

• Declares allowed and forbidden actions
• Enforces capacity and constraint bounds
• Requires refusal on violation

Non-scope:

• No skills, agents, or workflows
• No automation or runtime behavior
• No release tag until externally required

URFOPS is a specification layer only.