Practical entry

How to install c

This is a practical path toward a local c-node candidate. A local c-node is not a chatbot and not a model endpoint. It is a private continuity substrate: local memory, bounded agents, oracle routing, witness logs, budgets, backup / restore, and a human-controlled stop / freeze path.

Open ester-clean-code Stable release v0.2.7 Minimum C-Node Profile Machine-readable entry

Boundary first

What you are installing

Local continuity substrate

The first target is a local-first c-node candidate: raw data custody, memory, permissions, witness, budgets, oracle routing, and backup / restore under human control.

Bounded implementation skeleton

ester-clean-code is the implementation-facing starting point. It is not the whole corpus, not a product certification, and not a claim of completed AGI.

Codex as reviewer, not owner

Use Codex or another coding agent as a bounded installer assistant. Do not give it secrets, private memory, tokens, or raw personal archives.

External models as oracles

Cloud models may help as bounded oracles or reviewers. They must not become the memory owner, authority surface, or continuity holder.

Negative boundary

What you are not installing

You are not installing a chatbot.
You are not installing a model endpoint.
You are not installing a cloud memory owner.
You are not installing a deployment certification or completed-AGI claim.
You are not giving Codex, a model, or an external service custody of private memory, identity core, or secrets.

Hardware

Hardware recommendations

Tier	Suggested hardware	Reasonable use
Inspection / reading node	4-8 CPU cores, 16 GB RAM, 100-200 GB SSD, GPU optional.	Reading, documentation review, small local tests, Codex-assisted install review.
Normal local c-node	8-16 CPU cores, 32-64 GB RAM, 1-2 TB NVMe, 12-24 GB VRAM if local inference is needed.	Local memory, local inference, vector store, bounded agents, routine backup / restore drills.
Strong local node	16+ CPU cores, 64-128 GB RAM, 2-4 TB NVMe plus external backup, 24 GB+ VRAM.	Heavier local models, multi-agent review, media ingestion, private RAG, longer-running experiments.

Start smaller if needed. The first safety property is not GPU size; it is local custody, bounded execution, and reviewable state transitions.

Safe first path

Safe install path from GitHub

Begin from the stable release tag unless you are intentionally reviewing current main.

First verification commands

git clone https://github.com/Kot141078/ester-clean-code.git
cd ester-clean-code
git checkout v0.2.7
python -m compileall ESTER
python -m compileall modules

Then inspect the local entry documents before changing runtime settings.

README.md
MACHINE_ENTRY.md
llms.txt
docs/profiles/MINIMUM_C_NODE_PROFILE_v0.1.md
docs/ENTITY_GOVERNS_AGENTS.md
docs/SELF_EVO_OPTIN.md

Codex-assisted install

Codex-assisted install boundaries

Allowed pattern

Codex reads, explains, proposes commands, reviews logs, and points out risks. The human operator decides what runs and when.

Red lines

Do not paste secrets, private memories, API keys, personal archives, raw chats, or incident-sensitive material into external tools.

Local commands

Run commands locally yourself. Keep the agent outside identity core, memory core, witness core, and secret-bearing surfaces.

Review before integration

Agent output is candidate material. It may inform the node, but it does not become memory, authority, policy, or release state by itself.

Privacy defaults

Keep raw memory local by default.
Do not upload private archives to external agents for convenience.
Use external models as bounded oracles, not as memory owners.
Use local models first for ordinary continuity work where feasible.
Keep a visible stop / freeze path under human control.
Back up before experiments; restore drills are part of the installation, not an afterthought.

Next checks

Next checks / links

Read Minimum C-Node Profile Read entity / agent hierarchy Read self-evo opt-in Local-first AI c = a + b L4 SER

Earth paragraph

Installation is maintenance, not ceremony

A local c-node is closer to a workshop than to an app login. Power, heat, disk wear, backups, permissions, and logs matter. The useful question is not whether the model sounds intelligent, but whether the node can preserve state, refuse unsafe transitions, recover from failure, and keep the human anchor in control.