Skip to content

Framework + runtime CLI para OCC/ILSC: un “compilador” operacional que ejecuta módulos reproducibles (inputs YAML/JSON) y emite veredictos PASS/FAIL con witnesses/certificados auditables. Incluye el compendio canónico en PDF y el CLI para correr demos mínimos (MRD) de forma determinista y trazable.

License

Notifications You must be signed in to change notification settings

MarcoAIsaac/OCC

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

57 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

OCC - Operational Consistency Compiler

English | Español

CI License: Apache-2.0 Python DOI arXiv: pending

OCC is a reproducible runtime with a stable CLI (occ) to execute MRD modules (YAML/JSON inputs) and emit PASS/FAIL/NO-EVAL verdicts with auditable reports.

Why OCC exists

In UV/BSM-heavy modeling workflows, physically meaningful claims can remain difficult to falsify because inaccessible assumptions can absorb failure signals. OCC provides an operational filter before experimental deployment:

  1. Is the claim evaluable in a declared operational domain \(\Omega_I\)?
  2. Does it satisfy unavoidable consistency constraints?
  3. Does it avoid UV reinjection as an escape route?

OCC does not replace experiment. It improves pre-experimental triage quality.

Start here

Quickstart

Fast path

make bootstrap
make smoke
make check

To run docs locally:

make docs-serve

To integrate compendiums automatically (EN + ES + audits):

make integrate-all

macOS / Linux

git clone https://github.com/MarcoAIsaac/OCC.git
cd OCC
python -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install -e ".[dev]"

occ --help
pytest -q

Windows (PowerShell)

git clone https://github.com/MarcoAIsaac/OCC.git
cd OCC
python -m venv .venv
.\.venv\Scripts\Activate.ps1
python -m pip install --upgrade pip
python -m pip install -e ".[dev]"

occ --help
pytest -q

Discoverability commands

occ quickstart
occ doctor
occ list
occ predict list
occ judge examples/claim_specs/minimal_pass.yaml
occ judge examples/claim_specs/nuclear_pass.yaml --profile nuclear

Desktop app (Windows)

Run desktop frontend:

occ-desktop

Desktop stores persistent local data in:

  • ~/.occ_desktop/settings.json
  • ~/.occ_desktop/occ_desktop.db (SQLite run history)

Built-in AI assistant (Assistant tab):

  • Providers: offline (deterministic OCC copilot) and OpenAI (official API).
  • API key source: OPENAI_API_KEY environment variable (recommended) or session-only key field.
  • Model is configurable (default: gpt-4.1-mini).
  • Optional runtime-context injection for OCC-aware troubleshooting.

Experiment Lab (new in 1.4.0):

  • Run claim matrices across profiles (core / nuclear) and detect verdict divergence.
  • Export auditable artifacts: lab_report.json, lab_results.csv, lab_profile_summary.csv, lab_verdict_matrix.md.
  • CLI: occ lab run --claims-dir examples/claim_specs --profiles core nuclear --out .occ_lab/latest

Download prebuilt Windows package:

If the direct installer link returns 404, open release 1.5.0 and wait for workflow Windows desktop release to finish uploading assets for that tag. This pipeline runs automatically on every push to main (rolling desktop-latest) and on version tags (for example 1.5.0 or v1.5.0). If needed, trigger the workflow manually and set release_tag (example 1.5.0 or desktop-latest) to refresh assets.

Windows checksum verification:

certutil -hashfile .\OCCDesktop-Setup-windows-x64.exe SHA256

Compare with the OCCDesktop-Setup-windows-x64.exe row in OCCDesktop-windows-x64.sha256.

From source without install entrypoint:

python -m occ.desktop

Build .exe on Windows (PowerShell):

.\scripts\build_windows_desktop.ps1

To reduce SmartScreen warnings in distributed binaries, configure repository secrets:

  • WINDOWS_CODESIGN_PFX_B64: base64-encoded .pfx certificate.
  • WINDOWS_CODESIGN_PFX_PASSWORD: password for the .pfx.

Without a trusted code-signing certificate (ideally EV), SmartScreen warnings cannot be fully eliminated for fresh binaries.

Mobile app (Android)

Android companion app (android/) includes:

  • Workbench tab (claim YAML + core/nuclear judge profiles)
  • Lab tab (profile matrix over sample claims with divergence summary)
  • Assistant tab (offline OCC guidance)
  • History tab (local Room database)

Required Android permissions:

  • INTERNET (optional online endpoints / links)
  • ACCESS_NETWORK_STATE (network availability checks)

Build locally:

cd android
./gradlew assembleRelease

Prerequisites: JDK 17 and Android SDK (ANDROID_HOME configured).

Generated APK:

  • android/app/build/outputs/apk/release/app-release.apk

Download prebuilt APK:

Release automation:

  • Workflow .github/workflows/android_release.yml publishes Android assets automatically on pushed version tags (1.5.0 or v1.5.0).

Maintenance helpers

python scripts/release_doctor.py --strict
python scripts/check_docs_i18n.py --strict
python scripts/ci_doctor.py --workflow CI --limit 12
python scripts/generate_release_notes.py

Guided claim-to-module pipeline:

python scripts/mrd_flow.py examples/claim_specs/minimal_pass.yaml --generate-module

Automatic module generation

If a claim does not map to an existing module, OCC can generate an extension module:

occ module auto examples/claim_specs/minimal_pass.yaml --create-prediction

Useful options:

  • --publish-prediction: append generated prediction to predictions/registry.yaml.
  • --no-research: disable web research.
  • --module-name mrd_auto_my_module: force module name.

Run standalone claim research:

occ research examples/claim_specs/minimal_pass.yaml --show 5

Documentation portal (EN/ES)

MkDocs site includes two languages with English default and browser-aware switch to Spanish when the reader's language is Spanish.

Local build:

python -m pip install -e ".[docs]"
mkdocs serve

Run a module

occ run ILSC_MRD_suite_15_modulos_CANON/mrd_4f_dict/inputs/mrd_4f_dict/pass.yaml --out out/
cat out/report.json

Typical output:

PASS

Full suite verification

occ verify

For long runs, prefer the manual full-suite workflow in GitHub Actions.

Domain expansions

v1.5.0 keeps the nuclear-domain lock set (j4_nuclear_guard, L4C*/L4E*) and adds Experiment Lab matrix workflows plus Windows desktop distribution via GitHub Releases (OCCDesktop-Setup-windows-x64.exe).

Repository layout

  • occ/ - runtime and CLI
  • ILSC_MRD_suite_15_modulos_CANON/ - canonical MRD suite (15 modules)
  • ILSC_MRD_suite_extensions/ - extension suite (tooling/meta-MRDs)
  • docs/ - documentation and canonical PDFs
  • tests/ - smoke and regression tests

License and citation

Publication notes

  • Zenodo DOI workflow and badge template: docs/RELEASING.md
  • arXiv preprint is recommended for discoverability

About

Framework + runtime CLI para OCC/ILSC: un “compilador” operacional que ejecuta módulos reproducibles (inputs YAML/JSON) y emite veredictos PASS/FAIL con witnesses/certificados auditables. Incluye el compendio canónico en PDF y el CLI para correr demos mínimos (MRD) de forma determinista y trazable.

Topics

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors