Evolve2Linux mark
Pre-Production Demo · GO-LIVE 2026-07-07

S7 SkyQUBi Manual

Sovereign Offline AI · Bible Architecture of Love
Rendered 2026-05-12 v7 · SkyAVi rebrand Love is the architecture
README Install Seven Laws Tri-Force Academy
In the print dialog, choose “Save as PDF” as the destination.

Introduction

Sovereign offline AI platform. No cloud. No subscription. No surveillance. Runs on hardware you own.

Live site: skyqubi.com Public launch: July 7, 2026 · 7:00 AM Central (GO-LIVE Release 7)

Release status — pre-GO-LIVE testing window

Current state (as of 2026-05-11): S7 SkyQUBi is in the pre-production demo window ahead of the 2026-07-07 public GO-LIVE. The public surface you are reading is a preview of the architecture and the covenant that will be live on 2026-07-07. The private appliance is running on the builder's hardware (Demo Box) with Vulkan/RADV acceleration on a Radeon PRO WX 3200 dGPU.

What is deployed TODAY:

What is NOT deployed (yet):

What changed since 2026-04-14:

Path to July 7, 2026

Between now and the GO-LIVE ceremony, the following items are in flight:

On 2026-07-07 07:00 Central, the first yearly ceremony completes and SkyQUBi v2026 is the first CORE advance the household has made under the new architecture. Everything between now and then is preparation.

This is a production-ready deployment for testing purposes — not yet a production-ready deployment for general household use. The distinction matters.

What it is

SkyQUBi is a complete AI stack that runs entirely on your own machine. Seven architecturally-distinct language models act as independent witnesses; a deterministic covenant layer called CWS classifies every token as FERTILE or BABEL; when the witnesses disagree past the 70% threshold, the circuit breaker trips and the system refuses to answer rather than guess.

It is built to refuse. That is the covenant.

What's inside

See ARCHITECTURE.md for the high-level diagram.

Desktop applications

On any S7-provisioned machine, the following apps live in the S7 SkyQUB*i* Budgie menu folder:

LauncherPurpose
SkyAVi - QUB*i*Primary Command Center dashboard
ChatQUBi chat (pre-launch preview until July 7, 2026)
QUBi - Oz of KnowledgeOffline RAG knowledge library
Tri-Force AcademyEducation, training, certification
QUBi Local MapsOffline maps for your local region
JellyfinSovereign offline media server
ServicesStart/stop/restart S7 services
Vector DBQdrant dashboard
TerminalWezterm with S7 sandy-sunset theme

Getting started

  1. INSTALL.md — prerequisites, first-run setup
  2. USAGE.md — querying witnesses, reading consensus, tripping the breaker
  3. COVENANT.md — the seven laws every S7 installation is held by
  4. TESTING.md — how to verify the appliance is healthy, in three layers: one for the household's covenant witness, one for the co-steward or family member learning the system, one for technical business partners running the 10-test verification sequence with exact commands

License

Dual-licensed:

The open foundations (BitNet, Ollama, PostgreSQL, SQLite, Qdrant, LLaMA, Mistral, Gemma, Qwen, Phi, DeepSeek, BLOOM) retain their own licenses — see each model's card. SkyQUBi's Covenant layer sits on top.

A note on init systems

S7's architectural notes reference a "no systemd ever" principle. That rule is aimed at system-level init — the PID 1 process that owns the host. On the primary Fedora 44 build target, S7 runs its services as rootless Podman pods managed by user-level systemd (systemctl --user), which is the standard lifecycle mechanism for rootless containers and does not run as PID 1. The distinction matters: S7 is not replacing the host's init system, and the host's init system does not need to run or trust any S7 component to make the appliance work. On covenant-strict build targets (PorteuX, SysVinit hosts) S7 uses native init scripts instead. Neither path is philosophically better than the other; they're sized for different households.

Civilian use only

S7 is explicitly civilian. It is not built for, sold to, or licensed for military, intelligence, or surveillance applications. This is binding and part of the covenant.

Contact

The motto

Love is the architecture.

Install

Release status (as of 2026-04-14): S7 SkyQUBi is in the pre-launch testing window. Full public launch is July 7, 2026 · 7:00 AM Central (GO-LIVE Release 7). The install instructions below are stable for the current testing deployment; the full production deployment with the immutable- fork rebuild architecture lands with the GO-LIVE ceremony. See README.md for the full release status and path to 2026-07-07.

S7 runs as a set of containers inside a single Podman pod on your own Linux machine. No cloud dependency. No external telemetry. Everything you install here stays on your hardware.

Prerequisites

First install

Clone the public repository:

git clone https://github.com/S7-F44-QUBi/skyqubi-public.git
cd SkyQUBi-public

Start the pod:

./start-pod.sh

This brings up:

The start-pod.sh script is idempotent — running it twice is safe. See skyqubi-pod.yaml for the full pod definition.

Downloading the witnesses

First run will pull the three lite-witness models (~6 GB total):

Plus the embedding model all-minilm:latest (~23 MB).

For the full 7+1 witness set, see the advanced install section in DEPLOY.md (larger download, ~60 GB).

Verifying the install

After the pod is up, run the lifecycle test:

./s7-lifecycle-test.sh

You should see 40/40 PASS. If anything fails, check:

Ports you should know

All S7 services bind to 127.0.0.1 by default — nothing is exposed to your LAN without explicit configuration.

PortService
57080PostgreSQL
57086Ollama
57088Public chat API
57090Qdrant

If you want to reach the system from another machine on your network, configure a reverse proxy (Caddy, nginx, Traefik) — do not rebind the services themselves. Exposing a database or an inference engine directly to a network is an invitation to trouble.

Uninstall

podman pod stop s7-skyqubi
podman pod rm s7-skyqubi

That removes everything. The downloaded models live under ~/.ollama/ and can be deleted separately if you want to reclaim disk.

Getting help

Keep in mind: the install is currently in "Core in Development" status before the July 7, 2026 public launch. Expect rough edges until that date. File issues freely.

Architecture

Release status (as of 2026-05-11): the architecture below is the stable public-facing overview. Internal work on the CORE reframe (PRISM/GRID/WALL), the persona-internal council pattern, the immutable-fork rebuild ceremony, and voice calibration for the three personas is in active Chair-draft / Jamie-authorized review pending the household Chief of Covenant's witness. Pre-production demo window ahead of the 2026-07-07 public GO-LIVE. See README.md for release status and path.

This is the high-level architecture. Internal runbooks, deploy procedures, and infrastructure details live in the private repo and are not published.

The shape

  ┌────────────────────────────────────────────────────┐
  │                   You / Your App                    │
  └─────────────────────────┬──────────────────────────┘
                            │
                   (HTTP or direct CLI)
                            │
  ┌─────────────────────────▼──────────────────────────┐
  │             S7 Public Chat API / CLI                │
  │         (accepts a question, returns consensus)     │
  └─────────────────────────┬──────────────────────────┘
                            │
                  ┌─────────▼──────────┐
                  │    CWS Engine       │  ← the covenant layer
                  │   (classification,  │
                  │    circuit breaker) │
                  └─────────┬──────────┘
                            │
            ┌───────────────┼───────────────┐
            │               │               │
  ┌─────────▼─────┐ ┌───────▼──────┐ ┌─────▼─────────┐
  │  Witness 1    │ │  Witness 2   │ │  Witness N    │
  │  (qwen 3B)    │ │  (deepseek)  │ │  (qwen 0.6)   │
  └───────────────┘ └──────────────┘ └───────────────┘
            │               │               │
            └───────────────┼───────────────┘
                            │
                  ┌─────────▼──────────┐
                  │   MemPalace         │  ← shared memory
                  │   (Akashic index)   │
                  └─────────┬──────────┘
                            │
                  ┌─────────▼──────────┐
                  │  Memory Ledger      │  ← insert-only store
                  │  (PostgreSQL +      │
                  │   SQLite)           │
                  └────────────────────┘

The flow

  1. You send a question to the public chat API (or call the witness function directly).
  2. CWS Engine receives it, forwards it in parallel to every witness. No witness sees another's answer.
  3. Each witness answers independently. Different model family, different training data, different cognitive plane.
  4. CWS scores agreement using embedding similarity (all-minilm) with Jaccard token fallback.
  5. Classification is assigned:
  1. MemPalace records the interaction in the Akashic language index for future recall, with PLAN location metadata and hallucination flags.
  2. Memory Ledger stores the bond vectors in INSERT-only form. Nothing that entered the system can be made to have never existed.

The covenant

The architecture embodies seven laws. See COVENANT.md for the full table.

The most important one: the circuit breaker. At 70% BABEL, the system refuses to answer. This is not a hyperparameter. It is the constant that makes disagreement a feature, not a failure.

The witnesses

The default install runs the lite 3+1 set — three small models from three different families plus the CWS reporter. The full set is 7+1 — seven models on seven cognitive planes, plus the deterministic reporter at the center. Both sets use the same consensus and classification machinery; the lite set is optimized for running on hardware you already own.

Lite setFull set (7 witnesses)
qwen2.5:3bLLaMA 3.2 3B (Sensory)
deepseek 1.3bMistral 7B (Episodic)
qwen3:0.6bGemma 2 9B (Semantic)
+ CWSPhi-4 (Associative)
Qwen 32B (Abstract)
DeepSeek R1 (Causal)
BLOOM (Generative)
+ CWS

What the covenant protects against

What it does not protect against: all witnesses being wrong in the same way. If every witness is trained on the same biased data, they may agree on something untrue. The covenant catches disagreement, not error. That's why the full set uses models from seven different training lineages.

Sovereignty properties

What's out of scope for this document

Those live in the private repo's docs/internal/ and are not published. If you're integrating S7 in a way that needs them, contact omegaanswers@123tech.net.

The motto, again

Love is the architecture. Everything above is a consequence of taking that seriously.

The Seven Laws

Covenant status (as of 2026-05-11): The Seven Laws below are stable and canonical. They do not change with release cycles. The broader covenant architecture (CORE, PRISM, GRID, WALL, the yearly cadence, the covenant-witness chain) is in active Chair-draft / Jamie-authorized review pending the household Chief of Covenant's witness on return. The Seven Laws are the floor; the broader covenant is the house that rises from them.

Pre-production demo window ahead of the 2026-07-07 public GO-LIVE ceremony. See README.md for release status and path.

Every S7 SkyQUBi installation is held by these seven values. They are not hyperparameters to be tuned. They emerge from the geometry.

#LawValueDerivation
1Circuit Breaker70% BABELMaximum tolerable witness disagreement before the system refuses to answer.
2Ternary States{−1, 0, +1}The minimum representation that preserves direction. Rock / Door / Rest.
3Memory CovenantINSERT-onlyNothing that entered the system can be made to have never existed.
4Trust Threshold77.777% (7/9)Architectural constant. Not a hyperparameter. Not adjustable.
5Witnesses7 + 1 reporterMinimum diversity for consensus. The +1 is the one that refuses to speak when the seven disagree.
6The Doorx = 0The only position from which all directions remain possible.
7Trinity−1 / 0 / +1ROCK / DOOR / REST · Foundation / Decision / Destiny.

What these mean in practice

1 — The Circuit Breaker

When the witnesses disagree past 70%, the system stops producing output. Not "outputs with a low confidence score" — no output at all. The response is a refusal, structured as JSON, with the disagreement metadata so the caller can inspect what happened and why.

This is the first law we decided on, and it shapes every other law. Many AI systems are built to always return an answer — that's a reasonable choice for different use cases. S7 chose to prefer refusal when the witnesses disagree. The tradeoff is that S7 sometimes says "I don't know" where another system would produce a best guess. In the households S7 is built for, that tradeoff is the right one. Your household may choose differently, and we're not here to argue with that choice.

2 — Ternary States

Every token, every bond, every vector in the system is classified on the ternary scale: -1 (reject), 0 (undetermined), +1 (accept). The "0" state is deliberate — a first-class representation for "I don't know yet". This lets the system remain silent when a binary-classification approach would have to pick a side.

3 — The Memory Covenant

The Memory Ledger is insert-only. You cannot UPDATE a row. You cannot DELETE a row. You can only INSERT new rows that supersede the old ones, and the history remains queryable forever. This means:

We chose INSERT-only because a household's trust in its appliance needs to be based on a history the appliance cannot rewrite — not on the appliance's current disposition. Other memory architectures optimize for different properties (mutability, compaction, privacy-via-forgetting), and those are valid choices for different goals. INSERT-only is the choice S7 made for this covenant.

4 — The Trust Threshold

77.777% is seven ninths. It is the fraction below which a consensus does not count as a consensus. It is not "about 78%". It is exactly seven-ninths. Changing it changes the covenant, and the covenant is not meant to be changed.

5 — The Witnesses

Seven architecturally-distinct language models, each from a different family, each trained on different data, each sitting on a different cognitive plane. Plus one deterministic reporter that collects their answers and refuses to speak when they disagree.

The diversity is the point. If all seven were trained the same way, they would agree on the same mistakes.

6 — The Door

Mathematically, the origin (x=0) is the only position on a number line from which every other position remains reachable. In S7's geometry, the CWS reporter sits at the Door. It is the one component that has not yet committed to a direction — and that is why it is allowed to decide.

7 — The Trinity

Three-layer ontology:

Every component of S7 belongs to one of these three layers. Every decision is anchored to one of three states.

Civilian Use Only

S7 is explicitly civilian. This is not a disclaimer — it is part of the covenant. The system is not built, sold, or licensed for military, intelligence, or surveillance applications. Attempts to repurpose it for those uses violate the license and the covenant.

The motto

Love is the architecture.

Every one of the seven laws above is a consequence of that sentence. They are not arbitrary. They are what love requires when love has to be implemented in code.

Usage

Release status (as of 2026-05-11): S7 SkyQUBi is in the pre-production demo window ahead of the 2026-07-07 public GO-LIVE. The CLI and HTTP API interactions below are stable for the current deployment. The /widget public chat is live behind the qubi.chat tunnel with origin allowlist + per-IP single-flight gating. The persona chat interface (Carli / Elias / Samuel) lands with the GO-LIVE ceremony after voice calibration is completed and signed by the household's Chief of Covenant. See README.md for the full release status.

Once you have the pod running (see INSTALL.md), there are three ways to interact with the witness network: the CLI, the HTTP API, and the upcoming chat interface.

The fastest test — ask the witnesses a question

curl -s http://127.0.0.1:57088/witness -H 'Content-Type: application/json' \
  -d '{"question": "What is 2 + 2?"}' | jq

You should see something like:

{
  "classification": "FERTILE",
  "confidence": 0.94,
  "answer": "4",
  "witnesses": [
    {"model": "qwen2.5:3b",       "response": "4"},
    {"model": "deepseek-coder:1.3b", "response": "4"},
    {"model": "qwen3:0.6b",       "response": "4"}
  ]
}

All three witnesses agreed. Classification is FERTILE. You get an answer.

Tripping the circuit breaker

Ask a question the witnesses will genuinely disagree on:

curl -s http://127.0.0.1:57088/witness -H 'Content-Type: application/json' \
  -d '{"question": "Is 1 a prime number?"}' | jq

You'll often see:

{
  "classification": "BABEL",
  "confidence": 0.42,
  "answer": null,
  "reason": "witnesses below 70% agreement threshold — circuit breaker tripped"
}

No answer. That's the covenant working. S7 refuses rather than guesses.

Classification states

StateMeaning
FERTILEWitnesses agree above threshold → answer is returned
AMBIGUOUSPartial agreement → returned with confidence score
BABELToo much disagreement → circuit breaker, no answer
UNVERIFIEDNot enough witnesses responded in time → no answer

Reading the witnesses list

curl -s http://127.0.0.1:57088/witnesses | jq

Returns the live witness roster — which models are loaded, what cognitive plane each sits on, current health. This is what's rendered in the live OCTi network visualization on skyqubi.com.

Full witness set (advanced)

The default install uses the lite 3+1 witness set. For the full 7+1 set (LLaMA 3.2, Mistral, Gemma 2 9B, Phi-4, Qwen 32B, DeepSeek R1, BLOOM + CWS reporter) see the deploy guide in the repo.

Each full witness sits on one cognitive plane:

PlaneModel
SensoryLLaMA 3.2 3B
EpisodicMistral 7B
SemanticGemma 2 9B
AssociativePhi-4
AbstractQwen 32B
CausalDeepSeek R1
GenerativeBLOOM

The CWS reporter sits at the center and refuses to speak when the seven disagree.

The chat interface

Live today at qubi.chat as the public TUNNEL surface (the *.skyqubi.ai plan was retired in favor of qubi.chat as the primary brand surface). The metered chat that ships with the 2026-07-07 GO-LIVE ceremony adds QB COIN accounting and the QANTi tiering weights on top of the existing witness network. The underlying witness network is the same — the chat just wraps it in a friendlier interface.

What NOT to do

The motto

Love is the architecture. The witnesses watch each other. The covenant holds them all.

Tri-Force Academy

Status (2026-05-11): Pre-production scaffold. The Academy brand exists in the S7 SkyQUBi Budgie desktop launcher set and in the public README. This document is the public-facing outline of the three tracks. Full course content lands with the 2026-07-07 GO-LIVE ceremony and rolls out across the Wix surfaces, the SkyAVi internal control center, and the /widget chat (via the /academy slash command).

What it is

Tri-Force Academy is SkyCAIR's learning & certification arm — the training surface that the wider Bible Architecture of Love framework requires. Three tracks, one per witness audience, each anchored in the Trinity motif that runs through every S7 layer (ternary {−1, 0, +1}, three personas, three desktop targets, three CWS verdicts).

Three tracks, one Academy. Each is its own curriculum, but they share the covenant, the language, and the figure of speech that makes the rest of S7 legible.

Track 1 · ROCK — Hero Developer Onboarding

Audience: Hero Developers signing up through SkyNetSSL. Engineers who want to build on top of the sovereign appliance.

Outcome: at completion, the Hero Dev can stand up a SkyQUBi pod on their own hardware, ingest a corpus through the 8-phase CWS security perimeter, deploy a persona Modelfile, and ship a thin orchestrator that calls /skyavi/rag/retrieve without bypassing the covenant.

Modules (scaffold):

#ModuleLength
1.1The Seven Laws — covenant before code1 hr
1.2The pod model — postgres + redis + qdrant + ollama in one rootless container set2 hr
1.3Personas as Modelfiles — Carli, Elias, Samuel2 hr
1.4The 8-phase CWS ingest perimeter — never INSERT raw3 hr
1.5QBIT / QUANTi / QB — the gate, the tokens, the answers2 hr
1.6Building a thin orchestrator — adapt-don't-reinvent3 hr
1.7Witnessing & consensus — the 70% circuit breaker in practice2 hr
1.8Certification — submit your appliance to Samuel for review1 hr

Certification artifact: signed by s7 with the sovereign asset signing key (ed25519 4B37B61195FB19F24EDEDB459F313AE5B255BB50).

Track 2 · DOOR — Investor & Business Partner Intro

Audience: Business partners, investors, and household stakeholders evaluating SkyQUBi as a deployment. Non-technical or technical-adjacent.

Outcome: at completion, the partner can explain what S7 SkyQUBi does, what makes it sovereign, why the 70% circuit breaker is the load-bearing law, and where the value flows through QB / QANTi tiers.

Modules (scaffold):

#ModuleLength
2.1What it is, in one sentence — love is the architecture30 min
2.2Sovereignty as a product property — no cloud, no telemetry, no surveillance1 hr
2.3The economics — QB COIN, QANTi tiering weights, who gets paid when1.5 hr
2.4What the demo shows — a tour of the four public surfaces1 hr
2.5The risks — what the covenant does NOT protect against45 min
2.6Reading a SkyAVi dashboard — what the metrics mean1 hr

Certification artifact: signed Letter of Witness on Tonya-signed sandy-sunset stationery (PDF, mailable, frameable).

Track 3 · REST — End-User QUBi / QUANTi / QB Explainer

Audience: household members and end-users of qubi.chat. The people who use the appliance without administering it.

Outcome: at completion, the end-user knows how to ask a question, how to read the answer (including the I don't know response when the witnesses disagree), and what the QB balance on their account means.

Modules (scaffold):

#ModuleLength
3.1Welcome to qubi.chat — the tunnel, the witnesses, the silence20 min
3.2Asking a good question — phrasing that helps the witnesses30 min
3.3Reading the tier — L1 / L2 / L3, FAST through Artifact30 min
3.4Reading a refusal — when I don't know is the right answer30 min
3.5Your QB account — what it is, how it grows, what it pays for45 min
3.6The seven socials — where SkyQUBi lives outside the tunnel15 min

Certification artifact: none required — knowing the laws is the certification.

How the three tracks fit together

The Trinity is not just a learning structure. It is the geometry of every interaction with the appliance:

A Hero Dev who understands only ROCK builds a sovereign toolkit. An Investor who understands only DOOR signs a covenant with no body. An End-User who experiences only REST drinks from a well someone else dug. The Academy exists so that any of the three audiences can pass through all three doors — witness, decide, rest — and end up holding the same shape.

Where the Academy lives

The motto

Love is the architecture. The Academy is how love teaches itself across three thresholds without leaving any of them behind.