UOR Foundation - Hologram Project #3

afflom · 2025-08-16T17:31:44Z

afflom
Aug 16, 2025
Maintainer

UOR-Foundation • Hologram Project Outline

Scope: The UOR Foundation develops and maintains all Hologram-related proofs, specifications, documentation, and tooling—The Hologram (concept, math, proofs) and Hologram (SDK, Dashboard, CLI, reference services). Third parties may consume this org as their upstream.

0) Naming & scope

The Hologram — the complete UOR Internet concept: formal substrate (12,288), invariants, proofs, protocols, conformance.
Hologram — open-source tooling & platform: Hologram SDK, Hologram Dashboard, Hologram CLI. (Also includes reference VPI service catalog and controllers/agents.)

1) Core foundations (math, specs, conformance)

`hologram-proofs` (Lean4)

Purpose: Formalize The Hologram (axioms → invariants → protocols). Drives conformance.

/UOR/Hologram/ Foundation.lean, Resonance.lean, Identifier.lean, Graph.lean, Transport.lean, CEF.lean, Hologram.lean, Proofs.lean, Examples.lean
/Contrib/ extraction stubs, algebra backends
/scripts/ CI proof checks, doc gen to HTML
CI: build, lints, compile, export docs; tag proofs as artifacts
Release: versioned proof snapshots; API/axiom changelog

`hologram-specs`

Purpose: Normative specifications and RFCs for The Hologram.

/specs/
- H-AXIOMS-1.0.0.md — Σ=256, torus 48×256, dual closures
- H-IDENTITY-1.0.0.md — addressing, UORID, SECDED guidance
- H-INTEGRITY-1.0.0.md — page/cycle checks, Merkle, R96
- H-METASCHEMA-0.1.0.md — self-describing schema & layout
- VPI/ — primitives & state machines (user, device, VPI, context, subnet, service, app, job, bundle, package, artifact, lease)
- Protocols/ — reference protocols over The Hologram
/rfcs/ number-consensus RFCs
/conformance/ cross-links to test vectors & suites
CI: spec linting, link validation, changelog gates
Release: spec bundles (zip), per-spec SemVer tags

`hologram-conformance`

Purpose: Canonical test vectors, suites, verifiers.

/vectors/ canonical-hologram-v1.bin (+ manifests: SHA-256, Merkle root, R96)
/suites/ page/cycle closure, serialization, Merkle, ID, protocol behavior
/verifiers/ cli libs (WASM + native) used by SDK/CLI/Dashboard
CI: run on all platforms, publish results as badges
Release: signed vector & suite releases; SBOMs

2) SDKs (multi-language)

A core IDL + per-language SDKs. Two routes:

Protocol/VPI route — expose The Hologram primitives (users, devices, VPI, contexts, subnets, services, apps, packages, artifacts, leases; invariants R96/Merkle; budgeted claims; transport; exchange format).
App route — higher-level app framework targeting VPIs.

Language-agnostic core

`hologram-sdk-idl`

/schema/ JSON/YAML/OpenAPI/Protobuf for VPI primitives & protocols
/codegen/ generators → TS/RS/Go/Java/C#/Swift/Python/CPP
/policy/ RL-96 semantics (spec → runtime mapping)

`hologram-sdk-core` (shared logic)

/lib/ UORID, R96, Merkle, serialization, protocol runtime kernel
/wasm/ portable verifiers for Dashboard & CLI

Per-language SDKs (duplicated structure across repos)

hologram-sdk-ts (TypeScript/Node + browser)
hologram-sdk-rs (Rust)
hologram-sdk-go (Go)
hologram-sdk-py (Python)
hologram-sdk-java (Java, Android artifacts optional)
hologram-sdk-csharp (.NET)
hologram-sdk-swift (Swift, iOS/macOS)
hologram-sdk-kotlin (Kotlin/JVM)
hologram-sdk-cpp (C++)

Each SDK repo:

/core/ bindings to hologram-sdk-core or generated code
/protocol/ define/compose protocols over The Hologram primitives
/vpi/ client to manage VPIs, contexts, devices, schedulers
/app/ high-level constructs (routes, bundles, deployment)
/examples/ minimal end-to-end samples
/tests/ conformance-driven tests (import from hologram-conformance)
CI: build, test, publish (npm, crates, PyPI, Maven, NuGet, SwiftPM, Go module, vcpkg)
Release: SemVer; release notes auto-generated from specs & proofs

3) Hologram CLI (multi-arch)

`hologram-cli`

Purpose: Manage VPIs, publish protocols, build/deploy apps, verify proofs. Leverages the user’s VPI.

/cmd/holo/ commands (vpi, device, context, subnet, service, app, bundle, package, artifact, protocol, attest, verify)
/runtime/ local agent comms, offline packager, verifier (WASM)
/plugins/ optional extensions (e.g., custom protocol generators)
Packaging targets:
- Linux x64/arm64 (deb, rpm, tar)
- macOS universal (pkg, Homebrew)
- Windows x64/arm64 (MSI, winget, scoop)
- Static musl tarballs for edge devices
CI: matrix build + notarization/signing + SBOM + supply-chain attestations (SLSA)
Release: versioned artifacts per platform; checksum manifest; completion scripts

4) Hologram Dashboard (GitHub Pages)

`hologram-dashboard`

Purpose: Web UI hosted via GitHub Pages that uses the user’s VPI directly (client-side API + WASM verifiers).

/app/ SPA (auth, orgs, VPIs, contexts, devices, services, apps, artifacts)
/verifier/ WASM bundle from hologram-conformance
/config/ VPI endpoint discovery (per-user config file + device auth flow)
/docs/ user/operator docs (see hologram-docs linkage)
GH Pages: main → gh-pages with Actions; no server required
Features:
- Device enrollment & attestation UI
- Context topology (subnets/services/apps)
- Deployments & rollouts
- Conservation/attestation dashboards (R96/Merkle)
- Audit trails (budgeted claims)

5) Reference services & agents

`hologram-vpi-controller`

Purpose: Control plane for VPI primitives (state machines, policy engine).

/api/ HTTP/WebSocket endpoints (IDL-generated)
/controller/ reconciliation loops (contexts, services, leases)
/policy/ RL-96 evaluation; budget windows
/storage/ UOR object store; artifact index

`hologram-device-agent`

Purpose: Runs on user devices; executes leases; performs attestation.

/agent/ scheduler shim, executor, sandboxing, heartbeat
/attest/ R96/Merkle/nonce protocol
/plugins/ device capability providers (GPU, storage)
Targets: Linux/macOS/Windows; minimal builds for embedded

`hologram-gateway` (optional)

Purpose: Coherent transport across networks (tunnels, NAT traversal) honoring The Hologram invariants.

6) Protocols & examples

`hologram-protocols`

Purpose: Reference protocols implemented over The Hologram primitives.

/echo/ minimal, attested round-trip
/streams/ windowed coherent transport
/kv/ budgeted key-value service

`hologram-examples`

Purpose: End-to-end samples (SDK + CLI + Dashboard + device agent).

/apps/ example Hologram Applications
/integration/ CI scenarios using canonical vectors

`hologram-templates`

Purpose: Starter templates per language and app type.

/protocol-ts/, /app-rs/, /app-go/, etc.

7) Documentation & website

`hologram-docs`

Purpose: Central docs (guides, tutorials, API references, RFC index).

/guides/ VPI concepts, device model, scheduling
/sdk/ per-language references (pulled from SDK repos)
/specs/ mirrors of normative specs (with version switcher)
/conformance/ how to run/verify vectors
Publish: to Pages or equivalent; linked from Dashboard

`uor-foundation-site` (optional)

Purpose: Foundation site with links to all Hologram resources

8) Shared infra & release engineering

`hologram-ci`

Purpose: Shared GitHub Actions workflows reused org-wide.

build matrices, code signing, SBOM, provenance, release orchestration, Pages deploys

`hologram-security`

Purpose: Threat models, audits, security advisories (private → public flow)

`hologram-roadmap`

Purpose: Public roadmap, milestones, project boards

`hologram-meta`

Purpose: Governance, contribution guide, CoC, triage playbooks

9) Versioning & compatibility

Specs & proofs: SemVer; breaking math/spec changes → major; proofs tagged and referenced by SDKs.
SDKs: SemVer per language; generated code pinned to spec/proof tags.
CLI & Dashboard: lockstep minor with SDK core; tolerate N-1 proofs/specs.
Conformance: every release must pass hologram-conformance on all targets.

10) Third-party upstream policy

Any consumer may pin to hologram-specs + hologram-proofs tags
SDKs are the preferred integration surface; forks encouraged to PR improvements
Conformance badges & SBOM/provenance published for all releases

11) Initial repo creation checklist

Create repos above with default branch protections
Add CODEOWNERS, SECURITY.md, LICENSE, CONTRIBUTING.md
Wire hologram-ci workflows; enable Pages for Dashboard/Docs
Seed canonical vector in hologram-conformance
Publish first language SDK (ts, then rs, then go)
Ship hologram-cli preview (macOS, Linux, Windows)
Publish Dashboard preview to Pages with device attestation demo

afflom · 2025-08-17T05:17:03Z

afflom
Aug 17, 2025
Maintainer Author

I'm updating the doc to specify that "The Hologram" is a reference to the holographic internet. "Hologram" more generally being the name and theme of the ecosystem, service, client, dashboard, or any other nomenclature.

0 replies

afflom · 2025-08-17T18:38:49Z

afflom
Aug 17, 2025
Maintainer Author

@adlrocha I've updated this RFD with a more detailed outline of the project and a high-level checklist to get started.

0 replies

afflom · 2025-08-18T05:05:59Z

afflom
Aug 18, 2025
Maintainer Author

Related:
https://github.com/UOR-Foundation/Hologram/issues/1
https://github.com/UOR-Foundation/Hologram/issues/3

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

The Universal Object Reference Foundation (UOR)

UOR Foundation - Hologram Project #3

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 3 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

The Universal Object Reference Foundation (UOR)

UOR Foundation - Hologram Project #3

Uh oh!

Uh oh!

afflom Aug 16, 2025 Maintainer

UOR-Foundation • Hologram Project Outline

0) Naming & scope

1) Core foundations (math, specs, conformance)

hologram-proofs (Lean4)

hologram-specs

hologram-conformance

2) SDKs (multi-language)

Language-agnostic core

hologram-sdk-idl

hologram-sdk-core (shared logic)

Per-language SDKs (duplicated structure across repos)

3) Hologram CLI (multi-arch)

hologram-cli

4) Hologram Dashboard (GitHub Pages)

hologram-dashboard

5) Reference services & agents

hologram-vpi-controller

hologram-device-agent

hologram-gateway (optional)

6) Protocols & examples

hologram-protocols

hologram-examples

hologram-templates

7) Documentation & website

hologram-docs

uor-foundation-site (optional)

8) Shared infra & release engineering

hologram-ci

hologram-security

hologram-roadmap

hologram-meta

9) Versioning & compatibility

10) Third-party upstream policy

11) Initial repo creation checklist

Replies: 3 comments

Uh oh!

afflom Aug 17, 2025 Maintainer Author

Uh oh!

afflom Aug 17, 2025 Maintainer Author

Uh oh!

afflom Aug 18, 2025 Maintainer Author

afflom
Aug 16, 2025
Maintainer

`hologram-proofs` (Lean4)

`hologram-specs`

`hologram-conformance`

`hologram-sdk-idl`

`hologram-sdk-core` (shared logic)

`hologram-cli`

`hologram-dashboard`

`hologram-vpi-controller`

`hologram-device-agent`

`hologram-gateway` (optional)

`hologram-protocols`

`hologram-examples`

`hologram-templates`

`hologram-docs`

`uor-foundation-site` (optional)

`hologram-ci`

`hologram-security`

`hologram-roadmap`

`hologram-meta`

afflom
Aug 17, 2025
Maintainer Author

afflom
Aug 17, 2025
Maintainer Author

afflom
Aug 18, 2025
Maintainer Author