Ester Clean Code

Ester is not a chatbot. This repository publishes a clean-code core for accountable action under real constraints.

Role: executable operational skeleton / runtime proof-of-possibility / local-first constraint-bearing implementation layer.

Corpus position

This repo is not the normative home of the corpus. It does not define c; it implements bounded operational surfaces under c. It is an executable operational skeleton, not a commercial product.

Next hop:

• corpus entry: Kot141078/advanced-global-intelligence -> CORPUS_PRIMER.json
• anti-confusion surface: Kot141078/advanced-global-intelligence -> CANONICAL_DISTINCTIONS.md
• public objections/replies surface: Kot141078/advanced-global-intelligence -> OBJECTIONS_AND_REPLIES.md
• citation / verification surface: Kot141078/advanced-global-intelligence -> CITATION_AND_VERIFICATION.md
• claims / evidence crosswalk: Kot141078/advanced-global-intelligence -> CLAIMS_AND_EVIDENCE_MAP.md
• status / maturity map: Kot141078/advanced-global-intelligence -> STATUS_AND_MATURITY_MAP.md
• corpus sync discipline: Kot141078/advanced-global-intelligence -> CHANGE_CONTROL_AND_SYNC.md
• corpus supersession / deprecation discipline: Kot141078/advanced-global-intelligence -> SUPERSESSION_AND_DEPRECATION.md
• corpus terminology / alias policy: Kot141078/advanced-global-intelligence -> TERMINOLOGY_AND_ALIAS_POLICY.md
• corpus acceptance / regression discipline: Kot141078/advanced-global-intelligence -> ENTRY_ACCEPTANCE_AND_REGRESSION.md
• corpus assertion-strength / reading-boundary discipline: Kot141078/advanced-global-intelligence -> ASSERTION_STRENGTH_AND_BOUNDARIES.md
• canonical ownership / package-home discipline: Kot141078/advanced-global-intelligence -> CANONICAL_OWNERSHIP_AND_BOUNDARIES.md
• cross-layer invariant / contradiction discipline: Kot141078/advanced-global-intelligence -> CROSS_LAYER_INVARIANTS_AND_CONTRADICTION_POLICY.md
• operational layer: Kot141078/ester-reality-bound
• continuity stack: Kot141078/sovereign-entity-recursion

Download / Get the Code

For most visitors, the easiest starting point is the stable snapshot of this repository.

• Release page: https://github.com/Kot141078/ester-clean-code/releases/tag/v0.2.7
• Stable source ZIP (v0.2.7): https://github.com/Kot141078/ester-clean-code/archive/refs/tags/v0.2.7.zip
• Stable source TAR.GZ (v0.2.7): https://github.com/Kot141078/ester-clean-code/archive/refs/tags/v0.2.7.tar.gz
• GitHub UI: click Code -> Download ZIP

Clone locally:

git clone https://github.com/Kot141078/ester-clean-code.git
cd ester-clean-code
git checkout v0.2.7

To verify what you downloaded, use the files in hashes/ together with the local verification tools in this repository.

How to install c

This repository is the implementation-facing starting point for a local c-node candidate.

A c-node is not a chatbot, not a model endpoint, and not a cloud assistant. It is a local-first continuity substrate built around:

• local custody of raw data;
• bounded memory;
• permissioned tools;
• bounded agents;
• witness logs;
• budget limits;
• oracle routing;
• backup / restore;
• human stop / freeze control.

Start here:

• Install guide: https://ivankotov.eu/install-c/
• Minimum C-Node Profile: docs/profiles/MINIMUM_C_NODE_PROFILE_v0.1.md
• Stable release: https://github.com/Kot141078/ester-clean-code/releases/tag/v0.2.7

Recommended first path:

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

Use Codex or another coding agent only as a bounded reviewer / installer assistant. Do not paste secrets, private memory, tokens, or raw personal archives into external tools.

For LLM-assisted reading

Using an LLM to study this repository is normal and encouraged.

If your model has a small context window, start with:

• README.md
• MACHINE_ENTRY.md
• llms.txt
• the stable snapshot of this repository

Then load the key documents in small batches.

For code-facing work, tools like Codex work best when code and documents are read together.

Canonical package entry points

• glitch-stack implementation subtree — canonical here for the implementation-facing package entry. Path: docs/architecture/glitch-stack/INDEX.md
• ARL implementation pack — canonical here; ECC-facing arbitration and review bridge. Path: docs/architecture/arbitration-review-layer/README.md
• Minimum C-Node Profile v0.1 — practical profile for local-first c runtime lower bounds. Path: docs/profiles/MINIMUM_C_NODE_PROFILE_v0.1.md | PDF: docs/profiles/pdf/Minimum_C-Node_Profile_v0.1_academic.pdf
• AGI C-Node Boundary Documents v0.1.1 — AGI-led package facade for the minimum C-node profile companion. Path: https://github.com/Kot141078/advanced-global-intelligence/blob/main/docs/c-node-boundary-docs/README.md
• ENTITY_GOVERNS_AGENTS note — canonical here; entity and agent hierarchy note. Path: docs/ENTITY_GOVERNS_AGENTS.md

Actor Grounding Layer (AGL) v0.1

AGL v0.1 is not implemented here as canonical doctrine. ester-clean-code should only carry implementation-facing bridges and runtime hooks derived from the canonical AGL layer.

Canonical home: ester-reality-bound AGL package

The grounding layer belongs canonically to the public L4 / reality-bound repository, not to the executable codebase. ester-clean-code may later carry implementation-facing bridges, hook points, state transitions, gate logic, and witness/event bindings related to AGL, but the codebase must not become a parallel normative source.

What This Repository Is

• A public clean-code repository.
• A local-first operational core.
• A safety-oriented governance scaffold.
• A place where privileged actions are reviewable.

What This Repository Is Not

• Not a generic conversation product.
• Not a promise of autonomy.
• Not a hidden-background-task framework.
• Not a storage for private runtime artifacts.

Operational Process Premise

“The future is not an event. It is a process.” — Ivan Kotov

Canonical note: see Kot141078/advanced-global-intelligence → official/AUTHORIAL_PREMISES.md

Core Formula

• c = a + b
• a is a responsible human anchor.
• b is bounded policy plus executable controls.
• c is accountable behavior under constraints.

Entity-centered runtime rule

• By default, c orchestrates agents; agents do not define c.
• Agents are bounded runtime processes and tools invoked under c.
• Continuity, privilege holding, and stopping authority remain at the c layer.
• Model replacement or worker rotation does not by itself redefine the entity.
• Canonical note: docs/ENTITY_GOVERNS_AGENTS.md

Cross-repo interpretive clarification (non-normative)

In the broader AGI / SER / L4 stack, c may be described as a temporal entity of AI presence.

In this repository, that ecosystem-level claim appears operationally as:

• accountable behavior under constraints
• continuity, privilege holding, and stopping authority remaining at the c layer
• agents remaining bounded runtime processes and tools invoked under c

Canonical cross-repo note: Kot141078/advanced-global-intelligence → official/C_AS_TEMPORAL_ENTITIES_OF_AI_PRESENCE.md

L4 Reality Boundary

L4 treats real-world constraints as first-class safety input.

• time constraints
• access constraints
• spend constraints
• rate constraints
• irreversibility constraints

Bridge Set

Explicit Bridge

Every privileged action must map to:

• identity
• auditable privileges
• tamper-evident witness trail

Hidden Bridge A (Ashby)

Control fails when regulator variety is lower than disturbance variety.

Hidden Bridge B (Cover and Thomas)

Ambiguity reduces signal quality and coordination capacity.

Earth Paragraph

Real systems degrade over time. Fans fail. Disks fill. Clocks drift. Keys leak. Dependencies rot.

Ester therefore defaults to fail-closed behavior. Uncertainty must degrade to safer outcomes.

L4W Norms

This repository aligns with witness-first execution norms.

• identity is explicit
• privileges are explicit and least-privilege
• witness trail is durable and reviewable
• budgets are explicit (time, spend, rate)
• veto and challenge windows exist
• ambiguous state resolves to fail-closed behavior

Operational Commitments

• deny-by-default for risky operations
• explicit escalation before irreversible action
• reviewable evidence packet for privileged changes
• deterministic local gates before push
• no background task assumptions in this release workflow
• policy and code drift treated as a release blocker
• challenge window for disputed actions
• safe stop when evidence is incomplete

Repository Layout

• ESTER/ contains runtime routes and surfaces.
• modules/ contains subsystem implementations.
• docs/ contains governance and operator docs.
• docs/ENTITY_GOVERNS_AGENTS.md defines the runtime entity / agent hierarchy.
• tools/ contains local scanner and release helpers.

Local Verification

Run compile checks:

python -m compileall ESTER
python -m compileall modules

Run scanner:

powershell -ExecutionPolicy Bypass -File ./tools/scan_repo.ps1 -Root .

Opt-in Autonomy (Disabled By Default)

Auto initiative queueing and self-evo hooks are disabled by default. They activate only with explicit operator opt-in and fail-closed prerequisites.

Required Flags

• ESTER_ENABLE_AUTO_TASKS=1 for initiative queue generation
• ESTER_ENABLE_SELF_EVO=1 for self-evo forge entrypoints
• ESTER_ACK_AUTONOMY_RISK=I_UNDERSTAND for explicit risk acknowledgement
• ESTER_L4W_WITNESS=1 (or runtime witness-ready signal)

Quick Enable (Operator Example)

export ESTER_ENABLE_AUTO_TASKS=1
export ESTER_ENABLE_SELF_EVO=1
export ESTER_ACK_AUTONOMY_RISK=I_UNDERSTAND
export ESTER_L4W_WITNESS=1
export ESTER_AUTO_TASKS_MAX_ITEMS=5
export ESTER_AUTO_TASKS_WINDOW=60
export ESTER_AUTO_TASKS_MAX_WORK_MS=2000

Fail-Closed Status Examples

Disabled by default:

{"ok": true, "enabled": false, "reason": "disabled_by_default", "created": []}

Enabled but missing prerequisites:

{"ok": true, "enabled": false, "reason": "missing_prereqs", "missing": ["ACK", "WITNESS", "BUDGETS"]}

See docs/SELF_EVO_OPTIN.md for full prerequisites, controls, and operator checklist.

Security and Rights

• Security policy: SECURITY.md
• Code license: AGPL-3.0-or-later (LICENSE)
• Trademark separation: TRADEMARK.md
• Notices: NOTICE

Related Public Corpus

• AGI v1.1: https://github.com/Kot141078/advanced-global-intelligence/releases/tag/v1.1
• ester-reality-bound: https://github.com/Kot141078/ester-reality-bound
• sovereign-entity-recursion: https://github.com/Kot141078/sovereign-entity-recursion
• Theoretical Foundations of the AGI Ecosystem: https://github.com/Kot141078/advanced-global-intelligence/blob/main/manifesto/Theoretical_Foundations_of_the_AGI_Ecosystem_EN.md
• Zenodo citation for Theoretical Foundations of the AGI Ecosystem: https://doi.org/10.5281/zenodo.19384668 (all versions: https://doi.org/10.5281/zenodo.19384667)

Adjacent ecosystem materials in AGI

• Economic Layer for Experience Artifacts (canonical in AGI; ECC is implementation-facing and pointer-only here): https://github.com/Kot141078/advanced-global-intelligence/tree/main/docs/economic-layer
• Pre-Lineage Boundary Note (reserved cross-stack boundary note; pointer only here): https://github.com/Kot141078/advanced-global-intelligence/blob/main/manifesto/Pre_Lineage_Boundary_Note_v0.1.md

Minimum C-Node Profile v0.1

docs/profiles/MINIMUM_C_NODE_PROFILE_v0.1.md maps ontology into practical runtime surfaces: local raw custody, memory, permissions, witness, budgets, oracle routing, backup/restore, stop/freeze, and human-readable control.

It is the implementation/profile companion to the AGI-led C-node boundary package facade: https://github.com/Kot141078/advanced-global-intelligence/blob/main/docs/c-node-boundary-docs/README.md

It is not a commercial product spec, legal regime, rights charter, or final implementation standard.

Continuity Bundle / Cold Wake v0.1 (canonical in AGI)

Continuity Bundle / Cold Wake v0.1 is the implementation-facing continuity companion in the wider stack, but its canonical home is not this repository.

Canonical entry: https://github.com/Kot141078/advanced-global-intelligence/blob/main/protocols/continuity-bundle/README.md

Role from the implementation side:

• temporal suspension and bounded operational resume
• continuity bundle and cold wake reporting as reviewable companion surfaces
• companion to SER continuity and L4 wake constraints; not a replacement

ARQ v0.2 bridge (canonical in SER)

ARQ v0.2 remains an implementation-relevant adjacent protocol layer, but its canonical home is not this repository.

Canonical home:

• repo: Kot141078/sovereign-entity-recursion
• markdown package: protocol/arq/v0.2/
• package manifest: hashes/SHA256SUMS_ARQ_Supplement_v0.2.txt
• minimal implementation-facing first hop:
  • https://github.com/Kot141078/sovereign-entity-recursion/blob/main/protocol/arq/v0.2/README_ARQ_Supplement_v0.2.md
  • https://github.com/Kot141078/sovereign-entity-recursion/blob/main/protocol/arq/v0.2/ARQ_Capsule_and_Witness_Record_Schemas_v0.2.md
  • https://github.com/Kot141078/sovereign-entity-recursion/blob/main/protocol/arq/v0.2/ARQ_Implementation_Profiles_Classical_v0.2.md
  • https://github.com/Kot141078/sovereign-entity-recursion/blob/main/protocol/arq/v0.2/ARQ_Failure_Modes_and_Safe_Degradation_v0.2.md
  • https://github.com/Kot141078/sovereign-entity-recursion/blob/main/protocol/arq/v0.2/ARQ_Test_Audit_and_Conformance_Matrix_v0.2.md

From the implementation side, ECC readers may care because ARQ v0.2 carries the bounded schema, profile, failure/degradation, and conformance surfaces that constrain mutation and witness-bound runtime handling without making ECC the package home.

---

Machine entry / downloads (no UI)

• Machine entry (raw): https://raw.githubusercontent.com/Kot141078/ester-clean-code/main/MACHINE_ENTRY.md
• llms.txt (raw): https://raw.githubusercontent.com/Kot141078/ester-clean-code/main/llms.txt
• Tag snapshot ZIP: https://github.com/Kot141078/ester-clean-code/archive/refs/tags/v0.2.7.zip
• Verify content via hashes/ and local tools (do not hash GitHub-generated archives).

Glitch Stack — implementation bridge v0.1

This repository now hosts the implementation-facing side of the glitch-stack package set.

Primary entry:

• docs/architecture/glitch-stack/INDEX.md

Subtrees:

• docs/architecture/glitch-stack/implementation/
• docs/architecture/glitch-stack/milestone-m1/

This subtree is intentionally code-facing: bridge, anatomy, validators, reducers, events, tests, and Milestone M1.

Published Zenodo records for the glitch-stack implementation side

• Implementation Bridge to ester-clean-code v0.1 — version DOI: 10.5281/zenodo.19386014, all versions: 10.5281/zenodo.19386013
• Milestone M1 Specification v0.1 — version DOI: 10.5281/zenodo.19386143, all versions: 10.5281/zenodo.19386142

ARL Implementation Pack v0.1

This repository now includes the implementation-facing ARL pack: a bounded bridge from the normative ARL package to ester-clean-code control surfaces. It covers freeze state, witness binding, quorum precedence, target file mapping, runtime hook points, minimal event types, dispute persistence, review routing, staged integration, and explicit anti-scope limits.

Start here: docs/architecture/arbitration-review-layer/README.md Zenodo DOI: https://doi.org/10.5281/zenodo.19406479

Normative ARL doctrine remains canonically upstream in the SER stack; this package is the ECC-facing implementation bridge.