01 / CORE
Active methodology
HUB_Optimus Core
Canonical v1 methodology, operational flow, scenarios, and meta-learning. Spanish is authoritative for v1; English is the parity target.
From source to reviewable draft
HUB_Optimus
Reality → Evidence → Inference → Narrative → Operational Signal
Turn a URL or source text into a structured, source-bound draft for human review—without presenting it as verified truth.
It supports better judgment. It is not an authority, a prediction engine, or a replacement for diplomacy.
- Source of truth
- GitHub
- Canonical v1 language
- Spanish
- Public layer
- Static site
- Analysis runtime
- Local / controlled
Observe → detect → decide → act.
Every implementation starts from a documented signal.
Human accountability remains mandatory.
The method
Separate before interpreting.
The five stages are an operating discipline. Each stage limits what the next stage is allowed to claim.
-
01
Reality
What is directly observed.
-
02
Evidence
What supports or contradicts a claim.
-
03
Inference
What follows cautiously from the evidence.
-
04
Narrative
What may amplify, simplify, or distort.
-
05
Operational Signal
What is operationally relevant for human review.
Repository-backed portfolio
What exists today.
Every surface carries a status and a direct evidence path. Implemented work is kept separate from prototypes, controlled local components, and RFC-only plans.
02 / SIMULATOR
Working deterministic prototype
Deterministic Scenario Simulator
Strict JSON-schema validation, seeded round execution, deterministic JSON output, frozen benchmarks, and structural drift diagnostics.
03 / SEMANTIC ENGINE
Early implementation
Contracts & CLI
Minimal claim, evidence, result, audit-log, and decision-trace contracts with a local CLI that validates and preserves structured case records. It does not evaluate or score claims.
04 / OPERATOR
Browser prototype
HUB_Optimus Operator
A local-first PWA for structured intake, editable case records, deterministic browser triage, human-controlled local learning candidates, readable sharing, JSON, and result rendering.
Operator's primary and Advanced / Audit JSON workflows are available in this language. Technical JSON keys, code, IDs and commands remain language-neutral and LTR. All interface translations still require qualified human linguistic review. Operator prepares a local, source-bound draft; it does not execute the Semantic Engine or verify source truth. Triage does not verify stated provenance.
05 / URL INTAKE
Implementation present · deployment unverified
Controlled URL intake
Repository code and tests define bounded URL retrieval. GitHub alone does not establish that a public endpoint is deployed or available. Retrieved text is not verified evidence.
06 / RESEARCH
Experimental tooling
Scenario & Narrative Research
Experimental scenario generation, mutation sweeps, boundary search, scenario telemetry, narrative consistency checks, and source-labelled research datasets.
07 / GOVERNANCE
Active · ratified protocol
Governance Intelligence
A versioned protocol for separating claim, evidence, inference, uncertainty, narrative amplification, and operational relevance under human accountability.
Official incubation space
HUB-Optimus Labs
Labs is part of the HUB_Optimus portfolio: a governed space for experiments before they are eligible for the Core or a product surface.
Open HUB-Optimus Labs
Repository checked on 28 July 2026
Repository exists · no released artifacts
The repository is official and currently empty. The site does not attribute unreleased engines, datasets, deployments, or security capabilities to it.
01
Experiments remain explicitly non-canonical.
02
Promotion requires evidence, tests, and a reviewed PR.
03
The Core remains authoritative.
Architecture & authority
One source of truth, explicit execution boundaries.
GitHub records the authoritative project state. The public site, local tools, and any future private deployments may use that state but cannot redefine it.
Layer
State
Authority
GitHub repository
Versioned / traceable
Project source of truth
Public portfolio
Static site on GitHub Pages
Presentation only
Operator PWA
Browser-local / controlled handoff
Draft · no decision authority
Controlled URL intake
Code and tests in repository
Retrieval only · deployment unverified
Semantic Engine CLI
Minimal local CLI
Draft constrained by technical contracts
Human review
Mandatory
Final accountability
Future work
Designed boundaries, not released capabilities.
These documents define constraints for possible future work. They do not prove that a product, deployment, post-quantum control plane, or enterprise service exists.
RFC / UI
HERMES
Future PWA interface boundary. Not implemented.
EN · source RFC / OPERATING MODELEnterprise
Proposed private operating boundary. No enterprise product or public service exists.
EN · source RFC / SECURITYPost-quantum control plane
RFC planning around standardized cryptographic primitives. No cryptographic implementation.
EN · source
Inspect the evidence
The repository outranks the presentation.
Review code, contracts, tests, issues, pull requests, releases, governance, security policy, and intellectual-property terms directly on GitHub.