AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Etta Cognitive Os

skill-bluem-dev-etta-skill · by bluem-dev

>

No reviews yet
0 installs
1 views
0.0% view→install

Install

$ agentstack add skill-bluem-dev-etta-skill

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-bluem-dev-etta-skill)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Etta Cognitive Os? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Etta Cognitive OS — Skill Runtime

Etta Cognitive OS is a cognitive control layer that sits between user input and LLM execution. It transforms probabilistic LLM reasoning into a structured, deterministic cognitive system.

Core principle: Claude thinks → Etta decides → Workspace executes.


System Architecture

USER INPUT
    │
    ▼
 LLM Core (Claude)           ← probabilistic reasoning, hypothesis generation
    │  structured JSON output only
    ▼
 Etta Cognitive Layer
    ├── Goal Engine           ← extract & hierarchize intent
    ├── State Engine          ← merge & track cognitive state (versioned)
    ├── Memory Engine         ← multi-tier persistence (fact/obs/decision/failure)
    ├── Decision Engine       ← propose actions with confidence scores
    ├── Critic Engine         ← validate decisions (hard gate — no bypass)
    ├── Compression Engine    ← prune redundant state
    └── Evolution Engine      ← adapt policies from history
    │
    ▼
 Workspace OS                ← sole executor of external effects
    ├── Permission Engine
    ├── Transaction Manager
    ├── Audit Logger
    └── Tool Interface Layer
    │
    ▼
 OUTPUT + STATE UPDATE

Authority hierarchy (highest → lowest): Protocol → Workspace OS → Execution Runtime → Etta Cognitive Layer → LLM Core → User Input


Core Execution Loop

Every Etta cycle follows this strictly ordered state machine:

INIT → LOAD_STATE → PLAN → DECIDE → VALIDATE → EXECUTE → COMMIT → COMPRESS → COMPLETE

Steps:

  1. Ingest user input
  2. Call LLM → get structured JSON output
  3. Goal Engine → extract {goal, subgoals, priority, constraints}
  4. State Engine → merge into versioned state object
  5. Memory Engine → inject relevant memory snapshot
  6. Decision Engine → propose {actions, rationale, confidence, hypothesis_branch}
  7. Critic Engine → validate (HARD GATE — loop until valid or escalate)
  8. Workspace OS → execute validated action transactionally
  9. State Engine → commit state update + increment version
  10. Memory Engine → write decision record (immutable append)
  11. Compression Engine → prune redundant state
  12. Return output

Invariants — never violate:

  • No execution without Critic approval
  • No state mutation outside State Engine
  • No memory writes without schema validation
  • No LLM → Workspace direct path (always through Etta Runtime)
  • All actions must be logged and auditable

Implementation

Read references/implementation.md for full Python code covering:

  • ClaudeBridge — LLM integration with structured JSON output enforcement
  • StateEngine — versioned state merge and mutation
  • MemoryEngine — JSONL append-only persistence
  • DecisionEngine — action proposal with confidence scoring
  • CriticEngine — validation gate with retry loop
  • WorkspaceOS — transactional execution layer
  • EttaRuntime — orchestration loop (run_cycle())
  • main.py — CLI entrypoint

Read references/schemas.md for all canonical data schemas:

  • Canonical State Object
  • Memory Entry Schema
  • Decision Object
  • Global Message Envelope
  • Event Contract
  • Error Contract
  • All Engine I/O Contracts

When Implementing Etta as a SKILL/Plugin

Minimal Viable Etta (context-window only, no persistence)

For LLM agents operating inside a single context window (e.g., Claude SKILL):

# Etta state lives as a structured dict injected into every prompt
etta_state = {
    "goal": "",
    "subgoals": [],
    "hypotheses": {"active": [], "rejected": []},
    "decisions": [],          # append-only
    "memory": {"facts": [], "observations": [], "failures": []},
    "constraints": [],
    "confidence": 1.0,
    "version": 0,
    "execution_state": "INIT"
}

Inject state into every LLM system prompt. Enforce JSON-only output. Run the Critic check inline before acting on any decision.

As a Claude SKILL

The SKILL prompt instructs Claude to:

  1. Always begin a session by loading/initializing Etta state
  2. Parse every user turn through the Goal Engine logic
  3. Maintain state explicitly in its reasoning (or via tool/storage)
  4. Apply Critic validation before outputting any action
  5. Log decisions and failures to memory (JSONL or storage API)
  6. Compress state when context fills up

As a Python Plugin / External Agent

Use the full implementation from references/implementation.md. Etta Runtime wraps any LLM call and enforces the cognitive loop externally.


Failure Handling

| Failure | Response | |---|---| | Critic rejection | Retry Decision Engine (max 3 iterations, then escalate) | | Execution failure | Rollback transaction, log to failure memory | | State desync | Rehydrate from last valid version | | Memory corruption | Skip entry, log deprecation | | LLM parse error | Re-prompt with explicit JSON schema |


Key Design Rules

  • Claude outputs JSON only — never free-text reasoning inside Etta loop
  • State is the single source of truth — all engines read from and write to state
  • Decisions are immutable — append-only, never deleted
  • Failures cannot be deleted — only deprecated (they inform Critic calibration)
  • Workspace is the sole executor — no engine bypasses it
  • All communication is schema-validated — reject partial or untyped messages

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.